Navigating frontend interviews in 2022: onsite interview — behavioral

By Mike Chen

The behavioral interview is conducted by other engineers or people that work closely with engineers. The goal is to assess whether you handle tough situations in a way that’s consistent with company culture.

This is the fourth post in a series about what to expect from the frontend interview process in 2022. Here’s where we are in this series:

  1. Overview and reverse interviewing
  2. Researching your company
  3. Informational phone screen
  4. The onsite interview — live coding challenge
  5. The onsite interview — behavioral
  6. The onsite interview — systems design
  7. Offer and negotiation

Behavioral interviews are typically geared towards mid-level or senior engineers, but you may encounter them early on in your career.

The company’s goal with behavioral interviews is to assess:

  1. How you resolve conflict or differences of opinion
  2. What your communication style is like
  3. Whether you’re an empathetic person
  4. Whether you can explain technical concepts to less technical people

General tips

1. Understand the culture

Look for a vision/values/culture page on your company’s website. If it’s there, make sure you read it.

If they have a detailed page that a designer clearly put thought into (e.g. Netflix, Airbnb, Amazon), culture is extremely important to them. Don’t just read: memorize this page.

Tie these values into your answers at every opportunity.

2. Don’t use hypotheticals

People want to hear about your concrete experience. Avoid saying things like “I would” do this or that. Even if your interviewer doesn't challenge you on this type of speculation, they’ll dismiss your answers as fluff.

Many people swear by the STAR framework. Following this framework keeps your answers anchored in past behavior.

3. Reflect on conflict

In our experience, interviewers are particularly interested in how you deal with conflict. Prepare several examples of how you dealt handled disagreement with coworkers.

4. Keep it brief

Don't talk for more than 90-120 seconds at a time. If you find yourself going deep on a topic, pause and offer to go on if the interviewer wants to hear more.

5. Pay attention to job title

The interviewer's job title provides critical guidance as to what they're looking for, even if they ask generic questions.

  • Product managers want to hear you tie your work to business outcomes
  • Designers want to hear that you care about shipping pixel perfect designs
  • Other engineers want to hear that you make good decisions and are easy to work with

Example questions

The specific questions you'll get asked will vary depending on which function(s) you're talking to. Here are a few examples:

Product managers

  1. How have you worked with product managers in the past? How have you resolved disagreements with them?
  2. Tell me about the last time you missed a deadline. How did you communicate it? How did you mitigate the negative impact?
  3. What project management methodologies have you worked with before (e.g. Scrum/Agile, waterfall)? What did you like or dislike about them?


  1. Design and engineering can be at odds with one another, with designers proposing ideas that may not be performant, accessible, or easy to implement. How do you weigh trade-offs between achieving fidelity with the designs and technical constraints?
  2. Tell me about the process of working with designers in your current role. What does the communication cadence look like? Who does what in the relationship?
  3. Have you enjoyed working with designers in the past?
  4. Tell me about the pros and cons of design systems. Have you worked with them in the past? What did you like about them?
  5. Tell me about some websites or apps that you feel are particularly well-designed. What makes them well-designed?

Other engineers

  1. What makes for an effective code review?
  2. What's your preferred method for aligning with your team on controversial decisions (e.g. adopting a new tool, library, or coding standard)? What's worked particularly well for you?
  3. How do you approach disagreement with other engineers? What are the right avenues to communicate your disagreement?
  4. What's your favorite/least favorite thing about being an engineer?
  5. What are the immediate steps you would take when you're notified of a critical issue in production?
  6. When you launch a new feature, how do you ensure it continues to work as intended?

What’s next?

In the next post, we’ll take a brief look at systems design interviews. Follow @frontendeval and stay tuned for more!

Get future questions delivered straight to your inbox for free

Sign up and receive instant access to new questions when we publish them.

We‘ll only use your information to deliver new questions and to provide you updates about our product. We‘ll never spam you or sell your information without your consent. Unsubscribe at any time.