5a. Designing the interview loop

5a. Designing the interview loop

A well-designed interview loop serves two purposes: (1) it gives you a clean signal on the candidate’s skill and values and (2) it gives the candidate confidence in your team and approach to team building.

Below are a few best practices to help you design a thoughtful interview loop that’s specific to your team. These best practices are from Viet Nguyen, our Head of Customer Talent Advisory. His team advises hundreds of Gem customers on how to recruit effectively. Prior to Gem, Viet spent the past 5 years in recruiting leadership at a number of great startups, including One Medical where he led tech recruiting.

Feedback? Suggestions? Ideas? Comment directly, suggest edits, or email steve@gem.com and viet@gem.com 

High-level best practices

  • Do the research and define what you need. It’s difficult to make a hiring decision if you don’t know what you’re looking for. It’s even harder for others to help you evaluate candidates if you’re not able to articulate what you’re looking for. If you don’t take the time to document what you’re looking for, you’ll be shooting for a constantly moving target.
  • Design an interview loop that’s representative of your team’s values. If your team is practical, creative, and/or collaborative make sure you use your interview loop to highlight that for candidates.
  • Evaluate the whole person. As you’re defining what you’re looking for, make sure to include all the skills and personality traits required to be successful and an interview loop incorporates ways to assess these qualifications.
  • Know how you’re going to evaluate the results. Similar to designing an experiment, you need key performance indicators (“KPIs”) to objectively measure successes and failures.

Define what you need

It’s important to take the time to define what you’re looking for before you start recruiting for a number of reasons:

If you’ve never hired for a role or hired in-general before, the best way to develop the necessary context is to leverage your network. We suggest identifying 5-10 experts — people who have hired for the role before or people who are currently/previously in the role and learn as much as you can from them. Another option is to leverage your investors to make introductions to experts from their networks.

Your interview loop will say something about you

We’ve all been through interviews where the interview has nothing to do with the job. This is often the by-product of either (1) not knowing any better or (2) not having the time to do better.

Design the interview loop to sell candidates on your team’s culture and values. At Gem, we care deeply about practicality and collaboration. So rather than doing a standard set of whiteboarding engineering interviews, we decided to go with something more bespoke to Gem.

Our onsite interview is a 1-2 day event where engineering candidates spend time working on a project with another engineer on the team. When we were building the founding team, candidates did this interview with the founders.

This interview structure allows us to evaluate and showcase what we care about — practicality and collaboration. To see exactly how we did this, check out


Know what you’re looking for

It’s imperative that you take the time to write down what you’re looking for before you design the interview process. This list of hard skills and personality traits will guide you on how to design the interview process. Having a reasonably well-defined list will make it easier for you to crowdsource ideas from your network on how to evaluate the respective skills.

If you’re able to at least answer the following questions, you’ll be in good shape. Let’s call this your Spec doc.

  1. What are the 2-3 personality traits (e.g. collaboration) we care about?
  2. What are the 2-3 hard skills (e.g. expert in Machine Learning) we care about for this role?
  3. Are there any experiences we require for the job (e.g. experience working on small, nimble teams)

We suggest 2-3 because you don’t want an exhaustive wish list as opposed to a list of requirements. Coming up with 2-3 items will also force you to ruthlessly prioritize the things that are important.

Extra Credit: Define the bar or what ‘good’ vs. ‘great’ look like. If you’re able to define these things, it will make debriefs a lot more structured.

Building the Interview Loop

You’ll typically see candidates through 5 or 6 stages. For example:

1. Initial Sell Conversation

Goal of this section is to sell the candidate on the opportunity. You can learn more about the


2. Remote Screen #1

The first remote screen tends to focus on the candidate’s background, experiences, and any particular personality traits you’re looking to evaluate. This is where you will want to dig deep into the candidate’s motivations and the personality traits from your Spec doc.

Sometimes founders and hiring managers have a hard time pivoting from the sell conversation to the first screen. Proper framing really helps here — “Up until this point, our time has been focused on us sharing information with you. If it’s OK with you, I’m going to shift gears and start getting to know you a little bit. Sound good? I have a few standard questions I’d like to go through to get to know you better.”

3. Remote Screen #2

This second screen tends to focus on technical or practical skills. This interview should map to the hard skills in your Spec doc.

For engineers, this is your standard coding screen. For Sales candidates, you might have them role-play their current product demo. For Design, you might have the candidate for a portfolio review.

This interview is important because it’s the first time you’re evaluating the baseline skills required to do the job. If this interview isn’t properly designed, you will end up wasting everyone’s time bringing non-qualified candidates onsite.

4. Onsite Interview

In previous interviews, you were able to get a broad view on the candidate’s hard skills and personality traits. The Onsite Interview will be used to dive deep into each of these areas. We suggest choosing 3-4 focus areas from your Spec doc that you care the most about and/or feel like you’ve gotten the least amount of signal.

5. Offer

To make a decision on whether to extend an offer, you’ll run a debrief. You’ll also do a mix of formal and back-channel references.

Remember to design a thoughtful interview loop that is representative of your team.

Pro-tip: Ask candidates for feedback on your interview process and continuously iterate.

Run an interview pre-brief

Once the interview panel is defined, it is critical to get all of your interviewers together for a pre-brief to align on the role, so everyone’s prepared and knows what they’re looking for.

Your goal with the pre-brief is to make sure everyone understands:

  • A high-level overview of the role.
  • Which focus areas each interviewer is responsible for.
  • How they’re going to evaluate each focus area, including specific questions and what “good” looks like.

Without a pre-brief, you run the risk of interviewers missing an important focus area, or asking the wrong questions, or asking duplicative questions, which can lead to the wrong signal or lack of signal and waste lots of time.

As part of the pre-brief, we also recommend creating a slack channel for every interviewer on your loop to make it easy to coordinate on candidates, debriefs, and the loop itself (especially if you’re remote). At Gem, we have eng-hiring, design-hiring, product-hiring, etc.

Next Steps

Back ← Back to home here ← 5. How to interview here
Next Up → 5b. Best practices for interviewers here → Skip ahead to selling & closing here

Feedback? Suggestions? Ideas? Comment directly or email steve@gem.com