In recent years, I’ve gained a wealth of experience from well over a hundred job interviews, whether as a candidate or as a technical expert. I’ve distilled this experience into the following points, which can make any interview more successful. As a software developer, I am focusing exclusively on the IT industry. These tips may also be useful in other sectors, but I cannot personally vouch for them.
The more often you face the situation of a job interview, the more confident you will become. I recommend practicing with friends or family. If no one is available, consider applying to jobs you’re not necessarily interested in taking.
Rule: Attend every interview you are invited to!
Many candidates struggle to present their resumes in an organized, chronological, and fluent manner. As an interviewer, you often ask the same questions to ensure comparability between candidates. You can easily score points here if you can present your milestones confidently and smoothly.
In the interview confirmation, you’ll often see the names of the participants. Always take this opportunity to research them:
Never refuse a drink. You wouldn’t believe how often your voice can fail. If someone has to get a drink during the interview, it can disrupt the flow of the conversation. Taking a sip of water also gives you a chance to pause, think, and calm your nerves. Rule: Always accept the drink!
That’s absolutely fine. But don’t start rambling or making something up. Any experienced colleague will immediately sense your uncertainty and may reject you. Be honest and say you don’t know, and then turn the question back. The technical colleague will likely explain it in front of the manager, and you will have learned something new.
Far too often, candidates show up in suits that are too tight or too loose, fidgeting with their collars and sweating. It’s not a problem to ask about the dress code beforehand. The company’s website often gives you a good idea of what to expect in terms of clothing. While clothes do make the man, they also reveal whether you feel comfortable. If you’re not a fan of suits, wearing slacks with a polo shirt is perfectly fine. It’s important to consider whether you’re applying for a consulting role or an in house development. Your new employer will judge whether you can be shown to a client. A neat appearance and clean clothes are more than enough. You don’t always need a suit.
Only one in fifteen candidates brings something to write with. I think that’s a big mistake. As mentioned earlier, you can jot down questions you couldn’t answer. You might also want to note:
Due to nerves, you’ll often forget much of the conversation afterward. Taking occasional notes also shows you’re interested and well-organized.
Candidates without a pen and paper usually have only one or two questions. They forget the rest, which is a big mistake. If you don’t ask questions, it shows that you haven’t engaged with the company. It suggests:
My best interview as a candidate was when the potential new team tried to grill me. I sat alone in the middle of a circle of people. But since I had my notebook full of questions, I was able to turn the tables on them.
Good areas for questions include:
It might sound obvious, but it’s too often neglected:
In my experience, it’s rarely about finding someone with a specific skill set. It’s about finding the right mindset. Everything else can be taught. No one wants to work with (or keep) a brilliant developer who can’t collaborate, refuses to accept other opinions, and makes everyone else’s life miserable. So, what drives you? What do you need to thrive? What do you want to learn? How do you want to grow? Answer these questions for yourself and bring them up in the interview, even if you’re not asked.
Do you have questions or suggestions? Reach out to me on Twitter