Interview scorecard template

Python Developer interview scorecard

Evaluate Python 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 check fluency beyond scripting: generators, decorators, typing with mypy, asyncio versus threading, and framework depth in Django, FastAPI or Flask, plus packaging with poetry or uv. Use the rubric to compare role-specific evidence consistently.

See AI scoring
software dataasynciodjangopytestpython
TL;DR
For technical proficiency, look for evidence the candidate explains CPython internals such as the GIL, contrasts asyncio with multiprocessing from real use, and names library versions confidently. For systems and trade-offs, look for evidence the candidate describes a concrete bottleneck (N+1 queries, cold starts), the trade-off weighed, and the measured latency or cost outcome after the change. 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 beyond scripting: generators, decorators, typing with mypy, asyncio versus threading, and framework depth in Django, FastAPI or Flask, plus packaging with poetry or uv.

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

Explains CPython internals such as the GIL, contrasts asyncio with multiprocessing from real use, and names library versions confidently.

02
Evaluation factor

Systems and trade-offs

25% weight

Probe how they structured a service: ORM query patterns, Celery or RQ task queues, caching in Redis, migration strategy, and where they chose Python over another runtime.

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 a concrete bottleneck (N+1 queries, cold starts), the trade-off weighed, and the measured latency or cost outcome after the change.

03
Evaluation factor

Evidence and rigour

25% weight

Ask for their testing and profiling habits: pytest fixtures, coverage thresholds, mocking external APIs, cProfile or py-spy runs, and how a regression was caught before release.

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 specific test suites and profiler output, quantifies speedups or defect reduction, and admits where coverage was thin and why.

04
Evaluation factor

Collaboration and communication

15% weight

Look for evidence of code review practice, type hints and docstrings written for others, contributions to open source or internal libraries, and work with non-Python teammates.

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 examples of review comments that changed a design, and explains technical constraints clearly to product or data colleagues.

Evidence-led prompts

Interview questions for a Python Developer

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

  1. 01

    What is your experience using Python for web or service development?

  2. 02

    Tell me about a project where you used Python to automate a process.

  3. 03

    Can you describe using object-oriented features to solve a complex problem?

  4. 04

    Can you explain your understanding of Python's design philosophy?

  5. 05

    How do you use comprehensions and generators, and when would you avoid them?

See the complete Python 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