Interview scorecard template

Computer Programmer Analyst interview scorecard

Evaluate Computer Programmer Analyst 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 fluency in the stack they claim: C#/.NET, Java, or COBOL, plus SQL joins, stored procedures, and version control workflow in Git or TFS branching. Use the rubric to compare role-specific evidence consistently.

See AI scoring
software dataapplication developmentlegacy modernizationrequirements analysissql
TL;DR
For technical proficiency, look for evidence the candidate names languages and frameworks with version detail, writes non-trivial SQL from memory, and explains their branching and code review workflow. For systems and trade-offs, look for evidence the candidate explains a concrete trade-off they made, such as denormalising a reporting table, and names the performance or maintenance cost accepted. 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 fluency in the stack they claim: C#/.NET, Java, or COBOL, plus SQL joins, stored procedures, and version control workflow in Git or TFS branching.

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 and frameworks with version detail, writes non-trivial SQL from memory, and explains their branching and code review workflow.

02
Evaluation factor

Systems and trade-offs

25% weight

Probe how they weigh batch versus real-time processing, index design against write cost, and when they refactor legacy modules instead of wrapping them in new interfaces.

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

Explains a concrete trade-off they made, such as denormalising a reporting table, and names the performance or maintenance cost accepted.

03
Evaluation factor

Evidence and rigour

25% weight

Test debugging discipline: reproducing a production defect, reading query execution plans, log analysis, unit test coverage, and how they validate data migrations before cutover.

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

Walks through a real defect with evidence gathered (logs, execution plan, test case) rather than guesswork, and cites the fix's measured effect.

04
Evaluation factor

Collaboration and communication

15% weight

Assess how they turn vague user requests into specifications: requirement gathering sessions, use cases, sign-off documents, and status updates to business owners during releases.

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

Describes translating ambiguous business asks into documented specs, and handling scope changes with stakeholders without stalling the release schedule.

Evidence-led prompts

Interview questions for a Computer Programmer Analyst

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

  1. 01

    Can you describe a complex programming project you have recently worked on?

  2. 02

    What programming languages are you proficient in?

  3. 03

    Do you have experience in database modelling and design?

  4. 04

    Do you have experience in systems analysis, and which methodologies have you used?

  5. 05

    Can you explain your understanding of the software development lifecycle?

See the complete Computer Programmer Analyst 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