Questions you need to ask as a developer in a job interview!
In almost every job interview, the candidate is inevitably asked if they have any questions. Most of us say no, which is very often the wrong strategy. Here are three questions every developer should ask in their job interview. You're more likely to get the best answers from leads or technical project managers, HR leaders may not have all the answers.
How does the company deal with bugs?
Every developer knows that a large part of his job consists of creating and fixing bugs.
How companies deal with bugs is a separate chapter. If there are any debugging techniques you prefer, you should learn about them during the interview. This opens the door for you to learn more about the company's debugging process. Is there a dedicated QA system, are you responsible for the bugs you have produced yourself, or do you only enter them as a JIRA ticket?
Other questions to consider in this context are: Are many tests written in development? What monitoring systems are there? These answers not only give you an insight into the company's QA process, but also shed light on part of the day-to-day operations. If the company uses a system that you personally aren't a big fan of, at least you're forewarned.
How can I introduce myself to the team?
One of the most important questions is who you will work with: How many members does the team consist of? Are all colleagues senior developers? Is it a “diverse team”? If it's a large team, are there subgroups of developers working on different projects? Do the teams also change? What collaboration techniques are being used within teams and across the organization?
You might also want to learn more about career advancement opportunities. Does the company offer you good development opportunities? Do junior developers have a chance to grow and thrive? Even if you're not a junior developer anymore, this question is important: You can't climb the corporate ladder if nobody is able or willing to take your place.
Where and when do I have to work?
Most of us have to commute to the office every day, although that's not always optimal. It is therefore worth asking during the interview whether there is the possibility of working remotely. If yes, what are the guidelines? Do many employees use this option? Are these also available during the weekend or in the evening? Are flexible working time models also offered?
A good work-life balance is important and you should be in a position to have one. With that in mind, it's good to know when and where you need to work.
Conclusion
With these questions you will learn more about your future team, the company structure, the daily workload and development opportunities. If you don't get the answers you expect, this is still a good time to end the application process. It's always better to learn all about a company before you start working there.
