JobFrame / Software Engineering
technology
Software Engineering
Software Engineering is a job family — a stable cluster of work with shared purpose, outputs, responsibilities, and labor-market identity. On the frame it spans 12 canonical roles across the P track, 7 levels in all.
Titles that map here
Employers call this work many things — these all resolve to Software Engineering.
The job family matrix
Every level of the family, side by side — what genuinely changes as the work scales, and what it pays. Open any level for its full profile.
Core / General
P1 Software Engineering Entry-Level 0–2 yrs · $66k open profile › | P2 Developing Professional 1–3 yrs · $77k open profile › | P3 Software Engineering Mid-Level 3–5 yrs · $88k open profile › | P4 Software Engineering — Senior Professional 5–8 yrs · $117k open profile › | P5 Software Engineering Senior Individual Contributor 8–12 yrs · $148k open profile › | P6 Software Engineering — Principal Professional 12–18 yrs · $201k open profile › | P7 Distinguished Software Engineer 15–22 yrs · $247k open profile › | |
|---|---|---|---|---|---|---|---|
| Median pay | $66k | $77k | $88k | $117k | $148k | $201k | $247k |
| Scope | Own tasks within a defined component | Defined deliverables / small features | Features or a sub-system end-to-end | A system or set of related features | Multiple systems or a technical domain | Organization-wide architecture and the hardest problems | Cross-organization / enterprise technical strategy |
| Autonomy | Close supervision; work reviewed frequently | General supervision; reviewed at milestones | Works independently on standard work; reviewed on the non-standard | Self-directed; reviewed at critical decision points | Sets direction within the domain | Defines direction; minimal oversight | Operates autonomously at the enterprise level |
| Complexity | Routine problems with known solutions | Some non-routine problems; applies established patterns | Diverse problems; adapts existing approaches | Complex, ambiguous problems; devises new approaches | Novel, high-ambiguity problems; establishes the approach | Strategic, open-ended problems shaping the technical future | Industry-level, highly ambiguous problems |
| Impact | Own deliverables | Own and immediate-team deliverables | Project / team outcomes | Multi-team / function outcomes | Org / multi-team outcomes | Organization-wide | Enterprise-wide |
| Decision rights | Few independent decisions; escalates the rest | Routine technical choices within guidance | Owns implementation decisions for own scope | Owns technical decisions for a system; influences adjacent design | Authority over a technical domain | Sets technical strategy for a major area | Final technical authority across multiple domains |
| Leadership | None — building the craft | May guide interns | Mentors juniors informally | Technical lead for focused efforts; mentors several | Leads cross-team technical initiatives | Recognized authority; multiplies many teams | Sets technical direction org-wide; develops principals |
GxP / Regulated Software & Systems Engineering
P2 Developing Professional 1–3 yrs · $77k open profile › | P3 Software Engineering Mid-Level 3–5 yrs · $88k open profile › | P4 Software Engineering — Senior Professional 5–8 yrs · $117k open profile › | P5 Software Engineering Senior Individual Contributor 8–12 yrs · $148k open profile › | P6 Software Engineering — Principal Professional 12–18 yrs · $201k open profile › | |
|---|---|---|---|---|---|
| Median pay | $77k | $88k | $117k | $148k | $201k |
| Scope | Defined deliverables / small features | Features or a sub-system end-to-end | A system or set of related features | Multiple systems or a technical domain | Organization-wide architecture and the hardest problems |
| Autonomy | General supervision; reviewed at milestones | Works independently on standard work; reviewed on the non-standard | Self-directed; reviewed at critical decision points | Sets direction within the domain | Defines direction; minimal oversight |
| Complexity | Some non-routine problems; applies established patterns | Diverse problems; adapts existing approaches | Complex, ambiguous problems; devises new approaches | Novel, high-ambiguity problems; establishes the approach | Strategic, open-ended problems shaping the technical future |
| Impact | Own and immediate-team deliverables | Project / team outcomes | Multi-team / function outcomes | Org / multi-team outcomes | Organization-wide |
| Decision rights | Routine technical choices within guidance | Owns implementation decisions for own scope | Owns technical decisions for a system; influences adjacent design | Authority over a technical domain | Sets technical strategy for a major area |
| Leadership | May guide interns | Mentors juniors informally | Technical lead for focused efforts; mentors several | Leads cross-team technical initiatives | Recognized authority; multiplies many teams |
Adjacent families
The work that sits closest to Software Engineering on the frame — by coordinate distance, not by hand.