A complete application in a minute
Tailored resume and cover letter, ready to send.
JotPsych in Brooklyn Navy Yard is building software for behavioral health clinicians. Our scribe has drafted millions of patient notes and we’re expanding into billing, audits, and prior-authorization using AI-powered coding agents.
As Product Builder you will own the end-to-end path from customer discovery to a shipped feature, talking to clinicians and billers, iterating with engineers, and learning why changes are needed.
Brooklyn Navy Yard, Full-time
You've done product for years, and lately you've been building. A prototype over a weekend. An internal tool nobody asked for. Then Monday comes and you're writing the spec for something you already made, and waiting for an engineer to make it again.
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.
Here the prototype is the spec. That's already how we work: a working prototype comes out of customer discovery, and engineering takes it to production. Our patient page took three days of engineering once the prototype was right.
You'd run that whole path. You talk to the clinicians and billers, find the problem worth solving, and build the first working version. Then you take it as far toward production as you safely can, with an engineer reviewing your work and telling you why they changed it. We expect that to be further every month.
This is healthcare. Anything that touches patient data gets hardened by an engineer before it ships, and sometimes the answer is no, or not yet. You'll be told why.
We expect you to learn the reason, so you don't get the same no twice.
What you're trusted to ship on your own starts small and grows with your pull requests.
We use agents to build, and we use them to think before we build. Before something gets built here, somebody has gathered what customers said, laid out the options, and written the long version of the decision. Some of us print it and read it on paper.
We'll ask how you use AI in your own work. We're looking for people who use it to slow down and think before they let it build.
Nobody here ships agent output unread.
You’ll also write evals: the evaluations that prove a feature works on real notes and real claims.
Deciding what a good note or a clean claim looks like is product work. Here you write that down as a check an engineer can run.
We work full weeks in the office, five days. Most of us also work about half a day on a weekend.
Everyone here is busy, so there's little hand-holding. Engineers will review your code and answer a good question. Nobody is going to run a course for you. The technical side you pick up from your own pull requests and from what the engineers change in them.