Live data from Hacker News

How programmers should write their resumes

doesnotcompute.biz

71–74 of 74 posts

Re: How programmers should write their resumes

#71
post #31

Earlier quoted context omitted.

Haha. If a company doesn't want to hire me because my resume is not in .docx format, I probably don't want to be working there anyway!

Job candidates have a zillion "well if they don't want to work with me I don't want to work there" rules. But companies also have a zillion "well if they don't want to work with me I don't want them working here" rules. Listen, sometimes in the real world you have to do something a little unpleasant every now and then. Candidates should bend a little to employers, and employers should bend a little for candidates.

This only applies when you're in a position where if you don't get the job, it's a bad thing. But when you get to a certain point, getting a job is easy. It's getting the right job which is hard.

Re: How programmers should write their resumes

#72
post #63
post #31

Earlier quoted context omitted.

Haha. If a company doesn't want to hire me because my resume is not in .docx format, I probably don't want to be working there anyway!

If you judge a company based on its hiring team's practices, you'll probably rule out a lot of great companies.

If you call them and let them know they're not accepting your format of resume, ask them if you can send a physical version, and get a negative response, then it's the companies loss, surely.

Re: How programmers should write their resumes

#73
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…

I have to agree with your disagree but point something out also.

> HR sees a unfamiliar format, and simply bins that resume.

When they bin the good resumes, they bin the good candidates, which means the chances of the current employees not being particularly good is higher. This would make me think twice about working for a company that says no to the better candidate because HR found their job too difficult.

Re: How programmers should write their resumes

#74
post #23
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.

Animated GIFs/cat video?
Post reply on HN