Team: Product

Reports to: CTO & CPO

Works closely with: CMO, Head of AI, UX Director, Engineering, Business development, Business intelligence, Clinical team, and genetic counselor.

Why This Role Exists

A mother notices that her two-year-old is developing differently than the children she sees on the playground. She brings it up at the next well-child visit. The pediatrician has fifteen minutes, a growth chart, a vaccine schedule, and a full waiting room. The concern is real and the visit is short, and what happens next depends almost entirely on how well that concern gets translated into something a clinical system can act on.

That translation is our product. Family Health Checker lets the family prepare before the doctor visit — symptoms, photos, family history—and hands the clinician something structured instead of an incomplete story told from memory. Face2Gene receives the case information from Family Health Checker—it helps the clinician review the phenotype findings, contextualize symptoms and HPOs, consider relevant syndromes and genes — cutting the time needed to prepare the clinical documentation that a referral or a lab test order actually needs.

There is a second, quieter failure this role exists to prevent. A health system agrees to a deployment in March, and by August nothing has been turned on, because nobody decided who sends the invitation before the visit or who acts on the output when it arrives. The product worked. The pathway never existed.

Building and growing these products is the job. You will be the person who decides what our products do, what they are allowed to claim, how a clinical insight earns a clinician’s attention, and how a family moves from a first concern to a real next step. You will not do it alone—our clinical, medical, and technology teams are there with you—but you will own it in the product, every day.

We are a small company, and that shapes the role in two ways. The surface is wide: you will touch the family experience, the clinician experience, deployment, and measurement, without a large product organization around you. In exchange you get the whole problem rather than a slice of it, and decisions that take a quarter somewhere else take a week here.

Working with Our Clinical Team

• You do not have to be a clinician to do this job well. Our Chief Medical Officer, our clinical team, and our genetic counselor are the clinical expertise, and they are close at hand.
• What we need from you is the ability to take a clinical question to the right person, ask it precisely, listen carefully, and turn the answer into a product decision rather than a meeting note.
• A clinical background is genuinely welcome, and it will make parts of this easier. It is desired but not a requirement.
• Curiosity, care with detail, and a habit of checking rather than assuming will get you far.

What You Will Own

Face2Gene – Clinician Decision Support

• Clinical decision support layer: How the product helps a clinician understand why a case merits further review, referral, testing, follow-up, or reassurance, and how prioritized genes, syndrome considerations, and phenotype findings are presented for clinician review.
• Report credibility layer: Showing which inputs drove a finding—photo-analysis-AI supported phenotype signals, symptoms, developmental observations—with source tags a clinician can inspect.
• Skeptical-clinician language mode: Clinical, evidence-aware wording used when a parent-originated summary reaches a clinician, so the first impression is a structured case rather than an app result.
• Pediatrician speed mode: A workflow that fits within a short visit and does not require the clinician to be a geneticist.

Family Health Checker – The Family Experience

• Parent-facing result language: Educational, useful without being alarming, and explicitly not a diagnosis.
• User guidance & safety: Photo guidance, consent moments, and managing points in the flow where a family is most anxious.
• Escalation messaging: Next-step language that clearly directs a family on what actions to take.
• Next-gen features: Help develop the next generation of visual-AI results, symptoms, and health history assessment.

Pathway, Deployment, and Integration

• Family Health Checker to Face2Gene handoff: Turning what a family entered into a package a clinician can work from, rather than a consumer report a clinician has to re-enter. Share and open rates are a product problem, not a marketing one.
• Digital front door: Making Family Health Checker straightforward for a health system to send before visits, embed in a portal, deploy by QR code in a waiting room, and white-label.
• Integration surface: PDF and structured export, FHIR document exchange, single sign-on, and the Epic pathway—working with engineering on what we build and with the health system on what they configure.
• Non-code deployment factors: Who owns the invitation, who acts on the output, what the security and privacy review will ask for, and how a Phase 1 is scoped so it can be measured without disrupting a stretched team.
• Routing and documentation: Configurable next steps across pediatrics, developmental pediatrics, genetics, telehealth, testing, and follow-up, with referral packets, draft letters of medical necessity, ICD-10 support, and requisition readiness as drafts for clinician review and editing.
• Laboratory ordering: Integrations and buyer logic that go with lab orders (distinct from health-system buyer logic).

Evidence, Quality, and Measurement

• Review representation: Representing product in clinical and regulatory review, user experience and usability testing, and AI model performance gates.
• Evidence standards: Defining the evidence bar for a claim before it appears in the product, and working with our AI and validation lead on what has to be measured before we can say something.
• Metrics & instrumentation: The metric tree from intake completion through clinician action to outcome capture, the instrumentation behind it, and dashboards a health system can read without asking us.
• Post-market business intelligence: Model alignment, escalation routing behavior, and user experience that has drifted outside its usefulness, friendliness, or compliance boundary.
• Advisory relationships: Engaging with clinical advisory and design partners to turn feedback into concrete product decisions.

Your First Year

First 60 days:

You have studied the workflows used by general and developmental pediatricians, and geneticists, and can describe the pathway from parent concern to next-step action in your own words. You have audited every parent-facing and clinician-facing screen against our user audiences and produced a prioritized list of potential gaps. You know the three places the pathway most often breaks.

By 4 months:

The product and engineering team has delivered an improvement you designed. A Phase 1 deployment is running with named metrics and a named owner on the other side. The clinical review has a defined, documented process with you being a part of it.

By 9 months:

A skeptical pediatrician who has never met us can use one of our products and understand within a minute what it is, what it is not, and what to do next. A new health system can go from agreement to live use on a documented path with a predictable calendar. The evidence bar for our clinical claims is enforced while providing a smooth user experience.

What We Are Looking For

Required

• Product Experience: 4+ years in product management, including at least one product owned from definition through to live use with real users. You remember what it cost to get it there.
• Healthcare Domain Knowledge: Working knowledge of healthcare. You have built software used in a clinical, diagnostic, or patient-facing setting, or can show that you learn a regulated, high-stakes domain quickly and enjoy doing it. (A clinical license/career is not required).
• Claim Judgment: Sound judgment about what software may claim. Ability to explain, without reciting policy, why a parent-facing result includes what it includes while a clinician-facing product shows deeper insight, defending that rationale under pressure.
• Expert Collaboration: Ability to take clinical, scientific, or regulatory questions to the right person, ask them precisely, and convert the answers into product decisions.
• Product Discipline: Comfort with being the person who says "no". Recognizing that some of your best work will be a release that did not ship in the form it was proposed.

Recommended

• Deployment & Interoperability: FHIR and HL7 v2 familiarity. Experience working with major EHRs (Epic, Oracle Health, athenahealth, etc.) in production environments. An Epic implementation background is a strong signal.
• Deployment Realism: Understanding that health-system rollouts involve stakeholders, security reviews, training burdens, and operational readiness, with a track record of planning for each.
• AI Output Mechanics: Understanding AI needs: calibration, rationale transparency, and knowing what success/failure looks like when required data is present or missing from training sets.
• Regulated Quality Systems: Experience working inside a regulated software quality system (design controls, intended use, risk management, human factors, change control, post-market surveillance). Familiarity with FDA thinking on clinical decision support software and predetermined change control plans is a major plus.
• Clinical Knowledge: Familiarity with (or ability to quickly learn) HPO terms, phenotype-driven test selection, letters of medical necessity, and payer documentation. Exposure to genetics, pediatrics, developmental pediatrics, diagnostics, or lab ordering is preferred.
• Workflow Economics: Ability to design to a time budget, evaluating what a workflow costs a clinic in minutes and who carries that operational cost.
• Metrics & Event Taxonomies: Experience owning a metric tree and event taxonomy from definition through instrumentation, evaluating impact through pathway change rather than features shipped.
• Advisory Management: Track record of running design partner or clinical advisory groups and translating insights directly into product changes.

About FDNA

FDNA builds on a simple observation: the information a family already has—what they have noticed, what they have photographed, what runs in the family—is clinically useful if someone organizes it properly.

• Face2Gene: Clinician-facing differential decision support for rare disease. Helps clinicians review phenotype findings, organize symptoms/HPO terms, consider syndrome possibilities and prioritized genes, and prepare documentation for referral, testing, and follow-up. AI stack includes DeepGestalt, FeatureMatch, and GestaltMatcher.
• Family Health Checker: Parent-facing and non-diagnostic. Helps families answer health/family history questions, provide photos for phenotype review, and produce a clinician-ready summary that makes the next visit more productive.

We work with health systems, pediatric networks, genetics departments, independent practices, and testing laboratories, and we contribute to a large-scale federally funded rare-disease research initiative.