Interview scorecard template

Senior Software Engineer interview scorecard

Evaluate Senior Software Engineer candidates across 4 weighted areas: technical proficiency, systems and trade-offs, evidence and rigour, and collaboration and communication. Technical proficiency leads at 35%, so check depth in their primary stack: language internals, concurrency, ORM or query tuning, test frameworks. Ask them to walk through a specific pull request they. Use the rubric to compare role-specific evidence consistently.

See AI scoring
software databackend engineeringcode reviewdistributed systemssystem design
TL;DR
For technical proficiency, look for evidence the candidate names languages, frameworks and profiling tools precisely, explains a real PR line by line including edge cases and test coverage choices. For systems and trade-offs, look for evidence the candidate describes trade-offs with numbers: p99 latency, cost per request, failure modes, plus the option they deliberately declined and why. Apply the written 1–5 anchors to every answer, record the evidence behind each rating, and use the factor weights to reach a consistent overall assessment.
Complete evaluation framework

What to assess and how to score it

Review the evidence signals before interviewing. Then use the anchored descriptions—not instinct alone—to choose the score that best matches each answer.

01
Evaluation factor

Technical proficiency

35% weight

Check depth in their primary stack: language internals, concurrency, ORM or query tuning, test frameworks. Ask them to walk through a specific pull request they authored and defended.

Evidence to listen for

  • Command of the languages, frameworks, and data tools the role actually uses
  • Understands correctness, performance, and failure modes, not just syntax
  • Has opinions on testing and can justify them
  • Reads and reasons about code they did not write

Five-point scoring guide

1
Poor

Cannot work independently; fundamentals are missing.

2
Needs Improvement

Weak fundamentals; output needs heavy review.

3
Satisfactory

Competent for the role; needs guidance on complex or unfamiliar work.

4
Very Good

Strong practitioner; handles hard problems with little guidance.

5
Excellent

Names languages, frameworks and profiling tools precisely, explains a real PR line by line including edge cases and test coverage choices.

02
Evaluation factor

Systems and trade-offs

25% weight

Probe architecture calls they owned: database choice, caching layer, queue versus cron, monolith split. Ask what they rejected and what the latency or cost budget was.

Evidence to listen for

  • Reasons about scale, latency, cost, and failure before writing code
  • Names the trade-off they chose and what they gave up
  • Understands the data lifecycle end to end
  • Anticipates what breaks at ten times the volume

Five-point scoring guide

1
Poor

No thinking beyond the immediate task; no awareness of scale or failure.

2
Needs Improvement

Limited architectural awareness; struggles with design decisions.

3
Satisfactory

Works within an existing design; makes sound local decisions.

4
Very Good

Designs for scale and maintainability; articulates trade-offs clearly.

5
Excellent

Describes trade-offs with numbers: p99 latency, cost per request, failure modes, plus the option they deliberately declined and why.

03
Evaluation factor

Evidence and rigour

25% weight

Test how they prove things: load tests, metrics in Datadog or Prometheus, feature flags, staged rollouts, postmortems for an incident they caused or resolved.

Evidence to listen for

  • Validates results rather than trusting output
  • Knows how their work is measured and what a bad result looks like
  • Can describe a time their own analysis or model was wrong and how they caught it
  • Careful about data quality, leakage, and silent failure

Five-point scoring guide

1
Poor

Ships unvalidated work; no notion of how correctness is checked.

2
Needs Improvement

Validates superficially; misses obvious quality or leakage issues.

3
Satisfactory

Reasonable checks in place; rigour drops under time pressure.

4
Very Good

Validates thoroughly; can name a real error they caught in their own work.

5
Excellent

Cites dashboards, error rates and rollback thresholds; separates hypothesis from confirmed root cause without blaming teammates.

04
Evaluation factor

Collaboration and communication

15% weight

Assess how they review others' code, mentor mid-level engineers, and negotiate scope with product managers when a sprint estimate slips or requirements shift mid-flight.

Evidence to listen for

  • Explains technical work to non-technical stakeholders
  • Gives and takes code or peer review constructively
  • Documents enough that the work survives their absence
  • Aligns with team process rather than working around it

Five-point scoring guide

1
Poor

Cannot work in a team; resistant to feedback.

2
Needs Improvement

Communication issues create rework; lone-wolf tendencies.

3
Satisfactory

Adequate team member; documentation and review participation are light.

4
Very Good

Communicates well; reliable reviewer and collaborator.

5
Excellent

Gives concrete examples of review comments that changed a design, and describes raising risk to stakeholders early with options.

Evidence-led prompts

Interview questions for a Senior Software Engineer

Use these prompts to surface evidence for the weighted factors above and compare candidates against the same role-specific criteria.

  1. 01

    Which programming languages are you most proficient in?

  2. 02

    Can you share your experience with front-end or back-end development?

  3. 03

    Do you have experience with database design and query performance?

  4. 04

    Do you have experience with microservices architecture?

  5. 05

    Can you describe a time you had to make a critical technical decision during a project?

See the complete Senior Software Engineer question set
Put this rubric to work

Score every candidate against the same standard

Add these weighted factors to Hirevire and let AI evaluate recorded answers against your rubric.

Explore AI Scorecards