The cheap part is the money
Eight sessions cost $140. They are not what makes the difference, and this page says so before it sells anything. Four weeks, twice a week, live: coding, system design, and the parts a solved problem never shows — how you narrow it, what you say while you think, and what you do when you are stuck.
Eight hours a week, for four weeks
$140 buys the eight sessions. What moves a pass rate is the thirty-two hours around them — two of every eight are in session, the other six are yours, and if those six are not in the diary before week one they will not appear on their own.
Priced this way on purpose. The sessions are cheap because the expensive part is not for sale.
- 2 hrs
- In session, with an engineer.
- 6 hrs
- Alone: the problems set after each session, the write-ups, the second attempt at the one you got wrong.
- 92%
- Pass rate on the technical round
- 100+
- Problems solved across the four weeks
Three of the six rounds. Not the other three.
A hiring loop has six stages and they fail for different reasons. Shaded rows are what these four weeks cover. If you are losing one of the unshaded ones, the money belongs on a different page and this one will not pretend otherwise.
- 01
Recruiter screen
Motivation, salary, availability, a light skills pass.
Mock Interview Package - 02
Technical phone screen
One or two problems in a shared editor, under 45 minutes.
Covered here - 03
Onsite coding rounds
Two to four problems, live, with an interviewer watching you think.
Covered here - 04
System design
An open-ended design pushed until you reach a trade-off you have to defend.
Covered here - 05
Hiring manager / behavioural
Your history, your judgement, how you work with people.
Mock Interview Package - 06
Team fit and final
Values, cross-functional questions, the closing pitch.
Mock Interview Package
The unshaded rounds are a different muscle and a different rehearsal: the Mock Interview Package.
Almost every screen is one of these wearing a story
The third line on each card is the part people lose on: not the solution, the follow-up after it. Which families get the weight is decided in week one from your baseline.
Two pointers & sliding window
Longest or shortest stretch of a sequence that satisfies some constraint.
“Now the constraint changes halfway through.”
Hashing and counting
Group, deduplicate or match things that are equal under some key you have to invent.
“What if the key collides?”
Binary search on the answer
Minimise a maximum, or maximise a minimum, when the search space is the result rather than the input.
“Prove the predicate is monotonic.”
Trees and recursion
Anything asked about every path, every subtree, or the relationship between a node and its children.
“Now do it without recursion.”
Graphs: BFS, DFS, ordering
Reachability, shortest hops, dependency order — usually disguised as a scheduling story.
“There is a cycle. What now?”
Dynamic programming
Count the ways, or find the best, when today’s choice depends on what you already decided.
“Reconstruct the actual answer, not just its value.”
Heaps and intervals
Top-k, merging overlapping ranges, scheduling rooms and meetings.
“It is a stream now, and it does not fit in memory.”
Design primitives
Queues, caches, sharding, replication, consistency — the pieces every open-ended design is assembled from.
“Which one breaks first under ten times the load?”
Four weeks, two sessions a week
- Week 1
Baseline and complexity
Two problems solved cold, so the plan is built on where you actually are. Complexity analysis until Big-O stops being a formality.
- Week 2
Patterns and screens
The handful of families above that cover most screens. Two timed phone screens run to the real clock, with a code review after.
- Week 3
System design
Deep-dives at the level you are actually targeting. Trade-offs defended under pressure, not listed.
- Week 4
Full simulation
A back-to-back round in real conditions, scored the way the company scores it.
What you get
- 8 recorded practice sessions
- 50+ solved problem explanations
- System design templates and examples
- Big-O complexity cheat sheet
- Company-specific prep guides
- Technical interview checklist
One language, chosen in week one and not changed after
- One language, chosen in week one and not changed after.
- Your target companies and the format each of them actually runs.
- An honest list of what you are weak at — graphs, DP, concurrency, design.
- A current read on your coding level, however unflattering.
- Eight hours a week, blocked in the calendar before session one.
Engineers only, and deliberately so.
Four weeks. Eight sessions. One language.
$140. Send your target companies and the last technical round you failed; week one starts there.
- 8 sessions · 60 min each
- 28 days of support