standards and priorities. The role is accountable for improving the BU/function's
security outcomes and achieving agreed security objectives and metrics, working
closely with GRC, Security Architecture and other central Security capabilities.
The role combines security expertise, technical leadership, engineering thinking, data-
driven problem solving and strong business understanding. The Security Engineering
Lead is part of the BU technology organisation, identifying security weaknesses,
understanding their root causes and delivering practical solutions that measurably
reduce security risk.
The role is accountable for improving the BU/function's security outcomes and
achieving agreed security objectives and metrics.
Security expertise + Technology engineering + Data + Business accountability
Its success is demonstrated by what changes in the BU — not simply by what the
Security function reports about it.
Why Pearson?
This role represents a significant shift in how security is delivered across Pearson.
Rather than operating as a central advisory function, the Security Engineering Lead is embedded
within the business and accountable for driving measurable improvements in security outcomes
where risk is created and managed.
The role provides the opportunity to work directly with technology leaders, engineers and
business stakeholders to solve real security problems, improve resilience and reduce risk at scale.
Success is measured through better security outcomes, stronger technology practices and a
demonstrably more secure business.
DCL2 – Internal Use OnlyAs Pearson continues to strengthen its security capabilities, this role offers the opportunity to
influence technology decisions, improve security performance across critical services, and help
establish a model in which security is treated as an integral part of good technology engineering
rather than a separate compliance activity.
DCL2 – Internal Use Only
security operations.
Behaviours
DCL2 – Internal Use OnlyThink like an engineer.
They look for root causes, scalable solutions and ways to make security better through
technology and process.
Act like part of the business.
They understand commercial and operational priorities and find ways to improve
security without treating the BU as an external customer.
Own outcomes.
They don't stop at identifying a problem. They stay focused on getting the outcome
changed.
Use evidence.
They rely on accurate data and are prepared to challenge assumptions, including when
the data is uncomfortable.
Be pragmatic.
They understand that perfect security is not the objective; materially reducing risk and
improving resilience is.
Know when to collaborate.
They don't try to be the expert in everything. They bring in GRC, Architecture or other
specialists when appropriate.
Build capability, not dependency.
They leave the technology organisation stronger and more capable of managing
security itself.
for the BU/function.
exposures and areas of greatest risk.
improvement.
measurable risk.
DCL2 – Internal Use Only• Track progress against agreed objectives and intervene where performance is
not improving.
repeatedly addressing individual findings.
Drive remediation of security risk
Work directly with technology teams to improve performance against key security
The role is expected to understand why a metric is poor and determine what needs to
change to improve it.
This may include process changes, technology changes, automation, data
improvements, changes to ownership or escalation to senior leadership.
opportunities for intervention.
temporary remediation.
exercises.
DCL2 – Internal Use Only• Help teams interpret and apply Security policies, standards and control
requirements.
required and bring it into the work at the appropriate point.
The role should be evidence-led rather than activity-led: success is demonstrated
through improved security outcomes, not the volume of meetings, communications or
assessments completed.
changes in risk.
acceptance.
of security risks.
appropriately recorded and evidenced.
The Security Engineering Lead does not replace the DRO's accountability for risk; they
provide the expertise, insight and delivery focus required to improve the risk position.
requirements.
their services.
Security community.
DCL2 – Internal Use Only• Contribute to a culture in which security is treated as part of good technology
engineering rather than a separate compliance activity.
Key Relationships
The role reports to and works closely with the DRO.
The DRO remains accountable for the BU/function's risk. The Security Engineering Lead
is accountable for achieving agreed security outcomes and providing the DRO with the
expertise, insight and delivery focus required to improve those outcomes.
The role operates as part of the BU technology organisation and works directly with
engineering, infrastructure, application, identity and other technology teams to deliver
improved security outcomes.
GRC
GRC provides the independent governance and challenge function; the Security
Engineering Lead is focused on improving the BU's actual security outcomes.
Security Architecture
Works with Security Architecture where specialist expertise, design authority or
complex security decisions are required.
Participates in the Security community, sharing knowledge, patterns, data and
successful solutions while retaining primary accountability for the BU's agreed
outcomes.
related discipline.
teams.
technical outcomes.
of security problems.
than simply identifying problems.
Success will be measured primarily through improved security outcomes, for
The role is not measured primarily by the amount of security activity performed. The
measure is whether the BU becomes measurably more secure.
This role is intentionally designed as an embedded security engineering capability
rather than a traditional advisory BISO role.
The individual is part of the BU, understands its technology environment, works directly
with its engineers and leaders, and is accountable for improving agreed security
outcomes.
Unlike traditional advisory security roles, the Security Engineering Lead is expected to
influence, coordinate and drive remediation activity through the BU technology
organisation until agreed outcomes are achieved.
CapcoUK - London
Pay not posted
Posted Sep 18, 2026
BrillioNew York, New York
$120K–$130K / yr
Posted 21 days ago
CapcoUK - London
Pay not posted
Posted Sep 18, 2026
PearsonUnited States
Pay not posted
Posted Oct 12, 2026
checked 9 days agoCambridge ConsultantsUnited Kingdom
Pay not posted
Posted 25 days ago
DigitalBridgeBoca Raton, Florida +2
$235K–$290K / yr
Posted Oct 2, 2026
Source: the company job board. We last checked this job 1 h ago. We first saw it 1 h ago. A job on a job board does not always mean that the team interviews people now. We found this job board in a public list. We did not yet compare it with the careers page of the company.
No one has reported an interview at Pearson yet. Did you interview there? Add the questions.