Registered in the United Kingdom · Independent professional standards council
Home/Professional standards/Software Engineering
Technology · GSE-06

Judged on shipped work, not syntax recall

The Software Engineering standard certifies people who write code others can safely change years later. Assessment is built around real contributions — design decisions, review history and how you handled the maintenance nobody enjoys.

35,517 holders worldwide 6 levels +2.2% growth this year
What this standard certifies

Six capability areas, assessed on evidence

Each area is evidenced from your own work. Assessors look for what you decided and why, not for a rehearsed answer.

Design
Choosing structures that keep the next change cheap.
Testing
Tests that catch real regressions rather than inflating a number.
Code review
Raising the standard of a codebase through other people.
Maintenance
Refactoring, migrations and the unglamorous work that keeps systems alive.
Documentation
Writing down the reasoning, not just the interface.
Performance
Measuring before optimising, and knowing when to stop.
Levels in this standard

Software Engineering across the recognition ladder

The same six-level framework, expressed in the terms of this discipline. Experienced applicants can enter directly at a higher level through the portfolio route.

Level Post-nominal What it certifies Professional Experience Annual CPD
1BIPS Foundation BIPS-F Writes correct, readable code and understands why review and testing exist. 0–1 yr 10 h
2BIPS Practitioner BIPS-P Delivers features independently within an established codebase, with review. 1–3 yrs 15 h
3BIPS Professional BIPS-Pro Owns a service or major component and is accountable for its quality over time. 3–6 yrs 20 h
4BIPS Specialist BIPS-S Leads a specialism — architecture, performance, developer experience — with evidence. 6–10 yrs 25 h
5BIPS Expert BIPS-E Sets engineering standards and is recognised beyond one employer. 10+ yrs 30 h
6BIPS Fellow FBIPS Contributes to the profession through open work, teaching or standards. By election 30 h
Who it is for

Built for people already doing the work

Software engineers at any stage Self-taught developers seeking recognition Engineers moving between languages Technical leads Career changers with a portfolio Contractors evidencing capability
How you are assessed

Four stages, no written exam

1

Portfolio

You submit real work against the six capability areas.

2

Evidence review

An assessor checks provenance and your role in it.

3

Professional discussion

A recorded conversation about decisions and trade-offs.

4

Award & register

Your credential is issued and listed publicly.

Where it leads

Roles this standard opens up

Software Engineer

Builds and maintains the systems the business runs on.

Technical Lead

Owns the design and raises the bar around them.

Software Architect

Decides the shape of systems and defends the trade-offs.

Principal Engineer

Sets technical direction across an organisation.

Latest on software

What is changing in this field

Related standards

Often held alongside this one

Technology

DevOps & Reliability

The DevOps & Reliability standard recognises people who shorten the distance between an idea and production while making outages rarer and shorter.

GDO-055 levels
View the standard →
Technology

Cloud Engineering

The Cloud Engineering standard recognises people who can build infrastructure that survives contact with real traffic, real budgets and real failure.

GCE-035 levels
View the standard →
Data & AI

Artificial Intelligence

The Artificial Intelligence standard recognises people who can take a model from problem framing to production and stay accountable for what it does once it is there.

GAI-016 levels
View the standard →