Skip to main content
POST ATLAS
From pathwayOffensive Security (Pentest / Red Team)Listed as a long-term cert for that lane. Back to pathway
Cybersecurity

OSWE

OffSec's web-exploitation cert. The deepest hands-on AppSec credential for source-aware testers.

DifficultyAdvanced
Study6–9 months
Exam~£1,400
Valid3 years
Compare
POST verdict
WorkableMarket-level call. Not personal advice.

A real web-app exploitation signal where source-code review and chained-bug work is the scope. Outside that scope, the recognition runs thin.

Confidence: Medium Signal strength: Medium
Why this confidence
Recognised at UK web-focused consultancies and AppSec practices, but the addressable market is narrower than general pentest. Bug bounty output now competes with OSWE as a screening signal in the same hiring panels.
Why this signal strength
Strong within dedicated web-app pentest and AppSec consultancies running source-code-led engagements. Weaker in general pentest hiring, where OSCP plus engagement reps remains the screened combination and OSWE adds breadth rather than gating credibility. The source-code-only trap narrows the credential's signal at AppSec hiring panels valuing breadth across runtime and design review.
Who this pays off for

Best for

  • Web-app pentesters at UK consultancies running source-code-led testing against fintech, SaaS and bespoke enterprise web platforms
  • AppSec engineers wanting an exploitation-shaped credential to complement secure-code review and SAST tooling experience
  • Bug bounty hunters formalising chained-bug and authentication-bypass research into a recognised offensive credential
Who walks away with nothing

Usually a mistake for

  • A general pentest credential. OSWE is web-app and source-code focused; broad pentest hiring screens for OSCP plus reps instead
  • An AppSec engineering credential. The exam is exploitation-led, not secure-development-lifecycle or threat-modelling focused, and CSSLP or domain reps cover that ground
  • A bug bounty substitute. Mature programmes recognise documented critical-severity output more directly than the cert line item
The named failure mode

Common mistake

The OSWE-without-bug-bounty-context trap. Candidates pass the exam without a public research footprint or HackerOne or Bugcrowd track record, and UK web-pentest consultancies screen those signals together rather than weighting the cert alone.

Recruiter signal, not marketing

What it actually does

Credibility in dedicated web-app pentest hiring at named UK consultancies and in AppSec engineering roles where exploitation depth is valued. Sits naturally alongside Burp Suite Certified Practitioner and bug-bounty output. Does not substitute for OSCP in general pentest hiring, and does not displace CSSLP-style credentials in secure-development-lifecycle roles.

Falsifiability

What would change this call

  • OffSec updates the OSWE syllabus to cover modern API, GraphQL and identity-provider exploitation in a way that broadens its relevance beyond classical web stacks
  • PortSwigger's Burp Suite Certified Practitioner programme becomes the dominant screened credential for UK web-app pentest hiring, narrowing OSWE's market
  • Major UK web-pentest consultancies publicly shift their hiring criteria to weight documented bug-bounty output above structured exploitation certs

This tells you whether the cert is worth pursuing. It does not tell you whether it is worth pursuing for you.

See if it's right for you

In context

This cert in isolation tells you very little. Here is where it actually sits. The pathways that use it, and the roles it realistically supports.

Pathways that include it
Roles it realistically supports
  • Senior AppSec / code-review interviews
  • Bug-bounty credibility
Go deeper
Practitioner take

OSWE is OffSec's white-box web exploitation cert and it sits in a very specific lane: source code review, authentication bypass, and chained vulnerabilities in real applications. The WEB-300 course teaches you to read a codebase and turn a logic flaw into RCE, which is genuinely different work from running Burp against a black-box target. Take it when you're already in an application security or web pentest seat and the work involves source access. Skip it as a generalist web cert. BSCP plus a public lab portfolio carries further on a black-box pentest CV, and OSWE only pays back when the role specifically demands source-led review. The exam is brutal and the price is high; both only make sense with the seat already in front of you.

Authored opinion. Updated against current hiring conditions, not vendor marketing.

Recommended prior knowledge

  • Strong web app testing experience

Common misconceptions

  • OSWE alone clears HR filters; it doesn't replace shipped, documented work.

What this cert does NOT guarantee

  • Pentest or red-team roles by itself

The next step

A cert is a signal. A Career Verdict tells you whether the signal is worth sending.

A Career Verdict tells you whether this cert earns its place on your specific route, what it won't fix, and what to sit before or after it.

A route shows what people usually do. A Career Verdict judges whether it's realistic for you.

A Career Verdict includes

The call
A single written judgement on whether the route is realistic for you.
Plateaus and failure modes
The flat years and the specific ways this route tends to stall.
Where you stand
The strongest and weakest parts of your current position, named.
Salary reality
What this route actually pays, set against what you've been told it pays.
Certification rulings
Each cert on your list: useful, optional, or skip, with reasons.
Likely timeline
How long this route takes from where you actually are, not from zero.
Get a judgement on your situation£39, one-off. Built for your inputs, yours to keep.

Built on POST's practitioner-authored assessment framework, calibrated by James from twenty years across helpdesk, infrastructure and security. Framework is human-authored; the verdict applies it to your inputs.

Plan a route with this cert