SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
OpenLoop is a telehealth platform that enables companies to deliver virtual care across all 50 states. The Forward Deployed Engineer role is a customer-embedded position where you work directly in client environments to build integrations against OpenLoop's production API.
In this role, you will:
- Embed with client engineering teams and own end-to-end integration delivery, from initial scoping through go-live and post-launch support. You work in the client's codebase against OpenLoop's Partner API, handling their app, data, identity, and legacy systems.
- Build AI-enabled systems for clients and the platform: SDKs, reference implementations, CLIs, machine-readable documentation for coding agents, and agentic workflows (intake, routing, support, refill journeys) with human review by design, pre-launch evaluations, and post-launch monitoring.
- Operate and improve the deployment agent roster—tools that run tenant readiness gates, conformance checks, seeding, docs freshness validation, gap filing, and client communication drafting. You verify agent outputs and catch when they are wrong.
- Convert one client's needs into reusable platform capabilities. Contribute recipes and checks to a shared cookbook, maintain client manifests, and move recurring workarounds into the platform roadmap with evidence.
- Turn vague or over-promised client asks into phased, defensible scopes. You clearly articulate what is not being done and what the API cannot yet do.
- Maintain system integrity: checks lock published claims, manifests track dependencies, and changes are additive or explicitly superseding with compatibility windows. Breaking changes become proposals, not merges.
- Be the credible technical voice with clients and internal go-to-market teams. Distinguish between what cannot be done, what should not be done, and what will not fit the timeline—and deliver all three answers early.
- Raise the bar: share deployment learnings, review integration designs, and help build playbooks for the growing team.
OpenLoop operates with a flat structure and values Disciplined Intensity, Do No Harm (patient safety and data integrity first), Step In Stay In (ownership to outcome), Purposeful Speed, and Clarity Over Comfort. Core collaboration hours are CST 8am–5pm, with occasional flexibility for client work and periodic travel to clients and team sessions.
REQUIREMENTS:
- 5 to 15+ years of software engineering experience, with significant time delivering directly for external customers or partners in their environments (not only internal roadmap work). Depth of ownership matters more than years alone.
- End-to-end ownership of complex, customer-facing technical delivery. You can name the deployments you ran, what went wrong, and what you did about it post-launch.
- Strong integration engineering depth: API design and consumption, auth, webhooks vs. polling, idempotency, rate limits, pagination, schema drift, reconciliation, and comfort across the stack from APIs to data to cloud infrastructure.
- Daily experience building with AI agents. You can demonstrate how you verify agent outputs, when you stop trusting them, and how you evaluate LLM-based systems before they reach customers.
- Experience handling sensitive data with a security-first mindset, treating compliance constraints as design inputs rather than follow-ups.
- Excellent communication with technical and non-technical audiences, including delivering unwelcome news to customers early while maintaining relationships.
- Demonstrated judgment about scope: you can point to things you descoped, sequenced, or declined and explain why.
- Evidence of leverage beyond your own delivery: SDKs, tooling, checks, reference implementations, or practices you built that made others' work faster.
PREFERRED:
- Experience in healthcare or another regulated domain where mistakes have consequences beyond a rollback.
- Practical experience shipping LLM-based or agentic systems to production, including quality measurement and handling confidently wrong model outputs.
- Experience building developer platforms: SDKs, CLIs, API conventions, tested documentation.
- Familiarity with EHR, scheduling, pharmacy, or payments integrations; FHIR is a plus.
- Experience working alongside sales or solutions teams in pre-sales technical conversations without becoming a blocker.
- Bachelor's degree in Computer Science, Engineering, or a related technical field, or equivalent practical experience.
