Skip to content

Tracks

Three rooms. Pick the one closest to your next interview.

The track changes what the interviewer listens for. Length, resume, and the coding round are set when you start.

Students in a classroom, one standing with a notebook and backpack

Student

Final-year students, freshers, interns.

The room does not invent a job you have not had. It asks what you built, what broke, and whether you can explain it without hiding behind the team.

The room listens for

  • Your part, named in one sentence
  • A failure with a cause
  • A concept in plain words

Opening → Project defense → Fundamentals → Close

Interviewer. Walk me through the project you would defend first.

You. The attendance app. I owned the check-in API. The screen was shared with two classmates.

Follow-up. Check-ins duplicated on a slow network. What did you change?

An engineer in headphones thinking through a problem at a laptop

Software engineering

Junior to mid-level engineers.

Follow-ups stay on the decision you just described. The optional coding round is one small problem, discussed before you write a line.

The room listens for

  • The tradeoff, not the tool list
  • How you found the bug
  • Edge cases said out loud

Warm-up → Role questions → Optional code → Wrap-up

Interviewer. An API you shipped was wrong. How did you find out?

You. Clients retried and we stored the same write twice. A tester caught it in the pilot.

Follow-up. Before code: how do you make the second request a no-op?

A candidate in a blazer smiling, ready for the interview

A specific role

Switchers, analysts, support, HR screens.

Paste the job description. Questions come from that post: motivation, a story with a result, and what you would ask the panel back.

The room listens for

  • A detail from the job post
  • One story with a number or outcome
  • A question that is about the work

Screening → Behavioral → Motivation → Your questions

Interviewer. Connect your last job to this role in two minutes.

You. I ran vendor tickets. The useful part was writing the repro so engineering did not have to ask twice.

Follow-up. Give me one ticket where that write-up changed the fix.