Open role
Frontend Engineer
Own what the staff sees. A dense professional tool for people who read boards for a living, closer to a trading terminal than a dashboard.
About Handoff
Handoff is the operating system for a college football program. One store holds real league data (rosters, recruits, play by play, historical outcomes) and the program's own work: who owns an evaluation, what state it is in, what evidence backs it, who approved it. On top of that sit the surfaces the staff actually live in, from a GM reading spend against on-field output to a position coach building a game plan, plus a layer of domain agents that do the operational work around an athlete.
The role
You own what the staff sees. That is not a styling job. This is a dense, professional tool for people who read boards for a living, closer to a trading terminal than a dashboard, and the interface carries a specific promise: every figure on screen declares whether it was observed or derived, and state is communicated by form rather than by colour.
You will work across TypeScript on the client and Python on the model side, because the scores rendered in a column are computed in Python and the boundary between the two is where most of the interesting bugs live.
What you will own
Monochrome by rule, a rationed accent, provenance carried by form, mono for machine-legible content. You extend it and hold the line on it across every surface.
League-wide, filterable, sorted by fit, instant. The transfer board is the screen a GM opens first and it should feel like it.
Streaming transcripts, visible tool calls, and the inspector showing which specialist is reading a board and what it queried. Multi-agent handoffs have to read as a change of author rather than one seamless narrator, because a reader who cannot see the seam will misattribute a claim.
Tables in the hundreds of thousands of rows, with sorting and filtering that never blocks a keystroke.
One hue, provenance on the mark, no dual axes.
What we are looking for
- Excellent TypeScript. Strong React and modern Next.js, and you understand the server and client boundary rather than fighting it.
- Working Python. You can read and modify the numerical code producing the figures you render, and debug across the boundary.
- You care about dense data UI. Table layout, virtualisation, tabular numerals, keyboard paths, and the difference between information density and clutter.
- You have a point of view on visual design and can hold a system rather than ship one-off screens.
- You write clear copy. In this product the words are design material, and a label that overstates provenance is a bug.
Bonus
- Streaming UI: SSE or ndjson, partial rendering, abort handling
- Data visualisation without a heavyweight charting library
- Accessibility in dense interfaces, including forced-colours and reduced-motion
- You have used an internal tool you loved and can say precisely why
How we hire
- 01Intro conversation with the founder (45 min)
- 02A design and build critique on a real screen from the product. We will ask what is wrong with it, then how you would fix it (90 min)
- 03A paid work sample: one real surface, end to end
- 04Two reference conversations
No algorithm puzzles. Bring something dense you have built.