The posting
About Adit
- Adit replaces the pile of disconnected software that dental, optometry, chiropractic, and orthodontic practices in the US have been stuck with for decades. Calls, texts, patient forms, online scheduling, reviews, analytics, and payments run in one platform, integrated with the practice management systems clinics already use — Dentrix, Eaglesoft, Open Dental.
- Thousands of practices run their front office on us. Some have cut ten vendors down to one.
- Our users aren’t software buyers by training. They’re front-desk staff at a US dental clinic answering a phone with a patient standing in front of them. That constraint shapes everything we build — and it means part of this job is getting genuinely close to a customer you’ll rarely meet in person.
About the role
- You’ll own the backlog for the Patient Engagement squad — [N] engineers, a designer, and a QA engineer, based in [India / split across India and the US] — covering online scheduling, patient forms, appointment reminders, and two-way messaging. It’s the part of Adit that patients actually touch, and the part practices judge us on when a chair sits empty.
- Two things to be clear about up front:
- The team is dedicated to you, but doesn’t report to you. Engineers report through engineering management. Your authority comes from the quality and clarity of your backlog, not from a reporting line. If you’ve only ever directed work through org structure, this will be a hard adjustment. If you’ve earned a team’s trust by being the person who always has the answer ready, you’ll do well here.
- You report to the Director of Product in Houston. There’s no product manager between you and product leadership. You’ll help shape the quarterly plan for your area rather than inherit it, and you’ll own the stakeholder relationships that come with it — most of them 10.5 hours behind you.
What you’ll do
- Own and order the Patient Engagement backlog, keeping it transparent and current so everyone knows what’s next and why.
- Build the quarterly plan for your area with the Director of Product — you bring the proposal and the evidence, and you defend it.
- Write user stories and acceptance criteria that engineers can build from and QA can test against, with the edge cases already thought through. Written clarity matters more here than in a co-located role: your specs have to survive a night without you.
- Run backlog refinement, sprint planning, reviews, and release readiness alongside the engineering lead.
- Get close to US dental practices through the evidence available to you: recorded support and sales calls, ticket patterns in Zoho Desk, account and churn signals in Zoho CRM, and scheduled conversations with practices and with our US customer success team during overlap hours.
- Work PHI and HIPAA constraints into scoping from the start, not as a compliance review at the end.
- Manage dependencies on practice management system integrations, where release timing isn’t entirely ours to control.
- Bring evidence to prioritization: product usage, support ticket volume, churn signals, and what the sales team keeps losing on.
- Define success measures before a feature ships, then check whether it delivered — and say so honestly when it didn’t.
- Scope new EHR integrations. Read the vendor's API documentation, learn how practices actually use the EHR day to day, then map it against our platform to make sure the feature holds up in real workflows
- Run a weekly meeting with dental vertical stakeholders — sales, support, customer success — to track what the market needs right now and work through the client bugs piling up in the queue.
- Protect the overlap window. The hours you share with Houston are for decisions and unblocking, not status reporting.
What we’re looking for
- 3–5 years in a product owner, product manager, or business analyst role on a software product, including at least two years working directly with an agile delivery team.
- A track record of shipping — features you scoped, sequenced, and saw through to release, with a view on what happened after.
- Experience working with a distributed or offshore-onshore team, and a real answer for how you kept alignment across a time gap.
- Exceptional written communication. Most of this job is making complex things unambiguous in writing, for people who are asleep when you write it.
- Comfort influencing a team you don’t manage and stakeholders you rarely see in person.
- Comfort building your own analysis. You can pull a ticket export or a usage extract into a spreadsheet, find the pattern, and turn it into an argument. Basic SQL is a plus, not a gate.
- Enough technical fluency to have a real conversation about APIs, third-party integrations, and technical debt, and to push back when an estimate doesn’t add up.
- Willingness to work shifted hours to overlap with US Central Time.
- We don’t require a specific degree. If you’ve done this work, we want to talk.
Nice to have
- Products built for a US or Western market, especially where you weren’t in the same country as the customer.
- Healthcare, healthtech, or another regulated environment — HIPAA, SOC 2, PHI handling.
- SMB or multi-location customers, where the buyer and the daily user are different people.
- Products built on third-party integrations you don’t control.
- Discovery or delivery work on AI-driven features.
- CSPO, PSPO I/II, or SAFe POPM certification.
Tools we use
- Asana for delivery and roadmapping
- Zoho Desk for support and Zoho CRM for the sales and customer picture
- Google Workspace for docs, email, chat, and meetings · Adit itself, which you’ll use daily.
- If you’ve run backlogs in Jira, Linear, or Azure DevOps, you’ll be fine.
- We care that you can run a backlog, not which tool you ran it in.
