Head of Operations & Customer Success
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading (not given). Do not put Job ID/requisition numbers as headings (none). Remove boilerplate.
We need to preserve all substantive information.
Let's extract content:
Company description: "Formula Health is building the prescribing and fulfillment infrastructure for modern healthcare practices and compounding pharmacies. Our platform brings prescribing, pharmacy sourcing and routing, fulfillment, billing, refills, and the patient experience into one place - removing the operational overhead that comes with offering compounded medications and personalized treatments. Today, we support practices across weight management, longevity, functional medicine, primary care, dermatology, fertility, and other areas of personalized medicine. Why now?Formula sits at the intersection of two major shifts in healthcare: emerging regulatory tailwinds around peptides and AI making it possible to rethink legacy pharmacy infrastructure from the ground up. What was previously too cumbersome and slow to replace can now be rebuilt into a dramatically better product for pharmacies and providers. Our founders have seen this movie before. Aash was an early employee at Eucalyptus and Bryce at Virta Health, where they helped scale two healthcare unicorns. Formula is backed by Bling Capital and experienced operators and angels including Gokul Rajaram."
That's about the company. Could be placed under "About the role"? Actually "About the role" heading is for role description. But we have no explicit "About the role" section; we have "The Role". We could treat that as About the role. The instructions: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create those headings if content exists.
Thus:
- About the role: could include the description under "The Role" (the paragraph starting "You’ll work directly with the cofounders...").
- Responsibilities: could be the bullet list under "What you’ll own" (Onboarding & activation, Customer success, Revenue & usage, Day-to-day operations, Product & process, Pharmacy operations, Build the function). Those are responsibilities.
- Requirements / Qualifications / Skills: The "Who You Are" list (6-10 years experience, early-stage company, comfortable getting into weeds, first-principles problem solver, understand commercial side, direct analytical detail-oriented, healthcare/healthtech experience strongly preferred, experience building a team or background in consulting/strategy & operations is a plus). Could split into Requirements (mandatory) and Skills (preferred). But we can combine into one section "Requirements" or "Qualifications". The instruction says we can have multiple sections but prefer few substantive sections over many thin ones. We could have a single "Requirements" section covering all. Or we could have "Requirements" for mandatory and "Skills" for preferred. Let's see: The posting includes both mandatory and preferred. Could create Requirements (mandatory) and Skills (preferred). But we need to avoid thin sections. However we have enough content for each.
Let's decide: We'll have:
- About the role (prose)
- Responsibilities (ul list)
- Requirements (ul list for mandatory)
- Skills (ul list for preferred)
- Pay (p)
- Schedule (p)
We must not create Benefits if not present.
Now extract mandatory vs preferred.
Mandatory (seems like bullet points before "Healthcare / healthtech experience is strongly preferred..."):
- 6-10 years of experience across operations, customer success, BizOps/strategy, implementation, or similar roles at high-growth technology companies.
- You’ve worked in an early-stage company before and have experience building things from scratch.
- You’re comfortable getting into the weeds. You can handle a frustrated customer, dig into why something broke, and work with the team to fix it.
- You’re a first-principles problem solver with strong judgment and common sense. You can take an ambiguous problem, break it down, and figure out what actually needs to happen.
- You understand the commercial side of the job and how activation, retention, and expansion ultimately drive growth.
- You’re direct, analytical, detail-oriented, and move quickly.
Preferred/extras:
- Healthcare / healthtech experience is strongly preferred, especially in clinical, pharmacy, or healthcare operations.
- Experience building a team or a background in consulting / strategy & operations is a plus.
Thus we can put those in Skills.
Now Responsibilities list: from "What you’ll own" bullet points:
- Onboarding & activation: Get customers from signed to live to steady prescribing volume, and build a process that works as we grow from tens of clinics to hundreds.
- Customer success: Own the customer relationship after launch, from adoption and retention to helping clinics get more out of the platform. Start hands-on, then build the team around you.
- Revenue & usage: We're usage-based, so clinics only generate revenue when they place orders. Own the metrics that drive that, from time to first order to ongoing prescribing volume, and use them to decide where to focus across onboarding, activation, and customer success.
- Day-to-day operations: Own the issues that come up across orders, fulfillment, pharmacies, and prescribers. Fix what’s in front of you, then figure out how to keep it from happening again.
- Product & process: Work closely with engineering to turn manual work into product and recurring customer pain points into better workflows and features.
- Pharmacy operations: Help us build the processes to integrate efficiently with pharmacies and exponentially grow our pharmacy network
- Build the function: As we grow, figure out what we automate, where we need better process, and where we need people. Then hire and lead the team.
Also there is "Where the role goes" describing progression; could be part of About the role or Responsibilities? It's more about career progression. Could include in About the role as prose.
Now About the role prose: combine "The Role" paragraph and "Where the role goes" paragraph.
The Role paragraph:
"You’ll work directly with the cofounders to own everything after the deal is signed: getting clinics live, growing their usage, solving the operational problems that get in their way, and building the systems that allow Formula to scale. We’re looking for a hands-on leader who wants to build - someone excited to personally own and execute across the most critical parts of the function today, while building the systems, processes, and eventually the team to scale it. You’ll have the opportunity to shape the function from the ground up and grow your leadership scope alongside the business."
Where the role goes paragraph:
"You'll start hands-on. For the first few months, you'll be the one onboarding clinics, working through issues with pharmacies, and figuring out what should become a process, product, or a hire. As the business grows, we expect your scope to grow with it. That likely starts with a CS hire, then expands to include ops generalists and our pharmacy partnerships team. If things go the way we hope, within a year or so you'd be leading a team across customer success, operations, and pharmacy, with a real say in how Formula scales. We can't promise exactly how or when that happens– that depends on the business, and on you–but the scope is there for someone who wants to build it, and you'll be doing it alongside founders who have built and scaled $1B+ healthcare companies before."
We can combine into About the role.
Now Pay: "Compensation: Starts at $200K / year + equity". So we can put in
Pay: Starts at $200K / year + equity.
Schedule: "Employment Type: Full-time". So Schedule: Full-time.
Location is metadata; we could ignore or include as short p? The instruction says fold minor metadata into a short or drop it. Location is minor metadata; we could include a short p at top maybe. But we should not create a heading for it. Could include a
Location: San Francisco, CA – in-office.
before sections. That's allowed as minor metadata.
Now ensure we don't repeat job title. No title given.
Now output HTML fragment only.
Let's craft:
Location: San Francisco, CA – in-office.
About the role
You’ll work directly with the cofounders to own everything after the deal is signed: getting clinics live, growing their usage, solving the operational problems that get in their way, and building the systems that allow Formula to scale. We’re looking for a hands-on leader who wants to build - someone excited to personally own and execute across the most critical parts of the function today, while building the systems, processes, and eventually the team to scale it. You’ll have the opportunity to shape the function from the ground up and grow your leadership scope alongside the business. You'll start hands-on. For the first few months, you'll be the one onboarding clinics, working through issues with pharmacies, and figuring out what should become a process, product, or a hire. As the business grows, we expect your scope to grow with it. That likely starts with a CS hire, then expands to include ops generalists and our pharmacy partnerships team. If things go the way we hope, within a year or so you'd be leading a team across customer success, operations, and pharmacy, with a real say in how Formula scales. We can't promise exactly how or when that happens– that depends on the business, and on you–but the scope is there for someone who wants to build it, and you'll be doing it alongside founders who have built and scaled $1B+ healthcare companies before.
Responsibilities
- Onboarding & activation: Get customers from signed to live to steady prescribing volume, and build a process that works as we grow from tens of clinics to hundreds.
- Customer success: Own the customer relationship after launch, from adoption and retention to helping clinics get more out of the platform. Start hands-on, then build the team around you.
- Revenue & usage: We're usage-based, so clinics only generate revenue when they place orders. Own the metrics that drive that, from time to first order to ongoing prescribing volume, and use them to decide where to focus across onboarding, activation, and customer success.
- Day-to-day operations: Own the issues that come up across orders, fulfillment, pharmacies, and prescribers. Fix what’s in front of you, then figure out how to keep it from happening again.
- Product & process:
for prose. We must not repeat job title as heading (not given). Do not put Job ID/requisition numbers as headings (none). Remove boilerplate. We need to preserve all substantive information. Let's extract content: Company description: "Formula Health is building the prescribing and fulfillment infrastructure for modern healthcare practices and compounding pharmacies. Our platform brings prescribing, pharmacy sourcing and routing, fulfillment, billing, refills, and the patient experience into one place - removing the operational overhead that comes with offering compounded medications and personalized treatments. Today, we support practices across weight management, longevity, functional medicine, primary care, dermatology, fertility, and other areas of personalized medicine. Why now?Formula sits at the intersection of two major shifts in healthcare: emerging regulatory tailwinds around peptides and AI making it possible to rethink legacy pharmacy infrastructure from the ground up. What was previously too cumbersome and slow to replace can now be rebuilt into a dramatically better product for pharmacies and providers. Our founders have seen this movie before. Aash was an early employee at Eucalyptus and Bryce at Virta Health, where they helped scale two healthcare unicorns. Formula is backed by Bling Capital and experienced operators and angels including Gokul Rajaram." That's about the company. Could be placed under "About the role"? Actually "About the role" heading is for role description. But we have no explicit "About the role" section; we have "The Role". We could treat that as About the role. The instructions: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create those headings if content exists. Thus: - About the role: could include the description under "The Role" (the paragraph starting "You’ll work directly with the cofounders..."). - Responsibilities: could be the bullet list under "What you’ll own" (Onboarding & activation, Customer success, Revenue & usage, Day-to-day operations, Product & process, Pharmacy operations, Build the function). Those are responsibilities. - Requirements / Qualifications / Skills: The "Who You Are" list (6-10 years experience, early-stage company, comfortable getting into weeds, first-principles problem solver, understand commercial side, direct analytical detail-oriented, healthcare/healthtech experience strongly preferred, experience building a team or background in consulting/strategy & operations is a plus). Could split into Requirements (mandatory) and Skills (preferred). But we can combine into one section "Requirements" or "Qualifications". The instruction says we can have multiple sections but prefer few substantive sections over many thin ones. We could have a single "Requirements" section covering all. Or we could have "Requirements" for mandatory and "Skills" for preferred. Let's see: The posting includes both mandatory and preferred. Could create Requirements (mandatory) and Skills (preferred). But we need to avoid thin sections. However we have enough content for each. Let's decide: We'll have: - About the role (prose) - Responsibilities (ul list) - Requirements (ul list for mandatory) - Skills (ul list for preferred) - Pay (p) - Schedule (p) We must not create Benefits if not present. Now extract mandatory vs preferred. Mandatory (seems like bullet points before "Healthcare / healthtech experience is strongly preferred..."): - 6-10 years of experience across operations, customer success, BizOps/strategy, implementation, or similar roles at high-growth technology companies. - You’ve worked in an early-stage company before and have experience building things from scratch. - You’re comfortable getting into the weeds. You can handle a frustrated customer, dig into why something broke, and work with the team to fix it. - You’re a first-principles problem solver with strong judgment and common sense. You can take an ambiguous problem, break it down, and figure out what actually needs to happen. - You understand the commercial side of the job and how activation, retention, and expansion ultimately drive growth. - You’re direct, analytical, detail-oriented, and move quickly. Preferred/extras: - Healthcare / healthtech experience is strongly preferred, especially in clinical, pharmacy, or healthcare operations. - Experience building a team or a background in consulting / strategy & operations is a plus. Thus we can put those in Skills. Now Responsibilities list: from "What you’ll own" bullet points: - Onboarding & activation: Get customers from signed to live to steady prescribing volume, and build a process that works as we grow from tens of clinics to hundreds. - Customer success: Own the customer relationship after launch, from adoption and retention to helping clinics get more out of the platform. Start hands-on, then build the team around you. - Revenue & usage: We're usage-based, so clinics only generate revenue when they place orders. Own the metrics that drive that, from time to first order to ongoing prescribing volume, and use them to decide where to focus across onboarding, activation, and customer success. - Day-to-day operations: Own the issues that come up across orders, fulfillment, pharmacies, and prescribers. Fix what’s in front of you, then figure out how to keep it from happening again. - Product & process: Work closely with engineering to turn manual work into product and recurring customer pain points into better workflows and features. - Pharmacy operations: Help us build the processes to integrate efficiently with pharmacies and exponentially grow our pharmacy network - Build the function: As we grow, figure out what we automate, where we need better process, and where we need people. Then hire and lead the team. Also there is "Where the role goes" describing progression; could be part of About the role or Responsibilities? It's more about career progression. Could include in About the role as prose. Now About the role prose: combine "The Role" paragraph and "Where the role goes" paragraph. The Role paragraph: "You’ll work directly with the cofounders to own everything after the deal is signed: getting clinics live, growing their usage, solving the operational problems that get in their way, and building the systems that allow Formula to scale. We’re looking for a hands-on leader who wants to build - someone excited to personally own and execute across the most critical parts of the function today, while building the systems, processes, and eventually the team to scale it. You’ll have the opportunity to shape the function from the ground up and grow your leadership scope alongside the business." Where the role goes paragraph: "You'll start hands-on. For the first few months, you'll be the one onboarding clinics, working through issues with pharmacies, and figuring out what should become a process, product, or a hire. As the business grows, we expect your scope to grow with it. That likely starts with a CS hire, then expands to include ops generalists and our pharmacy partnerships team. If things go the way we hope, within a year or so you'd be leading a team across customer success, operations, and pharmacy, with a real say in how Formula scales. We can't promise exactly how or when that happens– that depends on the business, and on you–but the scope is there for someone who wants to build it, and you'll be doing it alongside founders who have built and scaled $1B+ healthcare companies before." We can combine into About the role. Now Pay: "Compensation: Starts at $200K / year + equity". So we can put in
Pay: Starts at $200K / year + equity.
Schedule: "Employment Type: Full-time". SoSchedule: Full-time.
Location is metadata; we could ignore or include as short p? The instruction says fold minor metadata into a shortor drop it. Location is minor metadata; we could include a short p at top maybe. But we should not create a heading for it. Could include a
Location: San Francisco, CA – in-office.
before sections. That's allowed as minor metadata. Now ensure we don't repeat job title. No title given. Now output HTML fragment only. Let's craft:Location: San Francisco, CA – in-office.
About the role
You’ll work directly with the cofounders to own everything after the deal is signed: getting clinics live, growing their usage, solving the operational problems that get in their way, and building the systems that allow Formula to scale. We’re looking for a hands-on leader who wants to build - someone excited to personally own and execute across the most critical parts of the function today, while building the systems, processes, and eventually the team to scale it. You’ll have the opportunity to shape the function from the ground up and grow your leadership scope alongside the business. You'll start hands-on. For the first few months, you'll be the one onboarding clinics, working through issues with pharmacies, and figuring out what should become a process, product, or a hire. As the business grows, we expect your scope to grow with it. That likely starts with a CS hire, then expands to include ops generalists and our pharmacy partnerships team. If things go the way we hope, within a year or so you'd be leading a team across customer success, operations, and pharmacy, with a real say in how Formula scales. We can't promise exactly how or when that happens– that depends on the business, and on you–but the scope is there for someone who wants to build it, and you'll be doing it alongside founders who have built and scaled $1B+ healthcare companies before.
Responsibilities
- Onboarding & activation: Get customers from signed to live to steady prescribing volume, and build a process that works as we grow from tens of clinics to hundreds.
- Customer success: Own the customer relationship after launch, from adoption and retention to helping clinics get more out of the platform. Start hands-on, then build the team around you.
- Revenue & usage: We're usage-based, so clinics only generate revenue when they place orders. Own the metrics that drive that, from time to first order to ongoing prescribing volume, and use them to decide where to focus across onboarding, activation, and customer success.
- Day-to-day operations: Own the issues that come up across orders, fulfillment, pharmacies, and prescribers. Fix what’s in front of you, then figure out how to keep it from happening again.
- Product & process: