Generalist Full-Stack Engineer

JotPsych makes software for behavioral health clinicians. Our scribe has handled close to two million patient encounters. The product reduces administrative time by about 90%. We're now expanding from the note into the full revenue cycle: billing, audit, prior-auth.

We're a small team. The work is hands-on. The next engineer we hire will shape a lot of what we ship next year.

---

The role

You'll be the fourth engineer on a small team. You'll ship user-facing features end-to-end, UI to backend to database to prompt, across JotPsych's clinical documentation, billing automation, and the shared intelligence layer underneath them.

The pattern we're standardizing on: a PM brings a high-fidelity working prototype out of customer discovery, you take it to production. Our patient-page surface took three days of engineering once the prototype was right. We want every surface to feel like that.

We don't want a specialist. We want someone who thinks in products, ships in days, and uses AI tools fluently enough that the boundary between "senior" and "founding" engineer starts to blur.

What you'd own in the first 90 days

• Ship 3 to 5 user-facing features on the clinical and billing surfaces
• Pick up design-adjacent frontend work that's currently bottlenecked on one person
• Contribute to the architectural unlock of our shared intelligence layer (we call it Cortex; it's load-bearing for the next two quarters of product velocity)
• Buy the team back time. Every test suite you write, every dev container you set up, every piece of infrastructure you harden lets the rest of us focus on harder problems
• Build your own judgment about our users and push back on decisions you think are wrong

Who you probably are

• 3 to 6 years of shipped production software. You've worked somewhere real. You know how prod breaks and how to fix it.
• Insight over experience. You form opinions fast and hold them lightly. You read a product and know what matters. This is the single thing we screen hardest for.
• AI-pilled. You use Claude Code, Cursor, whatever the next one is, fluently. You've noticed that the alpha from being technically savvy is declining and the alpha from having taste is growing, and you've been adjusting.
• Generalist by temperament. Backend one week, frontend the next, infra the week after. You're the engineer who doesn't need to be told what to pick up.
• Small-team excited. You're choosing us because six people moving fast is better than six hundred moving slow. You want to be in the room.
• NYC, 5 days/week at Brooklyn Navy Yard. Non-negotiable. We believe the in-person work we do in this specific office compounds, and we're not willing to dilute it.

Who you're probably not

• Someone who spent eight years at FAANG and wants a "startup sabbatical." That's not this.
• Someone looking for a title or a management track. This is an IC role on a team of ICs.
• Someone who only wants to do QA, only wants to do infra, or only wants to do backend. The team is too small for narrow specialists, and the work changes too fast.
• Someone who needs a designer to tell them what to build. The team is the designer.
• Someone who learned one stack ten years ago and stopped. The tools are changing monthly and we expect you to ride the curve.

Logistics

• Full-time, in-person 5 days at the Brooklyn Navy Yard. Non-negotiable.
• Competitive cash and equity, banded on experience and scope. We'll share specifics once we know we're talking.
• Full healthcare, standard benefits, and a desk with a view of the East River.