Developer interview template
Copy-paste interview script for evaluating any web developer: 14 questions grouped by intent, good/bad answer patterns, and the scoring sheet.
The companion to the vetting guide: the same 14 questions as a copy-paste interview script, grouped by what each one tests, with good/bad answer patterns and a scoring row per question. Use it on any candidate — including anyone you find through this site.
The fields, with guidance
Process questions (1–4)
Reveals how they run projects. Listen for mechanisms, not vibes.
Example: “Walk me through your last project — what went wrong?” Good: specific, owns a mistake, describes the fix.
Technical questions (5–9)
No technical knowledge required from you — the patterns tell the story.
Example: “How will you make the site fast?” Good: measurable budgets (LCP under 2.5s) and an image/code/hosting plan.
Ownership questions (10–12)
Decides how the relationship can end. The non-negotiables live here.
Example: “Who owns the code and when?” Good: you do, on payment — said without flinching.
Reference questions (13–14)
Verifiable history. Hesitation is data.
Example: “Can I speak to your last two clients?” Good: yes, unprompted caveats about NDAs aside.
Scoring
One point per good answer. Twelve-plus is a conversation; below eight, keep looking.
Example: Score as you go — the pattern across answers matters more than any single one.
The three red flags
Any one of these ends the evaluation regardless of score.
Example: No repo/version control · quotes without a written spec · bad-mouths every past client.
Copy this block
DEVELOPER INTERVIEW — [candidate] — [date]
PROCESS
1. Last project — what went wrong? [ ]
2. How are scope changes handled? [ ]
3. What happens after launch? [ ]
4. Who exactly does the work? [ ]
TECHNICAL
5. How will you make the site fast? [ ]
6. What happens to rankings on relaunch? [ ]
7. Show a live site running a real business [ ]
8. What would you never build on this stack? [ ]
9. Backups — and tested restores? [ ]
OWNERSHIP
10. Who owns the code, and when? [ ]
11. If we part ways, what do we keep? [ ]
12. Summarize your standard contract [ ]
REFERENCES
13. Can I speak to your last two clients? [ ]
14. What would they call your weakness? [ ]
SCORE: ___ / 14 (12+ = proceed)
RED FLAGS: no repo / no written spec / trashes clients -> STOP
Plain text on purpose — pastes cleanly into email, docs and project tools.
Run it on two or three candidates and the differences write themselves. The full reasoning behind every question is in the vetting guide.
Quarterly, and only when the numbers move
Get the rate report before you negotiate.
Updated rate bands across the major stacks and regions, plus what changed and why. No other email.