Marketing Campaign Operations Strategist

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. We have: Location: Remote (but we shouldn't repeat job title; location can be in a short p maybe). Department: Marketing, Reports to: Senior Manager, Marketing GTM. Probably we can include that in a short p. "Why Join Omnicell?" paragraph: can be About the role? Actually "Why Join Omnicell?" is more about company. Could be part of About the role. Then "What You’ll Do" with bullet points: responsibilities. Then "Who You Are" with Minimum Qualifications and Preferred Qualifications: that's qualifications. Then "How You’ll Elevate at Omnicell": maybe skills or behaviors. Then "Work Conditions": remote, travel up to 25%: schedule? Actually schedule maybe remote and travel. Then "Base Compensation: $72,456.00 to $115,000.00 (Actual compensation is subject to variation... We offer a comprehensive benefits package, including medical, dental and vision plans covering eligible US employees and dependents, voluntary wellness and employee assistance programs, life insurance, disability, retirement plans with matching, and paid time off.)": This includes Pay and Benefits. Thus we need sections: About the role (maybe combine Why Join Omnicell and overview), Responsibilities (What You’ll Do), Requirements (maybe Minimum Qualifications?), Qualifications (Preferred Qualifications?), Skills (maybe from Preferred Qualifications like HTML/CSS, paid digital campaigns, etc.), Benefits (benefits description), Pay (base compensation range), Schedule (Work Conditions remote and travel). Ensure we don't create sections with filler. We must not repeat job title as heading. Use

for each section heading. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none. We need to ensure we don't create sections with placeholder like "commensurate with experience". Not present. Let's extract content. About the role: Could be the "Why Join Omnicell?" paragraph plus maybe the introductory sentences before "What You’ll Do". The posting starts: "Location: Remote Department: Marketing Reports to: Senior Manager, Marketing GTM Why Join Omnicell? At Omnicell, we are transforming the future of healthcare through innovative technology that empowers providers, improves operational efficiency, and enhances patient outcomes. As a Marketing Campaign Operations Strategist, you will play a critical role in bringing our demand generation and account-based marketing strategies to life. This is an opportunity to combine marketing technology expertise, operational excellence, and data-driven execution to deliver impactful campaigns that accelerate pipeline growth across Omnicell’s portfolio. You’ll collaborate with cross-functional marketing, digital, and sales stakeholders while helping build scalable programs that create measurable business impact." Thus About the role can include that paragraph. Responsibilities: The bullet list under "What You’ll Do Drive Campaign Execution Excellence" etc. Also includes "Ensure Quality, Compliance & Data Integrity" and "Support Optimization & Continuous Improvement". Those are subheadings but we can treat as part of responsibilities list. We need to list each duty as

• . Should we keep subheadings? Probably not needed; just list items. Let's extract each bullet: - Building, configuring, testing, and launching campaigns within Salesforce Marketing Cloud Account Engagement (MCAE), including email programs, landing pages, forms, nurture journeys, and automated workflows. - Translating go-to-market strategies into scalable Revenue Lifecycle Management (RLM) automation that supports buyer progression through awareness, consideration, and decision stages. - Partnering closely with Demand Generation and GTM Planning teams to transform campaign briefs into fully operational and production-ready programs. - Managing campaign deployment timelines and ensuring flawless execution across multiple concurrent initiatives. - Supporting paid media activation across Google Ads, LinkedIn Ads, and social channels in collaboration with Digital Marketing teams. - Coordinating end-of-life (EOL) and product sunset communications, including audience segmentation, campaign logistics, execution timelines, and stakeholder alignment. - Maintaining campaign execution logs, status reporting, milestone tracking, and cross-functional handoffs to ensure transparency and accountability. - Execute comprehensive quality assurance processes for all campaign assets, including rendering validation, link testing, audience verification, suppression management, and Salesforce CRM integration checks. - Maintain high standards of data hygiene across MCAE and Salesforce CRM systems. - Monitor campaign workflows to identify operational bottlenecks and opportunities for process improvement. - Establish and uphold repeatable operational standards that improve campaign consistency, scalability, and execution quality. - Execute and document A/B and multivariate testing initiatives focused on subject lines, messaging, creative assets, and calls-to-action. - Analyze operational performance and recommend enhancements that improve campaign efficiency and effectiveness. - Troubleshoot marketing automation issues, Salesforce synchronization challenges, and campaign delivery problems, ensuring timely resolution and thorough documentation. - Drive operational best practices that improve speed-to-market while maintaining exceptional quality standards. That's a lot; we can keep them. Requirements: Minimum Qualifications: Bachelor's degree in marketing, business, communications, or related field OR equivalent experience. 3+ years of experience in marketing operations, campaign operations, or demand generation execution. Hands-on Salesforce Marketing Cloud Account Engagement (MCAE/Pardot) experience — required. Strong understanding of Salesforce CRM campaign and lead object relationships. Demonstrated experience executing ABM and lifecycle email programs at scale in B2B environments. We can put these as list items. Qualifications: Preferred Qualifications: Bachelor’s degree in Marketing, Business, Communications, or a related field, or equivalent experience. Experience supporting Account-Based Marketing (ABM) programs in a complex B2B environment. Background in healthcare technology, SaaS, or enterprise solution selling organizations. Salesforce Marketing Cloud Account Engagement (Pardot) Specialist certification. Working knowledge of HTML and CSS for email troubleshooting and template modifications. Experience managing or supporting paid digital campaigns through Google Ads and LinkedIn Campaign Manager. Familiarity with social media management and publishing platforms such as Oktopost. We could treat these as Skills maybe. But we have separate Skills section. The instructions: Use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to allocate content accordingly. We could put Minimum Qualifications under Requirements, Preferred Qualifications under Qualifications, and then Skills maybe extract specific skill items like HTML/CSS, paid digital campaigns, social media platforms, etc. But we could also put all preferred qualifications under Qualifications and leave Skills empty? But we must not create a section with filler. So if we don't have specific skill content beyond what's already in Qualifications, we could omit Skills section. However we have some skill-like items: "Working knowledge of HTML and CSS for email troubleshooting and template modifications." "Experience managing or supporting paid digital campaigns through Google Ads and LinkedIn Campaign Manager." "Familiarity with social media management and publishing platforms such as Oktopost." Those could be considered Skills. But they are also part of Preferred Qualifications. To avoid duplication, we could put them under Skills and keep Qualifications for education/experience preferences. But the instructions say we should prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one Qualifications section? But we need to follow the headings list; we can omit sections if no real specific content. So we could have: About the role, Responsibilities, Requirements, Qualifications (including preferred qualifications and skills), Benefits, Pay, Schedule. That would be 6 sections. That seems okay. Thus we will not have a separate Skills section. Now Benefits: The paragraph about benefits: "We offer a comprehensive benefits package, including medical, dental and vision plans covering eligible US employees and dependents, voluntary wellness and employee assistance programs, life insurance, disability, retirement plans with matching, and paid time off." Pay: Base compensation range: "$72,456.00 to $115,000.00 (Actual compensation is subject to variation due to such factors as location, education, experience, and skillset." Schedule: Work Conditions: "Remote-based role. Up to 25% travel for team meetings, customer engagements, industry events, or business-related activities." We should not include location repeated? Could be part of Schedule. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:

  About the role

  ... (the about role paragraph)

  Responsibilities

  • ... each duty
  ...

  Requirements

  • ... minimum qualifications
  ...

  Qualifications

  • ... preferred qualifications
  ...

  Benefits

  ... benefits paragraph

  Pay

  Base compensation: $72,456.00 to $115,000.00 (Actual compensation is subject to variation due to such factors as location, education, experience, and skillset.)

  Schedule

  Remote-based role. Up to 25% travel for team meetings, customer engagements, industry events, or business-related activities.

  We need to ensure we preserve all substantive information. Did we miss any? The "Why Join Omnicell?" paragraph we included. Also the introductory sentences before "Why Join Omnicell?" Actually the posting starts with "Location: Remote Department: Marketing Reports to: Senior Manager, Marketing GTM Why Join Omnicell?" So we might want to include location, department, reports to in About the role or maybe as a short p. The instructions: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include location, department, reports to in a short p before About the role or within About the role. Probably better to include them in a short p before the About the role heading? But we cannot have extra text outside sections? The instruction: Output ONLY the HTML fragment. It didn't forbid having a p before first heading. But we could incorporate them into About the role paragraph. Let's include location, department, reports to in the About the role paragraph: "Location: Remote. Department: Marketing. Reports to: Senior Manager, Marketing GTM." Then the rest. Thus About the role paragraph: "Location: Remote. Department: Marketing. Reports to: Senior Manager, Marketing GTM. At Omnicell, we are transforming the future of healthcare through innovative technology that empowers providers, improves operational efficiency, and enhances patient outcomes. As a Marketing Campaign Operations Strategist, you will play a critical role in bringing our demand generation and account-based marketing strategies to life. This is an opportunity to combine marketing technology expertise, operational excellence, and data-driven execution to deliver impactful campaigns that accelerate pipeline growth across Omnicell’s portfolio. You’ll collaborate with cross-functional marketing, digital, and sales stakeholders while helping build scalable programs that create measurable business impact." Now Responsibilities: we have the list. Requirements: Minimum Qualifications list. Qualifications: Preferred Qualifications list. Benefits: as given. Pay: as given. Schedule: as given. Check we didn't miss any substantive info: The "How You’ll Elevate at Omnicell" section includes behaviors: Collaborate, Inspire, Develop, Execute, Impact. That's substantive; we might want to include that somewhere. Could be part of Skills or Qualifications? It's about behaviors/competencies. Could be placed under Qualifications or maybe a separate section like "Competencies". But we don't have a heading for that. We could incorporate into Qualifications as bullet points. Or we could create a Skills section for those behaviors. Since we omitted Skills, we could add them under Qualifications as well. But we must not invent sections;