A complete application in a minute
Tailored resume and cover letter, ready to send.
JotPsych in New York City is seeking a senior software/product engineer to translate clinician and biller feedback into production features. You will own end-to-end delivery from customer conversations to UI, backend and database changes, while also shaping what to build based on user needs.
You’ll join a small team with daily AI-assisted development, participate in customer calls, and write evaluations showing a feature’s effectiveness on real notes and claims.
The decisions about what you build get made in a meeting you aren't in. You've shipped features you could tell were wrong the day the ticket arrived. You'd like to be the one who talked to the customer first.
JotPsych makes software for behavioral health clinicians. Our scribe has drafted more than 3.1 million patient notes and cuts administrative time by about 90%. We're now expanding from the note into the revenue cycle: billing, audit, prior-auth. We're a small team, and we build through AI coding agents all day.
You'll take features from a customer conversation to production, UI to backend to database to prompt. That half of the job you already know.
The other half is deciding what to build. You'll sit in on calls with clinicians and billers, then run your own. You'll write down what you think we should build and why, and we'll argue with it.
Early on we'll be fairly prescriptive. The first projects come from us, with our reasoning. You have the technical half, and we're going to teach you the rest: taste, craft, and how to manage a product. As your read on our users holds up, more of the deciding moves to you. We want that to happen fast, though not in week one.
The work swings. Some weeks you're forward deployed: out with a practice or on the phone with their biller, fixing their actual problem. Other weeks you're doing systems work, deep in the codebase on something every feature depends on. Most weeks land somewhere in between. Which one you get depends on what's needed that week.
A working prototype usually comes out of customer discovery, and engineering takes it to production. Our patient page took three days of engineering once the prototype was right. We want every surface to go like that.
You'll also write the evals for what you ship: the evaluations that prove a feature works on real notes and real claims. We'd rather hear it from an eval than from a clinician.
We work full weeks in the office, five days. Most of us also work about half a day on a weekend. It isn't a hacker house, and it is more than most jobs.
Everyone here is busy, so there's little hand-holding. You'll get direction and blunt feedback, and nobody has spare hours to sit beside you while you ramp. Look at your current week and your commute before you decide you want this one.