Worked example · fictional people and company
Evidence review: Alex Morgan
Alex's projects show direct work on two of the role's core problems: duplicate payouts and queue lag at peak load. Three requirements are supported with quotes. Postgres scale and mentoring aren't covered by any project yet. Alex's stated view on on-call differs from the role's one-week-in-six rotation.
Evidence supports · 3Still unclear · 2Discuss a difference · 1Designing idempotent APIs for money movement
Evidence supports“I designed client-supplied idempotency keys, wrote the migration for two years of payout records and rolled it out behind a flag. Duplicates went to zero the next quarter.”
Debugging distributed queues in production
Evidence supportsFound and fixed a hot-partition lag during peak load.
Postgres performance on very large tables
Still unclearAsk: What's the largest Postgres table you've tuned, and what changed?
Writing incident reviews that change practice
Evidence supportsWrote a review whose actions became team defaults.
Mentoring mid-level engineers
Still unclearAsk: Tell me about someone you helped grow. What changed for them?
Owning on-call for a payments service
Discuss a differenceAlex prefers to avoid on-call; the role includes one week in six.