Delivery Manager

We need to output HTML fragment with sections: About the role? Actually we have sections: About VideoAmp (company description) maybe not needed? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - About VideoAmp (company description) - could be "About the role"? Actually "About the role" is a heading suggestion, but we have "The Role" section describing responsibilities. Could treat that as "About the role" or "Responsibilities". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate ones. We have: - The Role: description of what the Delivery Manager does (responsibilities). Could be "Responsibilities". - What You'll Do: bullet list of duties (client onboarding, platform configuration, reporting & deliverables, support & troubleshooting, ongoing account support). That's responsibilities. - What You'll Bring: qualifications/experience/skills. Could be "Requirements" or "Qualifications" and "Skills". We have required experience and nice-to-haves. - Compensation & Benefits: includes base salary, equity, time off, health, financial, family, perks. That's Benefits and Pay. - Our Values: maybe not needed? Could be omitted as not a standard heading; but could be considered "About the company"? However instruction says include a section only when posting has real, specific content for it. Values are specific but not a standard heading; we could omit or maybe include as "About the company"? But they didn't list that as example heading; but we could still include if we think it's substantive. However they said prefer a few substantive sections over many thin ones. Values might be thin; but it's still substantive. However they gave examples of headings; we could add a section "About the company" but not in list. Safer to stick to the given headings. Thus we can have sections: - Responsibilities (What You'll Do) with sub-sections? Could break into subheadings? But we only need to output HTML fragment; we can include

  for each main section. Inside we can have

  • for lists. - Requirements / Qualifications (What You'll Bring) maybe combine required and nice-to-haves. - Benefits (Compensation & Benefits) maybe also include Pay (base salary) but they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state base salary and equity, so we can include Pay and Benefits. Could combine into one section "Compensation & Benefits" but they gave separate headings Pay and Benefits. We could make two sections: Pay and Benefits. However they said prefer a few substantive sections over many thin ones. So maybe combine into one section "Compensation & Benefits". But they said use headings like Pay, Benefits, etc. It's ambiguous. I'd include a single section "Compensation & Benefits" as it's substantive. We also need to include location: Remote US. Could be a short

    at top. We must not include boilerplate like EEO, values maybe? Values could be considered boilerplate? It's not EEO but still company values. Might be okay to keep but it's not a standard heading; we could drop. We must not repeat job title as heading. So no heading for "Delivery Manager". We must not include Job ID/requisition numbers. We must not include application instructions. We must not include duplicated lines. Now craft HTML. Start with a

    for location and maybe brief company overview? The "About VideoAmp" paragraph is substantive; we could include as a section "About the company" but not in list. However we could incorporate into a

    before sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we include a section "About the company" but not in list; but they didn't forbid other headings, just gave examples. Safer to include a section "About the company" as

    About the company

    with paragraph. But they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can use other headings as needed. Thus we can have:

    About the company

    VideoAmp is the tech-first measurement company transforming how advertising is valued, bought, and sold. Powered by currency-grade big data and a best-in-class technology stack, our platform gives advertisers, agencies, and digital partners the ability to plan, optimize, and measure media investments across every screen, from linear TV and OTT to CTV and digital video. VideoAmp is accelerating investment in agentic AI and intelligent optimization technologies, helping clients drive measurable, real-world outcomes in an increasingly complex media landscape. With 880% year-over-year measurement growth, 98% coverage of the TV ecosystem, and partnerships with 11 agency groups and 1,000+ advertisers, we're not just keeping pace with the industry. We're defining what comes next.

    Then location: maybe a

    Remote US

    before sections. Then Responsibilities:

    Responsibilities

    then list of duties. The posting has bullet points under "What You'll Do" with subheadings: Client Onboarding, Platform Configuration & Data Management, Reporting & Deliverables, Support & Troubleshooting, Ongoing Account Support. We could make each a

    ? But we only allowed

    for section headings; we could still use

    for subheadings? Not prohibited. But to keep simple, we can make a flat list of responsibilities using

    • each duty. However we risk losing detail. Better to keep subheadings as

      maybe okay. The instruction didn't forbid other heading levels; just said use

      for section headings (e.g...). It didn't say you cannot use other headings. So we can use

      for sub-sections. Thus:

      Responsibilities

      Client Onboarding

      ? Actually need proper nesting:

      Client Onboarding

      then
      • ... etc. We'll need to preserve all substantive information: each bullet under each subheading. Let's extract: Client Onboarding: - Partner with Account Management to schedule and help lead onboarding calls, confirming measurement scope, deliverables, and service expectations. - Send onboarding workbooks to clients and submit tickets for any setup items that are not self-service, looping in Solutions Engineers to address technical questions. Platform Configuration & Data Management: - Build and maintain custom audiences within the platform based on client-defined criteria. - Own creative fingerprinting for RaaS/CTV measurement, as captured in the client's digital data onboarding workbook. - Request and validate metadata mapping before building any client deliverable. - Open and manage tickets for pixel QA and discrepancy checks, escalating to Account Management when a client is unresponsive to changes that could impact renewal or upsell opportunities. Reporting & Deliverables: - Build and deliver platform dashboard reporting stipulated in the client's contract or order. - Build templated and contracted reporting decks in partnership with Account Management, who provides templates and any bespoke upsell content and owns final delivery of assets to the customer. Support & Troubleshooting: - Create and manage JIRA tickets for onboarding and troubleshooting needs. - Support troubleshooting of platform issues, including data discrepancies, report failures, and access issues. - Manage support requests tied to known product limitations (e.g., walled-garden reporting, local measurement). Ongoing Account Support: - Support recurring Office Hours and quarterly Account Reviews. - Provide input into billing-related reporting and account-specific trackers. - Contribute context and ticket history to escalations related to product issues, feature gaps, or revenue risk. - Stay informed on account plans, renewals, and capability upsell opportunities to help flag risk or growth signals. Now Requirements/Qualifications: What You'll Bring: - 4+ years of experience in a client-facing delivery, implementation, or technical account management role, preferably in ad tech, media measurement, or a related data-driven industry. - Strong organizational skills with the ability to manage multiple client accounts, tickets, and deliverables simultaneously without dropping details. - Comfort working with data platforms, ticketing systems (e.g., JIRA), and technical concepts such as pixels, tags, and data mapping. - Fluency in Microsoft Excel and PowerPoint; comfort learning new internal platforms and tools. - Strong written and verbal communication skills, with the ability to work cross-functionally with Sales, Account Management, and Solutions Engineering. - A proactive, QA-focused mindset with an interest in building repeatable, scalable delivery processes. - Ability to navigate ambiguity and escalate appropriately when client needs or risks arise. Nice-to-Haves: - Experience with pixel/tag implementation, ad serving platforms, or digital audience measurement. - Familiarity with CTV, cross-screen, or walled-garden measurement concepts. We could combine required and nice-to-haves under a section "Qualifications" with two sublists: Required and Preferred. Now Compensation & Benefits: Compensation & Benefits: - Base Salary $94,000 to $105,000 (commensurate with experience) - Equity participation included - Time Off: Discretionary & flexible PTO + Spring, Summer & Winter company breaks - Health: Inclusive and comprehensive medical, dental & vision - Financial: 401(k) with matching HSA & FSA - Family: Paid Maternity & Parental Leave for all family additions - Perks: Cell phone & wifi reimbursement, Commuter benefits We need to avoid filler like "commensurate with experience" - that's placeholder? It's actually a phrase but they said never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The phrase "commensurate with experience" is considered filler? They gave it as example of filler to avoid. So we should not include that phrase. We should just state the salary range without the qualifier. So "Base Salary $94,000 to $105,000". Equity: "Equity participation included". That's fine. Now we need to ensure we don't include any boilerplate like EEO, values, etc. We'll drop the "Our Values" section and the EEO statement at end. Also drop duplicated lines like "VideoAmp is an equal opportunity employer..." etc. Now produce HTML. We'll start with a

        for location: Remote US. Maybe also include a short

        for the company overview? Already have