Forward Deployed Engineer

About The Company

What’s Promptly in a nutshell

Promptly is building the first patient-centered global evidence network, offering real world data sharing and monetization capabilities. Together with a selected network of Partners, we generate new knowledge from harmonized datasets, augmented with the collection of longitudinal patient-reported data and patient-generated digital biomarkers within a secure and privacy-preserving environment.

We answer the question – is this patient treatment the best it could possibly be?

What’s Our Purpose

We exist to empower every patient and every health organization on the planet with evidence on the outcomes of care!

Why do we get up in the morning? Well, most healthcare professionals have chosen to work in healthcare driven by their desire to make a difference in patients’ lives. And so have we! We have chosen to follow this calling by addressing the biggest problem in healthcare: the lack of real-world evidence on the outcomes of care.

For us, society denying patients better care due to lack of access to data is unethical, in a world where technology improved so many aspects of our world. Making the right evidence available to healthcare organizations to help prevent one lost life, one care complication, one failed treatment is the moral obligation that big tech companies have – it’s our Hippocratic Oath.

At Promptly, everything we do is driven by our core purpose: to promote better healthcare at lower costs for patients every day, by making health outcomes available.

About The Role

As a Forward Deployed Engineer at Promptly, you embed directly with clients and co-create alongside them. You have the full latitude to develop new data products, design and test AI-powered solutions, and build workflows that didn't exist before you arrived, within the Promptly platform. Clients don't just use the product; they shape it, with you as the person who makes that happen. This is a builder role. Not a support role, not a success role, not an advisory role. You are here to build.

Our clients are hospital networks, national health systems, disease registries, research consortia, and life sciences partners. That means the workflows you build sit inside live clinical care - a clinician's afternoon list, a patient's follow-up, a registry's submission deadline. It also means the thing you are actually engineering is participation: whether clinicians and patients find it worth their time to contribute data at all. Get that right and everything downstream becomes possible. Get it wrong and no amount of engineering recovers it.

You are technically deep, fast, and curious. You reach for code before slides. You treat a client engagement like a product development cycle. And what you build with one client becomes the foundation for what Promptly ships to the next.

To be clear about what we mean by that: we are not looking for a software engineer who is interested in healthcare. We are looking for someone who knows healthcare from the inside — who has sat in the governance meetings, earned a clinical team's trust, and understood what a board actually needs to see — and who also builds.

What You'll Do

Reporting to the Head of Forward Deployed Engineering, your time will be spent overwhelmingly on client work rather than internal process. As a rough shape: around 60% building and co-designing directly with clients, including regular time on site; around 20% in the sandbox, prototyping and hardening what you have built into something the next engagement can reuse; and around 20% on engagement scoping, governance, and the standing loop back into product and engineering.

Here Is What That Looks Like In Practice

• You work side by side with clients to scope, design, build, and test new data products on top of the Promptly platform. You own the full cycle, from first conversation to something live.
• You co-design with clinicians and patients at the point of capture — sitting in clinic, understanding why a form goes unanswered, and building the version that gets used. Completion and cadence are engineering outcomes you own, not someone else's adoption problem.
• You model real clinical data: mapping partner source systems into OMOP, designing PROMs and registry structures, and building phenotype and concept definitions that hold up when the next client reuses them.
• You develop AI-powered solutions with clients, using the platform's capabilities and your own tooling to solve problems they didn't think were solvable yet.
• You build in the sandbox before the real data is ready — using synthetic and multimodal cohorts to prototype, prove feasibility, and give a client something working to react to in weeks rather than quarters.
• You create custom workflows, automation logic, and integrations that fit each client's operational reality. You don't configure templates; you build things that are genuinely new.
• You work across modalities — structured records, patient-reported data, device and wearable telemetry, imaging, and genomics — and across governance regimes where raw data does not move.
• You treat every client engagement as a product sprint. You identify the real problem, build toward a solution, test it with real users, and iterate until it works.
• You bring what you learn back into Promptly. Every pattern you see, every gap you find, every solution you build: it feeds product and engineering and makes the platform better for everyone.
  
  

How We Build With AI

At Promptly, AI-assisted development is part of how we work. We expect engineers to use coding agents, copilots, code search, AI-assisted debugging, and automated review to move faster through real engineering work.

We expect engineers to use AI as part of a modern development workflow, with the same standards of craft, quality, and accountability we apply to any production system. Strong engineers know where AI accelerates the work, where it introduces risk, and where human judgment needs to lead.

You own what you ship. You should be able to explain the design, inspect the diff, validate the behaviour, check the security and privacy implications, debug failures, and operate the system in production. If you cannot understand it, test it, secure it, and maintain it, you should not merge it — and if you cannot explain to a clinician why a system produced a given output, you should not put it in front of one.

What We're Looking For

This role is grounded in blended healthcare domain expertise, the ability to build trust inside healthcare organisations, and a track record of delivering real technical work in that setting. Those three things together are the job. Strong, demonstrable programming and data capability is essential — but it is the second requirement, not the first.

Required

• Demonstrable blended healthcare domain knowledge. You understand how clinical care, data, operations, and governance actually interact — not from the outside, but from having worked in or alongside healthcare organisations. You can tell the difference between a problem that looks technical and one that is really about pathway, incentive, or trust.
• Proven technical delivery in a healthcare setting. You have built and shipped things that clinical or operational users genuinely used. Not proofs of concept that stalled, not designs handed to someone else to implement — working systems, in live environments, with your name on the outcome.
• Trust-building with clinical and organisational stakeholders. You have earned the confidence of clinicians, information governance leads, and organisational leadership, and you understand that access in healthcare is earned rather than bought. You know how to be the person a clinical team calls.
• Experience working closely with, or within, local or national healthcare organisations. NHS trusts or health boards, national bodies and programmes, hospital networks, disease registries, or their equivalents in other European health systems.
• Direct experience with clinicians, patient groups, or healthcare executives. You have run design or engagement work with at least one of these groups and changed what you built as a result.
• C-suite engagement and value realisation. You can define what value an engagement is meant to deliver, articulate it in terms a healthcare board or executive team recognises, and evidence whether it actually landed. You are comfortable being in the room when that is assessed.
• Information governance and ethics experience. DPIAs, ethics and research approvals, data sharing agreements, IG committees, pseudonymisation, and working in environments where raw data cannot leave the owner. You treat governance as part of the build, not an obstacle to it.
• Strong, demonstrable programming and data capability. You write and debug your own code to a standard you would defend in review. Python and SQL are working tools for you, and you are comfortable picking up a modern application stack where an engagement needs one. We care that you can build; we do not require that "software engineer" has ever been your title.
• Hands-on experience with real clinical or health data. You have worked with the mess of hospital records, registries, or patient-reported data, not just clean extracts — and ideally with a clinical common data model such as OMOP.
• Practical understanding of AI/LLM-powered products. You understand how model behaviour, evaluation, reliability, and user experience affect systems that people rely on, and where human judgment has to lead.
• High agency in ambiguous, complex environments. You can make progress even when requirements, ownership, or process are not perfectly defined, and you help create clarity as you go.
• The ability to switch registers. A technical conversation with engineers and a strategic conversation with clinical, operational, or executive stakeholders — sometimes in the same meeting.
• Strong ownership and urgency. You treat client outcomes as your problem, follow issues through to resolution, and move quickly when something is not working.
• Good judgment under pressure. You simplify complexity, spot risks early, and make sound decisions without creating unnecessary noise.
• A collaborative, low-ego working style. You can work across product, engineering, customer success, and client teams while balancing competing priorities with integrity.
• Willingness to travel to client sites. We are remote-first, and you will plan your own week — but this is not a fully remote role. Embedded work means being physically present with clinical teams at the points that matter: co-design, go-live, and the sessions where trust is won. Expect this to cluster around engagement milestones rather than run at a steady weekly rate.
  
  

Preferred

• Familiarity with PROMs instruments, outcomes measurement, or disease registry operations.
• Experience with health data standards and terminologies: OMOP CDM, FHIR R4, HL7, SNOMED CT, ICD-10, LOINC, DICOM.
• Experience with federated or privacy-preserving architectures — federated learning, trusted research environments, secure data environments, or privacy-preserving record linkage.
• Experience generating or validating synthetic data, and a clear view of where it is and is not defensible.
• Real-world evidence, HEOR, HTA, or clinical trial feasibility exposure.
• Experience with benefits realisation, business case development, or outcome-based contracting in a healthcare context.
• Experience building or deploying AI/LLM-enabled workflows, agents, evaluation pipelines, or automation systems.
• A track record of turning field learning into product feedback, internal tooling, documentation, or repeatable deployment patterns.
• Experience creating onboarding, enablement, or implementation materials that help a team scale beyond one-off delivery.
• Additional European languages, particularly Portuguese, Spanish, or Welsh.
  
  

We know this is a broad ask, and we are deliberately casting wider than conventional engineering profiles to find it. If you have come to this work from informatics, research, health programmes, or clinical practice rather than from software, we would rather hear from you than not. We assess on what you have demonstrably built and owned, not on CV pattern matching. If you don't match every line but believe you're a strong fit, apply anyway.

Position

Remote-first, full time. You choose where you work from, within Europe or the UK.

This is not a fully remote role. Forward Deployed Engineering is embedded work, and some of it can only happen in the room — sitting in clinic to see why a workflow fails, running a co-design session with a clinical team, being present at go-live. Travel is concentrated around those moments rather than spread evenly, and it varies by engagement.

What We Offer

Ownership & Growth

• Real creative latitude to co-create products with clients and directly influence what Promptly builds next
• A role where your work compounds: what you build today shapes the platform for every client that follows
• Direct influence on the product roadmap from the field
  
  

Financial Benefits

• Competitive salary
• Annual performance bonus
• Equity compensation via our ESOP, open to all team members
• Annual training allowance
• Private health insurance
• Home-office equipment allowance
  
  

Non-Financial Benefits

• Equal opportunity and inclusive environment
• Flexible work schedule and vacation policy
• Corporate events and international team gatherings
  
  

Recruiting Process

• Initial Interview — meet your future manager and team to get to know each other and understand the scope of the role
• Technical & Strategic Assessment — a short case related to client co-creation or product deployment
• Final Interview (if needed) — a deeper conversation to align on expectations and vision
• Offer Stage — we share the offer and welcome you to the team
  
  

Our Culture & Values

Empathy — Ownership — Responsibility — Teamwork — Excellence

If you embrace these values, you will thrive at Promptly. We are a purpose-driven company where everyone acts as an owner, committed to improving healthcare through data, technology, and collaboration.

Data Privacy

Your personal data will be processed for the purposes of managing Promptly's recruitment-related activities, including setting up and conducting interviews, assessing candidates, and similar activities. Your data will be shared with Proef, a provider engaged by Promptly to help manage our recruitment process. For more information, please see Promptly's/Proef's Privacy Policy.

By submitting your application, you consent to Promptly processing your personal data for recruitment purposes and storing it for up to 12 months, unless you request erasure at [email protected].

By submitting this application, I confirm that all information provided is true to the best of my knowledge, and I accept that any false or incorrect information may result in my application being rejected or employment being terminated.

By submitting this application, I confirm that all the information given by me in this application for employment and any additional documents attached hereto are true to the best of my knowledge and that I have not wilfully suppressed any material fact. I confirm I have disclosed if applicable any previous employment with Promptly Health. I accept that if any of the information given by me in this application is in any way false or incorrect, my application may be rejected, any offer of employment may be withdrawn or my employment with Promptly Health may be terminated summarily or I may be dismissed. By submitting this application, I agree that my personal data will be processed in accordance with Promptly Health's Candidate Privacy Notice