Member Growth Operations Associate Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only 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: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Is this role not quite what you're looking for? Join our Talent Community..." etc. Also remove location-based compensation structure? Actually pay info is present: compensation range $84,000 to $110,000. So we should include Pay section with that. Benefits: they say "Information about Virta’s benefits is on our Careers page at: https://www.virtahealth.com/careers." That's not specific benefits detail; it's a link. According to rule: never create Benefits section unless posting actually states them. It only says see benefits page; not specific benefits. So we should not create Benefits section. Schedule: not mentioned. So omit. We need sections: About the role (maybe from mission description?), Responsibilities, Requirements (must-haves), Qualifications? Might combine. The posting includes "How You Will Work" which could be part of About the role or maybe separate. We'll treat "About the role" as the introductory paragraph about mission and role purpose. Then "Responsibilities" as the bullet list under Responsibilities heading. Then "Requirements" as Must-Haves. Also maybe "Nice to Have" could be under Skills? But we could include a Skills section for nice-to-have? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Skills for nice-to-have. Qualifications maybe overlapping with Requirements; but we can keep Requirements as must-haves, and Qualifications maybe not needed. But we should not create empty sections. So we will include About the role, Responsibilities, Requirements, Skills (nice-to-have), Pay. Possibly also "How You Will Work" could be part of About the role or separate section like "How You Will Work". But not in list of allowed headings; but we could incorporate into About the role. We must preserve all substantive information: include mission paragraph, role description, responsibilities bullet list, 90 Day Plan? That's also substantive. Should we include a section for 90 Day Plan? Not in allowed headings list but we could treat as part of Responsibilities or maybe a separate section like "First 90 Days". But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could add other headings if needed, but better to stick to those. However 90 Day Plan is substantive; we could embed it under Responsibilities or maybe under a separate heading like "First 90 Days". But to be safe, we could include a section "First 90 Days" as

though not in examples; risk of deviating. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical but not exclusive? It says "use

for section headings (e.g. ...)" meaning we should use h3 for headings, and those are examples. It doesn't forbid other headings. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can add a heading for 90 Day Plan if there is specific content. It's specific. So we can add

First 90 Days

. That seems okay. Also we have "How You Will Work" which is also specific; could be its own heading. But to keep sections few, we could merge How You Will Work into About the role or Responsibilities. However it's about success criteria; maybe better as its own heading "How You Will Work". But not in examples; still okay. We need to output only HTML fragment, no markdown fences. We must preserve all substantive info: include mission paragraph, role description, responsibilities bullet list (including sub-bullets?), 90 Day Plan bullet list, Must-Haves bullet list, Nice to Have bullet list, Pay info (range), maybe location info? Location-based compensation structure and remote-first etc. That's substantive but not under allowed headings; maybe we can include under About the role or a separate "Location" section. But we could include location info in About the role paragraph. We must remove boilerplate: "Is this role not quite what you're looking for? Join our Talent Community..." etc. Also remove "Virta uses Ashby..." etc. Also remove "As part of your duties at Virta, you may come in contact with sensitive patient information..." maybe that's substantive? It's about HIPAA; could be considered relevant but maybe it's boilerplate? It's about security and privacy; could be considered part of role but it's generic. Might be considered boilerplate; but it's specific to handling patient info. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The HIPAA statement is legal/privacy; might be considered boilerplate. Safer to remove it. Also remove "Virta has a location based compensation structure..." maybe keep pay range but not location restrictions? The location-based compensation structure and remote-first etc could be considered substantive about work arrangement. Might keep as part of About the role or a separate "Work Arrangement". But we can keep brief sentence about remote-first and office hubs. It's not boilerplate; it's specific. We'll keep. Also remove "Clinical roles: We currently do not hire in the following states..." etc. That's about hiring restrictions; maybe not needed for role description? Could be considered boilerplate but it's specific to corporate roles. Might be removed as it's not directly about the role. Safer to remove. We must not include application instructions like "For more information about AI usage..." etc. Remove. Now craft HTML. Structure:

About the role

Mission paragraph + role description + How You Will Work? We'll split. Better: About the role includes mission and role purpose. Then separate

How You Will Work

for success criteria. Then

Responsibilities

with

. Then

First 90 Days

with
. Then

Requirements

(Must-Haves) with
. Then

Skills

(Nice to Have) with
. Then

Pay

with

range. Make sure not to include empty sections. Now extract content. Mission paragraph: "Virta Health is on a mission to reverse metabolic disease in one billion people. Current treatment approaches aren’t working—over half of US adults have either type 2 diabetes or prediabetes, and obesity rates are at an all-time high. Virta is changing this by helping people reverse their metabolic condition through innovations in technology, personalized nutrition, and virtual care delivery reinvented from the ground up. We have raised over $350 million from top-tier investors, and partner with the largest health plans, employers, and government organizations to help their employees and members restore their health and take back their lives. Join us on our mission to reverse metabolic disease in one billion people." Role description: "Virta Health is seeking a Member Growth Operations Associate Manager to support the execution and continuous improvement of member communications across email, direct mail, SMS, and other campaign workflows. This is a hands-on generalist role for someone who enjoys moving between channels, learning interconnected systems, and bringing structure and accuracy to complex work. You will partner with teammates and cross-functional stakeholders to launch and maintain campaigns, complete rigorous quality assurance, keep client-specific content and channel rules accurate, and support custom communication needs. Some workstreams will be independently owned; others will require you to step in as a flexible partner based on team priorities and capacity." How You Will Work: "You will succeed in this role by being dependable, curious, and adaptable. You will develop broad knowledge across Member Growth Operations, independently own assigned work, and remain ready to support teammates when priorities or volume shift. The role is designed to increase cross-functional capacity and shared knowledge across the team rather than create another single-channel specialty." Responsibilities list: after "Responsibilities" heading we have bullet points: - Execute and quality-check cross-channel campaigns - Build, update, and maintain email templates used in Braze for new client launches and ongoing member communications. - Complete end-to-end QA across email, direct mail, SMS, and related campaign workflows, including content, links, personalization, client-specific language, audience criteria, and technical configuration. - Execute direct mail campaigns through PostGrid and Cornerstone, coordinating proofs, production timelines, approvals, and vendor handoffs. - Support custom communication workflows by translating approved requests into executable campaign plans, configurations, and QA steps. - Document issues, communicate risks early, and help strengthen QA controls based on lessons learned. - Support launches and ongoing campaign operations - Help set up new client launches, including campaign playbooks, email and direct mail Canvases, launch configurations, and operational readiness checks. - Coordinate file-ingestion requirements, validation, and data syncing to Braze in partnership with implementation, data, and marketing operations stakeholders. - Monitor dependencies and handoffs, maintain clear project plans, and ensure launch work progresses on time and without surprises. - Provide backup coverage across team focus areas and take ownership of assigned campaigns or processes from intake through completion. - Maintain client content and contact-governance processes - Manage client-level CML updates and help maintain an organized, accurate, and scalable Braze catalog. - Process ‘Do Not Contact’ requests across channels, ensuring member opt-out requests are documented, validated, and applied accurately and promptly. - Maintain process documentation and operational sources of truth so work can be transferred and supported across the team. We need to preserve all; we can flatten into

• items, maybe nested lists for subpoints. Use
  • and inside li we can have another
    for subpoints. First 90 Days plan: bullet points: - Learn the team's core tools, playbooks, QA standards, launch workflows, and client-specific CML and Do Not Contact requirements. - Begin independently executing routine email and direct mail campaigns, completing cross-channel QA, and owning assigned launch and custom communication work. - Own all new email builds across our legacy ongoing client playbooks. - Become dependable backup coverage across multiple workflows and deliver at least one process or documentation improvement that increases accuracy or scalability. Requirements (Must-Haves): - 4+ years of experience in marketing operations, campaign operations, project management, or a related field. - Demonstrated project management experience, including organizing dependencies, managing multiple deadlines, and driving work through completion. - Exceptional attention to detail and a disciplined approach to quality assurance. - Ability to learn technical systems and workflows quickly and move comfortably between strategic context and hands-on execution. - Strong written and verbal communication skills, with the judgment to clarify requirements and escalate risks early. - Ability to prioritize effectively in a fast-moving environment and adapt as business needs shift. - Demonstrates a proactive use of AI tools to improve individual output and efficiency. Nice to Have (Skills): - Experience with Braze or another customer engagement platform. - Experience building or editing email templates, including