Software engineering track
Talk through the tradeoff, then write the code.
For intern to mid-level software engineers. The interviewer follows up on the decision you just described, can set one small coding problem, and can imitate 21 company-style interview loops.
- Intern to senior
- Optional coding round
- 21 company-style rooms
- 10-minute sessions

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?
What it is
The software engineering track, explained.
The Software engineering track is a technical interview you take out loud. It asks about systems you worked on, bugs you chased, and choices you made, and it keeps asking until the tradeoff is clear.
Turn on the coding round and the interviewer sets one small problem. You talk through the approach first, write it in the editor, and then discuss edge cases. Code is reviewed in the conversation and is never run.
Who it is for
- Engineers changing jobs who have not interviewed in a while
- New graduates moving from campus rounds to company loops
- Frontend, backend, full-stack, DevOps, and QA engineers
- Anyone preparing for a specific company's style of interview
The room listens for
- The tradeoff, not the tool list
- How you found the bug
- Edge cases said out loud
What you get
Everything in the software engineering room.
Follow-ups on your decisions
The next question comes from your last answer, so vague answers get a second, sharper question.
Optional coding round
One problem, discussed before you type. Write it in JavaScript, TypeScript, Python, Java, Go, Rust, or SQL.
21 company-style rooms
Imitate loops inspired by Google, Amazon, Microsoft, Meta, Flipkart, Razorpay, Infosys, TCS, and more.
Your role and level
Pick the job title and seniority, from intern to senior. Each session runs 10 minutes.
Resume and job description
Upload a resume and paste a job description, and the questions come from your real work and the role.
Score, transcript, and code
Four scores out of 5 with notes, the full transcript, and your code saved beside it.
Inside the room
Company loops and a coding round, when you want them.
Keep it a general engineering interview, or pick a company style and add one problem.
21 company-style rooms
Inspired by public interview loops. Not affiliated with these companies.
- Meta
- Amazon
- Microsoft
- MongoDB
- Walmart
- Flipkart
- Razorpay
- Apple
- Netflix
- Uber
- Stripe
- Adobe
- Oracle
- Atlassian
- Swiggy
- Zomato
- PhonePe
- CRED
- Infosys
- TCS
Coding round languages
- JavaScript
- TypeScript
- Python
- Java
- Go
- Rust
- SQL
How the coding round runs
- 1Hear one small problem
- 2Talk through the approach
- 3Write it in the editor
- 4Discuss edge cases
How a session runs
The rounds, in order.
- 01
Warm-up
- 02
Role questions
- 03
Optional code
- 04
Wrap-up
Why it is useful
Why it helps engineers
- 01
Explaining is a separate skill
Knowing the answer and saying it clearly under questioning are different. Practise the second.
- 02
Interrupt like a real panel
Talk over the interviewer and it stops to listen, the way people do in a real loop.
- 03
Debugging stories that land
Rehearse the wrong hypothesis, the clue, and the fix until the story is tight.
- 04
Know the loop before you walk in
Company-style rooms ask the way those companies publicly describe their interviews.
- 05
No mock partner to schedule
Run a session whenever you have 15 minutes, as often as twice a day.
- 06
Evidence, not vibes
Read the transcript to see exactly where an answer drifted.
FAQ
Questions about this track
Which languages does the coding round support?
JavaScript, TypeScript, Python, Java, Go, Rust, and SQL.
Is my code executed?
No. The interviewer reads your code and discusses it with you, the way a whiteboard round works.
Can I practise for a specific company?
Yes. Choose one of 21 company-style rooms during setup. They are inspired by public interview loops and are not affiliated with those companies.
Is this a coding-problem grinder?
No. There is at most one problem per session, and the focus is how you reason and explain, not how many problems you solve.
One rehearsal before it counts.
Free. Two sessions a day, up to 10 minutes each. No camera.
Start a free software engineering session