Interview scorecard template

Senior Full Stack Developer interview scorecard

Evaluate Senior Full Stack Developer candidates across 4 weighted areas: technical proficiency, systems and trade-offs, evidence and rigour, and collaboration and communication. Technical proficiency leads at 35%, so probe both ends properly: data modelling and API design as well as front-end state, rendering, and browser behaviour. Use the rubric to compare role-specific evidence consistently.

See AI scoring
software datafull stackseniorsoftware engineeringweb development
TL;DR
For technical proficiency, look for evidence the candidate genuinely strong on both ends, from schema and API design through to rendering and browser behaviour. For systems and trade-offs, look for evidence the candidate reasons about load, caching, and failure ahead of time, and names the trade-off they chose and what it cost. 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

Probe both ends properly: data modelling and API design as well as front-end state, rendering, and browser behaviour.

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

Genuinely strong on both ends, from schema and API design through to rendering and browser behaviour.

02
Evaluation factor

Systems and trade-offs

25% weight

Test how they reason about a system under load, and what they would change before it breaks.

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

Reasons about load, caching, and failure ahead of time, and names the trade-off they chose and what it cost.

03
Evaluation factor

Evidence and rigour

25% weight

Check their testing and review habits, and whether they can describe a bug that reached production and why.

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

Tests deliberately at the right level and can describe a production bug they caused, caught, and prevented recurring.

04
Evaluation factor

Collaboration and communication

15% weight

Assess how they operate at senior level: reviewing others, splitting work, and pushing back on a bad requirement.

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

Reviews and mentors effectively, and pushes back constructively on requirements that will not survive contact.

Evidence-led prompts

Interview questions for a Senior Full Stack Developer

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

  1. 01

    Walk us through your experience across front-end and back-end work: where do you go deepest, and where do you lean on others?

  2. 02

    Can you discuss your experience with database design and management? Walk us through a schema you designed and why you structured it that way.

  3. 03

    Can you discuss your experience with API design and development, including how you handled versioning and breaking changes?

  4. 04

    What is your experience with JavaScript frameworks like React, Angular, or Vue, and how do you handle state in a large front end?

  5. 05

    What steps do you take to ensure the security of the applications you build?

See the complete Senior Full Stack Developer 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