Manager, Technical Solutions

We need to output HTML fragment with sections: About the role? Actually the posting includes "About WPP Media", "The Opportunity", "Key Responsibilities", "Qualifications", "Life At WPP Media & Benefits", "Equal Opportunities", "Accommodations and Hybrid Work Policy", "US Pay Range". We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to these headings only when posting has real specific content. We should not invent sections like Schedule if not present. The posting includes Pay (US Pay Range). Benefits are described. Responsibilities are present. Qualifications/Education/Experience/Skills. About the role maybe from "The Opportunity". Could also have "About WPP Media" but that's company overview; maybe we can include as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content. We must not emit a heading followed by filler/placeholder text. So we need to ensure each heading has substantive content. We need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove "Equal Opportunities", "Accommodations and Hybrid Work Policy", "Privacy Notice", etc. Also remove "Life At WPP Media & Benefits" maybe we keep Benefits section. But we need to keep substantive benefits info: competitive medical, vision, dental insurance, significant paid time off, preferential partner discounts, employee mental health awareness days. Also mention employee resource groups, in-office events, etc. That's benefits. Pay: US Pay Range $60,000 - $140,000 USD. Schedule: Not present (no schedule info). So we should not create Schedule section. Requirements: Could be same as Qualifications? The instruction list includes Requirements as possible heading. We could combine Qualifications and Requirements? But we need to avoid thin sections. Perhaps we have sections: About the role (from The Opportunity), Responsibilities (Key Responsibilities), Qualifications (Education, Experience, Technical Skills, Soft Skills), Benefits, Pay. That's five sections. We must not repeat job title as heading. No Job ID. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from those sections. We need to format using

for headings,

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

  for prose. We need to decide what constitutes a list. For responsibilities, we have bullet-like sentences separated by periods. Could convert each responsibility item into

• . Similarly for qualifications: Education, Experience, Technical Skills, Soft Skills could be lists. We must not lose any detail. Let's extract content. First, "About WPP Media" paragraph: It's company overview. Might be considered part of About the role? The instruction says About the role heading for section about the role. Could include both company overview and opportunity. But we need to preserve all substantive information. So we can include that as prose under About the role. Then "The Opportunity": paragraph describing role. Also prose. We could combine them under About the role heading. Responsibilities: Under "Key Responsibilities" there are several subheadings: Software Development & Architecture, AI/ML System Integration & MLOps, Cloud-Native Development, Collaboration & Mentorship, Problem Solving & Innovation. Each has multiple sentences. We'll turn each sentence or clause into list items? Better to keep each bullet as a list item. We'll parse each sentence. Let's extract responsibilities: Software Development & Architecture: - Design, develop, test, deploy, and maintain high-quality, scalable, and resilient software applications and microservices for AI/ML automation initiatives. - Lead technical design discussions, propose architectural solutions, and ensure adherence to best practices in coding, security, and performance. - Write clean, maintainable, and well-documented code primarily in Python, with potential for other languages (e.g., Java, Go) for specific services. - Conduct thorough code reviews, provide constructive feedback, and ensure code quality standards are met. AI/ML System Integration & MLOps: - Operationalize machine learning models developed by Data Scientists, integrating them into production systems via APIs, batch processes, or streaming pipelines. - Implement and manage MLOps pipelines for model training, validation, deployment, monitoring, and retraining (e.g., using tools like MLflow, Kubeflow, Sagemaker, Azure ML, Vertex AI). - Develop robust data pipelines for feature engineering, data ingestion, transformation, and storage to support AI models. - Design and implement systems for real-time inference and prediction serving at scale. Cloud-Native Development: - Develop and deploy applications leveraging cloud platforms (AWS, Azure, GCP), utilizing services such as serverless functions, container orchestration (Kubernetes, ECS/AKS/GKE), managed databases, and message queues. - Implement CI/CD pipelines to automate the build, test, and deployment processes. - Monitor and optimize cloud resource utilization and application performance. Collaboration & Mentorship: - Work closely with Business Analysts to understand requirements and translate them into technical specifications. - Collaborate with Data Scientists to refine model interfaces, optimize performance, and troubleshoot production issues. - Partner with Product Managers to contribute to the technical roadmap and sprint planning. - Mentor junior developers, provide technical guidance, and foster a culture of continuous learning and excellence. Problem Solving & Innovation: - Identify and troubleshoot complex technical issues in development and production environments. - Research and evaluate new technologies, frameworks, and tools to improve our AI automation capabilities. - Proactively identify opportunities for technical improvement and contribute to strategic technical decisions. Qualifications: Education: - Bachelor's or Master's degree in Computer Science, Software Engineering, or a related quantitative field. Experience: - 8+ years of professional software development experience. - Minimum of 3-5 years of hands-on experience designing, developing, and deploying AI/ML-driven applications or components in a production environment. - Mandatory: Proven experience in the advertising, media, or marketing technology (AdTech/MarTech) industry, with a strong understanding of media planning, buying, optimization, and relevant platforms (DSPs, SSPs, Ad Servers, DMPs, CDPs). - Strong track record of delivering scalable and robust software solutions using Agile methodologies. Technical Skills: - Proficient in Python: Expert-level coding skills, including experience with relevant libraries (e.g., FastAPI, Flask, Django, NumPy, Pandas). - AI/ML: Experience deploying MCP, RAG Models, or context engineering. - Cloud Platforms: Extensive experience with at least one major cloud provider (AWS, Azure, or GCP), including services relevant to AI/ML (e.g., Sagemaker, Azure ML, Vertex AI, Lambda/Cloud Functions, EC2/VMs, EKS/AKS/GKE, S3/Blob Storage/Cloud Storage, RDS/Cloud SQL, Kafka/Kinesis/Pub/Sub). - MLOps: Solid understanding and practical experience with MLOps principles and tools for model versioning, monitoring, data lineage, and automated retraining. - CI/CD: Experience setting up and managing CI/CD pipelines (e.g., Jenkins, GitLab CI, GitHub Actions, Azure DevOps). - API Development: Experience designing and implementing RESTful APIs. Soft Skills: - Exceptional problem-solving and analytical skills with a strong attention to detail. - Excellent written and verbal communication skills, capable of explaining complex technical concepts to diverse audiences. - Strong collaboration skills, with the ability to work effectively in cross-functional teams. - Leadership qualities, including the ability to guide, mentor, and influence technical direction. - Proactive, self-motivated, and able to thrive in a fast-paced, evolving environment. Benefits (from Life At WPP Media & Benefits): - Competitive medical, vision, and dental insurance. - Significant paid time off. - Preferential partner discounts. - Employee mental health awareness days. - Variety of employee resource groups. - Frequent in-office events showcasing team wins, sharing thought leadership, and celebrating holidays and milestone events. - Access to global WPP Media & WPP networks to pursue passions, grow networks, learn at cutting edge of marketing and advertising. Pay: - US Pay Range $60,000 - $140,000 USD. - Individual compensation varies based on job-related factors, including location, business needs, level of responsibility, experience, and qualifications. - Competitive benefits package (already covered) and link to benefits page (we can keep mention but not as list? It's prose.) We should not include the link as list; maybe as prose. We must not include boilerplate like Equal Opportunities, Accommodations, Privacy Notice, etc. Now produce HTML. Structure:

  About the role

  ... combine company overview and opportunity paragraphs.

  Responsibilities

  • ... each responsibility item

  Qualifications

  Maybe we split into Education, Experience, Technical Skills, Soft Skills as subheadings? But instruction only allows h3 for section headings; we could use

  for each subsection? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using h3 for subsections, but likely they want only those top-level headings. However we could still use h3 for each major category like Education, Experience, etc. But that might be considered creating many thin sections. Better to keep Qualifications as one section with lists for each subcategory, maybe using

  ? Not allowed? They didn't forbid other tags, but they said use

  for section headings (list). They didn't say you cannot use other headings, but to be safe we can use

  for each major category (Education, Experience, Technical Skills, Soft Skills) as they are subsections of Qualifications. However that might be many sections but each has substantive content. Could be okay. Alternatively we could keep Qualifications as one section and inside use

  • for each bullet, and maybe include headings inside ? But they didn't forbid other tags. Safer to follow instruction: use

    for section headings (the examples). So we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. That's five sections. Inside Qualifications we can have nested headings? Not specified. We could just list all qualifications as a flat list, but that would lose grouping. However we can still preserve all detail; grouping is not required for correctness. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings inside. But to be safe, we can keep Qualifications as one section and inside use

    • for each bullet, maybe with to denote subheadings. That should preserve all info. Similarly for Benefits we can list. Pay: we can have

      with details. Let's craft. About the role paragraph: combine: "WPP is the trusted growth partner for the world’s leading brands. With exceptional talent, trusted data and intelligence, and world-class partnerships – all united by our pioneering agentic marketing platform, WPP Open – we help clients navigate change, capture opportunity, and deliver transformational growth. WPP Media is WPP's AI-driven media operating unit, bringing together media, data, and partnerships to deliver creative personalisation at scale. Connected through WPP Open and powered by Open Intelligence, clients see exactly where, how, and why their media investment is working. For more information, visit wppmedia.com. The Opportunity We are seeking a