Software engineer mock interviews
Practise the four rounds a software engineering loop is built from, out loud and on a clock. Drill one round, or run the whole loop for a role and get a debrief at the end.
- Coding, fundamentals, system design, behavioral
- Python, Java, Go, C++ or TypeScript
- Regular and lead
The rounds
Coding
Solve algorithmic problems live while explaining your thinking.
45 min
Language & CS fundamentals
Language internals, concurrency, memory, data structures and CS basics.
35 min
System design
Design a large-scale service end to end, with trade-offs.
45 to 50 min
Behavioral
Stories about conflict, ownership, failure and impact.
30 to 35 min
A full loop for one role adds a recruiter screen (12 to 15 min) and a hiring manager conversation (25 to 30 min).
Regular and lead level
- Regular
- New grad to mid-level, roughly 0 to 5 years: correct fundamentals, working solutions, clear communication and sensible testing.
- Lead
- Senior, staff and tech lead: you drive the conversation, handle ambiguity, weigh trade-offs and think about production and scale.
See the feedback before you start
Full reports from the real report pipeline, for a fictional student and a scripted interview.
Questions
What does the fundamentals round ask?
A fast run of questions on language internals, concurrency, memory, data structures and CS basics in your chosen language. Vera probes once or twice for depth on each and moves on.
What is a full loop?
Every round for one role, across several days, with a recruiter screen at 12 to 15 minutes and a hiring manager conversation at 25 to 30. Later rounds remember what you said in earlier ones, and the loop ends with a debrief.
Which level should I pick?
Regular for internships to mid-level roles, about 0 to 5 years. Lead for senior, staff and lead roles.