Ferrum Health | Operations Lead (Part-Time)
Ferrum Health
ferrumhealth.comFerrum Health is the platform health systems trust to take control of their clinical AI. We help hospitals deploy AI models, validate how they perform on their own patients, and measure outcomes across every service line. Our Model Hub includes 60+ validated models from third-party developers, and our platform runs across 400+ care sites for customers including Sutter Health, Allina Health, and Carle Health. Our mission is to make adopting clinical AI efficient for health systems, connecting clinicians with the tools they need to deliver the best possible care. We’ve raised $31M to date, including a Series A led by Foundry.
Ferrum is the one-stop shop for every clinical AI deployment in a health system. Clinicians, IT teams, and administrators rely on us for everything: deployment, configuration, support, and fixes when something breaks. As the connective tissue in a complex orchestra of third-party clinical AI models and dynamic hospital IT, we’re constantly adapting our solutions to meet each customer’s needs.
Our customers are happy and our customer team is excellent, but the way work moves between our Customer Success Managers and internal Technical Support and Engineering hasn’t kept pace with our growth. Requests come in ad hoc, context is spread across systems, and recurring work on our most-used models takes more hours than it should, often pulling engineers away from shipping new product.
We’re hiring a part-time Operations Lead to find where time is being lost, and implement the systems and playbooks that fix it. You’ll report to Peter Eason, our CFO, and work closely with our Director of Operations & Analytics, Customer Success Managers (day-to-day Account Managers), AI Partnerships Manager, and Engineering team. The role is roughly 20 hours a week for the first three months, shifting to around 10-15 hours a week once the core systems are in place.
Ferrum is a lean team, and everyone wears several hats. Your job is to give the team back focus: less context switching, clearer ownership, and more decisions made by the customer team instead of passed to engineering. You’ll own the operating systems that connect our customer team, model partners, and engineers, across three focus areas:
Diagnose and Prioritize
Learn how work gets done today by interviewing each member of the customer team, spending time with engineering, and tracing how a customer request gets solved.
Identify the biggest sources of lost time, starting with the models we deploy most often, and build a prioritized plan for what to address first.
Align on that plan with Peter and the team in your first month, so the early work sets the direction for everything after it.
Build Systems and Playbooks
Design intake flows for recurring work so engineering receives complete, well-scoped requests. For example, a new model deployment request should already include the customer’s cloud, the GPU shapes available in that cloud, the approved GPU models for that AI model, and expected study volume, including how it varies by time of day. That way the team can size the GPU nodes before engineering gets involved.
Build simple, repeatable playbooks for model deployment, support, and maintenance, using our existing customer implementation playbook as a reference point. Keep each one short enough that the team uses it, and modular enough to adapt to each health system.
Organize how information from third-party model developers, Cloud Service Providers, and other organizational inputs are captured and shared, so account managers and engineers work from the same source.
Work within the tools the team already uses, primarily Jira, Jira Service Manager and Slack. Adapt within the systems we have, rather than suggesting new tools for our tech stack.
Drive Adoption and Results
This is the component of the role that matters most.
Roll out new processes alongside the team, gather feedback, and refine them until they become the way the work gets done.
Define a few simple measures of effort against output, such as engineering time spent on customer maintenance and turnaround on common requests, to show what has changed. Keep them light. Nobody should be logging their day in six-minute increments.
Define and track a small set of measures, such as engineering hours spent on customer maintenance and turnaround time on common requests, to show what has changed.
Stay on to make sure new processes hold and drive efficiency for the team. Over time, scope further efficiency opportunities across the business, which may include areas such as hardware resource management, HR support, and compliance.
A hands-on operator: You do the work yourself. Your bias is to sit with a Customer Success Manager and fix a broken handoff, gather required inputs and information, implement a solution that optimizes the outcomes for the business. You’d rather ship a one-page checklist the team uses than a workflow diagram nobody opens.
Accountable for outcomes: You measure your success by adoption and hours saved, and you reinforce and refine a process until the team relies on it.
Disciplined about focus: Ferrum has no shortage of interesting problems. You stay laser-focused on this scope, in service of helping our customer team and engineers work together well.
Fluent with technical teams: You know how engineers plan their work, and you ensure the customer team brings them complete information and clear priorities.
Work with Customer Success Managers to prioritize and focus on the highest impact, highest yield problems first. Adhere to more stringent prioritization frameworks so not every new task is a P0
Builds systems thinkers: You teach the customer team to connect dots, gather what they need, and propose workable solutions instead of passing problems to engineering. When the missing piece is information only engineering has, you get it and structure it so the team can make the call next time.
Comfortable with a high bar: You work well with leaders who give direct feedback early and then let you run.
Preferred qualifications:
You’ve solved this problem several times at small and mid-sized companies, with 8+ years in Operations, Business Operations, Product Operations, or Management Consulting, ideally including time inside a B2B software or technical services company.
A track record of building operational systems in a complex environment where customers, partners, and engineering all depend on each other.
You’ve seen how a high-functioning small or mid-sized company runs, and you can adapt those workflows to a lean team.
Working familiarity with Jira and Slack-based workflows.
Experience in healthcare, health tech, or enterprise software is a plus.
Comfort working in a part-time capacity.
Hours: Part-time, likely starting at ~20 hours / week for the first 3-4 months, then scaling down to 10-15 hours / week, once solutions have been implemented, with potential to grow the role over time by expanding scope to additional aspects of the business.
Compensation: Starting at $8k-$10k / month.
Location: Remote (U.S. based).
November 1, 2026