Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesThere is no established, validated taxonomy that assigns software developers to ego-development stages. Ego-development theory describes how people make meaning and take perspective; it does not rank programmers by skill, job title, coding style, or years on the job. The stages can offer a lens for reflection, but applying them to developers as fixed professional categories goes beyond the available evidence.
What ego development describes—and what it does not
Ego development is a broad account of how people understand themselves and others, make meaning, and respond to complexity. It is distinct from software-development expertise, which concerns performance on particular tasks, and from seniority, which usually describes a person’s role or work history.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Psychology: A Complete Introduction | $11.04 | Buy on Amazon |
| 2 |
|
Psychology, 10th Edition | $127.72 | Buy on Amazon |
| 3 |
|
Psych 101: Psychology Facts, Basics, Statistics, Tests, and More! (Adams 101 Series) | $10.83 | Buy on Amazon |
| 4 |
|
Psychology | $248.90 | Buy on Amazon |
| 5 |
|
Psychology 2e (2026) | $32.73 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
That distinction matters: a developer might be highly skilled at debugging and still approach other situations in a different way. Neither technical capability nor a job title establishes an ego-development stage.
What are the stages of ego development?
Susanne Cook-Greuter’s Leadership Maturity Framework applies Ego Development Theory to leadership and presents nine levels of increasingly complex perspectives on self and reality. Her 2013 presentation names them as follows:
#1 Best Overall
- Impulsive
- Opportunist/Self-protective
- Conformist
- Self-conscious/Expert
- Conscientious/Achiever
- Individualist
- Autonomous/Strategist
- Construct-aware
- Unitive
Labels vary across theories and versions. A shared or similar name does not prove that two frameworks define or measure the same stage. For the original framework description, see Cook-Greuter & Associates’ Arc of Development and Cook-Greuter’s 2013 presentation, “The Nine Stages of Increasing Embrace in Ego Development Theory.”
Stages are descriptions, not a human-value ranking
Cook-Greuter describes stage accounts as idealizations: no person fits every feature of a stage description. They should not be treated as a rigid staircase or a ranking of people. Later stages are not automatically happier or better adapted; each level has strengths and vulnerabilities.
Rank #2
Can developers meaningfully be described “by stage”?
Only as a tentative reflective lens, not as a profession-wide classification. The sources reviewed do not establish an accepted or validated ego-stage taxonomy for software developers. They also do not support inferring a person’s stage from programming language, code quality, job title, or years of experience.
If a team uses stage concepts for reflection, it is safer to pose questions than to assign labels: How does someone respond to ambiguity, feedback, authority, collaboration, or competing constraints? Those questions may prompt discussion, but a response at work is not a diagnosis and cannot establish an individual’s stage.
Rank #3
- Used Book in Good Condition
Does being a senior developer mean being at a higher stage?
No such inference is supported. Seniority and expertise address different things from ego development. Baltes and Diehl’s 2018 conceptual theory treats software-development expertise as task-specific: a developer can have different levels of expertise across programming, requirements, testing, debugging, and other work. Their account describes gradual improvement through repeated task work, not discrete developmental stages, and notes that experience is not necessarily related to expertise.
That paper does not assess ego development or validate a connection between technical expertise and ego-development stages. A senior title or long work history therefore cannot be used as evidence of a higher ego-development stage. See Baltes and Diehl’s “Towards a Theory of Software Development Expertise”.
Rank #4
How is ego development measured?
Cook-Greuter describes the MAP, formerly also called LDP and SCTi, as a sentence-completion assessment intended to estimate a person’s recurring center of gravity in meaning-making. The provider says responses can span multiple stages and that a result represents the level a person reliably uses in ordinary circumstances. The scoring materials are proprietary, and accurate scoring requires specialized training; it is not an ordinary self-scoring quiz.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11The provider’s framework page describes more than 4,000 sentence-completion tests in the Harvard study underlying Cook-Greuter’s dissertation. That figure is the provider’s account of the study’s history, not evidence about software developers specifically.
Best Value
What reliability studies can—and cannot—show
A 2002 critical review by Manners and Durkin concluded that ego-development theory and the Washington University Sentence Completion Test had substantial empirical support. Later scoring research offers additional, bounded evidence. O’Fallon and colleagues’ 2020 STAGES validation paper compared scoring approaches across 73 inventories; when stages 2.0 and 2.5 were combined, weighted kappa values across four scorers ranged from 0.81 to 0.94. In a separate analysis of 71 inventories above Strategist, the paper reported overall weighted kappa of 0.76 for inter-rater reliability.
These figures describe agreement between scoring methods or raters in those study samples. They do not establish the accuracy of assigning stages to software developers. The authors also caution that reducing meaning-making to one ordinal “center of gravity” is a blunt simplification, that written assessments may favor verbal fluency, and that stage results should not be used to pigeonhole people or groups. Read the 2020 STAGES validation article and Manners and Durkin’s critical review for the studies’ scope.
Quick Recap
How to use the idea responsibly at work
- Keep constructs separate. Discuss technical skills, role seniority, and meaning-making as different topics.
- Use questions, not labels. Explore how people approach uncertainty, feedback, or conflicting priorities without turning observations into stage assignments.
- Do not infer a stage from code. A language choice, code review, or debugging result does not reveal an ego-development level.
- Treat formal assessments cautiously. A specialized written assessment has limits, including possible effects of verbal fluency, and a single score should not define a person.
- Check whether the framework fits the purpose. Stage language should not become a substitute for concrete evidence about a developer’s skills or performance.
Further reading
- Cook-Greuter’s 2013 overview of the nine levels.
- O’Fallon and colleagues’ 2020 STAGES scoring validation article.
- Manners and Durkin’s 2002 critical review of ego-development theory and measurement.
- Baltes and Diehl’s 2018 paper on software-development expertise.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
