Senior Manager, Strategic Insights & retail Media Operations
or drop it. The posting includes location, brand, time type, contract type. Probably we can include a short
for metadata like "Location: New York | Brand: Iprospect | Time Type: Full time | Contract Type: Permanent". Or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short
for location etc. We need to preserve all substantive information. So we need to capture: - About the role: description paragraphs at start: "We're seeking a strategic operator who bridges data-driven insights with operational excellence. This role combines brand analytics, audience strategy, and operational innovation to drive non-endemic advertiser growth while optimizing the frameworks that make retail media networks scale. You'll be part analyst, part architect—building both the case for why non-endemic brands should invest in retail media networks AND the systems that enable seamless execution at scale. You'll report to the Group Director, Commerce & Retail Media and partner closely with internal Dentsu teams, agency media planners, and retail/commerce network partners. This is a highly cross-functional role requiring deep operational expertise, strong storytelling instincts, and a passion for turning insights into action. The ideal candidate combines deep analytical expertise with a passion for process improvement and product innovation. They understand the end-to-end lifecycle of both strategic insights and operational frameworks—from market research through execution to measurement and continuous improvement." That's the about. - Responsibilities: The bullet points under sections: Strategic Insights & Non-Endemic Growth, Operational Strategy & Product Enablement, Cross-Functional Partnership & Storytelling. Those are responsibilities. We can combine into a
- list.
- Requirements: The "What You Will Bring" bullet list (systems thinker etc.) maybe considered Requirements or Skills. Also "Required Qualifications" list. We need to decide sections: Requirements, Qualifications, Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have:
- Required Qualifications: list of qualifications (3–6+ years experience etc.)
- Nice to Have: list (experience with RMN/CMN etc.) Could be considered Skills or Qualifications? Probably Qualifications includes required and nice-to-have? But we have separate headings: Requirements, Qualifications, Skills. We need to decide what goes where.
We could treat:
- Requirements: the "What You Will Bring" bullet list (skills/attributes). Or maybe "What You Will Bring").
- Qualifications: the Required Qualifications list.
- Skills: maybe the Nice to Have list? Or we could combine nice-to-have into Skills.
But we need to avoid thin sections. Let's see content:
What You Will Bring bullet list:
- Systems thinker who sees both how to improve the organization and the strategy behind each process
- Data-driven storyteller who explains complex findings simply to non-technical audiences, using visuals and clear takeaways over dense detail
- Cross-functional influencer who aligns technical, operational, and client-facing teams without direct authority
- Turns operational challenges and market opportunities into practical, scalable solutions
- Curious about AI, automation, and emerging tech, and eager to use them to improve operations and insights
- Comfortable with ambiguity and skilled at building the structure and governance that help organizations grow
- Proactive communicator and collaborator who bridges technical, operational, and business teams
- Passionate about non-endemic growth in retail media and how seemingly unrelated brands create value for retailers
That's a set of competencies/skills.
Required Qualifications list:
- 3–6+ years in retail media, commerce media, shopper marketing, media analytics, or advertising operations (agency, platform, retailer, or network side)
- Demonstrated success building sales/performance narratives that moved media budget—you know how to make data influence decision-making
- Experience designing, improving, or scaling operational workflows within retail media, eCommerce, digital advertising, or SaaS environments
- Track record leading process improvement or operational transformation initiatives
- Comfort with audience data, overlap analysis, and first-party data (loyalty data, clean-room environments a plus)
Nice to Have list:
- Experience with RMN/CMN ecosystem players, measurement partners, or retail-specific analytics platforms
- Background in sports, retail, or hospitality vertical media networks
- Familiarity with loyalty-driven monetization models
- Experience supporting self-service advertising products or platform operations
- Background implementing automation, AI-enabled workflows, or operational tooling
- Knowledge of ad serving technologies, order management systems, or campaign management platforms
We could map:
- Requirements: the "What You Will Bring" list (maybe considered requirements/skills). But the heading "Requirements" is appropriate for mandatory requirements. However the "What You Will Bring" list seems more like desired skills/attributes, not strict requirements. The Required Qualifications list is definitely requirements. So perhaps:
- Qualifications: Required Qualifications list.
- Skills: Nice to Have list (or combine with What You Will Bring). But we also have "What You Will Bring" which could be considered Skills.
We need to avoid too many thin sections. Perhaps we can combine "What You Will Bring" and "Nice to Have" into a Skills section, and keep Qualifications for Required Qualifications. Then we might not need a separate Requirements section. But the instruction says we can include a section only when posting has real specific content for it. So we can omit Requirements if we don't have distinct content. However we have "What You Will Bring" which could be considered Requirements? But it's more like desired attributes. Yet we could treat it as Requirements. Let's decide:
We'll have:
- About the role (paragraph)
- Responsibilities (ul list of the three sections)
- Qualifications (ul list of Required Qualifications)
- Skills (ul list combining What You Will Bring and Nice to Have)
- Benefits (ul list of benefits)
- Pay (p with salary range)
- Schedule (p with work schedule info: "Employees who live within a commutable distance of one of our hub offices, currently located in Chicago, metro Detroit, Los Angeles, and New York City, are required and expected to work from the office three days per week (two days per week for employees based in Los Angeles). Dentsu may designate other Hub offices at any time. Those who live outside a commutable range may be designated as remote, depending on the role and business needs. Regardless of your work location, we expect our employees to be flexible to meet the needs of our Company and clients, which may include attendance in an office.") That's schedule info.
We should also include location metadata maybe as a short p before sections: "Location: New York | Brand: Iprospect | Time Type: Full time | Contract Type: Permanent". That is minor metadata.
We must not include application instructions, EEO boilerplate, etc. Remove the equal opportunity statement, accommodation request, etc. Also remove "To begin the application process..." etc. Also remove "At dentsu, we believe great work happens..." etc. Also remove "Dentsu is committed to providing equal employment opportunities..." etc. Also remove "Dentsu also complies with applicable state and local laws regarding employee leave benefits..." maybe that's part of benefits? It's about leave benefits; but we already have benefits list includes paid sick and safe leave, paid parental leave, etc. The extra sentence about Colorado Healthy Families and Workplaces Act is maybe boilerplate legal; we should remove as per instruction: remove EEO/equal-opportunity/scam-warning boilerplate. That sentence is about compliance with state laws; could be considered legal boilerplate. Safer to remove.
Also remove "For further details regarding Dentsu benefits, please visit www.dentsubenefitsplus.com." That's application instruction? It's a link for benefits details; could be considered navigation? Probably remove.
Also remove "Applications will be reviewed on an ongoing basis, and qualified candidates will be contacted for next steps." That's application instruction; remove.
Also remove "At dentsu, we believe great work happens when we're connected..." etc. That's boilerplate; remove.
Also remove "Dentsu is committed to providing reasonable accommodation..." etc. That's EEO/accommodation; remove.
Also remove "We are here to support you." etc.
Now we need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
Location: New York | Brand: Iprospect | Time Type: Full time | Contract Type: Permanent
About the role
We're seeking a strategic operator who bridges data-driven insights with operational excellence. This role combines brand analytics, audience strategy, and operational innovation to drive non-endemic advertiser growth while optimizing the frameworks that make retail media networks scale. You'll be part analyst, part architect—building both the case for why non-endemic brands should invest in retail media networks AND the systems that enable seamless execution at scale. You'll report to the Group Director, Commerce & Retail Media and partner closely with internal Dentsu teams, agency media planners, and retail/commerce network partners. This is a highly cross-functional role requiring deep operational expertise, strong storytelling instincts, and a passion for turning insights into action. The ideal candidate combines deep analytical expertise with a passion for process improvement and product innovation. They understand the end-to-end lifecycle of both strategic insights and operational frameworks—from market research through execution to measurement and continuous improvement.
Responsibilities
- Strategic Insights & Non-Endemic Growth: Build the case for non-endemic brands in retail media networks using sales lift, incrementality, and attribution data, plus industry and market trends; partner with internal Dentsu teams on audience overlap and first-party data to find customer-base alignment opportunities; turn audience and performance data into strategic POVs and business cases that give agency media teams clear reasons to shift budget into RMNs/CMNs; contribute insights to presentations, POVs, and expansion strategies for retail/commerce clients; monitor the competitive landscape, advertiser demand, and market trends to bring outside-in intelligence into strategy work.
- Operational Strategy & Product Enablement: Design scalable operational frameworks and continuous improvement roadmaps for retail media workflows across managed-service and self-service products; evaluate existing processes and find ways to simplify, standardize, automate, and scale operations across teams; partner with Product and Engineering to prioritize operational enhancements and improve platform usability based on day-to-day operational insights; create standard operating procedures, governance models, and playbooks that improve consistency and decision-making; use data, automation, AI, and operational tooling to lead continuous improvement and boost productivity; lead change management and adoption of new processes and platform capabilities, including documentation and training.
- Cross-Functional Partnership & Storytelling: Turn complex data and operational challenges into clear narratives that shape budget decisions and strategic direction; create data visualizations and POVs for agency media planners and retail partners, focused on clear takeaways rather than dense reporting; connect insights, operations, and strategy so all teams see how data and process improvements drive business outcomes; influence without direct authority across internal Dentsu teams (Audiences, Analytics, Account Management), Product/Engineering, and external agency partners; advise leadership on operational risks, workflow gaps, and dependencies, and recommend scalable solutions that strengthen governance and maturity.
Qualifications
- 3–6+ years in retail media, commerce media, shopper marketing, media analytics, or advertising operations (agency, platform, retailer, or network side)