Interview scorecard
Software Engineer
Score each skill from 1 to 5. A 1 is below the bar for this role, a 3 meets it, and a 5 is above it. The examples show what each sounds like. Use 2 and 4 for answers that fall in between.
System design
Breaks an ambiguous problem into parts and reasons about the trade-offs between them.
Questions
- Walk me through a system you designed. What did you need to know before you started?
- What would break first if its traffic grew ten times, and how would you find out?
- Tell me about a design decision you'd make differently now. What changed your mind?
1: Below the bar
Jumps to a solution without clarifying requirements. Can't explain why one approach beats another.
3: Meets the bar
Reaches a workable design with some prompting. Names the main trade-offs but misses failure modes or scale limits.
5: Above the bar
Clarifies requirements first, compares alternatives unprompted, and explains what would break first and how they'd know.
Code quality
Writes code that someone else can read, test, and change without asking the author.
Questions
- Tell me about code you wrote that someone else later had to change. How did that go?
- Think of a recent piece of your code. What would you simplify if you had more time?
- How do you decide when code is good enough to ship?
1: Below the bar
Code works only on the happy path and is hard to follow. Naming and structure would need a rewrite before review.
3: Meets the bar
Readable, working code with reasonable structure. Edge cases and tests come up when asked.
5: Above the bar
Clear, well-structured code with edge cases handled. Explains their choices and what they'd simplify with more time.
Debugging
Finds the cause of a problem methodically instead of guessing.
Questions
- Tell me about the hardest bug you've tracked down. How did you narrow it down?
- What did you rule out along the way, and how did you confirm the real cause?
- How do you approach a problem you can't reproduce?
1: Below the bar
Changes things at random and hopes. Can't describe how they'd narrow the problem down.
3: Meets the bar
Forms a reasonable hypothesis and tests it. Needs a nudge to look past the first plausible cause.
5: Above the bar
Reproduces the issue, narrows it step by step, and confirms the root cause before fixing it. Says what they ruled out and why.
Communication
Explains technical ideas clearly to people with different levels of context.
Questions
- Explain something technical you worked on recently to someone outside engineering.
- Tell me about a time someone misunderstood you. What did you change?
- How do you make sure a written update lands with people who weren't in the room?
1: Below the bar
Answers are hard to follow or miss the question. Doesn't check whether the listener is keeping up.
3: Meets the bar
Clear on familiar topics. Loses structure on complex ones or leans on jargon.
5: Above the bar
Structures answers well, adjusts the depth to the audience, and asks clarifying questions before diving in.
Ownership
Takes responsibility for outcomes, including the unglamorous work after launch.
Questions
- Tell me about a problem you fixed that nobody asked you to fix.
- Describe something you shipped that went wrong afterward. What did you do?
- Tell me about work you kept improving after it shipped. Why did it matter?
1: Below the bar
Describes past work as tasks handed to them. Points at others when things went wrong.
3: Meets the bar
Follows through on their own work. Gives examples of fixing problems once someone pointed them out.
5: Above the bar
Gives specific examples of spotting a problem nobody assigned, fixing it, and making sure it stayed fixed.
Overall recommendation
Decide on your own, before you compare notes with the rest of the panel.