Healthspan is the world's leading digital longevity clinic. We help forward-leaning people add healthy years to their lives using the same evidence that's shaping the field — not the version that's been flattened into a supplement ad.
We're hiring the engineer who will build the surfaces that work gets delivered through. Not a frontend engineer in the traditional sense. The role we're describing doesn't have a settled title yet, so here's the honest version of what it is.
The role
Most companies hire a frontend engineer, hand them tickets, and wait for components. We're not doing that.
We're looking for an engineer who treats the product surface as a craft problem. You'll sit on the engineering team, report to the CTO, and partner closely with the project manager who runs the roadmap. Designs will come to you — but the moment a design hits an edge case the mock didn't cover, you don't file a ticket and wait. You make the call, ship it, and flag what you decided.
Your job is to understand product's intent — well enough that you can contribute opinions, push back when something is off, and translate ambiguous handoffs into shipped surfaces without losing the thread.
This is a primarily frontend role. The leverage in it is AI. Work that would have taken a frontend engineer 90 days last year takes you a week. Cursor, Claude Code, MCP, agent workflows — these are the difference between this role and the version of it that existed in 2024. We're hiring someone who already lives at that pace.
Patient portal, intake flows, lab interpretation surfaces, provider tools, marketing site, internal ops dashboards — code you write touches all of it. You ship the components, the polish, the integration work, and the AI features inside the product itself.
What you'll actually do
- Take designs and ship them. Designs come from the design team via the PM. You build them in code at production quality, on the timeline the PM scopes with you. Speed and craft, not one or the other.
- Handle edge cases without blocking. If a flow has a state the mock didn't cover, you make a defensible call and ship it. Empty states, error states, loading states, weird data shapes from the EMR — you resolve them and surface what you decided so the team can adjust if needed. The job is to keep the work moving.
- Use AI as a force multiplier, not a novelty. Cursor, Claude Code, MCP, in-house agents. The frontend that took 90 days takes a week — that's the bar. You're not impressed by your own workflow; you've been operating this way for a while.
- Build AI features inside the product. Lab interpretation drafts for clinicians, patient-facing explainers, intake summarization, internal automations. You have opinions about what the model should never do, when a human is required in the loop, and how to design for hallucinations.
- Contribute to product, even though you don't own it. Understand what's being built and why. Push back when something is going to land badly. Suggest the version that's 80% as costly and 95% as good. Earn the trust that gets you pulled into the conversation earlier.
- Hold the line on craft. Patient-facing surfaces feel premium and trustworthy. Internal tools feel fast. Loading states, empty states, error states — all deliberate. The product is a reflection of the medicine.
- Take HIPAA seriously without being slow. Audit trails, role-based access, careful error handling, secure data flows. You don't need to be a compliance expert — you need to notice when something needs care.
Who this is for
You've probably been underemployed by the conventional structure of an engineering team. You move faster than your tickets allow.
You're a real frontend engineer with real taste. Fluent with TypeScript, React, Next.js, Tailwind. Comfortable with auth, APIs, deploys. You can read a Figma file precisely, and when the file runs out, you can finish the thinking yourself. Your portfolio looks good — not generic-AI good, actually good.
You operate at native AI speed. Cursor, Claude Code, MCP, whatever dropped last month. You've shipped agents and AI features in production, not demos. You can read and write code well enough that "I'll just build it" is your default response to a missing tool. 5–10x throughput vs. a year ago is the floor, not the ceiling.
You're a strong individual contributor who plays well with a team. You can take a design and a brief and run with it without needing to renegotiate scope every day. You ask the right questions early so you don't have to ask them late. You make the PM's job easier, not harder.
You've done it somewhere visible. You can point to a company or a real product and show the work. A flow you owned, a surface you shipped, a system that's still running. Bonus if it's healthcare, DTC, or anywhere conversion and trust both matter. We're not interested in theory. Show the work, at a real company, with real users.
You have a feel for product copy. You don't need to be a copywriter, but when a button label or empty state is missing, you can write something simple that doesn't break the brand. You notice when microcopy is off and either fix it or flag it.
You care about longevity science, or you care enough to get rigorous about it quickly. This is health. The work has to be right before it's fast.
Who this isn't for
- People who freeze when a design has gaps
- People who ship but have no taste
- People who treat AI as a feature checkbox instead of a daily tool
- Anyone whose best work lives inside a Linear board
- Anyone who needs the spec to be airtight before they start
- Anyone whose engineering experience is theoretical, agency-side, or unverifiable
What we offer
- A seat on the engineering team at a category-defining clinic, with the autonomy of a much smaller company
- Equity commensurate with the scope
- A CTO, PM, design, and clinical team that respects the craft and will give you room to run
- Compensation that reflects the fact that one engineer doing this well is worth more than a team doing it the old way
To apply
Send us something you've built and the experience it produced. Not a resume summary — the actual thing. A product surface, an AI feature, an internal tool, a flow with the metrics attached. If the work is proprietary, describe it in enough detail that we can tell whether you did it. Name the company. Name the metric.
One link. One paragraph on what it does and what it moved.