Two people working in an office environment and talking.
Graphic that shows three different types of interview questions you should be asking.

Use these questions to identify a candidate’s technical knowledge and abilities

Use these questions to determine how a candidate handled situations in the past

Use these questions to assess a candidate’s personal traits and cognitive skills

Why this matters:

Depending on the candidate’s level of experience, the number and the types of programming languages they know should increase with time in the field. While an ideal candidate does not have to be an expert in every language, they should have experience with at least a few to succeed in the day-to-day work of the role.

What to listen for:

  • Candidates should have a baseline knowledge or experience with languages like PHP, Python, Ruby, Java, .NET, and JavaScript.
  • Look for indications the candidate is eager to learn new skills and is actively working on development.

Why this matters:

This technical question tests the candidate’s understanding of a widely used programming language. While technical knowledge is essential, it’s the latter part of the question that can help you determine their approach to building a website—and whether or not they’re a good fit for your company.

What to listen for:

  • Answers should demonstrate a thorough understanding of this important programming language and its use cases.
  • Strong candidates will avoid jargon and use simple descriptions to ensure they get their point across.

Why this matters:

This question will help you gauge the candidate’s awareness of the industry, as well as their appreciation for the nuances of application development. They are most likely thinking like a developer when they look at other apps, and their answer can give insight into their values when it comes to functionality.

What to listen for:

  • Listen for specific development concepts like user experience, load times, and navigation.
  • Candidates should demonstrate inspiration and motivation to constantly improve.

Why this matters:

How the candidate responds will give you a glimpse into their development process and working style. It will provide insight into the kind of projects they enjoy much and whether your role will provide them with similar opportunities. You will also get a look into where their passions lie.

What to listen for:

  • A strong answer will detail the candidate’s inspiration and specific examples of why they enjoy that type of work so much.
  • Look for indications they are truly passionate about their work—smiling, laughter, and enthusiastic hand gestures all point toward someone who loves what they do.

Why this matters:

Every back end developer will encounter a piece of broken code or a bug in their system. These obstacles are inherent to their work. The candidate’s answer will help you understand how the candidate solves problems. Are they inspired to work until it’s fixed? Did they ask for help?

What to listen for:

  • Look for enthusiasm for taking on challenges and problem-solving skills.
  • Probe for a detailed answer involving steps taken and final results.
  • Look for a positive attitude and reactions that show patience.

Why this matters:

User experience and design can be subjective. Whether shared by a colleague, client, or user, criticism is inevitable in this role, and they must be comfortable with that. An ideal candidate will face the situation with professionalism and open mind, looking for opportunities to improve.

What to listen for:

  • Signs of annoyance or frustration may indicate the candidate doesn’t receive feedback well.
  • A strong answer will detail the circumstances, feedback, and approach to find a solution.

Why this matters:

This question helps you see whether the candidate prefers to work independently or as part of a team. Both preferences are valid, but you’ll want to be sure their working style fits your work environment. If they prefer to work on their own, you may want to ask how they feel about teamwork.

What to listen for:

  • If they prefer to work independently, ask how they handle collaborative scenarios.
  • Strong answers will focus on the need for teamwork and agility, as there are often many developers working on a project.

Why this matters:

Some developers have a passion for the craft and intend to stick with it long term. Others see the role as a springboard for bigger things in the future. Either job outlook is understandable, but their preference will show how thoughtful and reflective they are in their approach to their chosen career.

What to listen for:

  • Look for answers that align with the values your company stands for.
  • There’s no wrong answer, but good responses may highlight traits like leadership, growth, or passion.

Why this matters:

Web development is a rapidly changing industry. Technology that thrives one year can become obsolete the next. In order to keep up with the changes, back end developers must have a commitment to continuous learning to ensure their skills don’t become outdated.

What to listen for:

  • Passionate and dedicated back end developers discuss their favorite tools, designers, thought leaders, blogs, and more.
  • Strong answers will include current participation in classes to update their skills.