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

How to write a developer resume that will get you hired

slideshare.net

Post reply on HN
Print view View original

151–160 of 208 posts

Re: How to write a developer resume that will get you hired

#151

Post by opendais »

vinceguidry wrote: post #111
Tyrannosaurs wrote: post #86

Earlier quoted context omitted.

I don't disregard them completely and I think CVs can be written in such a way that recruiters (who actually get very excited about such stuff these days) and HR people will be fine with this sort of thing. What I would say is that there is a difference between hobby code where you get to do what you want and code where you didn't control requirements and had to deliver to unreasonable people in unreasonable timefram…

I do agree with you RE: hobby code. I did a jQuery Facebook app for fun, but the one-off weather app I built for a major utility company was and should have been way more impressive even though I did the hobby project after the weather app with all the lessons I'd learned about Javascript from the one I got paid for. Ultimately this is why I don't take any of my side projects seriously anymore, and if there's somethi…

That doesn't work in the real world for most people. At my Day Job, I use Language X with version Y for everything. I use Library Z and T only. Oh, and I can use ancient language B as well but I cannot use any 3rd party code with B. You will use version control method G.

Any attempt to deviate from that is not permitted because it leads to compatibility issues with the rest of the codebase & it reduces the ability of other programmers to work efficiently on it.

I suspect many programmers operate under similar restrictions.

Re: How to write a developer resume that will get you hired

#152

Post by grecy »

pera wrote: post #37

> Sorry, you need JavaScript experience, but all I can see in the web development section is AngularJS and jQuery This actually happened to me a couple of weeks ago, and I do have JavaScript listed in my languages section...

I've been applying at our state government and keep hitting this. The standard joke is you could list your only experience as "Pizza Hut Delivery Driver", as long as you put the words "Linux, Javascript & Apache" in the description.

The HR people literally just do a "Find" for words without reading the rest, and that gets you a phone interview.

Re: How to write a developer resume that will get you hired

#153

Post by Tyrannosaurs »

talmand wrote: post #107
Tyrannosaurs wrote: post #86

Earlier quoted context omitted.

I don't disregard them completely and I think CVs can be written in such a way that recruiters (who actually get very excited about such stuff these days) and HR people will be fine with this sort of thing. What I would say is that there is a difference between hobby code where you get to do what you want and code where you didn't control requirements and had to deliver to unreasonable people in unreasonable timefram…

What I get out of that first statement is that you do tend to disregard unless the candidate knows exactly how to describe the related subjects on their CV in a way that makes you happy. And you don't see the problem that developers might have with that? Especially when they don't know the secret method of describing things to make recruiters happy? As for the rest, I think it's reasonable to assume that a candidate…

I think it's OTT describing it as a secret. If a job spec lists a skill, highlight where you've used it so I can see your experience. That's not difficult or counter intuitive or unreasonable.

Realistically I can't interview everyone and it wouldn't be in anyone's interest to do so. The current stats I have say I will first interview one in four screened CVs. Out of those about one in three will get a second interview and half of those an offer. So I interview maybe half a dozen people per appointment from about 25 CVs).

That means right now if you give up an hour of your time for a first interview (plus travel and so on), you've got a one in six chance of getting a job. If I interviewed more people, your chances go down. I may end up with a better recruit but I'm actually externalising a lot of the costs to the other candidates who don't get the role.

Re: How to write a developer resume that will get you hired

#154

Post by grecy »

dpweb wrote: post #114
peteretep wrote: post #2

I wrote this. It's a tiny bit Perl/UK-centric, but I think you could easily apply it to other markets. Happy to answer any questions...

Great slides - thanks. One surprise "leave off education". Would like to hear some more thoughts about that - haven't seen that before. 18 yrs experience so I'm sure its not too important (I did nothing spectacular in college, but did graduate) - still leave it off completely?

I second the question.

I have a bachelor of Software Engineering (certified Engineer) with First Class Honors, and I know I'm usually competing against people with a Comp Sci. degree, or even just a diploma. I think it's important to highlight my education, as it puts me a cut above.

Am I being a little stuck-up?

Re: How to write a developer resume that will get you hired

#155

Post by vinceguidry »

opendais wrote: post #151
vinceguidry wrote: post #111

Earlier quoted context omitted.

I do agree with you RE: hobby code. I did a jQuery Facebook app for fun, but the one-off weather app I built for a major utility company was and should have been way more impressive even though I did the hobby project after the weather app with all the lessons I'd learned about Javascript from the one I got paid for. Ultimately this is why I don't take any of my side projects seriously anymore, and if there's somethi…

That doesn't work in the real world for most people. At my Day Job, I use Language X with version Y for everything. I use Library Z and T only. Oh, and I can use ancient language B as well but I cannot use any 3rd party code with B. You will use version control method G. Any attempt to deviate from that is not permitted because it leads to compatibility issues with the rest of the codebase & it reduces the ability of…

I mean, if your job comprises only tasks and no responsibility, then your job then is to either demonstrate enough value so as to convincingly ask for responsibilities or hop around until you find someone that will give you the latitude you need.

I've worked three jobs in the last year where I had a lot of flexibility in this regard. And I enjoyed it when I was freelancing too. The world's a lot bigger than the little bit of it you're seeing now. Get out there and see some of it.

Re: How to write a developer resume that will get you hired

#156

Post by kasey_junk »

grecy wrote: post #154
dpweb wrote: post #114

Earlier quoted context omitted.

Great slides - thanks. One surprise "leave off education". Would like to hear some more thoughts about that - haven't seen that before. 18 yrs experience so I'm sure its not too important (I did nothing spectacular in college, but did graduate) - still leave it off completely?

I second the question. I have a bachelor of Software Engineering (certified Engineer) with First Class Honors, and I know I'm usually competing against people with a Comp Sci. degree, or even just a diploma. I think it's important to highlight my education, as it puts me a cut above. Am I being a little stuck-up?

From my experience the kind of degree someone has is virtually meaningless. The only time I even take it into account is when I'm choosing interns and the difference between Software Engineering and Comp Sci is still meaningless.

Re: How to write a developer resume that will get you hired

#157

Post by jackmaney »

robalfonso wrote: post #77
Bahamut wrote: post #5

"...did you wear a suit" I guess it might depend on the industry, but at most interviews I have done, the expectation has been to just wear jeans and whatever. I usually go with jeans and a polo shirt for safety.

I work at a very casual office, when I've interviewed I've seen just about everything from jeans/t-shirt to a suit. My take away is "look nice" regardless of what level of dress you have chosen. I've been impressed by candidates that wore suits. It shows they understand their appearance is important, however, it is not a deciding factor in the job, just a nice to have. Also had people show up in a suit that is 10 yea…

> Also had people show up in a suit that is 10 years out of style or with hideous tie,etc.

And a sense of fashion is relevant to the job...how, exactly?

Re: How to write a developer resume that will get you hired

#158

Post by kasey_junk »

JoeAltmaier wrote: post #131
logfromblammo wrote: post #129

Earlier quoted context omitted.

That attitude is a bit arrogant, and will only serve you well as long as potential employers have little alternative but to put up with it. But it is still less arrogant by far than the attitude of most employers with open positions that I have encountered. The "game" should be played with equal respect offered by both sides. Both parties are vetting the other before entering into a potentially long-term relationship…

I thought interviewing was a negotiation, you trying to get the best deal, them trying to convince you to work for peanuts. You meet in the middle, or you both walk away. All the talk of respect and time wasting and efficiency is missing the point. Arrogance is a tactic and if it works for you at your level, then more power to you.

When I'm on either side of the desk, I don't assume that it is the employers job to get a candidate to work for peanuts. The marginal cost difference between what a good candidate is worth to me, and what I can effectively negotiate is tiny in comparison to getting the candidates I want.

That is, it is much more expensive for me to get the wrong candidate, than to pay a little too much for a good one.

Re: How to write a developer resume that will get you hired

#159

Post by UK-AL »

Tyrannosaurs wrote: post #144
UK-AL wrote: post #84

Earlier quoted context omitted.

It's simple logic, people move because they can better deal somewhere else otherwise there would be no point. So if people move, the benefits aren't keeping up with other jobs they can get. Most employees are not loyal, because they know companies are not. If they think companies are loyal, they are probably new to the job market. Once a project ends, and there's nothing else to work on they will get rid of you. Ther…

Obviously there is no one rule for everyone but personally in 20 years working in IT I've never left a job because of money (and I've left a few). I've left because of uncertainty, because the work was bad, because there were too many arseholes where I was, because my skills were rusting but never for money. In the past five years a fair number of people have left the company I work for and I'd estimate about 25% wer…

I never meant for money(one part of it), i said a better deal, or a better complete package if you will.

Re: How to write a developer resume that will get you hired

#160

Post by Eiriksmal »

dpweb wrote: post #114
peteretep wrote: post #2

I wrote this. It's a tiny bit Perl/UK-centric, but I think you could easily apply it to other markets. Happy to answer any questions...

Great slides - thanks. One surprise "leave off education". Would like to hear some more thoughts about that - haven't seen that before. 18 yrs experience so I'm sure its not too important (I did nothing spectacular in college, but did graduate) - still leave it off completely?

That's what I'm also curious about. I never finished my degree and understand I have to leverage work experience and a killer portfolio to get my next development job, but have yet to figure out how to structure my resume around this niggling detail.

Leaving off the education section is interesting... I'm assuming this strategy is to give you an opportunity to create interest as a candidate before the (inevitable?) question comes up, "I see you didn't mention education on your resume... Could you tell me more about that?"

Edit: Grammatical fumbling.

Post reply on HN