Loading...
Please sign in to view your progress
Engineering manager interviews: people, execution, system design and behavioral. Train with Coach Leo, then take a mock with Daniel.
| # | Name | ||
|---|---|---|---|
1 | The EM Role and the Loop Document | ||
2 | ![]() | What does an engineering manager actually own, how does the loop score you, and what makes a
story read a level up? Tap to predict in Leo's 3D team lab, see a manager's seat among
partners, fix an unfair on-call rota, then practise two answers out loud with feedback: why
management, and the skills of an EM.
| |
3 | Story Bank and Leadership Style Document | ||
4 | ![]() | Turn your experience into answers that hold up. Watch a story bank leak and get fixed on a 3D
funnel, see why a leadership style lives in the action, pick the right move for four
engineers in Leo's 3D lab, then practise two answers out loud with feedback: tell me about
yourself, and your leadership style.
| |
5 | ![]() | The leadership-style round of an EM loop with Daniel, an engineering director. Introduce
yourself, then say what your style is and prove it with your own stories as he digs into the
details, asks how it would work on his team, and throws a curveball. Written report after.
| |
6 | One-on-Ones and Coaching Document | ||
7 | ![]() | Run 1:1s that people actually use. Read a team on skill and will in Leo's 3D lab, predict how
to coach an engineer who has gone flat, watch a growth plan hit a checkpoint and adjust, then
play the manager when an engineer says they're bored. Practise real loop answers with feedback
and a retry.
| |
8 | ![]() | The people round of an EM loop with Daniel, an engineering director. How do you run 1:1s and
grow your engineers? Hold up as he digs into your stories and your span of control, then handle
a report who says she's bored. Written report after.
| |
9 | Inheriting a Team Document | ||
10 | ![]() | Take over a team you did not build. Map the room in Leo's 3D lab, win over the engineer who
applied for your job, own a slipped promise, rank the team's real risks and lay out your first
ninety days. Practise two real loop answers with feedback and a retry.
| |
11 | ![]() | A leadership round of an EM loop with Daniel, an engineering director. You inherit a
struggling team of eight: what do you do in your first ninety days? Hold up as he digs into your
plan and reveals your strongest engineer has an offer. Then tell him about the best and worst team
you have been on. Written report after.
| |
12 | Performance Document | ||
13 | ![]() | Handle an underperformer fairly. Watch an engineer's bubble move on Leo's 3D talent map as
support lands, run a plan that is a real chance, exit someone with dignity, look after your
stars, and play the manager in the first hard conversation. Practise a real loop answer with
feedback and a retry.
| |
14 | ![]() | The people round of an EM loop with Daniel, an engineering director. How do you handle an
underperformer? Hold up as he escalates: no improvement, burnout, your tech lead, a role being cut.
Then tell him how you manage high performers. Written report after.
| |
15 | Hiring and Building a High-Performing Team Document | ||
16 | ![]() | Grow a team from four to twelve. Read a hiring funnel against its plan in Leo's 3D lab, predict
where it leaks, write the bar, run a debrief that is not a vote, see why output dips before it
climbs, and pace the hires in waves. Answer two real loop questions out loud with feedback and
a retry.
| |
17 | ![]() | A people-and-execution round with Daniel, an engineering director. Your team of four has
approval for eight hires in two quarters: how do you do it? Hold up as he digs into your loop,
your offers and your plan, then cuts the headcount. Then tell him about the best engineer you
ever hired. Written report after.
| |
18 | Execution and Delivery Document | ||
19 | ![]() | Catch the slip before it catches you. Predict what sets a launch date in Leo's 3D team lab,
watch a late task push the plan, test whether adding people helps, then practise setting up a
project and telling a VP the date will slip: with options, in a role-play, with feedback.
| |
20 | ![]() | The execution round of an engineering manager loop with Daniel, an engineering director.
Your team will miss a committed launch by three weeks: what do you do? Hold up as he digs into
your forecast, options and team, then asks you to add people and keep the date. Then tell him
about a late-project message you delivered. Written report after.
| |
21 | Tech Debt and Priorities Document | ||
22 | ![]() | Stop saying "the code is messy." Put the cost in pages, hours and lead time in Leo's 3D lab,
pick the first fix on a value-by-effort map, divide a quarter between features and debt, say
no with options, and give a big customer an honest phased yes. Two real loop answers with
feedback.
| |
23 | ![]() | The prioritization round of an engineering manager loop with Daniel, an engineering director.
Product wants three features and your on-call is burning: what do you do? Hold up as he digs
into your numbers, your plan and your team, then tells you the CEO promised a customer the
third feature. Then a trade-off story. Written report after.
| |
24 | Goals, OKRs and Measuring Impact Document | ||
25 | ![]() | Set a team's goals and show what you did. Pick bets from a company priority in Leo's 3D lab,
spot the key result that is really an output, write an OKR, handle a week-six slip, see how a
measure gets gamed, and build your own impact story. Answer two real loop questions out loud
with feedback and a retry.
| |
26 | ![]() | A goals-and-impact round with Daniel, an engineering director. Write next quarter's OKRs for a
ticket marketplace's checkout team, then hold up as he digs into your key results, your
capacity and a partner team's slip. Then tell him how you measure your impact as a manager.
Written report after.
| |
27 | Cross-Functional Work Document | ||
28 | ![]() | Bring your team's concern to a partner in their terms. Map a launch's partners in Leo's 3D lab,
win over a skeptical PM, see why adding engineers doesn't save a date, write a one-page decision
doc and escalate without a complaint. Practise three real loop answers with feedback and a retry.
| |
29 | ![]() | The cross-functional round of an engineering manager loop with Daniel, an engineering director.
Your tech lead and your PM disagree about scope a week before launch: what do you do? Hold up as
he presses on your plan and then changes the situation. Then tell him about a difficult
stakeholder. Written report after.
| |
30 | Hard Conversations Document | ||
31 | ![]() | Say the hard thing well. Watch a project lead walk from skeptic to supporter as you tell her the
project is cancelled, plan a layoff day with HR and legal, and learn what never to say. Rehearse
the conversation with Leo playing the engineer, then practise two real loop answers with feedback
and a retry.
| |
32 | ![]() | The hard-conversations round of an engineering manager loop with Daniel, an engineering director.
Your VP has told you a project your team loves is cancelled: how do you tell them? Hold up as he
presses on the order, your words and the aftermath, and then tests your honesty. Then tell him
about a conflict on your team. Written report after.
| |
33 | Project Retrospective Document | ||
34 | ![]() | A project deep dive is won on the follow-ups. Pick the project, tell it with your decisions in
front, draw the system at a manager's altitude, defend a result with a comparison, and say what
you would change. Practise your own project out loud with Leo's feedback and a retry.
| |
35 | ![]() | The project deep dive from a manager loop, with Daniel, an engineering director who goes deep.
Walk him through the most complex project you led and hold up as he digs into your decisions,
the system, your people and your numbers. Then a time you changed direction, and which of your
projects fits his team. Written report after.
| |
36 | The System Design Round Document | ||
37 | ![]() | Draw the system, then run it. In Leo's 3D lab, break a naive design, fix it, kill the control
plane on purpose, give every box an owner, phase a fourteen-week plan and pick the risk to
fix first. Then practise the manager's half of the round: staffing, shipping and the pager.
| |
38 | ![]() | The system design round of an engineering manager loop with Daniel, an engineering director.
Design a notification service for a marketplace, then say how you would staff and ship it.
He digs into numbers, failure and on-call, then cuts your team from eight to six. Then a team
architecture decision. Written report after.
| |
39 | ![]() | How does a system design round actually run, and what gets written on the scorecard?
Learn the four steps and where the minutes go, the five signals interviewers grade,
then scope a real prompt with Nora playing the interviewer: you ask the questions, write
the requirements, pick the deep dive and land the wrap-up.
| |
40 | Behavioral Ownership Document | ||
41 | ![]() | Behavioral rounds decide your level. Learn what each question is really scoring, tell a failure
story that owns its part, show scope, ambiguity and impact beyond your team, find the gap in your
story bank, and write a sixty-second "why us". Practise your own stories out loud with Leo's
feedback and a retry.
| |
42 | ![]() | The ownership round of a manager loop, with Daniel, an engineering director who goes deep. Tell him
about a time you failed as a people manager and hold up as he digs into what you saw, what it cost
and what you do now. Then a judgment call and why you want to work there. Written report after.
| |
43 | Leading a Team That Uses AI Coding Assistants Document | ||
44 | ![]() | Lead a team through AI coding assistants. Pilot on typical teams in Leo's 3D lab, hold a wave
when rework climbs, rank the security and review risks, measure speed and quality together, and
protect your juniors. Sketch a rollout plan and answer two real loop questions out loud with
feedback and a retry.
| |
45 | ![]() | A leadership-judgment round with Daniel, an engineering director. Leadership wants a thirty
percent productivity lift from AI coding tools: plan the rollout and how you'll measure it. Hold
up as he digs into your pilot, your numbers and your juniors, then reveals a security finding.
Then tell him about introducing something new to a team. Written report after.
| |
46 | ![]() | The whole EM onsite in one sitting. Daniel plays four interviewers: a hiring manager who keeps
asking "and then what did you do?", a peer manager with a slipping launch, a VP who wants your
hardest project in detail, and a staff engineer with a quick design question. Real follow-ups,
two curveballs, and a hiring report on all four rounds.
| |