In my career as a software developer I’ve been lucky. I’ve been lucky that finding work has never been terribly difficult. The longest I’ve ever been out of work is a month and a half. Six weeks might seem like a long time, especially in software; in my case I was unfortunate enough to experience a two-week delay in my interviewing thanks to the Snowpocalypse of 2010 and the aftermath of that event. When I’ve actively looked for work I’ve been pretty fortunate to have a good resume, good skills, and most importantly, a strong job market for the particular field I’m in.
What I’ve often struggled with is finding the right job. There are lots of bad jobs out there; many developers are in them. I’ve been in them. You know the type: jobs that have managers who think that being salaried means they own your every waking moment. Jobs with non-compete clauses that would force you out of your profession if they were enforced. Jobs that advertise for “good under pressure” people or “detail oriented” individuals.
At some point or another, every technical person will conduct a job search. And either by design or accident, they will encounter the nemesis of job searching: The Recruiter. These individuals are employed by companies whose sole purpose is to serve as an intermediary between job seekers and potential employers. Their marketing literature will say that they match you to potential jobs, and since they spend their days looking around for potential job openings, they have a better grasp of whats out there than you do. It’s their claim, anyway.
The big problem with recruiters is that they are typically paid based on two criteria: the salary of the jobs they put people in, and how many people they place. This might sound like a win-win, but really, it’s a win for the recruiter and a loss for the job candidate. What common strategies do recruiters use to lure job applicants, and why are they bad for you? Let’s take a look…
There seem to be lots and lots of PHP folks out there looking to hire good PHP developers. Finding the right developer can be a challenge, as can finding the right job.
I’ve been looking for a couple weeks now, and I wanted to put together a short blurb on why you should consider hiring me to be on your PHP development team.