Forward-Deployed / Delivery Engineer

You are the person on the ground when a health system turns Grid on, and the technical voice in the room while they are still deciding. You get access sorted, sources connected read-only, the inventory validated, and the first audit-readiness snapshot in front of a committee. You write the code that plugs Grid into a hospital's environment, and you turn every custom fix into a product feature the next deployment inherits. You will be the first person to run this end to end, so you build the playbook as you go.

What you'll own

• Deployments end to end: discovery, access, read-only connections, validation, the first inventory and audit-readiness snapshot, and the plan that gets there.
• The code. Custom connectors, transformations, and analyses against a specific system's data, in Python and SQL.
• The two-way loop: solve the blocker on-site, then merge the fix into the core product so the next hospital does not hit it.
• Pre-sale technical support alongside the GTM Engineer and founders (POC scoping, technical validation) and the technical relationship through security review and evaluation. There is no separate solutions-engineer role; this is you.

What we're looking for

• 4+ years in a forward-deployed, solutions, implementation, or delivery engineering role, facing customers directly.
• You write code (Python and SQL) and query a warehouse, rather than only configuring tools. You are AI-native: you use AI coding and agents to stand up connectors and analyses in fast build-test-launch cycles.
• You have sat through a hospital security review or vendor risk assessment from the vendor side. This is where early deals stall, and you have done it before.
• You build the onboarding and deployment playbook from scratch. There is not one yet.
• You can hold a room with a security reviewer, a skeptical clinician, and an analyst whose data you are questioning, and you will travel roughly 25%.

Nice to have

• Hands-on HL7, FHIR, Epic, or Cerner.
• You have been early somewhere that implementation and product were the same conversation.