Which Tech Role Fits a Senior Developer in the AI Wave?
You're good at your job, decently paid — and increasingly sure that watching this wave from an employee seat is the expensive choice. The obvious answer is “stay a developer, add AI.” Sometimes that's right. But it's the answer almost every developer gives, and for a third of them it's wrong.
The itch, named precisely
The pattern shows up in our assessment data and in half the senior-dev conversations on the internet: the job is fine, the pay is fine, and something is off anyway. Usually it's one of two things. Either the ladder quietly swapped building for coordinating — the promotion that traded your best hours for meetings — or the wave itself is the itch: a once-a-decade repositioning window is open, and your calendar looks exactly like it did in 2021.
Both versions get misdiagnosed as “I should learn more AI.” But skills aren't the bottleneck for a senior developer — positionis. The question isn't what to learn next. It's which role in the ecosystem converts ten years of engineering depth into the most leverage.
The default trap: “I'm a dev, so — Developer”
Identity is the worst career adviser in a hype cycle. The coder defaults to the Developer role reflexively, the way a lawyer defaults to Lawyer — and for many developers that default is genuinely correct: peak demand, straightforward conversion, the deepest use of existing skills. The problem is that the default is chosen without checking the alternatives, by people whose actual edge is explaining, or curating, or shipping small things they own.
Ten years of backend depth is a strong hand in at least four different games. Playing it in the wrong one doesn't fail loudly — it just compounds slower, for years.
What actually differentiates developers
Between two equally senior engineers, the role-relevant differences are almost never technical. They're behavioral:
- Do you need to own the outcome? Some devs are energized by a well-run team effort; others only come alive when the thing that ships is theirs.
- Does explaining energize or drain you?Writing about what you built, answering users, teaching — for some it's a second engine, for others it's overhead.
- How much income uncertainty can you actually absorb? Not aspirationally — actually. Months without a paycheck are a feature of some directions and a dealbreaker for others.
- Building or understanding? A great Saturday ends with something that works — or with a pattern nobody else has seen yet. Those are different roles.
The four realistic directions
For a senior developer entering the AI wave, four directions cover most honest outcomes (full descriptions on the roles page):
Stay a Developer — but specialized and visible
You want to build, you like being employed, and the wave is your specialization opportunity. The differentiator isn't more skills — it's making the work legible: the developer who builds in public compounds; the one who only codes gets commoditized.
The Open-Source Contributor
You can tolerate building things thousands use while nobody knows your name — and you understand that merged contributions are credentials no résumé can fake. A build-up role: the reputation converts later, into hiring, consulting, or founding.
The Micro-Founder
You'd rather own 100% of something small than 5% of something big, and your dream day has no meetings in it. The leverage model: a product that earns while you sleep. The cost: 12–36 months of patience alongside the day job.
The Infrastructure Landlord
You've felt compute pricing from the inside and see infrastructure as a market, not a cost. The shovel-seller position — earns regardless of which end-products win. The gate: capital requirements most other roles don't have.
(And sometimes the honest answer is none of the four — the developer whose real edge is explaining belongs in the knowledge-producer roles, and usually knows it the moment someone says it out loud.)
What a wrong pick costs
The classic version is the promotion story: the strongest builder on the team gets made lead, the calendar fills with coordination, and eighteen months later they're better paid, further from the work that energized them, and vaguely looking at job boards. That's a role mismatch experienced in slow motion — nothing failed, everything just got heavier.
Wave-timing makes the cost sharper: mispositioning during a hype phase means re-entering later, when the easy credibility is gone and the field is crowded. If the day-to-day of a direction drains you in the first thirty days, that's not a discipline problem — it's data.
Stop guessing — measure the fit
The four questions above are the sketch; the assessment is the instrument. 77 behavioral questions, five equally weighted dimensions, scored against all 23 ecosystem roles — plus a capacity check (hours, runway, risk) so the answer fits your life, not just your temperament. Free, results in minutes.
Dr. Bastian Brand — author of The Hype Cycle Playbook, the four-volume framework this assessment is built on. About the method →
Last reviewed: July 2026
Dr. Bastian Brand, Ph.D. — author of The Hype Cycle Playbook, the framework behind the roletype assessment and this blog. About the author →