Pager Health
Pager Health

Forward Deployed Product Engineer (Client Facing)

$250–285kUnited States (Remote)RemoteSeniorFull-time

Posted 18 days ago

The role in short

Embed with health plan partners to build and deploy production integrations and prototypes using Python, SQL, and healthcare interoperability standards.

Pager Health℠ redefines how members navigate to care and wellness, validated by clinicians and powered by AI.

We connect people to the right care at the right time, closing care gaps, reducing total cost of care, and improving health outcomes. Trusted by leading healthcare organizations since 2014, we serve 26 million members spanning the US and Latin America, backed by a licensed medical practice in all 50 states. Our unique balance of advanced AI and clinical expertise helps partners optimize medical spend without compromising clinical standards.
Learn more by visiting www.pagerhealth.com.

About the Role: 

We’re looking for a Forward Deployed Engineer to make Pager Health work inside our partners’ environments. You’ll work directly with health plan and payer technical teams to understand their systems, build the integrations and configurations that connect them to our platform, and prove out real use cases from first conversation through launch and early adoption. This is a hands-on engineering role that sits with the customer, combining the coding depth of a software engineer with the judgment of a trusted technical advisor.  

Reports into our Head of Engineering and partners closely with Sales, Product, Engineering, and Implementation. 

What You’ll Do: 

  • Partner with Sales during discovery to map a prospect’s architecture, data flows, and technical constraints
  • Build prototypes and proofs of concept that show how Pager Health solves a partner’s specific use case
  • Design and deliver integrations using APIs, data feeds, and healthcare interoperability standards such as HL7 and FHIR
  • Write production-quality code and configuration in Python, SQL, and other scripting languages to connect partner systems to our platform
  • Work side by side with partner engineering, IT, and security teams through implementation, testing, and go-live
  • Troubleshoot data, integration, and performance issues in live partner environments
  • Turn what you learn in the field into clear product feedback and reusable tools for Product and Engineering
  • Document solutions, integration patterns, and playbooks so future deployments move faster
  • Support security reviews, technical questionnaires, and RFP responses when deep technical detail is needed

What You Bring: 

  • Five or more years in software engineering, integration engineering, solutions architecture, or forward deployed roles
  • Strong coding skills in Python and SQL, plus experience with at least one additional language
  • Hands-on experience building and consuming REST APIs and working with JSON, flat files, and batch data exchange
  • Experience working in a major cloud environment such as AWS, Azure, or GCP
  • Comfort working directly with customer engineers and explaining technical tradeoffs to nontechnical stakeholders
  • Proven ability to own a problem end to end in ambiguous, fast-moving situations
  • Healthcare data experience strongly preferred, including HL7, FHIR, X12 Electronic Data Interchange (EDI) files such as 834 eligibility and 837 claims, or payer and provider systems
  • Working knowledge of HIPAA and secure handling of protected health information (PHI)
  • Willingness to travel to partner sites as needed (15–20%)

For Colorado, Nevada, New York, and Washington DC-based employment: In accordance with the Pay Transparency laws the pay range for this position is $250,000- $285,000. The compensation package may include stock options, plus a range of medical, dental, vision, financial, generous PTO, stipends for professional development, and wellness benefits.  Final compensation for this role will be determined by various factors such as a candidate's relevant work experience, skills, certifications, and geographic location. The range listed only applies to Colorado, Nevada, New York, and Washington DC.

At Pager Health, you will work alongside passionate, talented and mission-driven professionals – people who are building scalable platforms, solving critical enterprise-level challenges in health tech and providing concierge services to help individuals access the medical care and wellbeing programs they need.

You will be encouraged to shape your job, stretch your skills and drive the company’s future. You will be part of a remote-first, dynamic and tight-knit team that embraces the challenges and opportunities that come with being part of a growth company. Most importantly, you will be an industry innovator who is making a positive impact on people’s lives.

At Pager Health, we value diversity and always treat all employees and job applicants based on merit, qualifications, competence, and talent. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status.

Please be aware that all official communication from Pager Health regarding employment opportunities will originate from email addresses ending in @pager.com or @pagerhealth.com.  We will never request personal or financial information via email. If you receive an email purporting to be from Pager Health that does not adhere to this format, please do not respond and report it to security@pager.com.

Pager Health is committed to protecting the privacy and security of your personal information

Prep for this interview

5 questions likely to come up at Pager Health, each matched to a line in this posting.

  1. 1Cloud, deployment and security
    They wrote: “Experience working in a major cloud environment such as AWS, Azure, or GCP”

    How would you debug a deployment that works in staging but fails at the customer's site?

    How to answer

    Why they ask: Customer environments differ in ways you can't see. This tests method under pressure.

    1. Compare versions, config and environment variables
    2. Check network rules, proxies and certificates (common in enterprise)
    3. Look at resource limits and permissions
    4. Add the missing check to your install steps afterwards

    Tip: List the usual suspects and how you'd check each without full access.

  2. 2Integrations and APIs
    They wrote: “Design and deliver integrations using APIs, data feeds, and healthcare interoperability standards such as HL7 and FHIR”

    Walk me through connecting our product to a customer's internal system that has no documentation.

    How to answer

    Why they ask: This happens weekly in the job. They want a calm, step-by-step method.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. Agree on how failures get reported, and who fixes what

    Tip: Talk about finding the owner of the system first. The code is the easy part.

  3. 3Discovery and scoping
    They wrote: “Partner with Sales during discovery to map a prospect’s architecture, data flows, and technical constraints”

    A customer says “we want AI in our claims process.” What do you ask in the first meeting?

    How to answer

    Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.

    1. Map the current process: who touches a claim, in what order, with which systems
    2. Find the slowest or most error-prone step and ask what it costs them
    3. Agree on one measurable goal (for example time per claim, or error rate)
    4. Ask what data you can access, and who signs off on security

    Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.

  4. 4Data and SQL
    They wrote: “Write production-quality code and configuration in Python, SQL, and other scripting languages to connect partner systems to our platform”

    Write a query that finds each customer's first and most recent order.

    How to answer

    Why they ask: A quick check that you're comfortable with grouping, joins and window functions.

    1. Clarify the tables and what counts as an order (cancelled ones?)
    2. Use MIN/MAX with GROUP BY, or ROW_NUMBER() if you need the whole row
    3. Handle ties on the same timestamp, and customers with no orders
    4. Explain how you'd test it on a few known customers

    Tip: Say what you'd check in the data before writing the query: duplicates, time zones, nulls.

  5. 5Coding
    They wrote: “Work side by side with partner engineering, IT, and security teams through implementation, testing, and go-live”

    How do you keep quality high when you ship fast at a customer site?

    How to answer

    Why they ask: Speed is the job, but broken code at a customer is costly. They want your guardrails.

    1. Tests for the parts that touch customer data or money
    2. Code review even when it's fast, ideally by someone on the product team
    3. Feature flags and an easy way to roll back
    4. Clean up the shortcuts in the next release, and write them down

    Tip: Name the few checks you never skip, and what you skip on purpose.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

Similar roles at other companies

Pager Health

$250–285k · Remote

Apply