Level path

Security Practitioner

SecEng

Own features and services with solid implementation judgment across neighboring layers.

Total concepts 253

Curated for this specific career level.

Specific to this level 30

Concepts explicitly listed in this level.

Knowledge tracks 6

Concepts span multiple tracks and layers.

Job description signals Typical responsibilities

Identify, prevent, test, and respond to security risks across applications, infrastructure, identity, and data.
Run threat modeling, secure-code reviews, vulnerability assessment, incident response, and security automation.
Partner with engineering teams to make secure practices practical, repeatable, and measurable.
Own features end to end from design through implementation, testing, release, and support.
Make local technical tradeoffs and explain them clearly to teammates.
Improve reliability, maintainability, and observability of the systems you touch.
Collaborate with product, design, QA, operations, and adjacent engineering teams.

Cumulative view includes

Dev / Junior DevSE / Junior SESecEng / Junior SecEngDev / DevSE / Mid SE

Specific to this level 30 Cumulative 253

Track / layer mastery Concept coverage by layer

{}

Software

28 concepts

Security 28

Product

2 concepts

Web Applications 2

{}

Software

183 concepts

Security 55 Software Design 35 Programming 23 Programming Languages 13 System Design 13 Algorithms & Data Structures 12 Databases 10 Computer Networks 9 Software Architecture 5 Quality Assurance 5 Distributed Systems 2 Operating Systems 1

OPS

Operations

27 concepts

Deployment 11 Build & Packaging 7 Observability 5 Continuous Integration 2 Local Development 1 Runtime Infrastructure 1

MGT

Management

19 concepts

Business Foundations 10 Requirements & Planning 6 Delivery Methodologies 2 Team Leadership 1

Product

19 concepts

Developer Tools 11 API Products 4 Web Applications 4

Theory

3 concepts

Algorithmic Analysis 3

DATA

Data

2 concepts

Data Foundations 2

Learning scope Concepts by learning area

Specific to this level

Concepts introduced by this level

Level concepts

Secure Design

Apply security practices during design, implementation, and review.

Level concepts

Security Testing

Find, validate, and prioritize security weaknesses.

Security Testing Software · Security new Vulnerability Assessment Software · Security new Penetration Testing Software · Security new Man-in-the-Middle Attack Software · Security new Hacker Software · Security new Malware Software · Security new Trojan Software · Security new Virus Software · Security new

Cumulative level expectation

All concepts expected at this level

Inherited path

Coding Foundations

Developers begin by learning to translate requirements into working, readable code.

Inherited path

Developer Tooling

Daily development depends on version control, language tooling, static checks, and repeatable local workflows.

Git Product · Developer Tools awareness Compiler Software · Programming Languages awareness Interpreter Software · Programming Languages Package Manager Operations · Build & Packaging Linting Operations · Build & Packaging Code Editor Product · Developer Tools CLI Software · Operating Systems Version Control Product · Developer Tools Dependency Operations · Build & Packaging Artifact Operations · Build & Packaging Development Environment Operations · Local Development Software Ecosystem Software · Programming Repository Product · Developer Tools awareness Commit Product · Developer Tools awareness Branch Product · Developer Tools awareness Pull Request Product · Developer Tools awareness

Inherited path

Testing & Debugging

A developer owns not only writing code, but proving that it behaves as intended.

Unit Test Software · quality-assurance awareness Debugger Product · Developer Tools awareness Error Handling Software · Programming Code Documentation Software · Software Design Software Testing Software · quality-assurance awareness Test Case Software · quality-assurance awareness

Inherited path

Software Systems Basics

Even implementation-focused developers need a working vocabulary for clients, servers, interfaces, web requests, and the lifecycle surrounding a change.