신입 개발자가 안 보입니다 - 매니저가 위에서 본 진짜 이유

Overview

A developer manager explains why many companies are not hiring junior developers—especially in Canada—and why teams increasingly consist mostly of seniors. While AI tools are widely discussed online, the manager argues that most enterprises are not using AI in an autonomous, end-to-end “system-level” way. Instead, they primarily use AI as an IDE copilot-style assistant to generate code faster.

Because of this, AI’s real impact isn’t simply “replacing junior work,” but changing team structure and expectations.

Key claims about AI and hiring

• AI is not broadly deployed autonomously at the “agent/system infrastructure” level (e.g., custom infrastructure that fully executes complex tasks). The manager says most companies use AI for developer assistance—like code generation and minor automation—rather than running full AI workflows end-to-end.

• Indirect effects still matter: even with limited autonomy, AI enables a senior developer with AI to produce enough output that companies can staff fewer juniors.

How team composition and expectations shift

The manager describes a “staffing math” shift:

“1 senior + AI” ≈ “1–2 seniors + 2–3 juniors” (Previously, seniors mentored juniors through design and review, while juniors learned by elaborating.)

With AI assistance, juniors are less “required” for throughput. Companies respond by:

• Raising expectations for seniors (“extract more from them”)
• Increasing pressure, because faster code generation still requires:
  • review
  • product decision-making
  • alignment If the product can’t keep up, complexity grows—but leadership may still push for speed because it’s cheaper than training new hires.

The deeper reason: retention risk + senior availability

Beyond AI, the manager claims the fundamental driver is economics and risk:

• Companies have been burned by training investments. During periods like COVID, employees could leave after only 1–2 years, creating “trauma” around investing in juniors.
• Meanwhile, the market is described as saturated with experienced talent (especially after layoffs). As a result, senior recruiting is easier than developing juniors long-term.

Therefore, top management chooses a model of:

• a small set of full-time experienced seniors
• additional experienced contractors
• AI tools for productivity
• minimal true junior hiring (The manager notes “assistant” roles may exist via subsidies, but not as a strategy to grow teams.)

What differentiates strong vs weak developers in the AI era

The manager argues the performance gap between skilled and unskilled developers is widening:

• Less effective developers follow tickets literally and stop when blocked.
• Stronger developers independently understand context and constraints, ask questions, and propose multiple options even when blocked.
• In an AI era, developers who stay ahead by at least one step create value not only in their own tasks, but by improving team workflows—e.g., using AI to organize APIs across a domain and uncover issues like endpoints being called with different versions.

Advice to students and prospective juniors

To navigate these hiring trends, the manager recommends:

• Securing an internship—preferably through opportunities at “Yeongeul” (as referenced in the subtitles).
• Demonstrating key behaviors during internships:
  • bringing options, not just problems
  • using AI to improve beyond one’s own domain
  • actively participating in team process improvements

The manager also notes that converting interns to full-time may be safer than hiring unknown new graduates, because the company can evaluate performance first (and sometimes conversion may be to contract/full-time roles depending on circumstances).

Bottom line

The manager concludes that juniors aren’t being excluded mainly because AI “handles their work.” Instead, company hiring and staffing methods have changed: senior+AI is treated as cheaper than training entry-level developers.

The final encouragement is that genuinely talented people can still succeed without experience—by showing an “option-bringing” mindset, improving across boundaries, and leveraging AI effectively.

Presenters or contributors

• Video presenter: “I was a member at the development point” (unnamed in subtitles; presented as a “developer manager” perspective)