Other

junior developer

Based on 10 assessments · 1 from real users

32% Moderate risk

Average realistic automation risk across all junior developer profiles in the dataset.

Raw potential
74%
Realistic risk
32%
Research benchmark ?
45%

Raw potential = I/O automation ceiling. Realistic risk = adjusted for informal knowledge and social context. Research benchmark: Eloundou et al. (2023)

Distribution across 10 profiles. Middle half of junior developers score between 30% and 33%.

0% 50% 100%
p10 · 29%
37% · p90
On-screen work 79%

Done entirely on a computer. High AI exposure — these tasks are already in the automation zone.

In-person + screen 1%

Physical sensing, digital output — e.g. interviewing someone then writing a report. Partially protected.

Computer + action 1%

Computer input, real-world output — needs someone to act on it, not just software.

Fully in-person 19%

No computer required. Furthest from automation — the strongest human advantage.

3 synthetic profiles for a junior developer, ordered by automation exposure. Tab between them to see how task mix drives the score difference.

Task Time Type Exposure
Writing and debugging code based on requirements or tickets (implementing features, fixing bugs)
deep expertise social element
35% DD 28%
Attending meetings: standups, sprint planning, technical discussions, demos
16% AA 6%
Code review: reading teammates' code, suggesting improvements, approving pull requests
deep expertise
14% DD 13%
Writing or updating documentation, commit messages, and communicating progress in Slack/tickets
12% DD 47%
Collaborating with senior developers or peers to understand complex systems or unblock problems
deep expertise
11% AA 2%
Running tests, debugging test failures, and fixing issues found in QA or staging
9% DD 49%
Reading documentation, Stack Overflow, and learning new libraries/frameworks needed for tasks
1% DD 61%

Work as a junior developer? Map your specific role.

Start assessment →