Interview scorecard template

Network Performance Analyst interview scorecard

Evaluate Network Performance Analyst candidates across 4 weighted areas: technical depth, work that shipped, diagnosis under uncertainty, and working across the org. Technical depth leads at 35%, so check command of KPI families they actually work with: RRC setup success, handover failure, PRB utilisation, latency and jitter budgets, plus tools. Use the rubric to compare role-specific evidence consistently.

See AI scoring
engineering applied sciencedrive testingkpi analysisran optimizationtelecom
TL;DR
For technical depth, look for evidence the candidate names specific counters and thresholds, explains how each KPI is derived, and links degradation to a plausible physical or configuration cause. For work that shipped, look for evidence the candidate cites named optimisation projects with measured gains, for example throughput or drop rate improvements across a defined cluster or region. 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 depth

35% weight

Check command of KPI families they actually work with: RRC setup success, handover failure, PRB utilisation, latency and jitter budgets, plus tools like NetScout, Nokia NetAct, Huawei U2020 or Wireshark.

Evidence to listen for

  • Explains the physics or mechanism behind their work, not just the tooling
  • Names the standards, tolerances, and constraints they designed against
  • Can defend a design decision under follow-up questions
  • Distinguishes what they personally engineered from what the team delivered

Five-point scoring guide

1
Poor

Cannot explain the fundamentals of their own stated specialism.

2
Needs Improvement

Knows the vocabulary but not the underlying mechanism; struggles under follow-ups.

3
Satisfactory

Solid working knowledge for the role; depth thins out on edge cases.

4
Very Good

Strong command of the domain; explains trade-offs and defends decisions well.

5
Excellent

Names specific counters and thresholds, explains how each KPI is derived, and links degradation to a plausible physical or configuration cause.

02
Evaluation factor

Work that shipped

30% weight

Ask what they changed in a live network: neighbour list retunes, PCI or PRACH conflict fixes, capacity upgrades, QoS reprioritisation, and the before and after KPI deltas they can quote.

Evidence to listen for

  • Names specific programmes, parts, or systems that reached production or field use
  • States their own scope inside the project
  • Can give measured outcomes: yield, cycle time, cost, failure rate
  • Explains what went wrong and what they changed

Five-point scoring guide

1
Poor

No delivered work; experience is coursework, lab-only, or purely observational.

2
Needs Improvement

Contributed to projects but cannot say what shipped or what their part was.

3
Satisfactory

Has delivered real work; outcomes described without numbers.

4
Very Good

Names shipped work and their scope, with some measured results.

5
Excellent

Cites named optimisation projects with measured gains, for example throughput or drop rate improvements across a defined cluster or region.

03
Evaluation factor

Diagnosis under uncertainty

20% weight

Probe a messy case: intermittent packet loss or a cell with normal counters but poor user experience. Look for use of trace data, drive test logs, TEMS or CDR correlation.

Evidence to listen for

  • Describes a real failure they chased to root cause
  • Shows a method: isolate variables, reproduce, measure, eliminate
  • Distinguishes correlation from cause
  • Says what they ruled out and why, not only what the answer turned out to be

Five-point scoring guide

1
Poor

No diagnostic method; guesses or escalates immediately.

2
Needs Improvement

Trial and error with no structure; cannot explain how they narrowed the cause.

3
Satisfactory

Reasonable method on familiar problems; less structured on novel ones.

4
Very Good

Clear systematic approach with a real root-cause story.

5
Excellent

Walks a structured isolation path across transport, radio and core, rules out layers with evidence, and admits what remained unexplained.

04
Evaluation factor

Working across the org

15% weight

Assess how they push findings to field engineers, planning, core teams and vendors, including how they escalate a suspected vendor software defect or defend a capex request.

Evidence to listen for

  • Explains technical constraints to non-technical stakeholders without condescension
  • Has negotiated scope, cost, or timeline with manufacturing, product, or suppliers
  • Documents decisions so others can act on them
  • Takes review feedback without defensiveness

Five-point scoring guide

1
Poor

Cannot communicate outside their specialism; dismissive of other functions.

2
Needs Improvement

Communication gaps cause rework; avoids stakeholder contact.

3
Satisfactory

Works adequately with other teams; documentation is thin.

4
Very Good

Communicates clearly across functions; reliable collaborator.

5
Excellent

Describes concrete handoffs and reports that changed another team's roadmap or triggered a vendor patch, not just dashboards produced.

Evidence-led prompts

Interview questions for a Network Performance Analyst

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

  1. 01

    How have you contributed to improving network performance in previous roles?

  2. 02

    In what ways have you used data analysis to solve a problem?

  3. 03

    What reports and documentation have you produced for technical and non-technical audiences?

  4. 04

    Do you have experience diagnosing issues through packet analysis?

  5. 05

    How proficient are you with network monitoring tools?

See the complete Network Performance 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