<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1621132604871265&amp;ev=PageView&amp;noscript=1">

When you think of fun ways to spend your time, I’m sure interviewing isn’t high on the list. The “necessary evil” is vastly different across industries, especially in the field of technology. Developers and technical hiring managers alike can agree that this interview process is broken. One way to help make the technical interview process more pleasant for both parties is to give the candidate an interview agenda ahead of time. This also helps the hiring managers since any questions the candidate has can be properly addressed early on.

If you’re interested in putting together an interview agenda for your upcoming developer interviews, here are a few things to include.

Tell Them Who They’ll Be Interviewing With

When I interview candidates, I’m always impressed when they mention something they found out about me online prior to the interview. Whether it’s a project I worked on, a piece of content I wrote, or a shared connection we have in common, it shows that they did their research. On the flip side, when I’m interviewing for a new position, I like to familiarize myself with those who will be interviewing me. I may end up working with these people if I get the job, so I want to make sure I like them and can see myself working with them.

interview preparation.png

The same goes for developers- 35% said they want to be better prepared for the interview, including being informed of who they will be speaking with during the interview process. You don’t need to give them a biography of each of their interviewers, but shooting over a quick email with the names of each employee would suffice. Then it’s up to the candidate to do their research and become familiar with their prospective coworkers.

Similarly, we found that 47% of developers want to be introduced to the team during the interview process. While you can’t physically introduce them to your engineering team prior to the interview, you can give them an idea of what they are like. Include any collateral you have on the engineering team, such as blog posts they’ve written, projects they’ve worked on, or even a “Day in the Life” employer branding videos you created.  

Inform Them of Their Potential Assignments

You don’t have to give them the questions ahead of time, but if you’re going to have them perform a 2-hour live coding test, giving them a head’s up can help immensely. Break down the interview process to the developer – tell them how long each interview typically runs, what type of interview it will be (coding exam vs. a generic chat), and what they need to bring with them. Nothing is worse than coming in for an interview on your lunch break only to find out it’s actually a 5-hour long process.

Sort Out Expectations Up Front

To not waste anyone’s time, be sure to set expectations prior to the interview. Discuss the salary—whether it’s a range of a definitive number—prior to the interview. No one wants to waste their time interviewing with a company only to realize the salary they are willing to give is too low or, worse, is different than what they were originally told when applying.

interviewing developers ebook

Comments

Schedule a 15 minute call

Call +1-877-782-2577 or email careers@stackoverflow.com for answers to any questions you may have