Frontend Engineering
The interface is what the client actually sees and judges the whole project by — it has to stay fast and predictable under real usage, not just look right in a design review.
You'd work directly against a real design system and a real backend, not a static handoff file — close enough to the rest of the project to catch problems before they ship.
What you'd work on
- Build interfaces that hold up under real data, not placeholder content
- Work directly with design and backend, not through a handoff document
- Care about performance and accessibility as default, not an afterthought
- Fix the small rough edges most teams ship around
What we look for
- Ownership. You see a task through to done, not just your slice of it.
- Direct communication. You can explain a decision to a client who isn't technical, without hiding behind jargon.
- Craft. You care about the code nobody's reviewing as much as the code everyone sees.
- Curiosity. You pick up a new stack or protocol when the project actually calls for it.
How we work
No layer of managers between you and the client — you talk to them yourself, the same way founders do. We don't run a fixed hiring pipeline: if this role fits how you think, apply below and tell us what you'd actually bring to it.