You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
WPP

Technical Security Governance Lead - Application Security

  • Hybrid
  • 6+ years

Salary

Not stated

Similar roles pay £50K - 115K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company combines media intelligence, data, creative, production, enterprise solutions and strategic consulting, serving global brands across more than 100 markets.

The role sits in Technical Security Governance (TSG) and reports to the Director, Security Governance & Posture in the Group CISO organisation.

The goal is to make Secure Development stronger across the company through guardrails and assurance. The role does not own development pipelines, security tooling or software delivery.

Responsibilities

  • Serve as the company's senior technical authority on Application Security, giving judgement on Secure Development, assurance and software-security risk.
  • Learn how software is designed, built, tested and released across the company, and spot where common guardrails and engineering capabilities would help most.
  • Set practical Secure Development guardrails covering secure design, threat modelling, coding, dependencies, supply chains, CI/CD, cloud-native and AI-enabled development.
  • Work with engineers, architects and product managers to build the security capabilities and practices needed to meet those guardrails.
  • Build technical assurance that shows, on an ongoing basis, whether Secure Development controls exist, run and work.
  • Use engineering evidence, security tooling and targeted testing to find gaps, test assumptions and drive real improvement.
  • Help teams see recurring weaknesses and get better at finding, ranking and fixing software-security risk themselves.
  • Provide evidence and technical challenge where controls fail or risk remains, while the teams that build the software keep ownership of implementing and fixing it.
  • Keep the Secure Development approach current as engineering practice, technology and threats change.
  • Own Application Security Risk Factors across their lifecycle: log and document issues, advise on fixes, track progress and push where exposure is not being addressed.

Requirements

  • Solid working knowledge of modern software development and where security belongs in design, development, testing, CI/CD and release.
  • Real Application Security, Product Security, DevSecOps or Secure Development experience, with enough depth to work credibly alongside engineers and architects.
  • Skill at turning security expectations into engineering guardrails that teams can understand and apply.
  • Strong communication and stakeholder skills for working with engineers, architects, product managers and senior leaders.
  • Good technical judgement: weighing security against engineering constraints, knowing when to push back, and recognising when different approaches reach the same result.
  • Ability to lead through technical credibility, evidence and influence, without formal authority.
  • Hands-on software development, software engineering, DevOps or closely related engineering experience; 5+ years is particularly valuable.
  • Experience establishing or improving Application Security, Secure Development or DevSecOps practices with engineering teams.
  • Familiarity with threat modelling, SAST, SCA, DAST, secrets detection, CI/CD security, API security or software supply chain controls.
  • Experience using technology, automation or engineering evidence to provide security assurance at scale.
  • Experience influencing technical decisions where security and delivery priorities compete.
  • Experience with Security Champions, paved roads, developer enablement or similar programmes.
  • Experience with cloud-native, SaaS or highly distributed applications.
  • Experience with security for AI-enabled applications or AI-assisted development.
  • Familiarity with OWASP SAMM, ASVS, NIST SSDF, SLSA or similar frameworks.

Conditions

Hybrid role, with teams in the office around 4 days a week.

Accommodations or flexibility can be discussed with the hiring team during the interview process.

The company is an equal opportunity employer and considers all applicants without discrimination based on particular characteristics.

Benefits

  • Work alongside driven, inspired people who aim to do exceptional work.
  • Operate at a scale that is unmatched in the industry, with the chance to create, influence and complete projects.
  • Challenging, stimulating work alongside a group of creative problem solvers.

Where you’d work

Hybrid, 4 or more days a week in the office

You can work from

  • United Kingdom

About the company

WPP

Office in London, United Kingdom

Also hiring in Copenhagen, Denmark and United Kingdom

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 20 checks run
  • 1 red flag

Still hiring?

13 checks

1 red flag

How crowded?

7 checks

No red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details12 facts · Role, Location, Compensation
Tech stack
  • CI/CD
Seniority
Lead
Specialty
Security
Region
United Kingdom
Pay period
Annual
Show 7 more factsShow less

Role

Category
DevOps & Infrastructure
Specialty
Security
Seniority
Lead
Experience
5+ years
Tech stack
  • CI/CD

Location

Work model
Hybrid
Region
United Kingdom
Office
  • London, United Kingdom
Remote from
  • United Kingdom
Days in the office
4 or more days

Compensation

Salary
Salary by agreement
Pay period
Annual

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason