Founding Forward-Deployed Engineer

Healthcare operators should be able to build their own software. They know how their practice should run, where work gets stuck, and what a better tool would do.

AI makes it possible to build useful tools, but getting them into daily use takes more: connections to clinical and business data, protection for patient information, and the right access for each user.

Floracene provides that infrastructure. Operators can build applications, analytics, and agents on their own data and safely deploy them across their organization, without needing an engineering team.

We’re fresh out of YC and backed by Tier 1 investors.

You’ll lead customer deployments from the first conversation through software people use every day. You’ll work directly with the founders, solve customer problems, and help healthcare teams learn to build on Floracene themselves.

What you’ll work on:

• Choose the first problem: Understand the customer’s operation, identify where we can deliver the most value, and set a practical scope.
• Own the outcome: Take the deployment through adoption and stay involved until it delivers value in daily use.
• Build the core product: Turn recurring needs from deployments into reusable platform capabilities and contribute the engineering to make them work.

We’re building a software factory for healthcare teams: a platform where nontechnical operators can create applications, workflows, and agents - and use agents to build and improve those tools themselves.
Your work will make that promise hold up against real healthcare systems, messy data, and daily operational needs.

• Agents that solve real operational problems. Turn customer workflows into agents and repeatable automations. Design their context, tools, and evaluations; decide what agents should reason about, what code must enforce, and when a person needs to decide. Help operators use agents to build applications and other agents.
• A semantic layer grounded in how the customer works. Connect fragmented systems and resolve conflicting business definitions. Map source data into concepts and relationships people and agents can use, validate those mappings against real workflows, and keep them dependable as customer data changes.
• Precise permissions for sensitive clinical data. Translate customer access requirements into boundaries that give each user, agent, and application only the patient data and actions they are authorized to use. Test those boundaries against real workflows, including attempts to access data outside the permitted scope.
• Software customers can depend on without maintaining it themselves. Turn recurring deployment failures into automated detection, diagnosis, and tested repairs. Validate that fixes preserve the customer’s intended workflow, and help define when recovery can happen automatically or needs human judgment.
• Secure deployments that hold up in daily use. Engineer around real authentication, network, and integration constraints. Help develop automated penetration tests and vulnerability checks on pushed code, investigate failures, and turn recurring issues into platform safeguards.
• Helping operators become builders. Work alongside customers as they create, inspect, and improve their own tools. Identify where they need better context, controls, or feedback - and contribute the product engineering that makes the next deployment easier.

• High agency, above all: We believe that “action produces information.” You take initiative, make progress with incomplete information, and learn by building, shipping, and talking to customers.
• Proven problem-solving ability: You’ve turned ambiguous customer needs into software people use. You distinguish the underlying problem from the initial…