The setting
makes , a collaborative document application with tables, for teams that start by building a tracker in a doc and end up running a real application.
Disposable release rehearsals promise independence but multiply the combinations that must remain meaningful.
Engineers want freedom to combine document states and service versions, while the platform must keep rehearsal costs and results predictable.
Who you’d be doing this for
“Our annual planning doc sits untouched for months. When everyone comes back, I'm the one who has to explain anything that behaves differently.”
Azmera Tadesse · Document Administrator · a character in this brief
Oversees operational trackers that remain in use across application releases, including documents reopened after months of inactivity.
What is at stake
Product engineers cannot independently rehearse nine of 14 proposed release experiments in shared staging. You must weigh flexible combinations of old state and new code against repeatable results and a bounded compute bill.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- version freedom vs. reproducible evidence
- fast provisioning vs. compute limits
- realistic histories vs. customer data isolation
- local usefulness vs. central platform consistency
Why Superhuman
Long-lived document databases and a hybrid monolith-and-microservices codebase make a passing build different from evidence that an older tracker survives a release.
Written with these in mind
Not your kind of problem? 49 more at Superhuman, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Superhuman. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Software Engineer, Developer Experience (Full-Stack) (opens in a new tab)
- Build full-stack internal tooling and self-service platforms—front-end interfaces and back-end services alike—tailored to how the Docs team actually works.
- Engineering Manager, Release Engineering (opens in a new tab)
- Reduce friction for product engineers: cut build and test times, eliminate flaky tests and pipelines, and offer self-service paths so teams can ship without waiting on us.
- Partner with SRE, Infrastructure, and Security to keep the delivery platform reliable and compliant, including supply chain security, artifact integrity, and access controls.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on moving faster inside a system others depend on.
Telemetry-dependent Maintenance changes wait on shared integration capacity and reach validation later than other releases.
You have to weigh a narrow pilot that ships quickly against a reusable path that avoids one-off environments.
Agent-authored changes are passing CI while dependency failures emerge only after rollout.
You must weigh realistic pre-merge validation against the cost and control of disposable environments.
Patients are leaving booking after finding clinicians whose schedules looked promising in search.
You must weigh faster availability experiments against the reliability of live booking traffic.
The same setting, from another role
Each is set around Superhuman’s Superhuman Docs, written for a different role. They’re separate briefs, not the same scenario.
Nine of 14 replacement owners needed the tracker builder's help despite having access.
You weigh guidance that makes the first update safe against preparation that busy builders will actually finish.
Eight of 12 administrators misread who gains access after moving a document.
You must weigh a usable confirmation against suspending moves whose disclosures cannot be undone.
Seven of 12 new collaborators never reached a live edit in a shared tracker.
You need to weigh preserving useful orientation against taking people straight into their work.