Interview Gym

walk me throughtell me about a timewhy this rolewhat would you dohow did you measure itwhat went wrongwho disagreedwhat did it costwhat would you changewhere were you wronghow do you knowwhat happened nextwhy not the obviouswhat did you tradehow would you scale itwhat did you learnwhat would you do differentlywho else was involvedhow did you decidewhat did you assumewhat broke firsthow do you prioritisewhat did you shipwhere did it failhow would you explain itwhat did you cutwho pushed backwhat was the trade-offhow did you prove itwhat did it changewhat would you do firsthow do you know it workedwhat was the hardest partwhat would break at scalehow did you handle pushbackwhat did you not knowwho did you askwhat did the data sayhow long did it takewhat did you get wrongwhat did you ownwhat did you hand overhow did you hirewhat did you say no tohow did you sequence itwhat did the customer wantwhat went unspokenhow did you de-risk itwhat did you documenthow did you recoverwhat would you do with more timewhat did you automatewhat did you stop doinghow did you measure successwhat did the numbers misswho owned the outcomehow did you get buy-inwhat was the constraintwhat did you trade awayhow did you find the causewhat did you test firstwhat did you assume was truehow did the plan changewhat did you learn laterwhat would you repeatwhat did you refusehow did you split the workwhat surprised youwhat did you simplifyhow did you know when to stopwhat did it cost the teamwhat would you tell a new joinerwhat did you buildhow did you know it was rightwhat did you measure firstwho was the customerwhat did they actually needhow did you find outwhat did you do about ithow did you keep it runningwhat did you breakhow did you fix itwhat did it cost youhow did you justify itwhat did you give uphow did you decide the orderwhat did you leave outhow did you test itwhat did you monitorhow did you know it was livewhat did the team sayhow did you bring them alongwhat did you overrulewhere did you compromisehow did you recover trustwhat did you say to the customerhow did you handle the delaywhat did you do when it failedhow did you scope itwhat did you estimatehow wrong was the estimatehow did you plan the workwhat did you promisewhat did you deliverwhat slippedhow did you handle the pressurewhat did you learn from ithow would you do it againwhat would you automate nextwhat would you removehow do you keep it simplewhat is the riskhow would you spot it earlywhat would you tell your managerhow do you handle disagreementwhat did you change your mind aboutwho did you learn fromhow did you grow the teamwhat did you delegatewhat did you keephow did you measure the peoplewhat did you do lastwhere did the time gowhat was the real problemhow did you find itwhat did the first version look likewhat did you throw awayhow did you decide what to cutwhat did the second version fixhow did you know it was donewhat did you ship firstwhat did the users sayhow did you handle the feedbackwhat did you refuse to buildhow did you say nowhat did you trade for speedhow did you keep qualitywhat did you reviewhow did you catch the bugwhat did you do differentlywhat surprised the teamhow did you communicate itwhat did the numbers showhow did you know you were rightwhat did you doubthow did you check yourselfwhat would you ask mewhat do you want to knowhow did you know it matteredwalk me throughtell me about a timewhy this rolewhat would you dohow did you measure itwhat went wrongwho disagreedwhat did it costwhat would you changewhere were you wronghow do you knowwhat happened nextwhy not the obviouswhat did you tradehow would you scale itwhat did you learnwhat would you do differentlywho else was involvedhow did you decidewhat did you assumewhat broke firsthow do you prioritisewhat did you shipwhere did it failhow would you explain itwhat did you cutwho pushed backwhat was the trade-offhow did you prove itwhat did it changewhat would you do firsthow do you know it workedwhat was the hardest partwhat would break at scalehow did you handle pushbackwhat did you not knowwho did you askwhat did the data sayhow long did it takewhat did you get wrongwhat did you ownwhat did you hand overhow did you hirewhat did you say no tohow did you sequence itwhat did the customer wantwhat went unspokenhow did you de-risk itwhat did you documenthow did you recoverwhat would you do with more timewhat did you automatewhat did you stop doinghow did you measure successwhat did the numbers misswho owned the outcomehow did you get buy-inwhat was the constraintwhat did you trade awayhow did you find the causewhat did you test firstwhat did you assume was truehow did the plan changewhat did you learn laterwhat would you repeatwhat did you refusehow did you split the workwhat surprised youwhat did you simplifyhow did you know when to stopwhat did it cost the teamwhat would you tell a new joinerwhat did you buildhow did you know it was rightwhat did you measure firstwho was the customerwhat did they actually needhow did you find outwhat did you do about ithow did you keep it runningwhat did you breakhow did you fix itwhat did it cost youhow did you justify itwhat did you give uphow did you decide the orderwhat did you leave outhow did you test itwhat did you monitorhow did you know it was livewhat did the team sayhow did you bring them alongwhat did you overrulewhere did you compromisehow did you recover trustwhat did you say to the customerhow did you handle the delaywhat did you do when it failedhow did you scope itwhat did you estimatehow wrong was the estimatehow did you plan the workwhat did you promisewhat did you deliverwhat slippedhow did you handle the pressurewhat did you learn from ithow would you do it againwhat would you automate nextwhat would you removehow do you keep it simplewhat is the riskhow would you spot it earlywhat would you tell your managerhow do you handle disagreementwhat did you change your mind aboutwho did you learn fromhow did you grow the teamwhat did you delegatewhat did you keephow did you measure the peoplewhat did you do lastwhere did the time gowhat was the real problemhow did you find itwhat did the first version look likewhat did you throw awayhow did you decide what to cutwhat did the second version fixhow did you know it was donewhat did you ship firstwhat did the users sayhow did you handle the feedbackwhat did you refuse to buildhow did you say nowhat did you trade for speedhow did you keep qualitywhat did you reviewhow did you catch the bugwhat did you do differentlywhat surprised the teamhow did you communicate itwhat did the numbers showhow did you know you were rightwhat did you doubthow did you check yourselfwhat would you ask mewhat do you want to knowhow did you know it matteredwalk me throughtell me about a timewhy this rolewhat would you dohow did you measure itwhat went wrongwho disagreedwhat did it costwhat would you changewhere were you wronghow do you knowwhat happened nextwhy not the obviouswhat did you tradehow would you scale itwhat did you learnwhat would you do differentlywho else was involvedhow did you decidewhat did you assumewhat broke firsthow do you prioritisewhat did you shipwhere did it failhow would you explain itwhat did you cutwho pushed backwhat was the trade-offhow did you prove itwhat did it changewhat would you do firsthow do you know it workedwhat was the hardest partwhat would break at scalehow did you handle pushbackwhat did you not knowwho did you askwhat did the data sayhow long did it takewhat did you get wrongwhat did you ownwhat did you hand overhow did you hirewhat did you say no tohow did you sequence itwhat did the customer wantwhat went unspokenhow did you de-risk itwhat did you documenthow did you recoverwhat would you do with more timewhat did you automatewhat did you stop doinghow did you measure successwhat did the numbers misswho owned the outcomehow did you get buy-inwhat was the constraintwhat did you trade awayhow did you find the causewhat did you test firstwhat did you assume was truehow did the plan changewhat did you learn laterwhat would you repeatwhat did you refusehow did you split the workwhat surprised youwhat did you simplifyhow did you know when to stopwhat did it cost the teamwhat would you tell a new joinerwhat did you buildhow did you know it was rightwhat did you measure firstwho was the customerwhat did they actually needhow did you find outwhat did you do about ithow did you keep it runningwhat did you breakhow did you fix itwhat did it cost youhow did you justify itwhat did you give uphow did you decide the orderwhat did you leave outhow did you test itwhat did you monitorhow did you know it was livewhat did the team sayhow did you bring them alongwhat did you overrulewhere did you compromisehow did you recover trustwhat did you say to the customerhow did you handle the delaywhat did you do when it failedhow did you scope itwhat did you estimatehow wrong was the estimatehow did you plan the workwhat did you promisewhat did you deliverwhat slippedhow did you handle the pressurewhat did you learn from ithow would you do it againwhat would you automate nextwhat would you removehow do you keep it simplewhat is the riskhow would you spot it earlywhat would you tell your managerhow do you handle disagreementwhat did you change your mind aboutwho did you learn fromhow did you grow the teamwhat did you delegatewhat did you keephow did you measure the peoplewhat did you do lastwhere did the time gowhat was the real problemhow did you find itwhat did the first version look likewhat did you throw awayhow did you decide what to cutwhat did the second version fixhow did you know it was donewhat did you ship firstwhat did the users sayhow did you handle the feedbackwhat did you refuse to buildhow did you say nowhat did you trade for speedhow did you keep qualitywhat did you reviewhow did you catch the bugwhat did you do differentlywhat surprised the teamhow did you communicate itwhat did the numbers showhow did you know you were rightwhat did you doubthow did you check yourselfwhat would you ask mewhat do you want to knowhow did you know it mattered

Walk in already knowing what they will ask.

Generic prep is guessing, and a better resume does not answer the question. Paste the posting: know what they will ask, what to study first, and how to answer.

See how it works →

50 credits a month, no card. Enough for a posting read and several rehearsals.

What happens after you paste

WHERE THIS POSTING IS

Posting read6 requirements, each quoted
Company researchedTheir process, their stack
Plan written4 phases · 12 modules
Mock interview graded5 scores · 74

JOB POSTING

Senior Backend Engineer · Acme Corp · Remote (EU)
We are hiring a senior backend engineer to own our payments ledger service end to end. 5+ years of production Go. You have operated services on Kubernetes. You will lead incident response for payment-path outages.

Graded on the five things a real interview grades

Practising alone tells you nothing. Every answer comes back scored, with the reasons, on the five things an interviewer actually weighs.

Structure & narrative

Technical depth

Specificity & evidence

Communication

Role fit

DO THE MATH

What is the wait costing you?

Move the numbers until you believe them. The arithmetic is division, and the one assumption about how much preparation helps is yours to set - not ours to promise.

Target salary$120,000How long one interview process takes21 daysFrom first call to the answer.Companies you interview with before an offer3How many fewer, with preparation1Your assumption, not our promise. Start at one; the case survives at zero.

WHAT THE WAIT COSTS, WITH PREPARATION

$20,712$13,808

Earned between today and an offer you have not signed, with the processes preparation saves already taken off.

Per day of waiting: $329 / day
Each process that ends without an offer: $6,904
At your current pace: 3 processes at 21 days: $20,712
1 fewer, with preparation: −$6,904
Prep hours this replaces: 54 hrs

SEE A SCORED ANSWER

Pick a question they will ask

YOUR MOCK INTERVIEW · SCORED

88

How would you build a forecast for a business nobody has modelled before?

Start from the cash cycle rather than the P&L, because a division that looks profitable on paper can still be funding its own growth out of a facility. I would tie receivables days and payables days to the actual invoicing terms, build the statement from those two clocks, and only then layer revenue. On the last acquisition the two clocks explained 80% of the variance in the first quarter, so that is where I would spend week one.

Structure4.5/5

names the frame before the steps

Depth4.5/5

Specificity4.5/5

one number, one mechanism

Communication4.5/5

Role fit4/5

Sample output. In the app you answer out loud and are scored on all five dimensions. This is the shape that scores, from the notes your plan generates.

Pricing

Starter

50 credits a month. No card required.

$0

✓50 credits a month
✓No card required

Practice

The same product with smaller ceilings.

$8/ month

✓800 credits a month
✓Research briefs, study notes and resume tailoring

Pro Monthly

Everything, for the whole job search.

Most useful

$19/ month

✓2,400 credits a month
✓Research briefs, study notes and resume tailoring
✓Progress tracking across plans

Pro Yearly

One payment, twelve months.

$228$149/ year

Save $79 (35%), $12.42 a month

✓Everything in Pro Monthly
✓The same 2,400 credits every month
✓Lowest cost per month
✓Cancel any time from the billing portal

Two minutes from now, you will know what they will ask.

Paste the posting you are interviewing for. You get the questions that job implies, the order to study in for the days you have left, and a rehearsal that scores your answers - before the real interview tells you.

Free to start

No card

50 credits a month

Cancel anytime