01
Phone screen
Forty-five minutes, one problem, a stranger on the other end. Thinking out loud under a clock is the part nobody rehearses alone, and the part that decides it.
1:1 technical interview coaching
You keep going round the loop.
This is how you get out.
Phone screen, coding, system design, behavioral, onsite. Every round has its own bar, and most preparation only covers one of them. Crack The Loop is coaching for all of it — a coach who has sat on the other side of the table, working the whole loop with you.
coaching starts with a conversation about where the loop is breaking
Round by round
Every round, not just the one you can practice alone
Every company runs a version of the same sequence, and the rounds fail for different reasons. Your coach runs each one as a full mock — at the real bar, to the real length — then tells you what an interviewer would have written down about you afterwards.
02
Coding
Your coach watches how you get there — the questions you ask, the case you forget, the moment you stop talking — not just the answer you land on.
03
System design
A vague prompt and someone pushing on your assumptions. You learn where to start, what to name, and when to stop drawing — at your level, not a generic one.
04
Behavioral
The round engineers dismiss and then fail on. You build the handful of stories that carry a whole loop, and hear which ones do not land before they cost you.
05
Onsite
Four of the above in a day, with your energy draining. The week before is about pace and recovery as much as technique, and it is planned that way.
→
The offer
What you were doing this for. Your coach knows what the bar looks like from the other side of the table, because that is where they have sat.
Dedicated coaching
One coach, one program, the whole way through
Coaching here is not a marketplace of one-off hours. You work with the same coach across the loop, against a plan the two of you agree, and everything that happens is written down where you can both see it.
the plan
A program, not a series of hours
Which rounds to cover, in what order, and by when — built around the loop you are actually facing rather than a fixed syllabus.
the coach
The same person each time
Someone who remembers what you did last session, knows the habit you are trying to break, and can tell you when it stops showing up.
between sessions
Homework, set and reviewed
Problems chosen for the gap you have, worked in your own practice room. The room records, so your coach reviews the attempt rather than the answer.
after each hour
A written recap
What went well, what to work on, and what to do before next time — written by your coach, so nothing depends on what you remember.
the record
Every session, replayable
The code as it was typed, the audio, and a transcript. Go back to the moment you got stuck and watch what you did instead of guessing.
the dates
Deadlines the program knows about
An onsite on the 14th, an application closing Friday, a decision you are waiting on. The plan is built backwards from them.
What a session can be about
algorithms & data structures
system design
behavioral
front-end coding
front-end system design
mobile system design
project deep dive
engineering management
TPM
SRE
embedded systems
Tell us where the loop is breaking
Say which rounds you have coming and where the last one went wrong. You get a plan for the loop, and a first session that tells you something you did not already know about your own interviewing — or you stop there.