Who We Are

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.

The Role

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.

Engineering at Floracene

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.

Requirements

• 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 request and connect your engineering decisions to business outcomes.
• Strong engineering and execution: You use AI aggressively without outsourcing your understanding to it. You don’t ship slop. You personally review PRs, understand and test what you ship, and take responsibility for its quality.
• Product and technical judgment: You know when to ship an MVP, when to invest in architecture, and when a customer need should become a platform capability.
• Customer ownership: You earn trust, communicate clearly, manage competing needs, and follow through until the customer succeeds.
• In person in NYC: You can work from the office five days a week.

Nice to Haves

These are useful starting points, not a checklist.

• Experience as an FDE or a product engineer with direct customer responsibility.
• Experience at an early-stage startup or a team with exceptional peers.
• Familiarity with healthcare operations, EMRs, or integrations with clinical and business systems.
• Experience integrating and normalizing messy third-party data.
• Experience building LLM applications or agents used in production.
• Experience as a founder, or an ambition to become one. After building with us, we’ll support you when it’s time to start your own company. Though transparently, our goal is to give you work compelling enough that you’ll want to stay.

Why you should join Floracene

Applied AI is the most interesting place to build today. It’s where advances in models meet human beings in their daily lives and workflows, and where some of the most creative product and engineering work gets done.

Healthcare is the most interesting place to do that work. Human health is upstream of everything: our ability to learn, work, create, and spend time with the people we love. Helping people stay healthy at a cost society can afford is an extraordinary problem to work on.

It’s also an extraordinarily interesting engineering challenge. Healthcare is an enormous ecosystem of competing incentives, fragmented data, and aging systems. There are entire workflows to rethink and tools to rebuild from first principles. We believe AI gives builders a practical way to make this system work better without waiting for sweeping policy reform.

The scale of the opportunity is enormous. Healthcare is one of the largest sectors of the United States economy, with spending equivalent to 18% of total GDP in 2024. The US spent $5.3 trillion on healthcare in 2024, with spending growing roughly 7% that year. CMS estimates 7.3% growth in 2025 and projects another 6.3% in 2026. Research puts administrative costs at 15–25% of healthcare spending. Applying a rough one-fifth estimate to that spending implies about $1 trillion a year in administration alone. Even modest improvements at that scale matter enormously. We’re building Floracene to become the platform healthcare teams use to turn their operational knowledge into software they can own and improve. Our ambition is to build a category leader and a business with billions in revenue.

We have a real shot. Asaph and Jonah led deployments at major US hospitals at Palantir. We understand the workflows, the technical challenges, and what it takes to get software used in these environments. We know what needs to be done, and have the backing we need to do it.

You’ll join while the most consequential decisions are still ahead of us and work directly with Jonah, our CTO, on problems that demand excellent engineering. You’ll independently own meaningful work early, make core technical and product decisions, and take responsibility for entire customer outcomes. We also believe in rewarding exceptional performance with additional compensation, equity, and scope that reflect your impact.