10 questions · with what-you're-learning

Reference check questions for Frontend Engineer

Tailored to the shape of frontend engineer work. Universal questions plus the 3 role-specific ones that surface the most useful signal for this hire.

Universal

Works for any role

  1. 1

    How do you know [Candidate] — what was your working relationship?

    What you're learning:Establishes context. Their boss has a different read than a peer; a direct report has yet another.

  2. 2

    What stood out about [Candidate]'s work?

    What you're learning:Lets them lead with strengths. Listen for specifics vs generics — vague answers are a flag.

  3. 3

    Where did [Candidate] struggle? Where did they need support?

    What you're learning:Every strong candidate has growth edges. A reference who says 'nothing' is a flag of its own.

  4. 4

    How did [Candidate] respond when they got hard feedback?

    What you're learning:Single best predictor of how they'll perform under stress and how they'll grow in the next role.

  5. 5

    Would you hire [Candidate] again, knowing what you know now? For what kind of role?

    What you're learning:The crown jewel of any reference check. The 'for what kind of role' qualifier is the truth-tell.

  6. 6

    What's the working environment where [Candidate] thrives best?

    What you're learning:Cross-check against your team's actual environment. If they need a structured boss and yours is hands-off, big risk.

  7. 7

    Is there anything I should be worried about going into this hire?

    What you're learning:The open-ended catch-all. Often produces the most useful single fact in the whole call.

Frontend Engineer specific

What to ask about a frontend engineer specifically

  1. 1

    How well did [Candidate] partner with designers?

    What you're learning:Frontend engineers who push back on designs make the product better — IF they do it constructively. Reference will know which side.

  2. 2

    How did [Candidate] handle accessibility + performance requirements?

    What you're learning:These bite teams 6 months in. References can confirm whether [Candidate] kept them in mind or had to be reminded.

  3. 3

    Did [Candidate] propose component-library improvements, or just consume what existed?

    What you're learning:Senior FE engineers shape the design system. Mid-level use it. Reference can tell you which level [Candidate] actually operated at.

Reference-check 3 candidates, not 30.

Raffi calls every frontend engineer applicant and ranks them. You only reference-check the top 3 — the ones you're actually about to hire. $25 starter credit.

Hire a frontend engineer with Raffi →Interview questions for frontend engineer

Reference questions for other roles