Forward-Deployed Product Manager

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.

The constraint we're hitting isn't engineering capacity. It's the throughput of high-fidelity product insight from real customers into real specs. That's the role.

---

The role

You're not a traditional PM. You're not a designer. You're not exactly an engineer. You're the person who closes the loop between what's actually happening in clinicians' offices and what gets shipped.

You'd own the front of our product process: deep customer discovery, then high-fidelity front-end prototypes you build yourself, then a clean handoff to engineers who can move fast because the spec is right. Our patient-page surface took three days of engineering once the prototype was right. We want to apply that pattern to every surface.

You'll spend serious time with customers. You'll be on calls with everyone who churns. You'll go on shadows. You'll know the forms problem, the JotMeet problem, the JotRX problem at a level no one else on the team does, because you'll be the person who actually talked to the people experiencing them. Then you'll come back, build a prototype that solves it, and hand the engineers something they can ship.

What you'd own in the first 90 days

• Take 1 to 2 product surfaces (forms is the leading candidate) end-to-end: customer interviews, working front-end prototype, engineer handoff, ship
• Build the customer-call cadence: every churn gets a call, every beta has a follow-up, every angry customer hears from a human within a day
• Establish the "high-fidelity prototype before engineering" pattern as the default for every new product surface
• Push back on the founders and the engineering team when we're about to ship something the customers won't love

Who you probably are

• You can vibe-code a working front-end. Not Figma mockups, actual interactive prototypes the engineers can grab. You use Claude Code, Cursor, v0, whatever works. If "vibe-coding a working dashboard in three hours" sounds normal to you, we want to talk.
• Customer comfort is your superpower. You enjoy hard customer conversations. You'll volunteer to call the angry person. You can hold the room with a clinical professional and not need notes after.
• Insight over experience. You read a product and know what matters. You see structural bugs before they ship. You're the person on a team who keeps asking the obvious question that turned out to matter.
• AI-pilled, agency-pilled. You've noticed that the alpha from being technically savvy is declining and the alpha from having taste, agency, and good context arrangement is growing. You've been adjusting.
• Small-team excited. You want to be in the room where products are decided, not handed a backlog.
• 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

• A traditional PM who lives in roadmap docs and JIRA. We don't have a PM org chart. The work is the artifact.
• Someone who needs an engineer to translate their wireframes. You build it, or you're not the right person for this.
• Someone who finds customer calls draining or distasteful. You'd be on a lot of them.
• Someone allergic to writing code. You'd be writing code most weeks. You'd just be writing it in front of a customer or for an engineer to take from you.

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.