Product Engineer
JotPsych · Washington, DC/Remote (US - East Coast)
Mission
Behavioral health is more important than ever. But almost half of behavioral health clinicians report that they spend 5+ hrs per day on administrative work. Some of that admin work happens “in the room,” but no matter where it happens, we believe it’s too much.
JotPsych’s mission is to defeat admin work and let clinicians practice human-centered healthcare.
We already reduce note-taking time by 90%. But we’re just getting started. Billing, appointment scheduling, e-prescriptions, and more are right around the bend.
JotPsych: Background and Context
JotPsych | Spend less time on patient notes with our behavioral health scribe software
- 🛗 Elevator pitch: JotPsych software listens to behavioral health providers while they talk to their patients (with consent, of course). A few seconds after the patient leaves the room, the provider already has a robust draft of the medical note waiting for them. Super customizable, easy to integrate with any current workflow. Medical note completely done and submitted for insurance reimbursement before the next patient enters the room. No more typing during the session, no more catching up on notes at home in the evening. Eye contact and peace of mind. 🧘
- 🚀 JotPsych is a post-revenue, seed-stage software startup backed by Base10. The product currently reduces administrative time for behavioral health clinicians by 90% and is expanding to encompass other clinical and administrative workflows. You can learn more about JotPsych by visiting the website, reading up on our fundraise announcement, and/or by listening to the podcasts below:
- ⛓️ JotPsych was founded by Nate Peereboom and Jackson Bierfeldt. Nate’s mom was a nurse practitioner, so he grew up in the shadow of overwhelming medical documentation. Jackson is a language and audio nerd, and when GPT-3 hit the market, he knew something could be done here. The company is currently 10-15 FTE.
- 🚀 JotPsych has scribed for 1.5m+ patient encounters.
- Check out Who and how we hire
Role
You’ll take rough product ideas and ship them end-to-end — translating messy clinic workflows into smooth, intuitive software. You’ll work across our stack (React + Python + Postgres + AWS) to bring new features from prototype to production, balancing craft with velocity.
This is a promotion-track role: we’re hiring someone who can grow into a pod lead within 12 months — mentoring others, defining dev patterns, and shaping how product gets built at JotPsych.
You will work on
- Feature delivery: Own the full lifecycle from design doc → deploy.
- Product iteration: Partner with designers, clinicians, and founders to ship user-facing improvements weekly.
- System glue: Integrate LLM and backend microservices into cohesive experiences (streaming outputs, async jobs, realtime updates).
- Internal tooling: Build dashboards, QA views, and admin utilities that help clinics and our team operate faster.
- Technical mentorship: As we grow, guide junior engineers on clean abstractions, testing, and debugging.
Why this role is special
| Theme | Why it matters | Talking points |
|---|---|---|
| AI‑native backend | Few backend roles blend classic systems work with evaluation‑driven LLM services. | Design LangGraph services, maintain RAG pipelines, ship eval frameworks. |
| Healthcare‑grade reliability | Clinicians depend on us in real time. | Event‑driven microservices, graceful degradation, HA Postgres + Mongo, immutable S3 storage. |
| Data architecture & frameworks | We balance structured medical data with fast AI workflows. | Shape encounter & billing schemas; craft internal libraries that unblock the whole team. |
| DevOps you own | Small team ⇒ engineers ship infra as code. | Pulumi/Terraform on AWS (ECS, Step Functions, SQS), automated blue‑green deploys, observability. |
| Compliance baked‑in | We handle protected health information every day. | Policy‑as‑code, secure defaults, well‑logged audit trails. |
| Fast growth, real autonomy | 10 people now — you’ll be engineering team member ~6. | Architect today, see it serve clinicians next week. |
Ideal Candidate
- 5–8 yrs professional engineering experience, including 3 + yrs building production web apps (React, TypeScript, Python/FastAPI or similar) at a startup pace.
- A bias toward action — you prototype fast, cut scope intelligently, and measure what matters.
- Full-stack fluency: you’re happy across the stack and can reason about APIs, UX, auth, data models, cloud services, and databases (Postgres, Mongo).
- Experience shipping modern AI systems — ideally involving LLMs, audio-pipelines (including ASR), or other real-time data flows.
- A pragmatic approach to testing, CI/CD, and observability — you build for reliability but know when to bend for speed.
- Comfort working in ambiguity and making product trade-offs without perfect specs.
- Curiosity about healthcare, language models, and how software can make clinicians’ lives easier.
- Bonus: familiarity with FHIR, audit logging, or insurance clearinghouses.
Tech We Use (and you’ll shape)
Python · Flask · FastAPI · Celery
Postgres · MongoDB · Redis · S3 (WORM)
AWS ECS · Step Functions · SQS · Kinesis
LangChain / LangGraph · OpenAI · Anthropic
Pulumi · OpenTelemetry · Supabase
(Experience in Go/Rust/GCP? We probably aren’t going to use those right now, but who knows? Teach us.)
Timing and location
We want to hire as soon as possible. We aim to complete the hiring process within a few weeks of your application.
🏡 🚞 This full-time role is officially remote, but with a strong preference for candidates located in Washington, DC (our HQ) or New York/Baltimore/Philly (quick train rides away).
For folks outside DC, we expect once-per-month travel to the office for the first 3 months, and then at least quarterly travel thereafter. Check out JotPsych HQ: A Guidebook for details.
Compensation
Compensation includes the following benefits:
- 🌎 Deeply meaningful work — you’re changing how behavioral health happens! Our customers literally hug us when they meet us at conferences and tell us how we’ve “changed their lives.” 🥲
- 🏥 Healthcare (we offer top-of-the-line health insurance)
- 💵 Cash (~$150-250k)
- 🧱 Material equity (~0.75%)

Application
At JotPsych, we know your time is valuable — and that thoughtful, creative engineering takes real energy.
That’s why we compensate all candidates for completing our technical stages at $100/hour.
We want this process to feel like a collaboration between peers, not a test.
Our hiring process is intentionally rigorous but transparent. Each stage is designed to mirror how we actually work: tackling ambiguous problems, reasoning clearly, and shipping solutions that matter.
Here’s it the process:
-
Submit the Form
Complete this form to introduce yourself and explain why you want to work at JotPsych.
Keep it short (≤ 200 words) but professional. Include your contact info, resume, LinkedIn, and portfolio / GitHub.
Important: Next to your first name, you must include a ninja emoji (🥷) — because you’ll be jumping and slicing through everything.
-
Case Interview (5–10% of applicants)
Selected candidates will receive a short technical case. Plan for about 3 hours of work.
You’ll get all necessary materials in advance, but be ready — it’s designed to challenge how you think, not just how well you write code.
At the end, you’ll submit a Loom video or screen recording showing your work in action and walking us through your process.
-
Behavioral Interview (45 min)
After the case, you’ll meet with our founders or tech leads.
We’ll dig into your past engineering experiences, your problem-solving patterns, and what motivates you.
-
Technical Interview (2.5 hours) This comprehensive session combines architecture review, debugging, and product critique to assess your full-stack engineering judgment.
- Part 1: Architecture Review (60 min) — You'll review a real or anonymized JotPsych service diagram or code snippet, identify strengths and risks, and propose one refactor with trade-offs.
- Part 2: Debugging Challenge (60 min) — You'll join one of our engineers in a shared environment to debug a small broken script or feature, forming hypotheses and isolating variables.
- Part 3: Product Critique (30 min) — We'll show you a prototype or in-progress feature and you'll share what feels unclear, overbuilt, or missing — and outline how you'd improve it in a week.We're testing technical judgment, problem-solving process, product intuition, and how you balance UX, tech, and time — not speed or perfection.
-
Co-Working Day
A small group of finalists are invited for a full-day on-site at our DC HQ (we’ll fly you out if you’re not local).
You’ll collaborate on a live problem, pair-build with our engineers, and join structured evening conversations about product direction, strategy, and vision.
We’re testing for speed, collaboration, and creative insight — not polish.
-
References (6×)
We take references seriously. Expect us to speak with ~six people who’ve worked closely with you.
Team Experience:
We deeply value the experience of gathering and working together, in our hometown but also elsewhere. Below is a snapshot of our “out of town” excursions.
Every year, we travel to Cleveland for “Summer Camp”. Here are some shots from 2024 and 2025. We rented a house, made huge strides in product development/sales, and secured our first paid customer. Plus, we did some great bonding.