Developers, cloud, data & ML, QA, security

Software & Engineering interviews. Scored the way the field scores.

72 job titles across 6 specialisms. Pick yours to see what interviewers score, the questions they ask, and where candidates lose it, then practise it live.

Last reviewed

What interviewers in Software keep scoring

Every title has its own model, but these competencies come up again and again. Each title page shows what a weak, adequate and strong answer looks like for each one.

Problem decomposition & design

Breaks an ambiguous requirement into components, chooses appropriate data structures and boundaries, and can explain the trade-offs of the design they picked.

Code quality & testing discipline

Writes code that others can read and change safely, and uses tests deliberately to protect behaviour rather than to hit a coverage number.

Debugging & production incidents

Finds the root cause of unexpected behaviour methodically using logs, metrics and reproduction, and closes the loop so the same failure does not recur.

Systems & data fundamentals

Understands how their code behaves on a real machine and network: concurrency, memory, I/O, databases, caching and the failure modes of distributed calls.

Delivery & scope management

Ships working software on a predictable cadence by slicing work, surfacing risks early, and negotiating scope rather than silently missing dates.

Code review & technical collaboration

Gives and receives code review that improves the codebase, and works through technical disagreements with evidence rather than seniority or volume.

Ownership beyond the ticket

Takes responsibility for the system and its users rather than only assigned tasks: notices problems, fixes what is broken, and follows work through to production and beyond.

Developing people & managing performance

Grows engineers through feedback, coaching and stretch work, and deals with underperformance directly and fairly rather than avoiding it.

Delivery & execution management

Gets software shipped predictably by setting clear priorities, removing blockers, managing scope and making risks visible early to stakeholders.

Technical judgement & engineering standards

Stays technical enough to evaluate designs, technical debt and quality trade-offs, and sets standards without micromanaging or making every decision.

Hiring & building the team

Builds a strong, diverse team through a fair and effective hiring process, sensible team structure, and deliberate onboarding.

Stakeholder & upward management

Represents the team to product, business and executives: sets expectations, negotiates priorities, delivers bad news early and protects the team from churn.

Interview like a Software hiring manager would.

Thirty minutes, voice to voice, scored against the competencies above. Five minutes of it free.