Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How programmers should write their resumes

doesnotcompute.biz

Post reply on HN
Print view View original

21–30 of 74 posts

Re: How programmers should write their resumes

#21

Post by mh_yam »

imdsm wrote: post #12

> "Don't try anything cute. You resume should be devoid of personality." I have to disagree. I got my current job because my resume stood out. It was the only one not written in MS word. The other candidates had equal if not greater experience than me, but I got the job before they even got a response. If you're going for a programming position where you're not expected to be different, then sure, but if you're going…

Agreed. My (LaTeX) resume that I spend many hours refining has caught the attention of many hiring managers, and I often get compliments on it. Curse those recruiters who reformat my resume into their shitty Word templates. I've had times where a hiring manager would have the recruiter's version of the resume, and when I handed them my pretty resume they were pleasantly surprised.

Re: How programmers should write their resumes

#22

Post by bjourne »

vezzy-fnord wrote: post #3

Not into GitHub? Register a memorable domain and throw together a to-the-point portfolio page instead. Or use another goddamned software hosting service? I'll never understand this sense of GitHub supremacy amongst trendies. Otherwise, the advice in general is subpar.

Then suggest one that is both better than GitHub and doesn't cost you any money. Sourceforge, Savannah, Google Code.. They all suck in comparison.

Re: How programmers should write their resumes

#23

Post by eshvk »

imdsm wrote: post #12

> "Don't try anything cute. You resume should be devoid of personality." I have to disagree. I got my current job because my resume stood out. It was the only one not written in MS word. The other candidates had equal if not greater experience than me, but I got the job before they even got a response. If you're going for a programming position where you're not expected to be different, then sure, but if you're going…

I suspect that there is a wide variance between didn't write the resume in MS Word while still making it respectable and added say animated GIFs/cat video.

Re: How programmers should write their resumes

#24

Post by MetaCosm »

imdsm wrote: post #12

> "Don't try anything cute. You resume should be devoid of personality." I have to disagree. I got my current job because my resume stood out. It was the only one not written in MS word. The other candidates had equal if not greater experience than me, but I got the job before they even got a response. If you're going for a programming position where you're not expected to be different, then sure, but if you're going…

I have to disagree with your disagree! Many (most) jobs go through a pre-screen. The project manager is far too busy to filter all the crap, HR does that. HR sees a unfamiliar format, and simply bins that resume.

If they specifically allow other formats, or request a specific format, use it. But, in the case that they don't specify -- go with the most common format in the industry, anything else is nuts.

Additionally, if the primary filter on talent is .docx versus .pdf (or .txt or even .tex) -- it is a place so stupid you probably don't want to work there anyway.

Re: How programmers should write their resumes

#25

Post by eshvk »

mh_yam wrote: post #9

Don't call yourself a programmer.

Exactly. A programmer is a line cook. You want to be thought of as a guy who has potential to be a Chef or is one. I think the whole "impact of your work in numbers" also dovetails into this. That changes you from being an interchangeable cog to someone who can bring value and change the company.

Re: How programmers should write their resumes

#26

Post by MetaCosm »

mh_yam wrote: post #21
imdsm wrote: post #12

> "Don't try anything cute. You resume should be devoid of personality." I have to disagree. I got my current job because my resume stood out. It was the only one not written in MS word. The other candidates had equal if not greater experience than me, but I got the job before they even got a response. If you're going for a programming position where you're not expected to be different, then sure, but if you're going…

Agreed. My (LaTeX) resume that I spend many hours refining has caught the attention of many hiring managers, and I often get compliments on it. Curse those recruiters who reformat my resume into their shitty Word templates. I've had times where a hiring manager would have the recruiter's version of the resume, and when I handed them my pretty resume they were pleasantly surprised.

The recruiters do that because lots of HR departments are explicit: docx or deleted.

Once you get through the screen, you can show them your fancy resume, but at that point, no one cares about your resume -- you already caught their attention and it is interview / references time.

Re: How programmers should write their resumes

#27

Post by jasonlotito »

Like all advice on resumes and interviews, this should be read with the understanding it only applies to the particular person writing the article. So, if you are applying to a company where this person is reading the the resume and decided whether to interview you, write the resume using this advice. Otherwise, it will make no difference.

Re: How programmers should write their resumes

#28

Post by _puk »

eshvk wrote: post #14
luch wrote: post #2

I rarely agree with the author of this blog post : - "Don't bother mentioning your G.P.A." : I know firms are only interested in your diploma's name, but it can be an advantage to mention you passed summa cum laude whereas another barely made it by coasting and offloading his share of works on others students (which is unfortunately a useful skill in the workplace). - "Don't bother using verbs other than "made" for p…

> "Don't bring up your hobbies." : This one really raised my hair. Not everyone is tweeting every part of their life (I certainly don't) so hobbies are a great way to lighten the mood during the interview and assessing the interviewee's personality. I think it is fluff. Unless you are going to put something strikingly like juggling live swords, it is something I would glaze over. There are other ways to lighten the m…

> I think it is fluff.

You may think so, but you've no idea who is ultimately reading your resume.

Granted keep it short, but more than once this has got someone from the "maybe" pile into the "we'll take a look cos he plays bass" pile.

Re: How programmers should write their resumes

#29

Post by luch »

bjourne wrote: post #22
vezzy-fnord wrote: post #3

Not into GitHub? Register a memorable domain and throw together a to-the-point portfolio page instead. Or use another goddamned software hosting service? I'll never understand this sense of GitHub supremacy amongst trendies. Otherwise, the advice in general is subpar.

Then suggest one that is both better than GitHub and doesn't cost you any money. Sourceforge, Savannah, Google Code.. They all suck in comparison.

BitBucket ?

Re: How programmers should write their resumes

#30

Post by [deleted] »

mh_yam wrote: post #21
imdsm wrote: post #12

> "Don't try anything cute. You resume should be devoid of personality." I have to disagree. I got my current job because my resume stood out. It was the only one not written in MS word. The other candidates had equal if not greater experience than me, but I got the job before they even got a response. If you're going for a programming position where you're not expected to be different, then sure, but if you're going…

Agreed. My (LaTeX) resume that I spend many hours refining has caught the attention of many hiring managers, and I often get compliments on it. Curse those recruiters who reformat my resume into their shitty Word templates. I've had times where a hiring manager would have the recruiter's version of the resume, and when I handed them my pretty resume they were pleasantly surprised.

[deleted]
Post reply on HN