Peer-to-peer mock technical interviews

Master the loop.
Design, Code, Test—and Cache Out!

Master technical loops by doing what real interviews demand: clarifying system design ambiguity, uncovering edge cases, tracing code manually, and getting live feedback from real engineers.

You can’t outcode an LLM. The LLM can’t out-context you.

System design is the new bar

As models absorb the coding, interviews are moving toward the work that cannot be automated: parsing highly ambiguous constraints, mapping out structural trade-offs between two defensible designs, and predicting exactly what breaks first under load. That structural judgment is exactly what senior loops are testing for.

The model codes. You are responsible

Algorithms haven’t stopped mattering—their role has just changed. When a model spits out a complex block of code, it can be subtly, dangerously wrong. DSA is no longer about memorizing syntax; it is about having the mental computer science framework to read generated code, trace its time/space complexity, simulate its edge cases, and spot the logical flaws before they hit production.

Master debugging. Trace your way.

Interviewers mark down the candidate who writes code and immediately reaches for Run. It says you cannot evaluate your own logic — and at the senior bar, that is the thing being measured. The candidate who walks their code by hand reads as someone who actually understands it.

Tracing binarySearch([1, 3, 5, 8, 13], 13)
Steplohimidnote
10425 < 13, go right
23438 < 13, go right
3444found

Does your loop still terminate when lo === hi? This is where you find out.

Each one teach one

Every interviewer here is an engineer who was recently the candidate. You are interviewed by someone who remembers the pressure, and you sharpen your own judgment by sitting on the other side of the table.

Be interviewed

$10.00 for a live session with voice, a shared editor, a whiteboard and written feedback at the end. Your card is held, not charged, until a peer accepts.

Interview someone

Earn $5.00 a session, and get the view from the other chair. Reading someone else’s approach is the fastest way to see holes in your own.

Or bring a friend

Already know someone who interviews? Send them a link and use the same room — editor, whiteboard and trace table — for nothing at all.

How a session goes

  1. Pick a problem. Work it alone first — the editor, whiteboard and trace table are all there before anyone else joins.
  2. Request an interviewer, or invite someone you know. A peer accepts and you are both in the same room, talking.
  3. Get written feedback. Scored on the axes that fit the problem — requirements and tradeoffs for design, problem solving and testing for algorithms — plus what to work on next.

Ready to be uncomfortable for forty-five minutes?

It is cheaper than the interview you are preparing for.