VP, AI Enablement

We need to output HTML fragment with sections: About the role? Actually we have sections: Overview (description), Responsibilities, Qualifications, Benefits (maybe), Pay (compensation range). Also maybe Company Description? 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. Thus we need to decide which sections to include based on content. We have: - Company Description (intro about Razorfish). Could be considered "About the role"? Actually "About the role" is typical heading for overview. The posting includes "Overview" after company description. We can treat that as "About the role" or "Overview". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - Overview => About the role (or maybe we could keep "Overview" but they said use those examples; but we can still use "Overview"? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to use those headings. So we can have

  About the role

  containing the overview description (company description + overview). However we need to avoid duplication. The company description is generic about Razorfish; the overview is specific to role. We could combine them into one prose block. - Responsibilities: we have a big list. - Qualifications: we have qualifications section. - Benefits: we have "Additional Information" describing benefits (wellness and benefits offerings). That's substantive. - Pay: we have compensation range. - Schedule: not mentioned; we should not create schedule section. - Skills: not separate; qualifications cover. Thus we will output sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We must not include filler like "commensurate with experience". Not present. We need to use
  • for any list of duties/requirements/benefits. For responsibilities, we have a list of bullet-like sentences. We'll convert each to
  • . For qualifications, also list. For benefits, list. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics. We must remove boilerplate: EEO, legal, accommodation contact, etc. Also remove duplicated lines. Also remove application instructions (none). Also remove navigation etc. We need to keep the compensation range text exactly? We can keep as prose. We need to keep the benefits description: list of benefits. We need to keep the company description and overview. Let's extract content. Company Description: "Hi there—at Razorfish, we’re leaders in what's next. Since the dawn of the internet, we’ve helped brands move first through every era of transformation, defining what digital means for business and now leading brands into the age of AI. Everyone has a prediction. Razorfish has a track record. Named a Most Innovative Agency three years running (2024–2026) by Campaign US, our work reflects a proven ability not just to anticipate what’s coming, but to help our clients actively shape the future. No matter the trend or cultural moment, delivering real business impact wouldn’t be possible without our people. We bring together curious, driven, and diverse thinkers who challenge convention, push boundaries, and hold a high bar for creative excellence. If you’re motivated to work alongside top performers, push the boundaries of what’s possible, and help define where technology, business, and marketing are headed next—this is the place to do it. Join us at razorfish.com." Overview: "As VP of AI Enablement at Razorfish, you will lead our AI enablement strategy across three pillars: (1) internal productivity and automation, (2) client innovation and our AI story, and (3) platform AI and partnerships (Google, Meta, Amazon). The role is both hands-on and strategic — you set the direction and you build alongside the team. We have already built and shipped a suite of agentic AI web applications, in production, spanning the media-planning lifecycle. That platform is not the whole job — it is the proof that we can build at the frontier and the engine that helps enable all three pillars. Your mandate is to grow that capability, deepen adoption, sharpen our market story, and turn platform partnerships into advantage. We are looking for someone rare: hands-on enough to build alongside the team and strategic enough to set the direction. The ideal hire is already on the frontier of agentic AI — someone with the ambition and ability to have built a platform like this in the first place. At minimum, you can develop a clear vision for how to advance all three pillars, grow adoption, and keep the work evolving as the underlying tools advance." Then "The three pillars" repeats description of each pillar. Might be redundant with overview but we need to preserve all substantive info. However we should avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say to remove duplicates, but later says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. The "The three pillars" section repeats the pillar descriptions already mentioned in overview. It might be considered duplicated lines. We should deduplicate. We can keep one description of each pillar, maybe from the responsibilities section which also details each pillar. Let's see responsibilities section includes details per pillar. Responsibilities list: - Own the AI enablement strategy. Develop and own a clear vision across all three pillars: internal productivity and automation, client innovation and our AI story, and platform AI and partnerships. - Build, hands-on. This is a builder's role. You will personally prototype and ship tools using modern agentic coding environments, stand up multi-agent workflows, and steer what the team builds — not just manage a roadmap from a distance. - Architect multi-agent systems. Decide when a problem is best solved with a single well-scoped prompt versus a deterministic multi-agent pipeline with auditable, computed outputs. - Grow our agentic platform. Evolve and scale our suite of agentic apps already in production as the platform that helps power all three pillars — it serves the pillars; it is not the whole mandate. - Pillar 1 — drive internal adoption. Partner with leaders across SEO, paid search, paid social, programmatic, ad ops, strategy, and media ops to find high-leverage use cases, replace brittle spreadsheet workflows, and build the literacy and documentation that make adoption stick. - Pillar 2 — client innovation and the AI story. Turn AI capability into pitch wins, sharper client deliverables, and new products — and build and tell our AI story to clients and the market through thought leadership and a credible external voice. - Pillar 3 — platform AI and partnerships. Stay ahead of platform-native AI across major platforms such as Google, Meta, and Amazon, guide teams on best practices, and build the partner relationships that unlock data access, co-development, and advantage — including connecting our tools directly to platform APIs. - Make build-vs-buy calls deliberately. Form and maintain a clear point of view on where platform-native and enterprise AI tools are the right choice versus where custom systems we build outperform them. - Govern data, cost, and risk. Keep the work defensible: metered-API cost controls, auditable outputs, per-user authentication, and strict confidential-client-data discipline. - Develop the team and measure impact. Mentor builders and analysts, raise the organization's AI literacy, and establish KPIs for productivity, quality, cost savings, adoption, and client/market impact — reporting to senior leadership. Qualifications: - Hands-on agentic building (strongly preferred, heavily weighted). Demonstrated experience building with agentic coding environments — modern AI coding agents such as Claude Code or Codex, Cursor, or equivalent — with real tools or pipelines you have personally shipped and that real users use. A portfolio beats a résumé line here. - Frontier fluency. You are already on, or visibly ready to jump to, the frontier of agentic AI — not someone who has read about it. You can speak credibly about what changed in the tooling in the last few months and what you adopted because of it. - Multi-agent / LLM systems understanding. Practical grasp of multi-agent orchestration, prompt and context engineering, schema-validated LLM output, and why deterministic computed numbers (not LLM arithmetic) make a deliverable defensible. - Strategic range. 8+ years in digital marketing, marketing operations, product, or business transformation, with a track record of driving adoption of new technology and workflows — and the ability to set vision, not just execute tasks. - Leadership without (and with) authority. 3+ years leading or enabling teams across disciplines; able to influence crafts that don't report to you and to mentor builders who do. - Marketing-workflow depth. Real understanding of how paid search, SEO, paid social, programmatic, ad ops, strategy, and media ops actually work, so you can spot where AI creates leverage. - Product and program instincts. Comfortable owning the development and deployment of internal tools end to end — scoping, shipping, measuring, iterating. - Storytelling and thought leadership. Able to build and tell a compelling AI story — internally, to clients, and in the market — and to represent the agency credibly as an innovator. - Partnership and stakeholder skills. Able to build productive relationships with major platform partners (e.g., Google, Meta) and to influence senior internal stakeholders. - Change management and communication. Able to build genuine enthusiasm for new tools while addressing real resistance, and to translate technical work into business impact for senior stakeholders. - Analytical, outcome-driven mindset. You measure impact and tell the truth about it. - Nice to have. Familiarity with cloud deployment (e.g. GCP Cloud Run), modern LLM APIs, the Model Context Protocol (MCP), and cost governance for metered AI/data APIs. - Education BA/BS in Marketing, Business, Computer Science, Information Systems, or related field. Equivalent demonstrated capability — especially a portfolio of shipped agentic tools — is weighed at least as heavily as the degree. Benefits (Additional Information): "The Power of One starts with our people! To do powerful things, we offer powerful resources. Our best-in-class wellness and benefits offerings include: Paid Family Care for parents and caregivers for 12 weeks or more Monetary assistance and support for Adoption, Surrogacy and Fertility Monetary assistance and support for pet adoption Employee Assistance Programs and Health/Wellness/Comfort reimbursements to help you invest in your future and work/life balance Tuition Assistance Paid time off that includes Flexible Time off Vacation, Annual Sick Days, Volunteer Days, Holiday and Identity days, and more Matching Gifts programs Flexible working arrangements ‘Work Your World’ Program encouraging employees to work from anywhere Publicis Groupe has an office for up to 6 weeks a year (based upon eligibility) Business Resource Groups that support multiple affinities and alliances The benefits offerings listed are available to eligible U.S. Based employees,