winkle
Back

Interview · Behavioural

Engineering manager

Covers performance, hiring, team design, on-call, delivery, prioritisation, technical decisions and incidents through real past experience. Suits senior managers and heads of engineering. Follow-ups push for what the candidate personally did, what they would change and how they knew it worked.

Suits: Engineering manager, Software engineering manager, Head of engineering, Engineering lead

Questions
7 of 18
Length
35 min
Format
Voice or typed
Levels
Senior to Staff
See this interview on a 30-minute call.
AI interviewerScored
Example
  1. Interviewer: Tell me about a time you changed someone's mind at work. How did you go about it?

  2. Candidate: Our team wanted to rebuild the billing page from scratch, and I thought it was the wrong call, so we put together a plan to…

  3. Follow-up

    Interviewer: You said "we". What did you say yourself, and what finally changed their mind?

  4. Scored on

    • People leadership30%
    • Delivery and prioritisation25%
    • Judgement and decisions25%
    • Communication and influence20%

    Score, reasons and recording. Your team decides.

An example exchange. This interview's own questions open when you use it.

What it listens for, and how much each part counts.

Every answer is scored against this guide, with the reasoning written beside the score. You get the recording or the written answers too, and your team makes the call.

  • People leadership30%
    Coaches, hires and handles performance fairly and directly.
  • Delivery and prioritisation25%
    Gets reliable delivery and balances features with health.
  • Judgement and decisions25%
    Makes and owns hard calls with evidence.
  • Communication and influence20%
    Works upward and across teams with honesty.
All interviews
  • Coding interview: problem solving

    Engineering · Technical

    Four classic problems, solved in words, that show how a candidate reasons about correctness and cost.

    Listens for

    • Problem understanding
    • Approach and correctness
    • Edge cases
    • Complexity reasoning
    Typed

    4 of 18 questions · 35 min · All levels

  • System design: backend

    Engineering · System design

    One notification service at burst scale, designed stage by stage to test estimates, scaling and failure.

    Listens for

    • Requirements and estimation
    • API and data design
    • Scale and throughput
    • Reliability
    • Trade-off judgement
    Voice or typed

    7 stages · 50 min · Senior to Staff

  • Frontend engineering deep-dive

    Engineering · Technical

    Tests real frontend judgement: performance on weak devices, state, accessibility, rendering and debugging.

    Listens for

    • Performance
    • Architecture and state
    • Accessibility
    • Debugging
    • Trade-offs and communication
    Voice or typed

    5 of 16 questions · 25 min · Mid to Staff