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.
More memory per build leaves fewer builds running at once.
Bazel builds need room to finish, while the fixed Kubernetes worker pool must keep the queue moving.
Who you’d be doing this for
“I've already told the team to expect the update today. Now they're asking whether to keep using the old workaround.”
Eero Moen · Document Administrator · a character in this brief
Maintains shared operational trackers and coordinates updates with the people who use them.
What is at stake
Six of 20 peak-hour builds restarted, leaving engineers waiting twice for unchanged code. You weigh more memory per build against fewer simultaneous builds in a worker pool that cannot grow.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- memory per build vs simultaneous build slots
- faster execution vs shorter queues
- local tuning vs a shared golden path
Why Superhuman
The hybrid monolith-and-microservices codebase sends hundreds of pull requests through a shared release feedback loop each week.
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)
- Has experience with large-scale build systems such as Bazel—or a very similar system used at large engineering organizations
- Work hands-on with build systems (such as Bazel or equivalents) and containerized, cloud-native infrastructure (Kubernetes) to make builds and pipelines faster and more reliable.
- 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.
- Know infrastructure as code (eg Terraform) and observability tooling, and use delivery metrics (DORA) to guide decisions.
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.
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.