Product Builder

JotPsych

New York (NY)

On-site

USD 170,000 - 210,000

Full time

20 hours ago
Be an early applicant

A complete application in a minute

Tailored resume and cover letter, ready to send.

Get past ATS filters

Benefits offered by this job

Full healthcare
Desk with East River view
Equity

Job summary

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.

Qualifications

  • A senior product person. Product, design or product ops. You read users well and you decide quickly.
  • Already building. A live app with users, a merged pull request at your company, a tool your team uses that nobody asked for. Bring it.
  • Able to debug it. When something the agent wrote breaks, you find the cause before you prompt again.
  • Clear about what you didn't build. We have more good ideas than we can build. Being able to say why you turned one down counts for a lot here.
  • Learning fast, with someone to show. There's a technical thing you couldn't do a year ago and can do now.
  • Sharp. You find the flaw in an argument, your own included.
  • Fine with hard review. Engineers will rewrite your code. You read the diff and ask why.

Responsibilities

  • Talk to clinicians and billers, identify a problem worth solving, and build the first working version.
  • Take the feature toward production with engineering review and iterative changes.
  • Own the end-to-end path from discovery to shipped feature, growing monthly.
  • Write evals to prove a feature works on real notes and real claims.
  • Define what makes a good note or clean claim in collaboration with engineers.

Job description

Product Builder

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.

The role

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.

Where engineers come in

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.

How we work with AI

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.

What you'd own in the first 90 days
  • Take one customer problem from the first call to a shipped feature
  • Merge your first pull request early. Keep going until they come back with few comments
  • Learn how our system fits together, well enough to know what you shouldn't touch yet
  • Write the evals for one surface
Who you probably are
  • A senior product person. Product, design or product ops. You read users well and you decide quickly.
  • Already building. A live app with users, a merged pull request at your company, a tool your team uses that nobody asked for. Bring it.
  • Able to debug it. When something the agent wrote breaks, you find the cause before you prompt again.
  • Clear about what you didn't build. We have more good ideas than we can build. Being able to say why you turned one down counts for a lot here.
  • Learning fast, with someone to show. There's a technical thing you couldn't do a year ago and can do now.
  • Sharp. You find the flaw in an argument, your own included.
  • Fine with hard review. Engineers will rewrite your code. You read the diff and ask why.
Who you're probably not
  • Someone whose week is status updates, alignment meetings and stakeholder decks. We're too small to need that job.
  • Someone who wants engineers to build what they describe.
  • Someone who takes "this isn't safe to ship" personally.
  • Someone who ships AI output without reading it closely first.
  • Someone looking for a title or a team to manage. This is an IC role on a team of ICs.
The pace

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.

Logistics
  • Full-time, in person five days a week at the Brooklyn Navy Yard. Non-negotiable.
  • A base salary of $170,000 to $210,000 a year, plus equity.
  • Full healthcare, standard benefits, and a desk with a view of the East River.
Get your free, confidential resume review.

or drag and drop your file here.

Similar jobs

Similar jobs worth comparing

Product Engineer
Product Engineer

JotPsych • New York (NY)

On-site
USD 170,000 - 210,000
Healthcare
Equity
Desk with East River view
+1
Engineering
Engineering

JotPsych • New York (NY)

On-site
USD 170,000 - 210,000
Full healthcare
Equity
Desk with East River view
Engineering
Engineering

JotPsych • New York (NY)

On-site
USD 170,000 - 210,000
Equity
Healthcare
Desk with East River view
Founder's Associate
Founder's Associate

JotPsych • New York (NY)

On-site
USD 110,000 - 140,000
Generalist Full-Stack Engineer
Generalist Full-Stack Engineer

JotPsych • New York (NY)

On-site
USD 170,000 - 210,000
Equity
Full healthcare
Desk with East River view
Product Engineer Intern
Product Engineer Intern

JotPsych • New York (NY)

On-site
USD 28,000 - 40,000
Generalist Full-Stack Engineer
Generalist Full-Stack Engineer

JotPsych • New York (NY)

On-site
USD 120,000 - 180,000
Healthcare
Equity
Desk with East River view
Product Engineer
Product Engineer

Harper • San Francisco (CA)

On-site
USD 140,000 - 280,000
Uber commuter benefits
Breakfast, lunch, dinner provided
Snacks, drinks and coffee daily
+2
Founding AI-Native Product Engineer — Hybrid NY
Founding AI-Native Product Engineer — Hybrid NY

Ellis • New York (NY)

Hybrid
USD 180,000 - 240,000
Competitive equity
Comprehensive benefits package
Flexible PTO
+3
Chief of Staff
Chief of Staff

JotPsych • New York (NY)

Hybrid
USD 130,000 - 160,000
Health and dental coverage
401(k) plan
Laptop setup stipend
+1