Atlassian Cuts QA and Support While Hiring 800 AI Engineers—What Happens When Junior Career Paths Disappear?

I’m still processing what happened last month. Atlassian announced they’re cutting 1,600 jobs—10% of their workforce—with heavy emphasis on QA and support roles. The kicker? They’re simultaneously hiring 800 AI engineers.

This isn’t just about one company. It’s about the disappearing ladder that got most of us into tech.

The Missing First Rung

My failed startup (RIP, 2023) had a scrappy team of 8. Our first hire after the founders? A junior QA engineer fresh out of a bootcamp. She caught bugs, asked annoying questions, and gradually learned enough about our product to transition into product management.

That path doesn’t exist anymore.

Entry-level postings in software development dropped 67% between 2023-2024. Junior hiring at the 15 biggest tech firms fell 25 percent. And now companies like Atlassian are saying the quiet part loud: AI tools reduced the need for manual testing by approximately 60%.

The Experience Paradox

Here’s what kills me: AI automates codified knowledge (the stuff you learn from books and tutorials), but not tacit knowledge (the stuff you learn by screwing up on real projects). For juniors, codified knowledge represents the expert part of their jobs. For seniors, those same tasks are the grunt work.

So we’re automating the learning curve.

Junior devs used to write CRUD apps, fix bugs, write tests. That’s where you learn why certain patterns exist, why tech debt accumulates, how systems break under load. AI can generate that code faster—but it can’t give you the experience of debugging at 2am when prod is down and your database transaction locks are cascading.

What Gets Lost?

From a design perspective, I’m worried about what happens to product teams when everyone has 10+ years of experience:

  1. Fresh perspectives disappear. Juniors ask “why do we do it this way?” because they don’t know the legacy reasons. That naivete is valuable.

  2. Diversity takes a hit. Entry-level roles were the most accessible—QA, support, junior dev didn’t require elite CS degrees or years of experience. They were the pipeline for first-gen college students, bootcamp grads, and career changers.

  3. Innovation gets narrower. Everyone on the team shares the same 10-15 years of industry baggage. Nobody’s questioning whether “best practices” are actually still best.

The 800 AI Engineers

Here’s where it gets complicated: Those 800 AI engineer roles Atlassian is hiring? They require advanced degrees, 5+ years of ML experience, and deep expertise in production AI systems.

We’re not replacing entry-level with entry-level. We’re eliminating the bottom rung and adding another rung at the top.

So… What Do We Do?

I don’t have answers, just uncomfortable questions:

  • For companies: How do you develop future senior engineers if you stop hiring juniors? Where will your next CTOs come from?

  • For bootcamps/universities: Are you training people for jobs that don’t exist anymore? What’s the honest career path now?

  • For current seniors: Do we have a responsibility to preserve junior roles even if AI is “more efficient”? Or is that just fighting the inevitable?

  • For people trying to break in: What’s the actual entry path in 2026? Technical writing? DevOps? Support engineering? Or is the door just… closed?

My startup failed, but at least we created one entry-level role that launched someone’s career. If we’d had AI tools and more funding pressure, would we have hired her at all?

I’m genuinely asking: When the entry-level roles disappear, what happens to the people who would have filled them—and what happens to our industry when we only hire people who already have experience?


Related: Tech Layoffs 2026: AI-Driven Cuts at Atlassian, Salesforce, Oracle