Thanks for sharing! Lots of great information in here. I've been a hiring manager for a role more than once and I can attest that it's all true. It would be nice if more people made CVs as easy to read as the tips here would produce. I even picked up one or two new ones for my own CV :-).
How to write a developer resume that will get you hired
61–70 of 208 posts
Re: How to write a developer resume that will get you hired
#62Earlier quoted context omitted.
'Or at least business casual' It really depends on the place. If there's a recruiter involved, ask them. Otherwise, (the following is based on my experience in the US, YMMV, etc), if they're not a software company, or are a defense contractor or similar, probably safest to go with a suit. If they are a software company, business casual is probably fine. If they're a startup, jeans and a t-shirt is probably fine. If y…
I don't have all these different kinds of clothing. (And no I don't want to own them either). Am I the only one who thinks this game should be played the other way around? If a company needs my services, they should impress me. I am not a model and I am sure as hell not a wage slave. I don't do CVs, and I sure as hell don't talk to HR. I am performing a necessary duty, if I can fill my role then my other traits will…
That really depends on the hiring environment you are working in. Right now, in most of the tech centers around, it is an employees market. This is not always true and it can be different for different tech centers, technologies, and employees.
So sure, while this is working for you right now, keep it in mind in the future when this bubble bursts.
I do find it interesting that an adult with professional career in the western world doesn't own at least 1 set of "professional" clothes. What do you wear to weddings and funerals?
Re: How to write a developer resume that will get you hired
#63> 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...
Good, if a company deals with a recruiter that dumb, imagine the quality of the rest of the staff you would have to deal with!
Re: How to write a developer resume that will get you hired
#64Earlier quoted context omitted.
It may seem like you were dressed OK, but do you really know? Does anybody ever say "we can't hire that guy, he dressed up?"
An applicant came to our job dressed in a suit and it looked really strange and made us question his judgement and experience.
If you didn't tell the applicant ahead of time not to wear a suit, it was your fault he wore one. Being dressed in a suit is the standard in the professional world. Just because you (and I) work in an environment that doesn't conform to that, doesn't make the applicants judgement suspect, it makes our worldview skewed and we should be prepared for that. Further, it is common courtesy to tell an applicant not to bother with a suit, just in case it is in the back of their closet gathering dust...
Re: How to write a developer resume that will get you hired
#65I 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...
I think the slides could use some dressing up.
What's the Perl scene like in the UK? As a former Perl professional, I'm continually not impressed by the caliber of some of my colleagues. I've actually left for greener pastures.
Re: How to write a developer resume that will get you hired
#66On slide 16:
Shows you actually care about programming
Re: How to write a developer resume that will get you hired
#67> 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...
Good, if a company deals with a recruiter that dumb, imagine the quality of the rest of the staff you would have to deal with!
A large company might have an HR department that is insulated from any of the 'technical' branches that company might have. Imagine if they had to have all sorts of knowledge about what every individual branch of the company does? It's their job to be gatekeepers that make sure the people coming in for interviews are not raising any red flags, further along in the hiring process skill will be determined.
Re: How to write a developer resume that will get you hired
#68I 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...
I think the slides could use some dressing up. What's the Perl scene like in the UK? As a former Perl professional, I'm continually not impressed by the caliber of some of my colleagues. I've actually left for greener pastures.
> I think the slides could use some dressing up
> What's the Perl scene like in the UK?
[1] Or, tried to, but there are still pockets of Perl everywhere that no-one ever got around to rewriting. See: Amazon, the BBC, etc.
Re: How to write a developer resume that will get you hired
#69I remember an awful confrontation with a first stage HR employee that was particularly nitpicking with my resume while not knowing the difference between Java and javascript. Ha.. keywords.
An awful confrontation is definitely not a way to go. May want to try coaching approach, politely explaining the difference. For all you know, it may have been an intentional filter. Bottom line though is that it helps you to use the same keywords they are looking for, to the extent you have the relevant experience.
Intentional meaning her toying with me to test my stability ? Any way I failed hard, I was in a bad place and immature. Of course I would do everything differently. Acceptance of the game instead of anger.
Re: How to write a developer resume that will get you hired
#70Earlier quoted context omitted.
As someone who has done a ton of hiring, switching jobs a lot is definitely a red flag. Not an automatic reject, but I frequently have to make choices like "It will take this person N months to become useful here, they switch jobs on average every M months. M-N seems like a pretty short time..."
So, would you advise towards a competence based CV? In case a frequent switching happened, what would you like to see in a resume?
> In case a frequent switching happened, what would you
> like to see in a resume?