Are Certifications Worth It in the AI Age? I’m Going for the Full Set.

You’re in an exam. You’ve spent the last hour checking your answers, then double-checking them, then — just to be sure — going back a third time through the handful you’re still not solid on. Now the cursor hovers over the Finish Exam button with all the finality that button deserves. You breathe through the palpitations, click it, and wait out that infinite minute while it tabulates the results… and then it shows you.

That’s my experience with every Atlassian cert exam I’ve ever sat. Nine ACPs now, a tenth already on the calendar, plus three ACAs and five ACHs. I know exactly how nerve-wracking these things are — probably better than just about anyone. And yet I keep going back for more, and I emphatically tell other people to do the same.

So it’s a fair question to ask: in an age where an agent can explain any permission scheme in three seconds, is a cert still worth the time, the money, and the palpitations? I think it is — more than ever. And not from the sidelines: I’d renew even if they set fire to the badge at the end. The exams aren’t being killed by AI. If anything, it’s making them more important than ever.

Let me tell you what I actually get out of them, and how they became a big part of growing into “The Jira Guy.”

The Badge Was Never the Point

Let me concede the obvious part first: the certification itself is a nice-to-have. It absolutely opens doors. In a market where it’s gotten harder to land an Atlassian admin role and every third resume swears its owner is a “Jira expert,” a current cert is a (relatively) cheap, verifiable signal that you’re not bluffing. That’s a real sign that someone has validated you know your stuff, and that’s something I won’t take away.

But it’s also the side effect. I firmly believe that the actual product that makes them worth your while is the studying you do along the way.

Because here’s what an exam format actually forces you to endure: it drags you, kicking and screaming, into the dark corners of Jira and Confluence you’ve done everything possible to avoid. Nobody wakes up and decides to spend a Saturday on notification schemes. (Well, no one normal.) Nobody explores field context edge cases for fun. Most people learn just the parts of the tool their job forces them into, and then they cheerfully ignore the rest — right up until the exam has them staring down the barrel.

Live in workflows all day? The exam sits you down with permission schemes. Now are you comfortable in permission schemes? Here’s notification schemes and field contexts, have a seat. It does not care what you personally need to use day-to-day. I made the same point about the humble Project field — a thing so simple most admins never think about it until the scheme it lives in breaks something. A cert makes you go looking before it breaks. That forced breadth is the entire value. The badge is just the receipt.

The New Exams Test the Part That Actually Matters

I remember the older ACP exams as brutal. Since then, Atlassian has made some changes to the kinds of questions that are on there. You rarely see “here is a question, choose the three correct answers.” Those were especially bad because the ACP doesn’t believe in partial credit. You either had all three correct or you got no credit for that question.

But I believe that the ACP has changed in another fundamental way, and this is the part I want people to notice. It’s shifted from testing whether you know how to do a thing to whether you know when and why you should. That is, you see fewer questions about where the post-function settings live, and more about why you’d choose a post function over an automation or API integration.

And I think that distinction is everything.

I can teach someone the mechanics of Jira admin — the clicks, the config, the how-to — in about a week. Teaching them when to reach for a permission scheme instead of a workflow condition? Why a given automation rule is the wrong fix even though it, technically speaking, “works”? That’s a six-month conversation. Minimum. That’s the judgment layer, and it’s the whole gap between someone who can operate Jira and someone you’d trust to design it.

And in my opinion, the old exams tested the week. The new ones finally poke at the six months, if not longer. This is no accident. I’ve made no secret that I’m close with the certification team, and they’ve confirmed to me that this is their entire direction and goal.

AI Runs on Borrowed Judgment

Now put the agents back in the room, because this is where the “why bother” question really gets its answer.

Atlassian’s entire repositioning right now — the AI-native dev tooling push I raised an eyebrow at — is about Jira becoming the place agents get their orders, their context, and their oversight. And every copilot, automation, and agent that touches your configuration is borrowing judgment from whoever set that configuration up.

And a big part of that borrowed judgment has a name I’ve been saying since Team ’26: governance. Not the scary compliance-binder kind — the everyday kind. Every scheme you consolidated, every field context you scoped, every project hierarchy you built to still make sense three years out is a judgment call you already made and baked into the instance. The agent doesn’t reason its way to any of that. It inherits it.

If that person understands scheme inheritance, project categories, and why six teams calling the same field six different things is a governance problem and not a naming preference — the agent amplifies good decisions. Fast.

If they don’t, the agent amplifies the mess. Also fast. With far more confidence than a human would’ve had making the same mistake by hand.

An AI can look up the answer. It cannot tell you the answer is wrong. Telling truth from hallucination is still your job — and that job runs on a model in your head that “just ask the agent” will never build for you. It’s the old electrician’s invoice, the one he supposedly handed Henry Ford: one dollar for the chalk mark, nine thousand nine hundred ninety-nine for knowing where to put it. AI is phenomenal at chalk marks. It is not the person who knows where they go.

Where I Draw the Line

To be clear, having a certification is not proof you can run a Jira instance well. I’ve met certified admins who froze the second a workflow transition broke under pressure, and I’ve met uncertified ones who could rebuild a permission scheme from memory at 2 a.m. in the middle of an outage. The exam tests the model. It does not test the judgment you only earn by breaking things in production and cleaning up your own mess afterward. Treat it as a floor, not a ceiling — and don’t let anyone, especially a vendor, sell it to you as more than that.

It also costs money and time, and not everyone has equal access to either. If you’re weighing a cert against something that would move your career further this quarter, that’s a real tradeoff, and I’m not going to make it for you. My argument was never “get certified no matter what.”

It’s this: don’t let “an AI can just look it up” talk you out of becoming the person who’d know when the AI is wrong. That person is about to be the most valuable one in the room. The studying is how you become them. The badge is just proof you did.

---

So renew it or skip it — that part’s yours to decide. But the next time you’re sitting there, cursor hovering over Finish Exam, heart going, wondering why you put yourself through this again — know that the knot in your stomach is what learning the corners of the tool actually feels like. No agent can sit that exam for you, and none of them can carry what you walk away with. Don’t outsource the one thing that was ever worth having.

But until next time, my name is Rodney, asking, “Have you updated your Jira issues today?”

---

Enjoyed this one? These posts are free and always will be — but if this saved you a headache or taught you something worth keeping, you can drop a tip in the Ko-fi jar. No paywall, no subscription, no catch. Just a thanks if the writing earned it.

→ Support The Jira Guy on Ko-fi