Lead Support Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content. We have content for About the role (maybe "About WPP Media" is company description, but we can treat as "About the role"? Actually "About the role" is a heading they suggest. The posting includes "Role Summary And Impact" which is about role. Also "Key Responsibilities". Also "Skills And Experience". Also "Life At WPP Media & Benefits". Also "US Pay Range". Also maybe schedule: hybrid approach (four days a week). So we can have sections: About the role (maybe combine company description and role summary?), Responsibilities, Skills (or Qualifications?), Benefits, Pay, Schedule.
We must not include boilerplate like EEO, privacy notice, application instructions, etc. Remove duplicated lines.
We need to preserve all substantive information. So we need to include details from each section.
Let's extract:
About WPP Media: description of WPP, WPP Media, AI-driven media operating unit, etc.
Role Summary And Impact: description of role: owning production stability, observability, system health for mission-critical global campaign governance and compliance platform. Lead Support Engineer, advanced L2+ L3 support for system on GCP, investigate complex production issues, implement minor code-level fixes in Python, lead RCA, improve reliability, work with EMEA Engineering Tech Lead, Product Owner, QA, connect production insights with technical roadmap priorities, combines hands-on SRE with technical squad leadership. Foundational monitoring and alerting in place, evaluate approach, define observability direction, strengthen system health monitoring, automate runbooks, reduce manual effort, help shape future support squad.
Key Responsibilities: list bullet points (they are sentences). We'll convert to - .
Skills And Experience: list of requirements.
Life At WPP Media & Benefits: description of culture, benefits: competitive medical, group retirement plans, vision, dental insurance, significant paid time off, preferential partner discounts, employee mental health awareness days. Also hybrid approach: teams in office around four days a week. Also note about accommodations.
Pay: US Pay Range $75,000 - $180,000 USD.
Schedule: hybrid approach, four days a week in office.
We must not include headings with filler like "commensurate with experience". Not needed.
We must not include Job ID etc.
We must not include duplicated lines.
We must not include cookie/navigation/legal/EEO etc. So remove equal opportunity statements, privacy notice links, accommodation request lines, etc.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... combine WPP Media description and role summary? Might be two paragraphs: one about WPP Media, one about role summary. Could be separate
elements.
Responsibilities
- ... each bullet
Skills and Experience
- ... each bullet
Benefits
... benefits description
Pay
US Pay Range $75,000 - $180,000 USD
Schedule
Hybrid work model with teams in the office around four days a week.
We need to ensure we don't include filler like "competitive benefits package, go to https://mybenefits.wpp.com/public/welcome for more details." We can keep description of benefits but remove the link and "go to". The sentence: "We offer a competitive benefits package, go to https://mybenefits.wpp.com/public/welcome for more details." We'll drop the link part and just say "We offer a competitive benefits package." But we already have benefits list. Might combine.
Let's extract benefits paragraph: "Our comprehensive benefits package reflects this commitment, including competitive medical, group retirement plans, vision, and dental insurance, significant paid time off, preferential partner discounts, and employee mental health awareness days." Also later: "We offer a competitive benefits package, go to https://mybenefits.wpp.com/public/welcome for more details." We'll keep the first sentence.
Now compile.
Responsibilities bullets: need to extract each sentence from "Key Responsibilities". They are:
- Own production stability, system health, and observability for a mission-critical campaign governance and compliance platform running on GCP.
- Diagnose and resolve complex, intermittent, and high-priority incidents across application, database, infrastructure, and networking layers.
- Read, debug, and implement minor fixes and patches directly within the existing Python production codebase.
- Define and advance the observability strategy using GCP Cloud Logging, Cloud Monitoring, Error Reporting, Prometheus, PromQL, and suitable service level indicators and objectives.
- Lead incident response, post-incident reviews, and end-to-end root cause analysis, partnering with the EMEA Engineering team on permanent remediation.
- Monitor execution flows, performance, data refreshes, automated checks, and recurring compliance reporting to ensure reliable system operation.
- Identify opportunities to automate manual support activity, develop and maintain runbooks, and reduce operational toil.
- Provide technical leadership to the L2+ support squad through coaching, knowledge sharing, prioritization, and effective handovers.
- Partner with Product, Engineering, and Quality Assurance teams to assess operational risk, improve release and change management, and influence technical roadmap decisions.
Skills and Experience bullets: extract each bullet from that paragraph (they are sentences separated by periods). Let's list:
- Advanced education in computer science, software engineering, information technology, or a related technical discipline, or equivalent practical experience.
- Strong, current Python proficiency, including the ability to read, debug, and implement fixes directly within a shared production codebase.
- Deep, hands-on experience supporting enterprise systems on Google Cloud Platform, including Compute Engine, Google Kubernetes Engine, Cloud SQL, BigQuery, Pub/Sub, Firestore, Cloud Functions, Identity and Access Management, and virtual private cloud networking.
- Complex production troubleshooting and root cause analysis experience across distributed systems, including leadership of post-incident reviews.
- Strong experience with Docker and Kubernetes, particularly deploying, managing, and troubleshooting applications running in Google Kubernetes Engine.
- High proficiency with GCP Cloud Logging, Cloud Monitoring, Error Reporting, Prometheus, and PromQL, including establishing service level indicators and service level objectives.
- Experience using Terraform for infrastructure as code, tracing infrastructure-level issues, and identifying improvements to infrastructure management.
- Strong Python and Bash scripting skills for automating support tasks, parsing logs, developing operational tools, and reducing manual effort.
- Solid querying and troubleshooting experience across Firestore, BigQuery, PostgreSQL, and MySQL.
- Experience leading, mentoring, or serving as a technical lead for a squad or technical team, along with strong knowledge of Incident, Problem, and Change Management practices and the software development lifecycle.
We may also include "Life At WPP Media & Benefits" description about culture: "Our passion for shaping the next era of media is powered by our commitment to Be Extraordinary, investing in our employees to inspire transformational creativity. We also Lead Optimistically, firmly believing in and Championing Growth and Development for every individual. This commitment allows WPP Media employees to leverage the extensive global WPP Media & WPP networks to pursue their passions, build vital professional connections, and learn at the cutting edge of marketing and advertising. We Create an Open environment built on trust and respect, where everyone feels they belong and has opportunities to progress. This inclusive culture is fostered through a variety of employee resource groups and frequent in-office events showcasing team wins, sharing thought leadership, and celebrating holidays and milestone events."
We can include that as part of Benefits section or separate "About the company" but we already have About the role. Could add a Culture
but not in list of suggested headings. 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 says "use for section headings (e.g. ...)". Likely they expect only those headings. So we should incorporate culture description into Benefits or About the role. Probably Benefits section can include culture and benefits.
Thus Benefits
will include both culture description and benefits list.
Let's craft Benefits paragraph: combine culture sentences and benefits list.
Now Pay: just the range.
Schedule: hybrid approach.
Now produce HTML.
Check for any boilerplate: remove equal opportunity statements, privacy notice, accommodation request, etc. Also remove "Please note that while our philosophy is the same across WPP, benefits may vary by office/country." That's boilerplate? Might be considered minor metadata but could be kept? It's about benefits variation; maybe keep? It's not essential but could be considered minor metadata. Safer to drop.
Also remove "WPP Media is an equal opportunity employer..." etc.
Remove "If you require accommodations or flexibility, please discuss this with the hiring team during the interview process." That's application instruction.
Remove "Please read our Privacy Notice..." etc.
Remove "While we appreciate all applications received, only those candidates selected for an interview will be contacted."
Remove "The base salary range for this position at the time of this posting is indicated below. Individual compensation varies based on job-related factors, including location, business needs, level of responsibility, experience, and qualifications." That's somewhat redundant with Pay range; we can keep just the range.
Now produce final HTML.
Let's write:
About the role
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.
This role is within WPP Media, where you will be instrumental in owning production stability, observability, and system health for a mission-critical global campaign governance and compliance platform. As Lead Support Engineer, you will provide advanced L2+ and L3-oriented support for a system running natively on Google Cloud Platform (GCP). You will investigate complex production issues, implement minor code-level fixes in Python, lead root cause analysis, and improve the reliability of distributed systems. Working closely with the EMEA-based Engineering Tech Lead, Product Owner, and Quality Assurance partners, you will connect production insights with technical roadmap priorities. The opportunity combines hands-on Site Reliability Engineering (SRE) with technical squad leadership. A foundational monitoring and alerting setup is already in place, giving you the platform to evaluate the current approach, define a clear observability direction, and strengthen system health monitoring across the environment. You will automate runbooks, reduce manual operational effort, and help shape the future support squad for a dedicated product used across global advertising campaigns.
Responsibilities
- Own production stability, system health, and observability for a mission-critical campaign governance and compliance platform running on GCP.
- Diagnose and resolve complex, intermittent, and high-priority incidents across application, database, infrastructure, and networking layers.
- Read, debug, and implement minor fixes and patches directly within the existing Python production codebase.
- Define and advance the observability strategy using GCP Cloud Logging, Cloud Monitoring, Error Reporting, Prometheus, PromQL, and suitable service level indicators and objectives.
- Lead incident response, post
About the role
... combine WPP Media description and role summary? Might be two paragraphs: one about WPP Media, one about role summary. Could be separate
elements.
Responsibilities
- ... each bullet
Skills and Experience
- ... each bullet
Benefits
... benefits description
Pay
US Pay Range $75,000 - $180,000 USD
Schedule
Hybrid work model with teams in the office around four days a week.
We need to ensure we don't include filler like "competitive benefits package, go to https://mybenefits.wpp.com/public/welcome for more details." We can keep description of benefits but remove the link and "go to". The sentence: "We offer a competitive benefits package, go to https://mybenefits.wpp.com/public/welcome for more details." We'll drop the link part and just say "We offer a competitive benefits package." But we already have benefits list. Might combine. Let's extract benefits paragraph: "Our comprehensive benefits package reflects this commitment, including competitive medical, group retirement plans, vision, and dental insurance, significant paid time off, preferential partner discounts, and employee mental health awareness days." Also later: "We offer a competitive benefits package, go to https://mybenefits.wpp.com/public/welcome for more details." We'll keep the first sentence. Now compile. Responsibilities bullets: need to extract each sentence from "Key Responsibilities". They are: - Own production stability, system health, and observability for a mission-critical campaign governance and compliance platform running on GCP. - Diagnose and resolve complex, intermittent, and high-priority incidents across application, database, infrastructure, and networking layers. - Read, debug, and implement minor fixes and patches directly within the existing Python production codebase. - Define and advance the observability strategy using GCP Cloud Logging, Cloud Monitoring, Error Reporting, Prometheus, PromQL, and suitable service level indicators and objectives. - Lead incident response, post-incident reviews, and end-to-end root cause analysis, partnering with the EMEA Engineering team on permanent remediation. - Monitor execution flows, performance, data refreshes, automated checks, and recurring compliance reporting to ensure reliable system operation. - Identify opportunities to automate manual support activity, develop and maintain runbooks, and reduce operational toil. - Provide technical leadership to the L2+ support squad through coaching, knowledge sharing, prioritization, and effective handovers. - Partner with Product, Engineering, and Quality Assurance teams to assess operational risk, improve release and change management, and influence technical roadmap decisions. Skills and Experience bullets: extract each bullet from that paragraph (they are sentences separated by periods). Let's list: - Advanced education in computer science, software engineering, information technology, or a related technical discipline, or equivalent practical experience. - Strong, current Python proficiency, including the ability to read, debug, and implement fixes directly within a shared production codebase. - Deep, hands-on experience supporting enterprise systems on Google Cloud Platform, including Compute Engine, Google Kubernetes Engine, Cloud SQL, BigQuery, Pub/Sub, Firestore, Cloud Functions, Identity and Access Management, and virtual private cloud networking. - Complex production troubleshooting and root cause analysis experience across distributed systems, including leadership of post-incident reviews. - Strong experience with Docker and Kubernetes, particularly deploying, managing, and troubleshooting applications running in Google Kubernetes Engine. - High proficiency with GCP Cloud Logging, Cloud Monitoring, Error Reporting, Prometheus, and PromQL, including establishing service level indicators and service level objectives. - Experience using Terraform for infrastructure as code, tracing infrastructure-level issues, and identifying improvements to infrastructure management. - Strong Python and Bash scripting skills for automating support tasks, parsing logs, developing operational tools, and reducing manual effort. - Solid querying and troubleshooting experience across Firestore, BigQuery, PostgreSQL, and MySQL. - Experience leading, mentoring, or serving as a technical lead for a squad or technical team, along with strong knowledge of Incident, Problem, and Change Management practices and the software development lifecycle. We may also include "Life At WPP Media & Benefits" description about culture: "Our passion for shaping the next era of media is powered by our commitment to Be Extraordinary, investing in our employees to inspire transformational creativity. We also Lead Optimistically, firmly believing in and Championing Growth and Development for every individual. This commitment allows WPP Media employees to leverage the extensive global WPP Media & WPP networks to pursue their passions, build vital professional connections, and learn at the cutting edge of marketing and advertising. We Create an Open environment built on trust and respect, where everyone feels they belong and has opportunities to progress. This inclusive culture is fostered through a variety of employee resource groups and frequent in-office events showcasing team wins, sharing thought leadership, and celebrating holidays and milestone events." We can include that as part of Benefits section or separate "About the company" but we already have About the role. Could add aCulture
but not in list of suggested headings. 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 says "use for section headings (e.g. ...)". Likely they expect only those headings. So we should incorporate culture description into Benefits or About the role. Probably Benefits section can include culture and benefits.
Thus Benefits
will include both culture description and benefits list. Let's craft Benefits paragraph: combine culture sentences and benefits list. Now Pay: just the range. Schedule: hybrid approach. Now produce HTML. Check for any boilerplate: remove equal opportunity statements, privacy notice, accommodation request, etc. Also remove "Please note that while our philosophy is the same across WPP, benefits may vary by office/country." That's boilerplate? Might be considered minor metadata but could be kept? It's about benefits variation; maybe keep? It's not essential but could be considered minor metadata. Safer to drop. Also remove "WPP Media is an equal opportunity employer..." etc. Remove "If you require accommodations or flexibility, please discuss this with the hiring team during the interview process." That's application instruction. Remove "Please read our Privacy Notice..." etc. Remove "While we appreciate all applications received, only those candidates selected for an interview will be contacted." Remove "The base salary range for this position at the time of this posting is indicated below. Individual compensation varies based on job-related factors, including location, business needs, level of responsibility, experience, and qualifications." That's somewhat redundant with Pay range; we can keep just the range. Now produce final HTML. Let's write:
About the role
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.
This role is within WPP Media, where you will be instrumental in owning production stability, observability, and system health for a mission-critical global campaign governance and compliance platform. As Lead Support Engineer, you will provide advanced L2+ and L3-oriented support for a system running natively on Google Cloud Platform (GCP). You will investigate complex production issues, implement minor code-level fixes in Python, lead root cause analysis, and improve the reliability of distributed systems. Working closely with the EMEA-based Engineering Tech Lead, Product Owner, and Quality Assurance partners, you will connect production insights with technical roadmap priorities. The opportunity combines hands-on Site Reliability Engineering (SRE) with technical squad leadership. A foundational monitoring and alerting setup is already in place, giving you the platform to evaluate the current approach, define a clear observability direction, and strengthen system health monitoring across the environment. You will automate runbooks, reduce manual operational effort, and help shape the future support squad for a dedicated product used across global advertising campaigns.
Responsibilities
- Own production stability, system health, and observability for a mission-critical campaign governance and compliance platform running on GCP.
- Diagnose and resolve complex, intermittent, and high-priority incidents across application, database, infrastructure, and networking layers.
- Read, debug, and implement minor fixes and patches directly within the existing Python production codebase.
- Define and advance the observability strategy using GCP Cloud Logging, Cloud Monitoring, Error Reporting, Prometheus, PromQL, and suitable service level indicators and objectives.
- Lead incident response, post