--- title: Junior engineers are skipping straight to... description: An engineering manager argues that junior developers are being pushed into architect-level thinking faster than they're building the judgment to support it,... canonical: https://daily.dev/posts/junior-engineers-are-skipping-straight-to-architect-level-thinking-cr04y7jer twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Junior engineers are skipping straight to architect-level thinking | daily.dev og:description: An engineering manager argues that junior developers are being pushed into architect-level thinking faster than they're building the judgment to support it,... og:url: https://daily.dev/posts/junior-engineers-are-skipping-straight-to-architect-level-thinking-cr04y7jer og:image: https://api.daily.dev/og/posts/Cr04y7Jer.png og:image:alt: Junior engineers are skipping straight to architect-level thinking og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Junior engineers are skipping straight to architect-level thinking **[LeadDev](https://daily.dev/sources/leaddev)** · 9 min read · 61 upvotes · 10 comments ## Summary An engineering manager argues that junior developers are being pushed into architect-level thinking faster than they're building the judgment to support it, largely because AI tools let them generate code before they understand the systems behind it. The piece proposes treating learning, understanding, and judgment as explicit growth metrics alongside output, and describes a three-phase model for AI proficiency (tutor, copilot, accelerator) with mentorship scaffolding that loosens as engineers mature. It stresses protecting senior engineers' bandwidth for mentoring and rethinking apprenticeship and internship programs so junior hires build real system ownership rather than just shipping more AI-generated code. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What are the three phases of AI proficiency for engineers as they grow from junior to senior? The three phases are AI as tutor, copilot, and accelerator. In the tutor phase, engineers use AI mainly to learn and ask Socratic questions about code and systems. In the copilot phase, they use AI for more complex work while owning design decisions and debugging independently. In the accelerator phase, experienced engineers treat AI like a fast junior partner, questioning its proposals and mentoring others, with scaffolding like mandatory pairing and close review loosening as judgment matures. _Engineering managers shaping AI adoption policies can find more perspectives like this through daily.dev._ ### Why might tracking code output alone be a poor metric for junior engineer growth when they use AI coding tools? Output alone hides whether an engineer actually understands and can own the systems they're shipping, since AI tools let them generate code faster than they build real judgment. A recommended fix is tracking learning, understanding, and judgment explicitly, for example checking whether an engineer can walk through a recent change and explain its underlying concepts, or how they respond during incidents and code reviews. _Leads rethinking how to measure junior developer growth can track this kind of thinking on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@yaireo** · 18 upvotes > It's like giving a 5 year old to run a restaurant **@oscarpearson** · 15 upvotes > Every time I read posts like this I'm just facepalming. We all saw this coming from a mile away. But not the managers or the C-level people. And they are the ones 'leading' us.. > > Somehow with AI everyone has entered a psychosis and lost the long-term view for things, because they have to jump on the hype train because everyone else is on it. Otherwise they might miss out on the trillions this tech will bring them. **@tenko** · 6 upvotes > and what th are those juniors supposed to do? they are expected to have fully functioning applications in their portfolio to even apply for _junior_ positions, which are growing scarce too cause ai writes better code than those juniors and everybody knows it. there's no place for juniors anymore, so their only choice is to extend their learning path and apply for mid positions. **@bits\_and\_bytes** · 3 upvotes > we don't have rights to blame junior, senior or manager. it is the mindset of everyone. > Manager should assign to the right person while shielding from Clients. > Junior should more focus on doing and will to learn. > Senor should manage his work and ownership of Junior. **@agustinbarrientos** · 2 upvotes > Incident explain-backs should join the growth check so juniors have to explain decisions under pressure. A senior can hold the rollback boundary while the junior leads a contained incident. ## Similar posts on daily.dev - [Microsoft execs warn agentic AI is hollowing out the junior developer pipeline](https://daily.dev/posts/microsoft-execs-warn-agentic-ai-is-hollowing-out-the-junior-developer-pipeline-zfchuraa9) · The New Stack · 1 upvotes · 0 comments - [Above the API: What Developers Contribute When AI Can Code](https://daily.dev/posts/above-the-api-what-developers-contribute-when-ai-can-code-5fi2t6rld) · DEV · 54 upvotes · 2 comments - [The Disappearing Senior: AI and Entry Level Jobs](https://daily.dev/posts/the-disappearing-senior-ai-and-entry-level-jobs-d3dlrkj2y) · SQL Authority · 168 upvotes · 32 comments - [How Artificial Intelligence Disrupts Engineering Progression](https://daily.dev/posts/how-artificial-intelligence-disrupts-engineering-progression-3oilsnrwc) · InfoQ · 0 upvotes · 0 comments --- Tags: [#career](https://daily.dev/tags/career), [#leadership](https://daily.dev/tags/leadership), [#ai-coding](https://daily.dev/tags/ai-coding), [#code-review](https://daily.dev/tags/code-review) [View this post on daily.dev](https://daily.dev/posts/junior-engineers-are-skipping-straight-to-architect-level-thinking-cr04y7jer) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Junior engineers are skipping straight to architect-level thinking","url":"https://daily.dev/posts/junior-engineers-are-skipping-straight-to-architect-level-thinking-cr04y7jer","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/junior-engineers-are-skipping-straight-to-architect-level-thinking-cr04y7jer"},"datePublished":"2026-08-25T09:38:25.288Z","dateModified":"2026-09-13T21:48:06.428Z","description":"An engineering manager argues that junior developers are being pushed into architect-level thinking faster than they're building the judgment to support it,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/19931621d7aa9dca7d0e1499415e24b1?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/19931621d7aa9dca7d0e1499415e24b1?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"LeadDev","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"LeadDev","logo":"https://media.daily.dev/image/upload/s--u_Q34nzh--/f_auto,q_auto/v1774514111/logos/leaddev?_a=BAMAMiWQ0","url":"https://daily.dev/sources/leaddev"},"commentCount":10,"discussionUrl":"https://daily.dev/posts/junior-engineers-are-skipping-straight-to-architect-level-thinking-cr04y7jer","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":61},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":10}],"keywords":"career,leadership,ai-coding,code-review","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"LeadDev","item":"https://daily.dev/sources/leaddev"},{"@type":"ListItem","position":3,"name":"Junior engineers are skipping straight to architect-level thinking"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/junior-engineers-are-skipping-straight-to-architect-level-thinking-cr04y7jer","comment":[{"@type":"Comment","text":"It’s like giving a 5 year old to run a restaurant","datePublished":"2026-08-26T13:04:34.441Z","url":"https://daily.dev/posts/Cr04y7Jer#c-mXVVb4WGv","author":{"@type":"Person","name":"Yair Even Or","url":"https://daily.dev/yaireo","image":"https://avatars.githubusercontent.com/u/845031?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":18}},{"@type":"Comment","text":"Every time I read posts like this I’m just facepalming. We all saw this coming from a mile away. But not the managers or the C-level people. And they are the ones ‘leading’ us…\nSomehow with AI everyone has entered a psychosis and lost the long-term view for things, because they have to jump on the hype train because everyone else is on it. Otherwise they might miss out on the trillions this tech will bring them.","datePublished":"2026-08-26T16:35:06.674Z","dateModified":"2026-08-26T16:37:02.331Z","url":"https://daily.dev/posts/Cr04y7Jer#c-usLFdPcj5","author":{"@type":"Person","name":"Oscar Pearson","url":"https://daily.dev/oscarpearson","image":"https://media.daily.dev/image/upload/s--QnXAEQGE--/f_auto/v1780119425/avatars/avatar_bPCgf4qQE?_a=BAMAMiWQ0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":15}},{"@type":"Comment","text":"and what th are those juniors supposed to do? they are expected to have fully functioning applications in their portfolio to even apply for junior positions, which are growing scarce too cause ai writes better code than those juniors and everybody knows it. there’s no place for juniors anymore, so their only choice is to extend their learning path and apply for mid positions.","datePublished":"2026-08-28T15:21:08.435Z","url":"https://daily.dev/posts/Cr04y7Jer#c-rwmc3g3F2","author":{"@type":"Person","name":"蘿安娜","url":"https://daily.dev/tenko","image":"https://lh3.googleusercontent.com/a/ACg8ocJRzdvPC6CCqN7zfkoUeaez9M3Do8Exp7bETQq7hkVg3PXM3UKN=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":6}},{"@type":"Comment","text":"we don’t have rights to blame junior, senior or manager. it is the mindset of everyone.\nManager should assign to the right person while shielding from Clients.\nJunior should more focus on doing and will to learn.\nSenor should manage his work and ownership of Junior.","datePublished":"2026-08-28T02:55:17.070Z","url":"https://daily.dev/posts/Cr04y7Jer#c-XfCs82XxL","author":{"@type":"Person","name":"bits_007","url":"https://daily.dev/bits_and_bytes","image":"https://avatars.githubusercontent.com/u/182549945?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3}},{"@type":"Comment","text":"Incident explain-backs should join the growth check so juniors have to explain decisions under pressure. A senior can hold the rollback boundary while the junior leads a contained incident.","datePublished":"2026-08-26T22:31:08.811Z","url":"https://daily.dev/posts/Cr04y7Jer#c-jzDQ1Pq8y","author":{"@type":"Person","name":"Agustin Barrientos","url":"https://daily.dev/agustinbarrientos","image":"https://media.daily.dev/image/upload/s--5ayxQnqn--/f_auto/v1788281802/avatars/avatar_wQYYVe5Tbj0NJ7C7qPoa8?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/junior-engineers-are-skipping-straight-to-architect-level-thinking-cr04y7jer#faq","mainEntity":[{"@type":"Question","name":"What are the three phases of AI proficiency for engineers as they grow from junior to senior?","acceptedAnswer":{"@type":"Answer","text":"The three phases are AI as tutor, copilot, and accelerator. In the tutor phase, engineers use AI mainly to learn and ask Socratic questions about code and systems. In the copilot phase, they use AI for more complex work while owning design decisions and debugging independently. In the accelerator phase, experienced engineers treat AI like a fast junior partner, questioning its proposals and mentoring others, with scaffolding like mandatory pairing and close review loosening as judgment matures. Engineering managers shaping AI adoption policies can find more perspectives like this through daily.dev."}},{"@type":"Question","name":"Why might tracking code output alone be a poor metric for junior engineer growth when they use AI coding tools?","acceptedAnswer":{"@type":"Answer","text":"Output alone hides whether an engineer actually understands and can own the systems they're shipping, since AI tools let them generate code faster than they build real judgment. A recommended fix is tracking learning, understanding, and judgment explicitly, for example checking whether an engineer can walk through a recent change and explain its underlying concepts, or how they respond during incidents and code reviews. Leads rethinking how to measure junior developer growth can track this kind of thinking on daily.dev."}}]} ```