About this role
You're past the part where everything is on fire. Your product works, and the interesting problems are now about craft and not breaking what people already depend on. You need a senior engineer to own meaningful surface area end to end and to be trusted with calls that don't need a meeting to authorize them. This is the role I'm looking for: the person others check with, not the one waiting to be checked.
What I'm looking for in you
- Small and technically serious; seniority means something real to you.
- You expect engineers to own the whole picture: the product intent, the system underneath, and the people around both.
- Engineers make calls without permission and leave code and teammates in better shape than they found them.
- No PM layer, no theater around ownership, enough trust to refactor the thing I keep tripping over instead of routing around it.
What you're building
Your product is real and in people's hands, so the work is equal parts shipping new surface area and keeping the existing system honest as it grows:
TypeScriptandNext.json the frontendNodeand/orGoservices underneath- AI where it earns its place, not as decoration
The role owns whole features from intent to production.
What you can expect from me
I can hold the whole picture at once: the product intent, the system under it, and the people who have to live with both:
- Ten years of shipping production web apps means I know which corners are safe to cut and which come back to bite.
- I've owned features from "should this exist" to "it's in production."
- I leave the code, the decisions, and the teammates in better shape than I found them.
- I make the call when a call is needed, without turning ownership into a performance.
