Revenue Operations Manager, Marketing

We need to output HTML fragment with sections: About the role? The posting includes "About This Role Your Mission" etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse content and create sections accordingly. We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). The posting includes "Why us?" and "About Us" and "Life at Linnworks". Those may be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why us?" and "About Us" might be considered not boilerplate but maybe part of company description; but we need to keep substantive info. However we only have sections defined: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to these. We have: - About This Role Your Mission: description of role. That fits "About the role". - What You'll Do: responsibilities. - What You'll Bring To The Role: qualifications/requirements/skills. - What Success Looks Like: maybe could be part of About the role or responsibilities? Not a defined section; maybe we can incorporate into About the role or Responsibilities. - Why us? Benefits: list of benefits. That fits Benefits. - About Us: company description maybe not needed; could be omitted as not required sections. But we must preserve ALL substantive information; do not invent or summarize away detail. However we can only output sections we have headings for; if we omit About Us, we lose that info. But maybe we can include it under About the role? Not ideal. The instruction: "Prefer a few substantive sections over many thin ones." We could include a section "About the company" but not in allowed headings list. The allowed headings are specified: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only use those headings. So we need to fit all substantive info into those sections. Possibly we can put company description under About the role or maybe under Benefits? Not appropriate. Could we add a section "About the company"? Not allowed. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning examples, not exclusive? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. So we should stick to those. Thus we need to embed company description somewhere, maybe under About the role as a brief note. But we must preserve all substantive info; we can include it as a paragraph inside About the role. Similarly, "What Success Looks Like" could be part of About the role or Responsibilities. We also need to ensure we don't create sections with filler like "commensurate with experience". Not present. We need to extract Benefits: list includes 401(k) Plan with employer match, Generous medical, dental and vision plans, Flexible spending, dependent care, and health savings accounts, Short‑Term and Long Term Disability, Life Insurance and AD&D Insurance, Health and Wellness Initiatives, Workplace Flexibility, 20 days Paid time off, 10 Company Holidays, 14 Sick Days, 2 Volunteer Days, Team Member Referral Program. Pay: not mentioned. Schedule: not mentioned. So we should not create Pay or Schedule sections. We need Requirements vs Qualifications vs Skills. The posting has "What You'll Bring To The Role" which includes experience, hands-on experience, understanding, etc. Could split into Requirements (experience) and Qualifications (skills) and Skills (maybe tools). But we can just put all under Requirements or Qualifications. However we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But we have both headings allowed; we could use Requirements for experience and Qualifications for skills. Let's decide. We have: Experience: 3+ years in Marketing Operations, Revenue Operations, GTM Operations, Demand Operations or similar role, ideally within B2B SaaS or technology. Hands‑on experience owning/administering a marketing automation platform, ideally Pardot / Salesforce Account Engagement. Experience working with Salesforce‑connected marketing processes and CRM data. Strong understanding of B2B lead‑to‑opportunity funnel and Marketing‑to‑Sales processes. Experience with lead lifecycle management, campaign operations, attribution and funnel reporting. Strong systems thinking and understanding of how data, integrations, automation and reporting work together. Strong analytical and problem‑solving skills, ability to turn ambiguous GTM challenges into practical solutions. Experience leading cross‑functional projects and working with stakeholders across Marketing, Sales and Revenue Operations. Proactive, curious approach and confidence to challenge inefficient or overly manual ways of working. Experience with enrichment tools, account‑based marketing, intent data, AI‑enabled workflows or emerging GTM technology would be a plus. We could treat the first bulleted items as Requirements (experience) and the later skill items as Qualifications/Skills. Let's create:

About the role

with paragraphs covering mission, what success looks like, maybe company description.

Responsibilities

with

• list of what you'll do.

  Requirements

  with
  • list of experience requirements (3+ years, hands-on Pardot, Salesforce-connected processes, B2B funnel understanding, lead lifecycle, campaign operations, attribution, systems thinking, analytical, cross-functional projects, proactive approach).

    Qualifications

    with
    • list of skills: strong systems thinking, analytical, problem-solving, leading cross-functional, proactive, experience with enrichment tools, ABM, intent data, AI-enabled workflows, emerging GTM tech (plus maybe "would be a plus"). But we might duplicate. Could also combine Qualifications and Skills into one. Given we have Skills heading allowed, we could put technical skills there: Pardot/Salesforce Account Engagement, ZoomInfo, Clay, Qualified, Gong, enrichment tools, AI/automation, etc. Let's decide: - Requirements: experience (years, B2B SaaS, etc.) - Qualifications: core competencies (systems thinking, analytical, problem-solving, cross-functional leadership, proactive) - Skills: specific tools/platforms (Pardot/Salesforce Account Engagement, Salesforce-connected processes, ZoomInfo, Clay, Qualified, Gong, enrichment tools, ABM, intent data, AI-enabled workflows, emerging GTM tech) We need to ensure we don't create sections with filler. All have content. Benefits section: list benefits. We must not include Pay or Schedule. Now we need to strip boilerplate: "Why us?" includes benefits list; we already captured benefits. The "Why us?" also includes culture statements: "We embrace diversity and inclusion..." etc. That's maybe boilerplate? It's about culture; could be considered part of Benefits? Not exactly. Might be considered EEO/equal-opportunity boilerplate; we should remove. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the diversity/inclusion statement and culture statements. Also remove "About Us" and "Life at Linnworks" sections as they are likely boilerplate/company description. However we need to preserve substantive information; but company description may be considered not essential to the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. But company description might be considered substantive? However they also said remove EEO/equal-opportunity boilerplate; "About Us" may not be EEO but still maybe considered boilerplate. The safe approach: keep only role-specific info: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Omit company description. Thus we will not include "About Us" or "Life at Linnworks". We'll keep benefits. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine mission and what success looks like. Paragraph: "We’re looking for a Revenue Operations Manager, Marketing to be the primary RevOps partner to our Marketing team at Linnworks. This is a hands‑on role for someone who understands how systems, data, process and automation come together to help Marketing generate demand, create pipeline and measure its impact on revenue. You’ll own the operational framework behind our marketing funnel — from campaign infrastructure and lead lifecycle management to scoring, routing, attribution, data quality and Marketing‑to‑Sales handoffs. You’ll work closely with Marketing, Sales, Revenue Operations and our Salesforce team to build processes that are scalable, measurable and easy for teams to use. We’re also investing in how we use AI, automation, enrichment and emerging GTM technology. You’ll play an important role in identifying practical ways these tools can reduce manual work, improve data quality, and help us identify, engage, and convert prospects more effectively. This position is open to applicants who live in either the Eastern or Central US time zones." Then maybe add success: "You’ll help us build a Marketing Operations function that scales: clearer lead management and handoffs, better data, stronger attribution and funnel visibility, less manual work, and a MarTech stack that genuinely supports the business. Most importantly, you’ll become a trusted operational partner to Marketing — helping the team execute more effectively and clearly demonstrate its contribution to pipeline and revenue." We can include that as another paragraph. Now Responsibilities: list items from "What You'll Do". Let's extract each bullet: - Act as the primary Revenue Operations partner to Marketing, translating business priorities into scalable processes, systems, data and reporting solutions - Own and continuously improve our Marketing Operations framework across technology, automation, governance and measurement - Own Pardot / Salesforce Account Engagement from a Marketing Operations perspective and help ensure our wider MarTech stack is effectively integrated and governed - Manage and improve the lead lifecycle, including capture, scoring, routing, nurture, recycling, ownership and Marketing‑to‑Sales handoffs - Own campaign operations and standards, including campaign structure, taxonomy, UTMs, segmentation, automation and QA - Improve Marketing data quality through better enrichment, deduplication, field governance, consent management and database hygiene - Help us get more value from tools including ZoomInfo, Clay, Qualified and Gong - Identify and implement practical AI and automation opportunities across Marketing and the wider GTM organization - Partner with our Salesforce and BI teams to improve funnel, attribution, campaign and pipeline reporting - Use performance data to identify conversion gaps, risks and opportunities across the funnel - Lead cross‑functional Marketing Operations initiatives from requirements and implementation through documentation, training and adoption Now Requirements: list experience items: - 3+ years of experience in Marketing Operations, Revenue Operations, GTM Operations, Demand Operations or a similar role, ideally within a B2B SaaS or technology business. - Hands‑on experience owning or administering a marketing automation platform, ideally Pardot / Salesforce Account Engagement - Experience working with Salesforce‑connected marketing processes and CRM data - Strong understanding of the B2B lead‑to‑opportunity funnel and Marketing‑to‑Sales processes - Experience with lead lifecycle management, campaign operations, attribution and funnel reporting - Strong systems thinking and an understanding of how data, integrations, automation and reporting work together - Strong analytical and problem‑solving skills, with the ability to turn ambiguous GTM challenges into practical solutions - Experience leading cross‑functional projects and working with stakeholders across Marketing, Sales and Revenue Operations - A proactive, curious approach and the confidence to challenge inefficient or overly manual ways of working Now Qualifications: maybe core competencies: strong systems thinking, analytical, problem‑solving, leading cross