How to write a developer resume that will get you hired
slideshare.net
How to write a developer resume that will get you hired
1–10 of 208 posts
Re: How to write a developer resume that will get you hired
#2I 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...
Re: How to write a developer resume that will get you hired
#3I'm still debating whether working for a company where the HR people does the initial filtering is worth working for. It's certainly something I was not doing when I was hiring, I was getting my resumes directly.
Re: How to write a developer resume that will get you hired
#4I 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...
Thanks for this, currently a PHP contractor looking for work in the UK and this certainly opens my eyes up to the issues with my CV. Probably explains why I haven't been getting many interviews!
What would you suggest for a contractors CV which is primarily filled with 1-2 month contracts?
I usually try get the last years work on the CV, but as you can imagine that starts to take up quite a bit of room when you have many short term contracts.
Re: How to write a developer resume that will get you hired
#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.
Re: How to write a developer resume that will get you hired
#6I 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...
Thanks for this, currently a PHP contractor looking for work in the UK and this certainly opens my eyes up to the issues with my CV. Probably explains why I haven't been getting many interviews! What would you suggest for a contractors CV which is primarily filled with 1-2 month contracts? I usually try get the last years work on the CV, but as you can imagine that starts to take up quite a bit of room when you have…
I would portray as one role, and a few really important projects.
For example:
Senior Consultant For the past 24 months, I've worked with a large number of varied clients to realise true business value for them. This has included Real Example A and Specific Detail B, but beyond the pure technical skills, it has highlighted the value of softer skills.
Most notably, I recently worked with the estate of Douglas Adams in an ecommerce towel distribution hub. Don't panic, I'm the right chap for the job.
Re: How to write a developer resume that will get you hired
#7"...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.
Which city are you in? I wonder if it's a cultural difference. In the UK, I'd always recommend dressing smart.
Re: How to write a developer resume that will get you hired
#8I 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...
Why are you perpetuating the myth that frequent switching of jobs is somehow detrimental to your career? Maybe that's true for corporate megacorp, but in the startup world I feel it's par for the course. At least all the best engineers I've worked with never stuck around long.
Re: How to write a developer resume that will get you hired
#9I'm still debating whether working for a company where the HR people does the initial filtering is worth working for. It's certainly something I was not doing when I was hiring, I was getting my resumes directly.
I think it's common enough that it doesn't provide you a good signal for what working for the company will be like
Re: How to write a developer resume that will get you hired
#10I 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...
Why are you perpetuating the myth that frequent switching of jobs is somehow detrimental to your career? Maybe that's true for corporate megacorp, but in the startup world I feel it's par for the course. At least all the best engineers I've worked with never stuck around long.
Depends what you mean by "long". I think people should move every two to three years. But you say "myth", and I can tell you categorically that CVs with lots of 6 to 18 month non-contract roles on them get rejected on that basis alone.