Skip to content

Case Study Technology/Software Industry

HackerOne Transforms Secure Coding Training Into a Developer‑Led Culture

Security Journey Case Study HackerOne Header

How a compliance‑driven program became a visible, energizing part of engineering life — powered by Security Journey.

Security Journey Case Study HackerOne Header

The Company

HackerOne is built on security — which meant its internal expectations for secure coding education were higher than simple compliance. Although the company had a training program in place, engagement lagged. Developers completed modules, but learning felt disconnected from real engineering work.

By partnering with Security Journey, HackerOne reframed training from a requirement into a visible, energizing part of engineering culture. The result: stronger participation, renewed curiosity, and a program that now scales across ~100 engineers and anchors onboarding, team identity, and continuous learning.

 

Region

North America

Number of Users

100

Company Size

Mid-Size

Industry

Cybersecurity / Software Technology

Compliance Requirements

SOC 2, ISO 27001, PCI

Case Study at a Glance

  1. The Challenge Training was compliant, but not engaging or meaningfully connected to everyday work.
  2. The Solution Reframed security education with clear structure, visibility, and developer-driven energy.
  3. The Impact Stronger engagement, more consistent participation, and a culture that celebrates security learning.

The Challenge

SJ Case Study HackerOne
  • Training technically met compliance requirements — but it wasn’t driving real learning.

  • Developers completed modules, but engagement was inconsistent.

  • Notifications triggered activity, but also frustration.

  • Training felt disconnected from day‑to‑day engineering

  • Engineers became better at “managing the system” than learning from it

HackerOne needed a program that strengthened skills, not just satisfied checkboxes.

The Solution

We're Here Every Step of the Way

Reframing Security Education

Instead of increasing pressure, HackerOne shifted the philosophy:

  • Focus on engagement, not enforcement

  • Make learning visible, social, and meaningful

  • Measure returning learners, not just completions

  • Build a developer‑centered experience

Structured Foundations

Security Journey provided a clear baseline of foundational paths across:

  • Web security

  • API security

  • AI/LLM security topics 

This created a shared starting point for ~100 engineers.

The Breakthrough: Visibility

Using Security Journey’s API, HackerOne built a Slack workflow that announced training completions.

The impact was immediate:

  • Progress became public

  • Engineers congratulated each other

  • Participation became social — even competitive

  • Training became part of team identity

The Results

A Culture Shift, Not Just a Training Program

HackerOne saw clear, observable changes:

  • Participation became steady instead of deadline‑driven

  • Previously disengaged engineers returned to the platform

  • Managers supported learning time more easily

  • Security conversations increased across channels

  • Training became part of onboarding and engineering culture