Vice President Group Director, MarTech Strategist – Systems and Experience Engineering
HybridEngineering$168k/yrFull-time
We need to output HTML fragment with headings
for 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 as heading. Must not include Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions.
We need to preserve all substantive information.
Let's parse the posting.
Company Description: Digitas description. That's not a section heading but could be part of About the role? The posting includes "Company Description" then "Overview Vice President Group Director, MarTech Strategist – Systems and Experience Engineering". Then description of role. Then "Key Responsibilities". Then "Qualifications". Then "Additional Information" includes benefits, compensation range, etc.
We need sections: About the role (maybe overview), Responsibilities, Requirements (maybe qualifications?), Qualifications (maybe separate?), Skills, Benefits, Pay, Schedule.
We need to decide what content goes where.
We have:
- Overview: description of role, consulting role, what you will do, fit, etc. That could be "About the role".
- Key Responsibilities: list of responsibilities bullet points.
- Qualifications: list of required and preferred qualifications.
- Additional Information: includes benefits description, compensation range, etc.
We also have "Company Description" which could be part of About the role? Might be separate but we don't have a section for company description; we could incorporate into About the role as a paragraph.
We need to avoid headings with filler like "commensurate with experience". Not present.
We need to include Pay section only if posting states compensation range. Yes: "Compensation Range: USD $168,150.00 - USD $241,605.00/Annually." Also mention bonus/incentive eligibility. So we should have Pay section with that info.
Benefits section: Additional Information includes benefits package: medical coverage, dental, vision, disability, 401K, parental and family care leave, family forming assistance, tuition reimbursement, flexible time off. Also mention Publicis Groupe motto etc. So we can include Benefits.
Schedule: Not mentioned. No schedule info (like full-time, remote). So we should NOT include Schedule heading.
Skills: Could be derived from qualifications? Might be separate but we could combine with Qualifications. However we need to decide if we have a Skills section with specific content. The posting does not have a separate "Skills" heading; but we could extract skills from qualifications: e.g., "Strong communication, facilitation, presentation, client engagement skills", etc. But we should not invent sections without real specific content. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if not explicitly present. However the list of allowed headings includes Skills; we can include if there is real specific content. The posting does mention skills in qualifications: "Strong communication, facilitation, presentation, and client engagement skills, especially with senior stakeholders." Also "Strong written and visual storytelling skills". Those are skills. So we could create a Skills section with those bullet points. But we also have Qualifications section which includes required and preferred experience. Might be better to keep Qualifications as required/preferred experience, and Skills as specific skill bullets. However the instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can choose which to include.
We need to preserve ALL substantive information. If we split qualifications into Requirements and Qualifications and Skills, we must ensure we don't lose info. Let's see what content we have:
- Required: 10+ years experience in technology strategy, product strategy, MarTech consulting, digital product, or enterprise marketing technology leadership.
- Experience in an agency, consulting, professional services, or client-facing advisory environment.
- Ability to turn business goals, user needs, workflows, platforms, and constraints into clear product direction, requirements, roadmaps, and delivery-ready briefs.
- Familiarity with MarTech, AdTech, data flows, generative AI, agentic workflows, orchestration, and responsible AI practices.
- Experience developing business cases, value models, adoption plans, and executive-ready recommendations.
- Strong communication, facilitation, presentation, and client engagement skills, especially with senior stakeholders.
- Experience guiding cross-functional teams through discovery, prioritization, planning, and delivery alignment.
- Strong written and visual storytelling skills, including assessments, roadmaps, operating models, workflow maps, and recommendations.
Preferred:
- Background with a major consultancy, systems integrator, digital agency, or enterprise MarTech organization.
- A track record of leading enterprise marketing technology assessments, selections, and transformation programs for large or complex organizations.
- Experience building business cases and presenting them to executive and financial decision makers.
- Exposure to AI orchestration, workflow automation, agent-enabled operating models, or vendor/platform evaluation.
- Experience supporting change management or adoption programs for marketing, content, media, data, or experience teams.
- Certification or hands-on experience with enterprise marketing platforms.
- Experience in regulated categories such as financial services, healthcare, or automotive.
- Public speaking published thought leadership, or external-facing point-of-view development.
Thus we could have:
- About the role (overview paragraph)
- Responsibilities (list)
- Qualifications (maybe combine required and preferred as list)
- Benefits (list)
- Pay (paragraph)
We could also have Requirements (maybe same as Qualifications). But to avoid duplication, we could treat Qualifications as required and preferred. The instruction includes both Requirements and Qualifications as possible headings; we could use Qualifications for required and Preferred as a sublist? But better to follow typical pattern: Requirements = required qualifications; Qualifications = preferred? Not sure. However we can include both if we have content. Let's see: we have required and preferred; we could put required under "Requirements" and preferred under "Qualifications". That would preserve both.
Thus:
- About the role (overview)
- Responsibilities (list)
- Requirements (required qualifications)
- Qualifications (preferred qualifications)
- Benefits (list)
- Pay (compensation range + bonus)
We should not include Skills unless we have distinct skills not covered elsewhere. The required and preferred already include skills like communication, storytelling, etc. But we could still have Skills section; but that would duplicate. Better to omit Skills to avoid thin sections.
Schedule: none.
Now we need to remove boilerplate: company description? That's substantive; we can include in About the role.
We need to remove "Additional Information" heading; we will incorporate its content into Benefits and Pay.
We need to remove lines like "If you require accommodation..." etc. That's boilerplate (accommodation contact). Should be removed as it's application instruction/EEO. Also remove EEO guidelines line. Remove "All your information will be kept confidential according to EEO guidelines." Remove "Publicis Groupe provides robust and inclusive benefit programs..." Actually that's part of benefits description; we can keep the benefits list but maybe remove the fluff about motto etc. The motto "Viva La Difference" is not essential but could be considered boilerplate? It's part of Additional Information but not directly about benefits; could be removed as it's not substantive for the job. However it's part of company culture description; maybe we can keep a brief sentence about culture? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The motto is not exactly boilerplate but could be considered fluff. Safer to keep only substantive benefits list.
Thus Benefits section: list items: medical coverage, dental, vision, disability, 401K, parental and family care leave, family forming assistance, tuition reimbursement, flexible time off.
Also maybe mention "robust and inclusive benefit programs and policies to support the evolving and diverse needs of our talent and enable every person to grow and thrive." That's somewhat fluffy but could be kept as a brief intro sentence. However we need to preserve ALL substantive information; the motto and inclusive statements are not essential to job but could be considered substantive about benefits. I'd keep a short paragraph summarizing benefits: "Publicis Groupe provides robust and inclusive benefit programs including medical coverage, dental, vision, disability, 401K, parental and family care leave, family forming assistance, tuition reimbursement, and flexible time off."
Now Pay section: include compensation range and bonus eligibility.
Now About the role: combine company description and overview. Let's craft a paragraph(s) that includes Digitas description and role overview.
We must not repeat job title as heading. So we will not include heading "Vice President Group Director, MarTech Strategist". We'll just have About the role heading.
Now Responsibilities: list bullet points from Key Responsibilities.
We need to ensure we preserve all responsibilities bullet points. Let's extract them:
- Assess client MarTech environments, workflows, data usage, vendor dependencies, and adoption gaps.
- Translate business problems into product opportunities, user requirements, priorities, acceptance criteria, and measurable outcomes.
- Shape future-state solutions with solution architects across MarTech, AdTech, AI agents, integrations, and orchestration layers.
- Create practical roadmaps with clear phases, dependencies, risks, decision points, and value milestones.
- Identify where AI and automation can improve operations, campaign execution, personalization, analytics, measurement, and experience delivery.
- Define what should be automated, assisted, escalated, or kept human-led, with clear decision rights and oversight.
- Evaluate platform capabilities, vendor roadmaps, licensing constraints, data access, permissions, and orchestration options.
- Establish guardrails for privacy, consent, brand safety, auditability, governance, escalation, and model limitations.
- Build business cases, executive recommendations, and vendor evaluation inputs that support clear investment decisions.
- Design operating models and change plans covering roles, governance, communications, training, launch readiness, and post-launch support.
- Identify where resistance to the change is likely to come from and own the plan to address it.
- Coach client teams through new ways of working, with the goal of leaving behind capability rather than dependency.
- Provide strategic oversight across implementation workstreams to keep delivery aligned to outcomes, scope, quality, and adoption goals.
- Partner with delivery, architecture, engineering, QA, infrastructure, and platform teams on requirements, feasibility, sequencing, launch readiness, and roadmap feedback.
- Support new business through discovery framing, capability presentations, RFP responses, scoping inputs, and executive storytelling.
Now Requirements (required qualifications) list:
- 10+ years of experience in technology strategy, product strategy, MarTech consulting, digital product, or enterprise marketing technology leadership.
- Experience in an agency, consulting, professional services, or client-facing advisory environment.
- Ability to turn business goals, user needs, workflows, platforms, and constraints into clear product direction, requirements, roadmaps, and delivery-ready briefs.
- Familiarity with MarTech, AdTech, data flows, generative AI, agentic workflows, orchestration, and responsible AI practices.
- Experience developing business cases, value models, adoption plans, and executive-ready recommendations.
- Strong communication, facilitation, presentation, and client engagement skills, especially with senior stakeholders.
- Experience guiding cross-functional teams through discovery, prioritization, planning, and delivery alignment.
- Strong written and visual storytelling skills, including assessments, roadmaps, operating models, workflow maps, and recommendations.
Now Qualifications (preferred) list:
- Background with a major consultancy, systems integrator, digital agency, or enterprise MarTech organization.
- A track record of leading enterprise marketing technology assessments, selections, and transformation programs for large or complex organizations.
- Experience building business cases and presenting them to executive and financial decision makers.
- Exposure to AI orchestration, workflow automation, agent-enabled operating models, or vendor/platform evaluation.
- Experience supporting change management or adoption programs for marketing, content, media, data, or experience teams.
- Certification or hands-on experience with enterprise marketing platforms.
- Experience in regulated categories such as financial services, healthcare, or automotive.
- Public speaking published thought