FDE - Forward Deployment Engineer (Founding Team)

About Solum

Solum builds AI employees for healthcare practices. We started with front desk agents for therapy providers in the U.S., and today we automate eligibility checks, verification of benefits, and prior authorization, with a strong focus on ABA practices.

We don't ask practices to change how they work. We integrate into the CRMs, EHRs, and operational systems they already run, so our AI team does the work the way an additional hire would.

Why this role exists

We're looking for a Forward Deployed Engineer to own how Solum connects to a customer, and to build that playbook from zero.

Every practice runs differently. Some live in HubSpot, ClickUp, Zoho, Salesforce, or a custom CRM. Others run on EHRs, spreadsheets, email threads, payer portals, and processes built up over a decade. Your job is to understand how each client actually operates, find the right trigger for Solum to start work, and deliver finished output back into their systems without making them change anything.

The role sits between engineering, product, operations, and the customer. You'll work directly with clients to map their workflow, design the integration, build it, and turn what you learn into a repeatable process so the next one is faster and safer.

We're early, and the current integration process has real room to improve. The right person sees that as the reason to join. You'll be expected to propose better systems, design patterns that scale, improve visibility, and define how Solum integrates with every customer from here on.

What you'll do

Lead integrations end to end. Run discovery on the client's current workflow, identify trigger points, map data requirements, define how completed work gets returned, and take it to production.

Build and maintain the connections. CRMs, EHRs, healthcare platforms, and internal tools. Reading API docs, wiring webhooks, syncing patient and lead data, mapping custom fields, handling files, and coordinating with the client's technical or operations team.

Write the first version of Solum's integration playbook. Standard discovery questions, implementation patterns, reliability checks, monitoring requirements, documentation, and the practices worth repeating.

Reduce what the client has to do. Anticipate edge cases and design workflows that fit how they already operate instead of asking them to adapt.

Make integrations hold up. Better logging, monitoring, error handling, retries, alerting, and internal visibility into whether an integration is actually healthy.

Turn repetition into product. Work with engineering, product, and operations so recurring integration needs become reusable features, internal tools, or automation.

Keep clients oriented. Translate technical requirements into plain next steps so the process feels organized and low-friction.

What we're looking for

Strong integration engineering. APIs, webhooks, authentication, data mapping, custom fields, file handling, error handling, retries, logging, and debugging workflows that span multiple systems.

Experience with CRMs, EHRs, or operational systems. HubSpot, Salesforce, Zoho, ClickUp, healthcare EHRs, RCM platforms, or other secure and legacy environments.

Excellent written and spoken English. You'll be in front of clients directly, asking the right questions and explaining tradeoffs.

Product and systems thinking. Given a customer outcome, you can read the workflow, find the right trigger points, and design how Solum should receive and return the work.

Who thrives here

Takes ownership without being asked, and would rather fix a broken process than file a complaint about it.

Reliability first. An integration is only worth something if it keeps running, is easy to monitor, and can be debugged quickly when it breaks.

Comfortable with ambiguity. Turning a messy, half-documented client workflow into something clean and maintainable is the interesting part of the job, not the cost of it.

Communicates as well with an operations manag