10 Questions Hiring Managers Ask Tech Candidates — And the best ways to respond
Preparing for an upcoming interview? Are you anxious about not being able to answer all the interviewer’s questions?
Don’t worry. If you read this article, you’ll be one step ahead of the competition. Plus, the best way to fight your nerves is to prepare by studying the company and thinking about your answers in advance. It’s much better to be prepared than it is to wing it.
Start your research here, with the list of common interview questions (and answers) we’ve compiled below!
Interview Question #1
How did you learn to program and what is the first thing you programmed?
Interviewers aren’t just asking about which college or university you attended. And they’re not simply trying to gauge your skills, so don’t worry if your first program was really basic. There’s no need to lie about it and upsell yourself on this question.
Don’t be deceived by the simplicity of the question. Interviewers are trying to get a sense of how passionate you are about programming. They want you to go deeper and share how you felt in the moment when you wrote your first program. Talk about the thrill of turning letters, numbers, and symbols into something that works in the real world.
Interview Question #2
What are the most important qualities in a developer?
This question is designed to unveil how you feel about the position you’re interviewing for and the attitude you’ll bring to the job. Interviewers are looking for an answer that strikes a balance between technical, problem solving, and soft skills (e.g. communication).
Remember that technical skills are important, but the best developers can learn any new language quite easily. What’s more important is the ability and the willingness to solve problems. That’s what programming is all about.
But an effective programmer also needs to be a team player. Few software products are built by a single developer, so it’s important to be able to work collaboratively in a team environment. Great developers are keen problem solvers and are eager to use their skills and energy to move the entire team forward.
Finally, a great developer is constantly refreshing their skill set. Because technology trends change so quickly, interviewers are looking for candidates who can adapt to new programming languages, frameworks, and tools.
Interview Question #3
What are your favorite and least favorite technology products?
This question is designed to test your enthusiasm and your technical knowledge. Interviewers are also trying to understand your preferences and whether you like the hardware, operating system, and software the company uses.
It’s OK if you don’t. But don’t just say “I don’t like … because it sucks.” Be specific. Talk about the advantages and disadvantages of certain tools. Tell the interviewer what you admire about the products you love, whether it’s a rock-solid or sleek design, intuitive interface, or better functionality for advanced users.
You could also talk about the tools you use to write and debug applications. Be sure to tell the interviewer about tools you’ve tried in the past and the reasons why you prefer one over another.
If you’ve ever had the opportunity to make the case for adopting new technology at a previous job, now’s the time to mention it. Explain why there was a need for new tech and discuss your reasoning behind choosing a particular product over another.
This is your chance to show off your technical knowledge and insights. Don’t be shy — it’s OK to get passionate!
Interview Question #4
Can you tell me about a recent side project you’ve worked on?
Companies love to hire developers who have side projects because it shows that you actually enjoy coding and it’s a sign that you’ll take pride in your work. It also proves that you’re curious, a natural problem solver, and that you’ll keep your skills up-to-date.
Remember, problem solving is the most sought-after skill among developers. The best indicator of job performance is how much time developers spend working on new ideas and testing new technologies. Be sure to tell the interviewer what interests you about your side project and describe the problem you’re trying to solve.
Most companies want to hire someone who’s going to do more than clock in and clock out. If you have an account on GitHub or any other public code repository, now’s a good time to let the interviewer know. They’ll want to browse it later on to get a taste of what you’re capable of. If you can demo your product during the interview, that’s even better!
And, of course, if you’ve ever started your own company, be sure to talk in detail about your challenges and successes.
Interview Question #5
Have you ever failed to deliver a product on time?
This question isn’t a test to find out if you’ve ever failed. It’s a test to find out how you deal with tough situations.
Failure is inevitable, especially if you’re working in an innovative environment. Interviewers are looking for your ability to go through the process of trial and error. They want you to show them you can admit mistakes, learn from them, and continue moving forward with what you’ve learned.
The best developers are resilient and thrive in tough situations. They don’t give up or hide when mistakes are made. Be sure to talk about how you turned a bad situation into a positive situation. Demonstrate that you worked hard to resolve the issue or come up with an alternate solution rather than simply telling your boss or client that there’s no way to solve the problem.
Interview Question #6
What are some of the more interesting or challenging problems you’ve worked on?
Interviewers are trying to understand what you’ve been working on recently. They may ask follow-up questions and probe for details during your explanation to gauge your knowledge.
They also want to know about your problem-solving approach. Be sure to tell the interviewer how you solved problems step by step. Go beyond the requirements set out by your boss and dig deeper into how you defined priorities and worked to get things done on time.
Interview Question #7
How do you explain complex technology to non-technical people?
They might ask you how the internet works, for example.
While it might be tempting to go into details about IP addresses, packet switching, and DNS servers, try to keep it high-level. You could use a metaphor, for example, but you don’t have to. The key is that you’re able to communicate complex concepts clearly so non-technical people can understand them.
As a developer, you’ll work a lot with other developers. But you will also spend time with non-technical people in HR, marketing, sales, and other technical people with different specialties, so it’s critical to be able to communicate effectively in non-technical language.
Don’t use acronyms or coding jargon in your answer. Break down technical ideas into simple-to-understand concepts.
Interview Question #8
What management style do you respond most positively to?
This is a tricky question that is designed to get how self-aware you are about your working style and the kind of leadership you respect. They’re trying to understand what motivates you and pushes you to give your best effort.
There isn’t exactly a right answer. They might be trying to gauge whether your preferred leadership style matches their own. But they’re also gauging your self-awareness, so as long as your answer is honest and insightful, it should go over well with the interviewer.
This is also a chance to show you have leadership potential. Even if you aren’t applying for a leadership position, employers are always looking for leadership qualities that are important for delivering projects on time, such as motivation, positivity, the ability to communicate with team members, and organizational skills.
Interview Question #9
Have you tried our product or made an account on our website? Do you have any suggestions to improve the process?
Your answer to this question better start with “yes and yes”! Never go to an interview if you haven’t even tried the company’s product. That just shows that you’re not very interested in the work they do.
Interviewers are testing your ability to think like a builder, not just a regular user. They’re also trying to see how you respond under pressure. So be sure to think critically about the product beforehand and during the interview show off your ideas as if you’re coming up with them on the spot.
The interviewer might even ask if you have a plan for your first six months on the job, so be prepared for that. Your answer will show how much you understand the requirements of the position. Be sure to align your ambitions with the job description, but dig even deeper and talk about specific milestones you would like to hit along the way.
Interview Question #10
Is there anything I haven’t asked you about that you want to make sure I know?
This is your chance to tell the interviewer why you want the job. Don’t focus on your qualifications; focus on your motivations and aspirations and be sure to talk about how the company is a good match for you. Interviewers are looking for someone who’s passionate and excited about the prospect of working with them.
The worst answer possible is “I just need a job”. That may be true, but there must be more to it than that. Tell the interviewer what really makes you excited about working for the company.
And don’t talk about perks like free snacks and ping-pong tables. Focus on the actual work and the challenges you’re excited to help solve.
*Bonus* Interview Question #11
Where do you see yourself in five years?
This is one of the most common interview questions in any field, so it’s a good idea to think about your answer.
Do you plan to learn as many new languages and technologies as possible? Are you aiming for a project/product management position?, etc.
It’s OK if you don’t know exactly where you want to be in five years. The main thing is to show that you’ve thought about the question and have some drive in you.
Conclusion
Remember, interviewers aren’t solely interested in your coding skills. They’re trying to gauge your enthusiasm and whether you’d be a good fit for their company.
The best way to show you’re keen is to do your research beforehand. This article is a great start, but you should also spend time learning everything you can about the company. That knowledge will show that you’re genuinely interested.
Another thing to keep in mind is that interviewers always ask if you have any questions before concluding the interview. You should come prepared with questions to ask. Be careful not to focus too much on salary and benefits: ask thoughtful questions about the company and your potential role.
A Skill Validation Platform for programmers, by programmers!
At Indorse we offer free code reviews so that you can test your skills and improve them. You can simply submit your GitHub repo, or complete one of our coding assignments, and have your code reviewed by a panel of expert developers spread across the globe! 💃🕺
If you’re like Aleksandar, Liam or Kishore , and want to join our community of expert developers, then this is for you (click on Become a Validator 😁)!
