Rules of engagement: How to hire (and get hired as) a developer

Hiring a developer, or getting hired as a developer, is a bit like online dating: Both sides are nervous, the risks are high and mistakes in picking the right match can be costly.

In this session we will look at the process from both perspectives — the interviewer as well as the interviewee.

We'll start with the things you can do even before sending out your first application. How can you increase your market value, so employers get curious about you? How can you do that without sacrificing your firstborn or selling out?

Once you found an advertisement for that dream job you send out an application (without sounding like an infomercial), keeping in mind that the main goal is to stand out from the pile and get to a first personal conversation. That first conversation might end up being a huge pain or disaster, and that’s not necessarily a bad thing! A job interview is a two-sided process, maybe the company is simply not a good fit for you?

Then there might be a technical test in the interview process (…which you pass with flying colors, no problem), and of course the always stressful interview negotiations about how much money you want.

I have been on both sides of the table, conducted interviews for developer positions at places like Duke University, Michigan State University as well as corporate companies. Sometimes the applicants were so nervous all I wanted to do was give them a hug, sometimes they acted so pompous I couldn’t wait to send them a rejection.

I recently applied for jobs as a developer myself, with some horrible and some fun experiences, ending up with a job offer from a great company for one of those coveted jobs that allow working remotely.

This session is not specific to Drupal, but suitable for any software- or web-developer. It doesn't matter where you are in your career, if you’re looking to get your first job as a developer or have been in the business for a while.