Post 2 — The On-Ramp Is Disappearing

  1. Print to PDF: Click the button → Save as PDF (1080×1080px per slide).
  2. Upload to LinkedIn: New post → document icon → upload PDF → swipeable carousel.
  3. Post tip: Paste the post text from linkedin_posts.html → put the task2vec.com link in the first comment.
Slide 1 / 7
Post 2  ·  Spring Framework · 57 Engineers Tracked
AI didn't kill junior jobs.
It killed the path to senior ones.
We tracked 57 engineers across 20 years of Spring Framework.
Here's what the data says about how expertise actually forms —
and what AI disrupts first.
1 / 7
Slide 2 / 7
Career trajectory — Spring Framework 2003–2022
57
junior starters
tracked
3+
year careers
minimum
10+
clustered tickets
required
72%
grew significantly into harder, more complex work
Defined as a 15+ percentage-point increase in "Escalate-tier" ticket share
from first year to last two years of career in the project.
2 / 7
Slide 3 / 7
Share of ticket types — 57 junior starters, by career year
The hard work share grows steadily with experience
Career yr 1
17%
Career yr 2
32%
Career yr 3–4
38%
Career yr 7–9
40%
Career yr 10+
44%
Automate — routine work
Assist — domain work
Escalate — complex work
3 / 7
Slide 4 / 7
What did growing engineers actually work on?
Early career (yr 1–2)
Assist
Spring IDE Tooling
14% of early work
Assist
Spring Web Flow
10% of early work
Assist
MongoDB Mapping
7% of early work
Assist
Bean Configuration
6% of early work
Late career (last 2 yr)
Escalate
JSF & Spring Web Flow
18% of late work
Escalate
Workspace & Class Loading
11% of late work
Escalate
Validation & Data Binding
9% of late work
Escalate
JDBC Compatibility
8% of late work
They didn't start on docs fixes. They started on bounded domain work — Assist tier. The on-ramp is exactly what AI disrupts first.
4 / 7
Slide 5 / 7
Where AI disrupts the learning path
The tier that built the most expertise is the
first tier AI makes easier
Automate
Routine, repetitive work. AI replaces this entirely. Never the primary learning vehicle.
Assist
Bounded domain work. AI drafts the solution — human reviews it.
← on-ramp here
Escalate
Architecture, concurrency, cross-cutting concerns. Requires deep expertise — destination.
With Assist tier: junior writes draft, senior reviews it → learning happens.
With AI assist: AI writes draft, junior reviews it → different skill. Possibly no learning.
5 / 7
The question for engineering leaders
Are your junior engineers still on a path to becoming
senior ones?
The data shows 72% of junior starters did grow into complex work — when they had an Assist-tier on-ramp.

That on-ramp is now the first thing AI adoption disrupts.

This isn't a reason to slow down AI adoption. It's a reason to have a deliberate answer to the question before it becomes a problem.
6 / 7
Run this analysis
on your own Jira
Your ticket history contains the same signals.
We can run the career arc analysis on your team's data.
Based on 69,000 Spring Framework tickets · 20 years of history
7 / 7