Tips for landing a php job in London

by oneafrikan on June 30, 2008

OK, so I’ve not got long so will be brief and to the point with this one, in the hope that it will help some of the people that read this blog, and maybe even some of the folks that are looking for devs to join their teams.

I’ve had to run through a lot of agencies and candidates in the last month or so, recruiting for Kindo, and these are some thoughts in no particular order:

As a candidate

DO:

  • accept there is lots of good competition; you have to stand out to be noticed
  • research on the company you’re interviewing at – it’s polite and will help you with 3, 4 and 5
  • send a cv that is relevant to the job spec – java experience won’t interest someone looking for a php person
  • learn how to sell yourself and articulate your experience – enough said
  • accept you’re going to have to send code to show what you can do – send your best relevant code
  • describe what your code is supposed to be doing to there is context – don’t just send a bunch of methods
  • comment more than you think you should – esp if you’re going to work in a team or be contracting
  • write documentation in the code for something like phpDocumentor – that makes people happy

As a general rule (unless you’re a superstar), your work environment, the people you work with, and the work you’ll be doing, should all supersede remuneration unless you have a specific reason (like a mortgage for example).

As someone recruiting

DO:
Read this first:
http://www.nickhalstead.com/2008/07/01/10-reasons-why-i-hate-recruitment-agents/

  • accept that it is going to take up a lot of your time
  • have a clear job spec and role description in place to send around
  • use your personal network first
  • get your agencies to send some cv’s to assess the kind of candidates they have
  • ask for source code if you like the cv – you’ll do less unnecessary face to face’s
  • expect them to do some filtering and work for you; if not, bin them
  • turn your phone off if you want quiet time to work
  • agree on terms first, or re-confirm them if circumstances change on your end

Hope that helps!! ;-)

Leave your comment

Required.

Required. Not published.

If you have one.

Protected with IP Blacklist CloudIP Blacklist Cloud