Most implementation roles put you behind a ticket queue. This one puts you in the room.
As a Forward Deployed Engineer, you are Genzeon''s primary technical presence at design partner client sites. You own the full problem lifecycle — from discovery through production — embedded directly in the client''s environment, working with their systems, their people, and their edge cases. You do not wait for requirements to be handed to you. You find the problem, build the solution, ship it, and feed what you learned back into the product.
This role is modeled on the FDE concept: part engineer, part consultant, part product partner. You are the person who makes the demo real, fixes the production break before anyone else knows it happened, and comes back to the team on Friday with three things the product needs to do differently based on what you saw in the field that week.
If you need a lot of process structure to do your best work, this is not the right role. If you thrive on ownership, ambiguity, and the satisfaction of shipping something that works in a live client environment — keep reading.
What You''ll Do
- Deploy to design partner client sites as the primary technical presence for PA automation implementation across payer environments — you are the face of the product in the field
- Own the full implementation lifecycle at each client: discovery, workflow analysis, build, test, deploy, and hypercare — without handing off between phases
- Build automation workflows directly in client environments using UiPath Studio, IXP, Orchestrator, and the Agentic framework, interfacing with healthcare systems including MHK, Epic, payer portals, and document repositories
- Run live demos and working sessions with client stakeholders — you present what you built, take feedback in the room, and iterate the same day when possible
- Troubleshoot and resolve production issues on-site before escalating; your instinct is to fix first and write the post-mortem after
- Translate client-specific edge cases, workflow exceptions, and integration surprises into structured product patterns — you know the difference between a one-off client quirk and a signal the product architecture needs to change
- Feed weekly structured learnings back to the Solution Architect and product team: what worked, what broke, what the client actually needed versus what they said they needed
- Work alongside the Business Analyst to pressure-test requirements against live workflows — you are the field validation layer for anything that looked clean on paper
- Collaborate with offshore developers to parallelize build capacity, delegating repeatable development work while you stay focused on client-facing iteration and high-complexity integration problems
- Present progress, findings, and implementation status to client stakeholders across IT, clinical operations, and compliance — without needing a prepared slide deck to do it
What You Bring
- 3+ years of hands-on UiPath development — Studio, IXP, Orchestrator, Agentic framework — and you can build a working, exception-handled automation from a whiteboard conversation in a single day when the situation calls for it
- Healthcare domain exposure — you have worked in or around payer operations, provider RCM, pharmacy, or clinical systems and understand enough of the landscape to have credible conversations with clinical and compliance stakeholders without a primer
- Proven ability to operate independently at client sites with minimal supervision — you identify what needs to happen next and do it, rather than waiting to be directed
- Strong debugging and production support instincts — you are calm under pressure, systematic in your troubleshooting, and you treat a production break at a client site as your personal problem until it is resolved
- Client-facing communication skills that work across audiences — you can explain what you are building and why it matters to a pharmacy compliance manager, an IT director, and a payer COO in the same meeting, adjusting register without losing accuracy
- High say-do ratio — when you commit to a delivery date, it is not a target, it is a promise
- Bias toward action: you ship, gather signal, and document — in that order — and you are comfortable with the iteration that comes from real-world deployment over theoretical completeness
Nice to Have
- Experience integrating UiPath automations with healthcare platforms such as MHK (MedHOK), Epic, Guiding Care, or CareRadius
- FHIR R4 API development experience — you have built or consumed FHIR-based integrations in a live healthcare environment
- Python or scripting experience for clinical NLP, document extraction, or handling unstructured PA-related data
- Prior startup, consulting, or FDE-style deployment experience where you were the only technical person on-site and owned the outcome
- You have been the person a client calls when something is broken at 4pm on a Thursday — and that does not bother you
How This Role Fits the Team
The Solution Architect defines what gets built. The Business Analyst defines what it should do. The Senior Developer builds it at scale. You make it work in the real world — and make sure what you learned in the field makes everything else better.
The FDE role is the feedback loop that keeps the product honest. Without it, the team is building for a version of the client environment that only exists in requirements documents. With it, the product evolves based on what actually happens when real payer staff interact with live automation on a Monday morning.
Never miss an opportunity! Create an alert based on the job you applied for.
