Sr. MarTech Manager, Paid Media

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. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to parse the posting. Let's extract sections: - About The Role: description paragraph(s). We'll put under

About the role

with

content. - Responsibilities: list of duties. The posting includes many bullet-like sentences after "In this role, you can expect to". Those are responsibilities. Also later "Act as a trusted technical partner..." etc. We'll gather responsibilities. - Requirements: maybe "To thrive in this role, you have [7+] years..." etc. That's requirements. - Qualifications: maybe similar to requirements? Might be overlapping. We could combine but spec says separate sections if content exists. We'll see if there is distinct "Qualifications" heading in posting? Not explicit. The posting includes "To thrive in this role, you have..." which is requirements. Then later "Deep hands-on experience..." etc. Those could be qualifications or skills. We'll need to decide. - Skills: maybe list of technical skills: APIs, SDKs, etc. - Benefits: The posting mentions "Full-time employees are also eligible for a bonus, competitive equity package, and benefits." Also later "What We Offer For Our Full-time, Regular Employees" includes many benefits. So we have benefits content. - Pay: The posting includes base salary range $153,000 to $200,000, plus bonus, equity. So we have pay. - Schedule: The posting includes "Our in-office work policy is designed to keep you connected - with four days a week in the office and Fridays from home for those near one of our offices, plus team and company-wide events depending on location." That's schedule info. We must not include sections with filler like "commensurate with experience". We have actual specifics. We must not include duplicated lines. We'll need to condense but preserve all substantive info; we can combine similar points but not lose detail. However we must not invent or summarize away detail. Summarizing may be okay if we keep the meaning? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details; we need to keep them. But we can still use

• to list each duty/requirement etc. We can break into multiple items but must keep all details. That's a lot; but we can try to capture each distinct point. Given length, we need to be concise but still include all specifics. Might be huge but okay. Let's extract each bullet. From "In this role, you can expect to": - Identify capability gaps, technical risks, and opportunities across paid media channels that support long-term channel goals — then help prioritize, shape, and execute the roadmap. - Translate channel and business objectives into technical requirements, integration plans, validation criteria, and clear ownership boundaries. - Coordinate onboarding and integration of paid media platforms, measurement partners, data providers, and activation destinations from requirements through launch and ongoing improvement. - Own the MarTech side of measurement and signal quality across conversion tracking, server-side conversion APIs, tag and event implementations, mobile measurement, attribution, deep linking, audience flows, and platform integrations. - Troubleshoot discrepancies across ad platforms, measurement partners, and first-party systems, partnering with Engineering, Data and Analytics, and channel teams when issues cross into their domains. - Bring particular depth to mobile and app measurement, including mobile measurement partners, post-ATT iOS measurement, aggregated postbacks, self-attributing networks, deep linking, deferred deep linking, SDK behavior, and app-campaign integrations. - Run vendor evaluations and RFPs end to end: define selection criteria, assess technical and measurement capabilities, coordinate security and privacy review, evaluate integration and migration effort, support contracting and renewal decisions, and hold vendors accountable to what they committed to deliver. - Evaluate and operationalize AI-enabled marketing capabilities, including creative tagging, performance prediction, campaign optimization recommendations, bidding and optimization signals, and workflow automation. - Lead pilots with clear hypotheses, measurable success criteria, appropriate controls, and explicit kill criteria. - Build practical skills, automations, or lightweight workflows yourself when that is the fastest and safest way to improve how marketing teams work. - Define metrics and standards that show whether the paid media MarTech layer is working, including measurement reliability, signal quality, integration health, time to launch, adoption, vendor performance, and spend efficiency. - Act as a trusted technical partner across Growth Marketing, Media and Acquisition, Product, Engineering, Data and Analytics, Legal, Risk, and external partners. That's responsibilities. Now requirements: "To thrive in this role, you have [7+] years in paid media technology, marketing technology, growth or marketing operations, ad tech, marketing engineering, or a related technical role — with ownership of platform integrations, not only usage of them." Then list: - Deep hands-on experience across paid media MarTech, with meaningful depth in at least two areas such as paid search, paid social, programmatic or omnichannel DSPs, mobile and app measurement, affiliate technology, media analytics, attribution, or bid management. - Direct experience implementing or specifying conversion tracking, server-side conversion APIs, tags and events, audience activation, and integrations that move paid media signals between platforms and internal systems. - You understand the handoffs to Data and Analytics without owning warehouse architecture or analytical models. - Strong mobile and app measurement experience, including practical knowledge of mobile measurement partners, post-ATT iOS measurement, aggregated postbacks, deep linking or deferred deep linking, self-attributing networks, SDKs, and app-campaign integrations. This is an important area of depth for the role. - Technical fluency with APIs, SDKs, data schemas, event taxonomies, identity and audience syncs, consent constraints, match rates, and the difference between a platform limitation, an implementation problem, and a data-quality issue. - A track record writing technical requirements and integration specifications that engineers and vendors can act on, including edge cases, monitoring needs, validation plans, and clear ownership boundaries. - Experience running vendor evaluations or RFPs end to end, including capability assessment, technical fit, security and privacy review, integration and migration effort, contract leverage, renewal decisions, and ongoing performance management. - Demonstrated ability to troubleshoot measurement and integration issues directly, hold a root-cause conversation with a vendor's solutions engineer, and communicate a clear interim assessment while the investigation is still underway. - Excellent communication and cross-functional influence skills. You can be credible with channel marketers, vendors, engineers, Product, Data and Analytics, Legal, and Risk — without relying on positional authority. - Practical experience evaluating AI or machine-learning marketing capabilities, with a healthy skepticism of vendor-reported lift and the ability to design pilots that produce a decision rather than just a demo. Then "Nice-to-have" items: we could treat as Qualifications or Skills? They are nice-to-have experience. Nice-to-have list: - Experience in fintech, financial services, or another regulated environment preferred, including comfort with consent, privacy, signal sharing, data matching, and compliance constraints. - Experience with incrementality and geo testing, media mix modeling, multi-touch attribution, survey-based attribution, clean rooms, creative measurement, dynamic creative optimization, or offline and upper-funnel channel measurement. - Experience evaluating AI-enabled creative, campaign optimization, bidding, audience, or marketing operations tools and deciding which pilots to scale, pause, or stop. - Experience building monitoring, QA, or alerting that catches broken tags, missing postbacks, audience sync failures, data-quality issues, or channel measurement drift before they become business problems. - Broader MarTech experience beyond paid media preferred, including CDP and reverse ETL, identity resolution, lifecycle or CRM platforms, web and CMS, experimentation, event taxonomy and instrumentation, personalization platforms, content or asset systems, or marketing data governance. We could put these under "Qualifications" or "Skills". Since they are experience/qualifications, maybe "Qualifications". But we also have "Skills" maybe for technical skills like APIs, SDKs etc. However many of those are already in requirements. We could structure: - About the role (paragraph) - Responsibilities (ul) - Requirements (ul) covering the required experience. - Qualifications (ul) covering nice-to-have. - Skills (maybe not needed if covered). But we could still include a Skills section for technical fluency items? However they'd duplicate. Better to put technical fluency under Requirements or Skills. Since we already have Requirements covering experience, we could put technical fluency under Skills. But the instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one? But they ask to use headings for sections like Requirements, Qualifications, Skills. We'll include only those with real content. We have content for Requirements (the required experience). We have content for Qualifications (nice-to-have). We have content for Skills? Could list technical fluency items: APIs, SDKs, data schemas, event taxonomies, identity and audience syncs, consent constraints, match rates, understanding difference between platform limitation etc. Those are already in requirements but could be moved to Skills. However to avoid duplication, we could keep them in Requirements and not create Skills section. But then Skills heading would be empty -> not allowed. So we omit Skills. Benefits: from "What We Offer For Our Full-time, Regular Employees" includes many items. We'll list them. Pay: base salary range $153,000 to $200,000, plus bonus, competitive equity package. Also mention actual base may be higher depending on location etc. Schedule: in-office work policy: four days a week in office, Fridays from home for those near one of our offices, plus team and company-wide events depending on location. Also mention fully remote program? It says "Whether you’re coming in regularly or are part of our fully remote program, you’ll stay engaged". So schedule includes hybrid and remote options. Now we need to strip boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes a lot of EEO at end; we must remove that. Also remove "A Little About Us" maybe? That's not boilerplate but it's about company; is that substantive? It's about Chime mission. Might be considered substantive but not required sections. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." However we only need to output sections for the headings listed. The "A Little About Us" is not under any of those headings; we could omit it because it's not requested. The instruction says "Output ONLY the HTML fragment — no /, no markdown code fences." It doesn't say we must include all text; we must include all substantive information but only under those headings? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That seems to refer to the content we include; we shouldn't omit details from the posting when we include them. But we can choose to not include sections that aren't requested? The headings list is given; we should include sections only when posting has real specific content for it. So we can omit "A Little About Us" because it's not under any of those headings. However that is substantive info about company; but not requested. The instruction may be interpreted as: when we include a section, we must preserve all substantive info from the posting for that section. Not that we must include every piece of the posting somewhere. So we can omit the "A Little About Us" paragraph. Similarly remove "We know that great work can’t be done without a diverse team..." EEO etc. Now craft HTML. We'll start with

  About the role

  ...

  Then

  Responsibilities

  • ... each responsibility. Then

    Requ