Jobs · OTHR

Customer Success Executive, Health Plans

Carrot · New York, NY · 1 mo ago
RemoteRemoteOTHR$108k–$130k/yrFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Must not include sections with filler like "commensurate with experience". Pay and Schedule only if posting actually states them. The posting includes Compensation: starting base salary range $108,000-$130,000. That's Pay. Schedule? Not mentioned. Benefits? The posting mentions benefits in "Why Candidates Join Carrot" includes comprehensive benefits, flexible time off, parental leave, etc. So we can include Benefits section with those details. Also "About Carrot" is company description; maybe we can put under "About the role"? Actually "About the role" heading is for role description. The posting includes "About Carrot" then "The Opportunity 🚀Carrot is seeking a Customer Success Executive...". That's role overview. We can put that under About the role. Then responsibilities: "What You’ll Own 💼" bullet list. Then requirements: "About You ✨" bullet list (required). Then nice to have: "Nice to Have ⭐" could be Skills? Or maybe separate Skills section? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content accordingly. Likely: About the role = overview. Responsibilities = What You’ll Own. Requirements = About You (required). Qualifications = maybe education/experience? Could combine with Requirements. Skills = Nice to Have? Or maybe Skills separate. Benefits = from Why Candidates Join Carrot. Pay = compensation range. Schedule = none -> omit. We must not include sections with placeholder text. Ensure we include all substantive info. Must not invent or summarize away detail. So we need to keep details like bullet points exactly as given, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Safer to keep the text as is, maybe copy bullet points verbatim. Use
  • . Use

    for prose. We must not include duplicated lines. Ensure we don't repeat same bullet. Let's extract content. About Carrot paragraph: "Carrot is the leading global fertility and family care platform, built on intelligent care orchestration: the right clinical guidance, at the right moment, in the context of each member’s life. More than a thousand multinational employers, health plans, and health systems trust Carrot to support millions of members across 195 countries – from pre-pregnancy through menopause and major life moments in between. Carrot's comprehensive clinical program delivers industry-leading cost savings for plan sponsors and award-winning experiences and improved outcomes for millions of people worldwide. Carrot is widely regarded as a defining force in healthcare innovation as a recipient of several top-tier awards, including Fast Company's 'Most Innovative Companies' and CNBC's '100 Barrier Breaking Startups'. The company is regularly cited by leading global outlets — including The Economist, Bloomberg, The Wall Street Journal, NPR, ABC News, and Harvard Business Review — as a leading voice on digital health, the future of work, and family health. Learn more at get-carrot.com." Then The Opportunity paragraph: "Carrot is seeking a Customer Success Executive to support customers in our Health Plans segment, one of Carrot's most strategic channels. You will partner with health plan customers, serving as the primary point of contact for account, product, and clinical stakeholders to ensure Carrot remains a valued, ongoing part of the benefits they deliver to their members. You'll work closely with these customers to promote retention, boost member engagement, and uphold excellent customer satisfaction. In this role, you will serve as a trusted advisor to health plan stakeholders, clearly communicate the value of Carrot's offerings through payer-ready reporting on utilization, outcomes, and cost savings, and respond proactively to customer questions and requests while navigating the operating rhythms of large payer organizations. As a Customer Success Executive dedicated to this segment, you will help shape how Carrot supports health plan customers, contributing to the playbooks and best practices that will scale as the channel grows, and playing a vital role in the growth and collaboration of our Customer Success team." That's role overview. What You’ll Own bullet list: - Own a portfolio of health plan accounts, serving as the primary point of contact and trusted advisor to plan account, product, and clinical stakeholders - Drive retention and renewal outcomes across your book of business, proactively identifying risks and building action plans that account for payer procurement and renewal cycles - Increase member engagement and program utilization across covered populations through data-informed recommendations and a regular cadence of business reviews - Present program value, outcomes, and cost-savings data to health plan leadership through clear storytelling, reporting, and executive-ready presentations - Partner cross-functionally with Health Plan Sales, Implementation, Business Intelligence, Legal & Compliance, and Member Success to deliver a seamless customer experience - Identify and support expansion opportunities within existing health plan relationships, including new lines of business and new populations, in partnership with the Health Plan Sales team - Contribute to the customer success playbooks, processes, and best practices for the Health Plans segment as the channel scales What Success Looks Like bullet list (first 12-18 months): - Built trusted, multi-threaded relationships across your portfolio of health plan customers, reflected in strong customer satisfaction and account health - Delivered consistent retention and renewal results across your book of business - Increased member engagement and program utilization across covered populations through proactive, data-informed recommendations - Established a regular cadence of business reviews and payer-ready reporting that clearly communicates value, outcomes, and cost savings to plan stakeholders - Contributed at least one scalable playbook, process improvement, or best practice adopted across the Health Plans segment About You bullet list (required): - A Bachelor's degree - 6+ years of professional experience working closely with external customers in a Customer Success, Account Management, or client services role in the health plan, payer, or healthcare benefits space - Experience working with or within health plans, with an understanding of how payers evaluate, launch, and manage partner programs - A track record of successfully managing complex, multi-stakeholder relationships and projects to deadline across simultaneous workstreams - Clear, empathetic communication skills, with comfort presenting to plan leadership and executive audiences - Enthusiasm for Carrot's mission and eagerness to become part of a collaborative, friendly, and dynamic team Nice to Have bullet list: - Existing relationships within national or regional health plans - Familiarity with payer operations such as clinical program integration, network strategy, or utilization and outcomes reporting - Experience with Salesforce or another CRM, managing tasks efficiently in a dynamic environment - Strong analytical, writing, and communication skills with sharp attention to detail - Comfort navigating ambiguity in a growing segment; highly organized, diligent, and self-motivated - Willingness to travel for customer meetings and industry conferences Why This Role Matters paragraph: "Health plans are one of Carrot's most strategic channels: a single plan relationship can extend Carrot's care to entire covered populations, and Carrot's reputation in the payer market is earned account by account. The Customer Success Executive is the steward of these relationships, translating Carrot's clinical program and platform into measurable value for plans and the members they serve. Every renewed partnership and every increase in member engagement means more people can access fertility and family-building care at scale. This role sits at the center of that impact, connecting customer outcomes in the payer market to Carrot's mission of providing care for everyone, everywhere." Interview Process details: we should remove application instructions? The instruction says remove application instructions. Interview Process is not exactly application instructions but could be considered part of process. However it's substantive info about interview steps. Should we keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Interview Process is not application instructions; it's about the interview process. Might be okay to keep but maybe considered part of application instructions? Safer to keep? The instruction says remove application instructions, not interview process. I'd keep it but maybe it's not needed for the job posting summary? However we need to preserve ALL substantive information. So we should keep it. Why Candidates Join Carrot paragraph: includes mission-driven, high-growth, competitive compensation, equity, comprehensive benefits, Flexible Time Off, parental leave, family-forming benefits, collaborative culture, etc. Compensation paragraph: "Carrot offers a holistic Total Rewards package designed to support our employees in all aspects of their life inside and outside of work, including health and wellness benefits, retirement savings plans, short- and long-term incentives, parental leave, family-forming assistance, and a competitive compensation package. The starting base salary for this position will range from $108,000-$130,000. Actual compensation may vary from posted base salary depending on your confirmed job-related skills and experience." Fraud and Security Notice: remove (boilerplate). A Note on AI: maybe keep? It's not boilerplate but could be considered generic. Might be considered not essential? It's about AI fluency. Could keep but maybe not needed. The instruction: remove boilerplate, duplicated lines, and application instructions. The AI note is not boilerplate per se but could be considered generic. I'd keep it? Might be considered not substantive to role. However it's part of posting. I'd keep it as a short paragraph maybe under a generic section? But we have no heading for AI. Could include as a

    after Benefits? But we shouldn't create new headings not listed. Could just include as a

    after Benefits? But we need to follow headings list; we can have extra

    not under a heading? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Likely we should only use those headings. Additional info can be in

    under appropriate heading or as a general

    before first heading? Probably better to incorporate into existing sections: AI note could go under Skills or Requirements? Not really. Could be its own

    after Benefits but before Pay? Might be okay as a

    without heading? The instruction says use

    for section headings (list). It doesn't say you cannot have other headings, but to follow the pattern. Safer to include AI note as a

    under Skills? Not ideal. Maybe we can omit AI note as it's not critical? But we must preserve ALL substantive information. So we need to include it somewhere. Could add a

    after Benefits heading but before Pay heading, without a heading. That's acceptable as long as we don't create a heading not in list. We'll just put a

    . Why Carrot? paragraph: similar to Why Candidates Join Carrot but more accolades. Could be considered duplicate? It's somewhat repetitive. Might be considered boilerplate? It's about accolades. Might be okay to keep but could be considered not essential. However it's substantive. Could include under Benefits or as a separate

    . Might be okay to include under Benefits as additional details. We need to avoid duplication. The "Why Candidates Join Carrot" already covers mission, benefits, culture. The "Why Carrot?" paragraph repeats accolades. Could be considered duplicate? Not exactly duplicate but similar. Might be okay to keep but we need to avoid duplicated lines. It's not duplicated lines exactly. We'll keep it as a

    maybe under Benefits or as its own

    after Benefits. Now structure:

    About the role

    Carrot is the leading global fertility and family

Similar jobs