Skip to content
Templates
WorkflowVersion 2

Hire a senior software engineer

A bounded fictional senior-backend work sample: interpret an API contract, diagnose retry and tenant-isolation defects, design tests, review a proposed patch, challenge release trade-offs and revise an evidence-based recommendation. Submitted artifacts are reviewed; code is not executed and no certification or automated hiring cutoff is implied.

Canvas

trigger, Start; activity, Diagnose an unreliable task-creation endpoint; evidence, Claim–Evidence–Reasoning (CER); activity, Design a repair and a layered test matrix; evidence, Test Pyramid; evidence, Claim–Evidence–Reasoning (CER); activity, Review a tempting but incomplete patch; evidence, Claim–Evidence–Reasoning (CER); evidence, SBI Framework (Situation–Behavior–Impact); activity, Challenge the release decision with a product partner; evidence, Decision Quality Framework; activity, Update the recommendation when verification is mixed; evidence, Claim–Evidence–Reasoning (CER); evidence, Decision Quality Framework; end, End

Activities

  • FormDiagnose an unreliable task-creation endpointPrimary focus: software specification analysis and traceable defect diagnosis. Separate demonstrated defects from assumptions before suggesting a fix.
  • FormDesign a repair and a layered test matrixPrimary focus: explicit software change and verification design. Produce reviewable pseudocode and test contracts without claiming execution.
  • FormReview a tempting but incomplete patchPrimary focus: consequential code review with constructive, attributable feedback. Review a separate supplied patch rather than repeating your own solution.
  • AI chatChallenge the release decision with a product partnerPrimary focus: senior engineering decision-making under delivery pressure. Explain feasible choices, clarify a stakeholder constraint and retain nonnegotiable isolation requirements.
  • FormUpdate the recommendation when verification is mixedPrimary focus: evidence-led revision and accountable handoff. Use new supplied verification observations to qualify the change recommendation and make missing proof explicit.