IBM tripling entry-level jobs after finding the limits of AI adoption

Redefining entry-level work with AI

• Commenters note entry-level roles are being rewritten from “do the work” to “monitor and correct the AI,” e.g., HR staff supervising chatbots instead of answering every question.
• For engineers, “routine coding” is expected to shrink while time spent with customers and domain problems increases.
• Some see this as turning juniors into “AI operators” or “expensive AI agents,” rather than traditional apprentices learning the craft.

Motives and IBM-specific skepticism

• Many suspect this is less about “limits of AI” and more about cost: replacing older, highly paid staff with cheaper juniors using AI.
• IBM’s history of layoffs and age-discrimination litigation is repeatedly raised as context.
• Others suggest the hiring might be concentrated in consulting or low-cost regions, not core US engineering, pointing to the relatively small number of listed “entry-level” openings.

Juniors vs. seniors in an AI-assisted world

• One camp argues AI makes juniors 2–3x more productive, potentially approaching mid-level output, so hiring more juniors is rational.
• Another camp counters that effective AI use requires senior-level judgment in architecture, data structures, domain knowledge, and QA; juniors alone plus LLMs will produce brittle “vibe-coded” systems.
• There’s concern that AI will erode the senior ladder and depress wages, turning “coder” into a commodity job, but others say senior experience is now more critical to keep AI-generated systems on the rails.

Customer interaction: opportunity or liability

• Some welcome engineers doing more direct customer work, arguing it improves understanding of requirements and leads to better software.
• Others warn many engineers lack the soft skills for this, and that product/PM “face people” still reduce friction and protect engineers from bikeshedding and politics.

AI productivity: hype, metrics, and reality

• Several commenters say corporate AI bets on replacing developers have underdelivered; AI is useful but not a drop-in replacement for most knowledge workers.
• Individual anecdotes report big personal productivity and side-business gains, but there’s skepticism about a broader “productivity boom” given the lack of visible breakout products.
• Attempts to quantify gains (e.g., “18% efficiency” via story points, tracking “tokens burned”) are viewed as noisy or superficial, more about KPIs than real value.