Work-sample pack 01 Node.js / JavaScript

Backend reliability.

Five failures across the life of a request. Trace the evidence, fix the cause, and prove the system holds.

About 175 min · at your pace5 multi-file incidentsAdvanced

Free with an account. New here? Try a shorter guest lab first.

Start an investigation

Start with the request.

Next investigation

Tokens rejected after deploy

Accepted fixes save your place. Each one unlocks a free debrief.

01 / THE WORK

The investigation sequence

Configuration → resources → state → side effects. Start in order, or choose your failure.

5 incidents
  1. 01

    Configuration & auth

    Tokens rejected after deploy

    The same API token works locally and fails in production.

    Investigation brief

    Trace a request through configuration loading and token validation.

    35 min · HardOpen incidentDebrief after acceptance
  2. 02

    Resource lifecycles

    A connection pool that runs dry

    A read API starts healthy, then queues requests and returns 5xx under load.

    Investigation brief

    Follow a borrowed resource through successful and failing requests.

    35 min · HardOpen incidentDebrief after acceptance
  3. 03

    Cache isolation

    An order from the wrong region

    An order endpoint returns another region’s data after a traffic burst.

    Investigation brief

    Follow an ownership boundary across a repository and its cache.

    35 min · HardOpen incidentDebrief after acceptance
  4. 04

    Retries & idempotency

    One payment, two charges

    A checkout times out. The retry succeeds, but the customer is charged twice.

    Investigation brief

    Reconstruct what happened on both sides of an ambiguous timeout.

    35 min · HardOpen incidentDebrief after acceptance
  5. 05

    Concurrency & recovery

    Two workers, one job

    A redelivered queue job races with another worker and applies its effect twice.

    Investigation brief

    Reason about interleaving workers and recovery after a failure.

    35 min · HardOpen incidentDebrief after acceptance
Source files + logsVisible checks + private validationFree debriefs after accepted fixes

Curated from existing Buglyst labs. Fictional scenarios in isolated workspaces; no live production systems.

Hiring for this kind of work?

Choose relevant work samples and review the candidate’s checks, patch and explanation. These labs are public; candidates may have practised them.

Explore Hiring
Prefer a shorter session?Open today’s season rep