Interview scorecard template

Esports Data Analyst interview scorecard

Pre-screening scorecard for Esports Data Analyst candidates.

See AI scoring
software datadraft analyticspython pandasriot apiscrim data
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 with the pipeline they actually use: SQL, Python with pandas, parsing CS2 .dem files or Riot/GRID/Bayes API feeds, plus dashboards in Tableau or Power BI.

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 specific endpoints, parsers and libraries, and describes a scrim or match dataset they built and queried themselves.

02
Evaluation factor

Systems and trade-offs

25% weight

Probe how they model a game: choosing between per-round, per-map and per-series units, handling patch changes, small sample sizes, and roster swaps that break historical comparability.

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 patch versioning and sample size limits clearly, and defends a chosen aggregation level against a plausible alternative.

03
Evaluation factor

Evidence and rigour

25% weight

Test whether their metrics survived scrutiny: draft win rate deltas, gold or economy differentials, vision score, expected damage models, and how they validated against actual match outcomes.

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 a metric they built, how it was backtested, and one case where the data contradicted coaching-staff intuition.

04
Evaluation factor

Collaboration and communication

15% weight

Assess how they deliver findings to coaches and players before a bo3: pre-match scout reports, ban priority sheets, VOD timestamps, and turnaround under tournament deadlines.

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 reports coaches actually used in prep, adapting depth and jargon for players versus management under tight deadlines.

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