B2B Campaign Manager

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. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting: It includes About Unleash Live (company description), The Role description, What You'll Own (streams), Scope Boundaries, What You'll Bring (essential requirements), How Success Is Measured, What You're Joining. We need to map to sections: About the role (maybe company overview and role summary). Responsibilities (what you'll own). Requirements (essential qualifications). Qualifications (maybe desired? but we have essential and valued). Skills (maybe specific skills like HubSpot, AI tooling, ABM, paid media, SEO/AEO). Benefits, Pay, Schedule: not provided, so we should NOT include those sections. We must not create sections with filler like "not specified". So omit Benefits, Pay, Schedule. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include details like company description, role description, streams details, scope boundaries, essential requirements, valued qualifications, success metrics, what you're joining. We need to avoid boilerplate like cookie/navigation/legal/EEO etc. Not present. We need to output only HTML fragment. Let's structure:

  About the role

  Unleash Live is an enterprise computer vision company... (company description) ... This is a B2B tech company. Our buyers are COOs, VP Operations, and Asset Managers at organisations running critical infrastructure across multiple sites. Our deals are complex, multi-stakeholder, and high value. Our marketing has to match. The Role: We're hiring a B2B Campaign Manager to own campaign execution across our North America and APAC market, with account-based marketing at the center of the role....

  But we need to separate responsibilities maybe. Better: About the role could include company overview and role summary. Then Responsibilities: What You'll Own (streams). Then Requirements: Essential (HubSpot proficiency, 5+ years B2B marketing enterprise deal values >$100K, AI tooling fluency or industry experience, builder's approach, commercial judgment). Then Qualifications: Highly valued (ABM experience, paid media judgment, organic/content channel depth, experience in lean fast-moving team). Then Skills: maybe list specific skills: HubSpot proficiency, AI tooling fluency, ABM, paid media for niche industrial audiences, SEO/AEO, etc. But we need to avoid duplication. Could combine. We must not repeat content unnecessarily but preserve all substantive info. Could list each bullet as
• . Let's extract bullet points: From "What You'll BringEssential": - Advanced HubSpot proficiency (independently build lists and smart segments, configure workflows and sequences, set up campaign tracking and attribution, pull reporting) - 5+ years in B2B marketing with enterprise deal values above $100K. Experience in environments with six month or longer sales cycles and multi-stakeholder buying committees, where marketing is measured on pipeline rather than lead volume. - Strong AI tooling fluency, relevant industry experience, or either qualifies. Daily practical use of AI tools in campaign and research workflows meets the bar, as does genuine experience marketing into Utilities, Oil and Gas, Mining, or comparable asset-intensive sector. - A builder's approach: energized by shipping campaigns rather than designing frameworks for others to execute; comfortable owning both streams independently, making own calls on prioritization, moving without waiting for detailed brief. - Commercial judgment: read pipeline data and draw conclusions; understand where enterprise deals stall and what marketing can do to unstick them. Then "Highly valued": - Account-based marketing experience: practical work (target account list construction and tiering, multi-touch programs against named accounts, account-level engagement tracking, feeding account intelligence back to sales). - Paid media judgment for niche industrial audiences: experience allocating budget across LinkedIn, paid search, display, video where addressable audience is small and precision matters more than volume. - Organic and content channel depth: building SEO and AEO programs that compound, running webinars and user groups as genuine pipeline channels, particularly in sectors where customer references are commercially sensitive. - Experience in a lean, fast-moving team where prioritization decisions sit with you rather than with a fully resourced campaign function. From "How Success Is Measured": - First 90 days: Build fluency in verticals and products, establish working relationships with sales team, have campaigns live and tracked in HubSpot across both streams. - From month four: - Stream 1, Sales ABM Support: * Marketing-influenced pipeline from named accounts: Contribution in USD against target account list. * Named account engagement: 2+ engagement signals per quarter per target account. * Sales-accepted leads per month: Against current FY function target. - Stream 2, Marketing Support: * Top-of-funnel pipeline contribution: From priority NAM verticals, weighted to Mining and Oil and Gas. * Event performance: Registration, attendance, follow-up conversion against event targets. * LinkedIn program efficiency: Cost per named-account engagement. * Organic growth: Traffic, ranking, answer-engine visibility trend over time. - Both streams: * HubSpot execution quality: Attribution configured, tracking complete, reporting delivered to sales. * Speed from MQL to first sales conversation: Under 5 business days. From "What You're Joining": - Small capable team building something real in a category that matters, working with technology genuinely deployed at scale with Tier 1 operators. - Foundations to build on day one: structured marketing operating system, governed AI tooling designed to accelerate research and campaign activation, defined target account list, established HubSpot infrastructure, sales team that wants marketing to succeed. - Company growing and marketing function growing with it. - Early enough seat to shape how campaign marketing scales, established enough business to build on real product, real customers, real pipeline. Also "Scope Boundaries": items that sit with other owners: Brand and visual identity (design team), Product marketing content and knowledge base (product marketing), PR and external narrative (Head of Marketing), MarTech architecture and system administration (already in place, focus is campaign execution and performance). Could be included under Responsibilities maybe as "What you will NOT own". But we can include as a note under Responsibilities or maybe as a separate section? Not required but we could include under Responsibilities as a note. We need to preserve all substantive info, so we should include scope boundaries. Now decide sections: - About the role: company description + role overview (maybe short). - Responsibilities: What You'll Own (streams details) + Scope Boundaries (what sits with other owners) maybe as note. - Requirements: Essential qualifications. - Qualifications: Highly valued (maybe treat as "Preferred qualifications"). - Skills: Could list specific skills like HubSpot, AI tooling, ABM, paid media, SEO/AEO, etc. But we already have those in requirements/qualifications. To avoid duplication, maybe we skip Skills section, or we can combine. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications. That's four sections. That's fine. We must not include Benefits, Pay, Schedule. Now produce HTML. We need to use

  for each section heading. Use

  • for any list. Use

    for prose. We need to ensure we don't create empty sections. Let's craft. About the role: combine company description and role summary. Paragraph: "Unleash Live is an enterprise computer vision company, building Orb (Automated Asset Inspections) and Prism (Always-on Asset Monitoring) for Tier 1 infrastructure operators in Utilities, Oil and Gas, Mining & Critical infrastructure. Our customers include Fortune 50 companies. We move fast, work closely together, and genuinely care about what we're building. The problems are real, the industries are critical to how the world operates, and the technology is genuinely exciting, if you want to be part of something that's going somewhere, this is it. This is a B2B tech company. Our buyers are COOs, VP Operations, and Asset Managers at organisations running critical infrastructure across multiple sites. Our deals are complex, multi-stakeholder, and high value. Our marketing has to match. The Role: We're hiring a B2B Campaign Manager to own campaign execution across our North America and APAC market, with account-based marketing at the center of the role." That's a paragraph. Now Responsibilities: We'll have a

    with items describing streams and scope boundaries. We need to preserve details: For each stream, list bullet points. Stream 1: Sales ABM Support: list of responsibilities. Stream 2: Marketing Support: list. Scope Boundaries: note what sits with other owners. We'll create maybe separate
    for each stream? Could combine but better to have headings inside? But we cannot add extra headings besides

    sections. We can embed

    headings inside? Not allowed? The instruction only says use

    for section headings. It doesn't forbid using or

    with bold. But to keep simple, we can have a

    introducing each stream then

    . Let's do:

    Responsibilities

    Stream 1 – Sales ABM Support:

    • Partner with sales to turn the named account list into consistent, well‑targeted engagement.
    • Build and run 1:1 and 1:few account‑based programs against the approved target account list.
    • Research accounts and develop campaign angles grounded in each account's specific operational context, business trigger, or asset challenge.
    • Support outbound with sequence content, account intelligence, and coordinated content amplification.
    • Align campaign sequencing with the account or vertical owner on the sales side before launch.
    • Own the HubSpot foundation for every program: company and contact lists, segmentation, workflows, sequence logic, and attribution setup.
    • Report account‑level engagement back to sales on a regular cadence, with a minimum of two engagement signals per quarter per target account.

    Stream 2 – Marketing Support:

    • Build top‑of‑funnel and always‑on programs that create demand across the North America market.
    • Design and run acquisition campaigns into priority NAM verticals, with particular focus on Mining and Oil and Gas where inbound is being built from a standing start.
    • Drive awareness, registration, and follow‑up for events, webinars, and user groups, which carry significant pipeline weight in sectors where public case studies are commercially restricted.
    • Run a continuous paid LinkedIn program targeting named accounts by company and job title, with budget allocation tied to the ABM target list.
    • Own organic and answer‑engine optimization (SEO/AEO) as a compounding channel, working with product marketing on supporting content.
    • Across both streams, ensure every campaign has a defined commercial objective, a target account list or ICP segment, HubSpot tracking configured before launch, and results reported against the original objective.
    • Measure pipeline contribution and account engagement, using reach and impression data as diagnostic signals rather than headline results.

    Scope Boundaries (owned by other teams):

    • Brand and visual identity – design team.
    • Product marketing content and knowledge base – product marketing.
    • PR and external narrative – Head of Marketing.
    • MarTech architecture and system administration – already in place; your focus is campaign execution and performance.
    Now Requirements (Essential):

    Requirements

    • Advanced Hub