Challenge 01
The blind service
Scenario
A Go service handling checkout has no traces and one ambiguous error rate metric. They instrument it without breaking it.
What you learn
Whether they choose span boundaries that match user actions.
In the workspace
$ ls challenges/
workspace, runbook.md, README.md
candidate has:
- · a real Linux box in the browser
- · kubectl, docker, terraform, jq, yq
- · cluster, repo and cloud creds pre-wired
- · auto-checks running in the background
interviewer sees:
- · every keystroke + every command
- · terminal + screen recording
- · auto-graded pass/fail per check