"The most valuable commodity I know of is information."

rebelutionary / 2.0

Applying for a Java job - HOWTO / 2005 Feb 01

OK - I've just about had it. We have a few jobs (Sydney and New York) open at the moment and as usual the overall standard of applications has been nothing short of appalling.

For anyone out there applying for any Java job, here are a few tips from me (as I sit on the other side of the fence):

1. Your cover letter or email should be in readable English

Poor language in your application letter is the fastest way to get your resume thrown in the bin without even getting read.

Gain experience through a combination of general skills and theoretical
knowledge is my motive.

Get someone to proof read it. I don't care what your grasp of English is, if you want to have any chance to get a job you have to at least fool the recipient into thinking that you can get through an interview to actually get to an interview.

Insincere flattery and other flowerly language in a cover letter look cheesy - forget it.

"With regard to the job opening In your esteemed Organisation"

"To your humble greatness I submit my application..."

In terms of language, poor English is one thing. Typos are completely another. If you can't send an important cover email without spell checking it, perhaps you shouldn't waste my, or your, time?

I beleive that I myself am the best suted and am the 'Perfect' match as to what you are looking for.

Sentences like this, no matter how much you believe in yourself, will make it very hard for a potential employer to believe in you.

2. Your experience should be relevant

Generally, people in job ads explain what they're looking for. You should therefore explain why you suit the role.

If the job is for a J2EE architect, don't tell me why your knowledge of CSS esoterica is important.

If the job is for a technical support person, don't tell me why your financial knowledge will help with our accounting!

3. Read the bloody job ad

Yes - this sounds simple, but for some reason people see a job ad, get inspired, fire off their resume and then wonder why the hell it takes them months or years to get a job.

Did you think of actually reading the ad first?

When we have jobs in our Sydney office, we explicitly put "You must be available in Sydney for an interview." - but despite this hundreds of hopeful people from around the world decide they should send in their resumes anyway. "I can telecommute!", "Relocations are always in willingness to be undertaken from country X" (for the language tips, read point 2!) etc are not going to get you a job.

We used to always ask for resumes in PDF, HTML or text format and delete any that are Word documents. Now we do read the Word documents because there are so many of them, however we still give those people a small cross against their names for not reading the ad.

I've always wanted to ask for all resumes to be typed in pink, just to see how many people actually read the ad. My guess is we'd get one or two per hundred who actually cared enough about their application to send a pink PDF.

Save a few poor bits and don't hit the send button if you haven't read the ad thoroughly.

4. Do something, anything to stand out

There are a million people who will apply for any given job with potentially relevant experience. Your task in a job application is to stand out from the crowd enough that you will get an interview. (Interviewing tips may come in a future post!)

Every time we have a developer position, we can get a few hundred resumes. We're not even going to interview 10% of that number. 50% or more will get cut based on the 3 rules above. Beyond that, you have roughly a 1 in 5 chance of standing out.

How do you stand out? There are plenty of ways to do it, my two favourites:

  • start a blog or write an online article - this shows you can communicate and you're interested enough in your choice of vocation to write about it under your own steam
  • contribute to an Open Source project - hell, fix a bug in any project you use then include the project on your resume as something you've "contributed to" (if they don't have a good bug tracker I can recommend one ;))

Other than that you can stand out by clearly reading the ad and responding to its requests,

5. So you have experience, explain it!

If you have had previous jobs, explain why or how your previous experience was good and most importantly - what the hell you did there!

"XYZ Corporation - Developer - Jun 2001-July2004"

Thanks - very useful. What did you do? Did you make coffee for the architect and senior developers? Did you develop the documentation and help files? Did you design a brilliant three tiered, event driven system that blew the previous sytem's performance away by 100 fold? Tell me!

Oh, and don't bullshit me. It's very easy to see.

"High School - 1997-2000."

"FooBar Technical College - 2001-2003."

"Massive Bank X - Senior Architect, Guru Developer and Indispensable Team Leader of 100 developers - 2004-Present."

Doubtful at best, lies at worst. If the rest of your resume doesn't reflect god-like status, you're likely to be thrown in to the trash.

Explain your experience, what you did and what you learnt, how you progressed in your career through positions 1, 2, 3, 4, but drop the bullshit.

6. Lose the insanity

"I truly had an experience of that of biting steel!"

I have no idea what this sentence really meant in the context, but it scared me about the person's previous work experience.

If these tips seem like common sense to you, congratulations you probably have a great job and will continue to have a fulfilling career (if you don't, tell us). From the perspective of someone who has hired a lot of developers in the last 3 years, sadly they are not.

Comments

As somebody who has recently been on both sides of the hiring table, your post rings all too true.

I'd also like to add:

"And don't call me to ask the status of your application 4 hours after emailing it to me (no doubt in the improper format). If I like you, I will call you - I don't want to have to akwardly lie to you and say it's still being processed. Or worse, if you catch me on a bad day have to tell you straight out that there's no way that your crap of a resume will get you any job, never mind this one."

Posted by: Ryan Daigle at February 1, 2005 3:32 AM

<font color="pink">Hey is that job still open? I live in Denver but I have always loved Sidny.</font>

Posted by: Shaun at February 1, 2005 4:18 AM

I've had the same experience. We're hiring a senior J2EE engineer http://jroller.com/page/thuss/Blog/hiring_a_java_spring_hibernate and out of several hundred resumes we've gotten I can count on two hands the number of applicants that exhibit a polished resume, proper english, ran spellcheck, and who took the time to write a thoughtful cover letter.

Posted by: Todd Huss at February 1, 2005 5:31 AM

I agree with almost everything in your article. The single thing I disagree with is the point about the spellchecker. I don't run spellcheckers. Ever. If I can't type it correctly, then I can't type it correctly. Not only that, but most spellcheckers in my mother tongue (Norwegian) sucks.

Spellcheckers are part of ruining an important part of our language. In Norway we combine words into concatenated words. As an example: "orddelingsfeil". (Word division error). Spellcheckers most of the time want to divide this into "ord delings feil" - which is plain out WRONG in Norwegian. The dorks that use spellcheckers tend to get this (and other concatenations) wrong every time. They divide the word into three words to get the spellchecker to stop complaining - trusting it to know the language better than them.

I'm pretty sure you can find plenty of errors in my english here - but hey - I'm not to worried about that. I'm far to angry at spellcheckers to ever want to use them.

Except for that - excellent rant.

Posted by: Anonymous Coward. at February 1, 2005 6:14 AM

RE: point #1 above

"learnt" is not a word :-)

See you in Vegas....

Posted by: Jason Carreira at February 1, 2005 6:49 AM

AC, it's a question of care. If you don't care enough to do _some_ sort of review over a job application, then it can't really mean that much to you. At the very least, sit down and proof read it.

Too many people treat a job application like a casual piece of email, and it really shows.

Posted by: Robert Watkins at February 1, 2005 6:50 AM

RE: Jason

http://dictionary.reference.com/search?q=learnt

Looks like a word to me!

See you in Vegas :)

Posted by: Mike Cannon-Brookes at February 1, 2005 7:28 AM

I understand and agree with your comments regarding good English usage in cover letters. However, I can understand why many people would want to send their applications despite knowing beforehand that a certain criterion needs to be met, for instance, the applicant should be eligible to work in this country. I, myself, have applied to jobs in the UK even if I know I will require sponsorship and the job ad says that they are not interested, but whenever I do, I kindly state this in my cover letter. Maybe the reviewer will find my skills relevant and will accept to sponsor me. I can never be too sure.

Posted by: Eddy Young at February 1, 2005 7:56 AM

What pisses me off most is when I find the candidate have a puffed up resume with many technical terms yet doesn't have much knowledge about them or just have a cursory idea.
Nowadays everyone knows EJB till you ask them few questions.

And if you are trying to impress me you better read about the company and make some intelligent comment about the business to show your maturity.

Here I also get resumes often with their beautiful pictures and with their marital status (why the hell do I care?) and their father's name and sometimes even their passport number!

Posted by: Angsuman Chakraborty at February 1, 2005 11:29 PM

Are those quotes for real? Oh boy do I have some fun ahead of me...

Posted by: Richard Rodger at February 2, 2005 1:11 AM

so it seems you are getting the top 99.9801% of candidates
(http://www.joelonsoftware.com/items/2005/01/27.html)
and maybe you got everybody you can in Melbourne ...

alek

Posted by: Aleksander Slominski at February 2, 2005 4:03 AM

Learnt vs Learned :
http://www.askoxford.com/asktheexperts/faq/aboutspelling/learnt?view=uk

Posted by: Tim Vernum at February 2, 2005 9:07 AM

I am viewing your site on an Apple 12 inch powerbook, but still I have a resolution over 1000 pixels wide. Yet because your site or table width is set so big I have to keep scrolling back and forth horizontally to read your article. The text should wrap to a narrower width. Before you rant and rave at the poor presentation/professionalism of others, you should fix yours! If you used this site as a reference of your own abilities, no one would hire you.

Posted by: Dave Parizek at February 3, 2005 4:34 AM

I am viewing your site on an Apple 12 inch powerbook, but still I have a resolution over 1000 pixels wide. Yet because your site or table width is set so big I have to keep scrolling back and forth horizontally to read your article. The text should wrap to a narrower width. Before you rant and rave at the poor presentation/professionalism of others, you should fix yours! If you used this site as a reference of your own abilities, no one would hire you.

Posted by: Dave Parizek at February 3, 2005 4:36 AM

Mike,
I have sat at both sides of the table, and I appreciate the comments that you have posted. I agree to all the concerns you have raised here.

Since you are having trouble getting a focussed repies from potential candidates, it might also help to think if there is something you can do to improve things. I admit that it feels cool to conclude how everyone else out there is stupid - but to get around the problem you need to look at your end too. So here goes:

1) Be specific. Don't have ads with "O-R Mapping is important to us, so we are looking for a person who is comfortable with Hibernate, TOPLink, Cocobase *and* Kodo" when looking for a developer. If a project is using all of these tools, its because either it is super-cool or a super-mess - many if not most J2EE shops anyway develop CRUD web GUIs for an RDBMS, so I am inclined to think its the latter.

2) Be realistic. Dont put out ads asking for "..should have 8-10 years of Java experience" to fill a developer position. Java itself is just reaching its 10th year of existence, and please tone down the ego and look if your application realistically needs those skills.

3) Dont be too picky. Maybe you will have trouble finding Tapestry + WebWork developers, but its highly likely that you can hire some good Struts + JSP developers and train them in the specific technologies you want to use.

Often I see advertisements from employers without any focus whatsoever ("Yeah, we are looking to hire James Gosling, if he can accept a developer salary!"). Also, often I see recruiters getting on their soapboxes and preaching how stupid every job-hunter out there is. After being on both sides at different periods in life, I feel that *both* sides can do better with some introspection.

Thanks,
Binil

Posted by: Binil Thomas at February 3, 2005 11:29 AM

Mike,

I think the most important word here is "respect." When you think about it, if the applicant does not respect you enough to submit a resume that is well formatted, concise and targetted to your needs, how can you expect them to do so once you have employed them. This is at least the approach that I take when applying for a position and definitely reflect my thoughts when I am the person doing the hiring.

I think that you have compiled a fairly comprehensive
list of my complaints in this area but have missed one of the most important, i.e. "keep it short!" Keeping the resume at around 2 pages helps to ensure that your resume is going to be read in the first place. It also ensures that you are not giving so much information away that the reviewer can look at it and decide immediately that they don't want to talk to you. From a candidate's point of view it is important that you get in front of the people that are doing the hiring, and this is when you can really impress (as long as you don't turn up with your arse hanging out of your pants).

Just remember, demand respect now, or you'll never get it.

Posted by: DVS at February 4, 2005 9:57 PM

Shouldn't it be "proofread" ? :)

Posted by: Thomas Risberg at February 6, 2005 5:33 AM

You mention that your company prefers resumes in PDF, HTML or plain text (rather than Word), but your web page will not render correctly in Firefox or Konqueror -- it only renders correctly in IE. I find this to be quite odd...

Posted by: David Roche at February 15, 2005 11:34 AM

About / LIFE

Atlassian

Atlassian / WORK

Photos / PERVE

Search / SEEK

Mates / BLOGROLL

Investments / FUTURE

© Mike Cannon-Brookes - 2000-2006