Your senior engineers need junior questions more than juniors need answers – www.cio.com

When juniors take naive questions to an AI assistant instead of a colleague, dashboards record fewer interruptions and higher velocity. What they miss is the erosion of senior engineers’ architectural fluency, and the single point of failure that hardens until an outage forces someone to explain the system out loud.
Over the past year, I watched engineering teams celebrate a quiet drop in Slack interruptions. A junior used to ask a foundational question in a channel: why does this service retry three times instead of once? Today that junior asks an AI assistant first, messaging a senior only if the answer fails in testing. Already, 51% of developers ask generative AI for help they once asked a colleague, and 62% do so to avoid looking uninformed.
Because AI now absorbs routine implementation and debugging, it strips away the trial-and-error juniors once needed to grow into seniors.
Most writing about this shift worries about what juniors lose: less mentorship, thinner context and a shallower feel for production systems. That worry is real, but it is only half the balance sheet.
The costlier loss belongs to the senior engineer and the organization paying them to hold the architecture together. It rarely gets discussed because from the inside it looks like uninterrupted focus time.
A junior engineer’s question was never just a request for a file path. It did three distinct jobs at once, and all three required a human on the receiving end.
First, it transferred tacit institutional memory that documentation never captured. When a senior explained why a payment service retried three times, they rarely recited the config. They narrated an incident from a year ago involving a partner’s rate limiter that never made it into a wiki. Documentation misses that history because nobody writes a design doc after the fact unless something breaks again.
Second, the question gave the senior a live audit of where the system had become needlessly opaque. A staff engineer who has owned a core service for three years goes blind to its rough edges; everything feels obvious once you know the history behind every compromise. A newcomer’s confusion is a free signal showing where the code no longer speaks for itself.
Third, and most overlooked, answering forced an articulation that kept the senior’s own mental model sharp. Explaining a state machine out loud to a colleague who asks follow-ups is a different mental discipline than silently knowing it. Teachers have known this forever: structuring knowledge for someone else exposes gaps and outdated assumptions in your own head. Seniors used to get that workout dozens of times a quarter for free.
Because those informal questions were never scheduled on a calendar or tracked in Jira, their disappearance triggers no alarm. When an AI assistant intercepts the first tier of naive questions, the senior simply gets interrupted less often. Over a single sprint, that silence feels like focus time. Over several quarters, it quietly erodes a senior engineer’s active command of the architecture they own on paper.
In practice, this decay stays hidden during routine code review because spotting a local bug on screen only requires passive recognition. Failure surfaces in postmortems when an incident demands active cross-system recall: tracing how failures cascade across service boundaries during a 2 a.m. outage. Across 211 million lines of analyzed code, structural refactoring has already collapsed from 25% of changes to under 10%, while duplicated code blocks jumped eightfold. Answering a junior’s “what happens if this service times out?” used to force seniors to trace those paths out loud every week. Without that rehearsal, the first live cross-boundary trace happens during an outage.
For a CIO or VP of Engineering, this creates a treacherous blind spot. Standard engineering health metrics do not merely miss this erosion; they actively misread it as progress.
When juniors turn to AI assistants instead of pinging seniors, short-term output metrics look healthier. Pull request cycle times tighten, ticket velocity ticks upward and seniors report fewer context switches on surveys. On throughput dashboards, the organization appears to scale effortlessly.
Underneath those green indicators, three structural risks accumulate.
An organization can coast on accumulated fluency for many months before the deficit shows. By the time it surfaces in postmortems or failed handoffs, the habits keeping senior engineers’ understanding sharp have been dormant for quarters.
When leaders notice institutional context slipping, their first instinct is more aggressive documentation or indexing wikis into AI retrieval tools. That solves lost context for readers, but not the senior engineer’s problem. Writing a static wiki page never forces a veteran to defend trade-offs or trace failure cascades under questioning. Documentation captures static answers; only live human friction keeps architectural fluency sharp.
Restoring that friction does not mean restricting juniors from using AI assistants, nor does it mean adding optional team meetings that get cut the moment a deadline tightens. If directors are rewarded solely on ticket velocity, informal coaching will always lose to the sprint board. Instead, leadership must embed live human articulation across the four moments where architecture is built, rehearsed, stress-tested and passed on.
Every seasoned engineer knows the feeling of trying to explain a familiar system out loud and finding the words no longer come cleanly. That stumble rarely means they lost their edge. It means the friction that kept their understanding sharp was automated away, and leadership must put it back before the next outage asks for an answer.
Nishant Virmani is a staff technical program manager at Google, where he drives large-scale software delivery, AI adoption, and platform governance across complex engineering organizations. With more than 15 years of engineering leadership across Google, YouTube and Apple, he specializes in scaling global consumer and enterprise platforms, aligning cross-functional teams, and building the operational frameworks that turn AI and platform bets into durable production outcomes.
Sponsored Links

source
This is a newsfeed from leading technology publications. No additional editorial review has been performed before posting.