The Unconventional Expert: 3D Printing My Way Through the Hardest Atlassian Exams
The 150% Commitment: Going All-In Because I Can't Help It
Most people see Atlassian certifications as a sensible professional milestone, a box to tick to keep the career moving. That’s a perfectly valid way to play it, but my brain doesn't really do "sensible." I’ve never been one for half-measures; if I’m going to do something, I’m going to disappear into the rabbit hole. When I set my sights on the Atlassian Certified Administration Expert status, I knew I wouldn't be satisfied with a surface-level approach.
Being neurodivergent means my "150%" setting is essentially my default. It’s less about "high-octane hyper-focus" (which sounds like a marketing slogan) and more about a persistent, loud internal drive to take a professional goal and make it my entire personality for six months.
Once I’ve set my mind to a path I'm passionate about, maintaining interest becomes effortless; the challenge isn't staying focused, but rather finding enough ways to feed that hunger for knowledge. I didn't start with a rigid study calendar; instead, I took the journey one certification at a time, immersing myself fully in the preparation for each before moving to the next. For me, this wasn't about dipping my toes in to see if I liked the water, it was about putting all my chips on the table and diving in.
2. The Neurodivergent Twist: Hardware, Robots, and Dopamine Loops
Because maintaining interest is effortless once I’m committed, the challenge isn't staying focusedit’s finding meaningful ways to channel that energy. To make the digital milestones of the Atlassian Cloud feel more "real," I decided to bridge the gap between software and the physical world through 3D design and printing. This wasn't just a distraction; it was a way to gamify a professional journey using my passion for creation.
Iterative Design: The Badge Stand Odyssey
The design of my certification display was a journey that mirrored the iterative nature of software development. My original concept, a single rigid stand for five badges soon hit a scalability wall. I wanted something modular and elegant that could grow with me, which eventually led me to a design that uniquely resembles a 3D version of the iconic Atlassian "A."
The "A" wasn't just an aesthetic choice; it was functional. The natural angles of the logo provided the perfect resting pitch for the badges to drop into. However, this created a significant engineering hurdle: printing high-resolution text and fine detail directly onto those sloped faces. After several failed variations of experimenting with different angles and support structures, it became clear that "printing in place" wouldn't meet my standards for quality.
To solve this, I moved to a modular snap-in system. By separating the custom titles and backplates from the main frame, I could print them at the optimal orientation for crisp, professional-grade detail. This shift to modularity also unlocked the ability to bridge the gap between the physical and digital:
The QR Phase: My first attempt at a "digital link" involved 3D-printed QR code inserts. This was an exercise in constraint management: nozzle resolution and print time fought against the complexity of the QR pattern. To keep the models printable and functional, I had to shorten URLs, balancing the use of external providers against rolling my own solution - just to keep the "dots" large enough for the printer to resolve. |  |
The NFC Evolution: Seeking a cleaner "V2" that bypassed the visual clutter and resolution limits of QR codes, I eventually shifted to embedding NFC chips directly inside the badges. This created a seamless, "invisible" link to my digital credentials. |  |
The "150%" Ecosystem: Meet Brovo
The immersion didn’t stop at the desk stand. My creative journey took a literal turn toward "scaling up" when I started printing an articulated "Dummy 13" robot. I began with the community favourite, standard 3-inch model, but quickly realised I could dream bigger. This led to a 20+ hour print of a 300% scale version, which naturally had to become my dedicated Atlassian mascot. With a bit of naming help from my friend Craig Smith, he was dubbed "Brovo" - a comedic nod to Rovo, AI, and the robotic nature of my new desk-side technical lead. To round out the ecosystem, I even experimented with DIY swag, 3D printing a custom template to paint my own Atlassian-themed T-shirt to wear during study sessions. For me, this is the essence of going all-in. It’s the power of combining a creator's mindset with professional goals to turn a digital certification path into a complete, tangible, and slightly unnecessary ecosystem. |  |
3. The Top-Down Strategy: Why I Started at the Summit
When planning an Atlassian certification path, the common logic is to build a foundation with Associate-level exams before tackling the Professionals. I took the opposite approach: I started with the most complex certifications on the map.
The "Deep End" Logic: Solving the Hard Stuff Early
There's a specific logic to starting with the most involved certifications. By wrestling with the "beasts” - global permissions, security, and site-level admin, you’re essentially setting the foundation for the entire house. Once you’ve dealt with the structural integrity of a Cloud Org, the smaller details of project-level settings stop looking like obstacles and start looking like common sense.
When you start at the top, every subsequent area of learning makes sense much faster. You aren't just memorising features; you’re seeing how they fit into the massive infrastructure you’ve already mastered. If you have the hands-on experience, don't be afraid to jump into the deep end as it makes the rest of the journey feel like a victory lap.
Prioritising Professional Context
Instead of following a pre-set curriculum, I prioritised Cloud Organisation Administration and Jira Administration for Cloud. My advice? Let your current workload dictate your study path. Because I was already architecting org-level security and cross-product configurations, these "beast" exams provided immediate ROI. They offered a formal framework for the decisions I was already making. Earning these high-level credentials early on wasn't just about a badge; it was about ensuring that the strategy and architecture I was delivering were backed by Atlassian’s best practices.
4. The Preparation Ecosystem: Beyond the Study Guide
While my journey was fueled by hyperfocus, my preparation was grounded in a multi-layered approach. Passing these exams requires more than just reading documentation; it requires a blend of official learning, technical curiosity, and "living" in the tools.
The Foundation: Atlassian Learning
My primary method of formal study was the Atlassian Learning online courses. These are essential for identifying the specific "areas of importance" the exams focus on. The system is intuitive, and the "badge" rewards for completing courses provide a great sense of momentum. Don't get me wrong, the official courses are great for learning what Atlassian wants you to know for the exam, but to pass the high-level ACPs, you have to get your hands dirty.
Wearing All the Hats: Admin, Dev, User; Be All Three
There’s no substitute for hands-on experience, and it comes in different forms. Over the past decade, I’ve worked as a Software Engineer, Technical Lead, and Atlassian Org Administrator in professional settings.
This multi-lens perspective is the ultimate study guide, but you don't necessarily need years in each role to succeed. My best advice is to move beyond the theory. If you haven't had the opportunity to hold these roles professionally, use Atlassian Sandboxes or personal subscriptions to simulate them. Build a project as a Software Lead, manage a space as a Subject Matter Expert, and then try to break (and fix) the global configuration as an Admin. Seeing the platform from every angle makes the exam logic click.
The Developer’s Edge: API-First Thinking
For those with a technical or development background, the Atlassian REST APIs are an underrated study tool. I didn't just study the UI; I looked at the underlying data structures. Building migration-based tooling and exploring user provisioning via the API provided a "backstage pass" to the platform. When you understand how a work item or an organisation is structured at the data level, you stop memorising "what" a feature does and start understanding "why" it behaves that way.
Prompting My Way to Expert: Using Rovo as my Study Mate
I’ve always found it slightly ironic to study for Atlassian exams using static PDFs or physical notebooks. Instead, I treated my certification path as a live project within the tools themselves, but with a modern twist: I offloaded the busywork to AI.
Standardised Note Taking: I used a combination of AI tools to generate study notes formatted to my exact specifications. These weren't just copy-pasted blocks of text; they were structured data ready to be dropped into Confluence for further refinement.
The Rovo Advantage: This is where things got interesting. I used the Rovo Chrome extension and Rovo Chat to "trawl" comprehensive documentation and instantly generate JQL function cheat sheets for my Confluence study pages. It turned hours of manual collation into a few clicks.
Visualising the JSM Web: If you’ve looked at Jira Service Management lately, you know it’s a sprawling web of requests, queues, incident management, on-call scheduling, response escalations, and a whole bunch more. To keep my head from spinning, I used Rovo to map out the connections. It took the tangled mess of JSM's "moving parts" and generated a head-to-toe diagram that actually made sense - something a standard slide deck rarely achieves.
The Kanban Reality Check: I did keep a Jira Kanban board, but not just for show. It was my "WIP" limit for my brain. If a certification task stayed in "In-Progress" too long, it was a signal that I needed to stop reading and start breaking things in my personal Atlassian sites until the concept clicked.
5. My Top Tips and Personal Difficulty Rankings
Reaching the Expert tier is as much about strategy as it is about study. If I had to boil my odyssey down to four core pieces of advice for anyone starting their own journey, they would be:
Immerse Yourself in the "Why": Get as much hands-on exposure as possible. Ideally, this happens in real-world professional situations, but personal sandboxes are a great fallback. Don't just follow the steps, understand why the tools work the way they do. Explore the weird edge cases that official courses usually ignore; that’s where the exam questions live.
Be Strategic with Atlassian Learning: Use the official paths to guide your formal study. Pay close attention to the Exam Overviews to pinpoint the topics of importance. If you’re time-poor, dedicate the highest amount of focus to the most heavily weighted sections of the exam. Most importantly: do all the practice questions and ruthlessly analyse the ones you get wrong until you actually understand the logic behind the "correct" answer.
Commit and Lock It In: Set realistic timelines and concrete goals. If you’ve worked through the course content, aren’t being tricked by the sample questions, and have a solid grasp of the linked documentation, you’re likely ready. Stop waiting for "perfect" knowledge; commit to the goal and lock in a concrete exam booking date.
The YouTube Advantage: "Exam Study Sessions" on YouTube are a massively underrated tool. They offer exposure to real discussions around complex topics and provide invaluable insights into exam techniques and the specific phrasing styles you can expect on the day.
The Atlassian Expert’s Difficulty Ledger
Based on my personal journey of tackling these exams, here is how I ranked them from "The Final Boss" level hard, down to "Introductory" level easy:
Rank | Exam / Credential | Difficulty | Why it’s Ranked Here |
08 | ACP-120: Jira Admin (Cloud) | 🔴 10 | The Final Boss. This ensures you truly understand the "Why" behind the logic and reinforces the gravity of the Admin role.
|
07 | ACP-420: JSM Projects | 🟠 09 | The Domain Divide. With my Software Engineering background, the sheer breadth and depth of required learning in the less-familiar ITSM space made this tough ask. |
06 | ACP-520: Cloud Org Admin | 🟠 08 | The Keys to the Castle. This demands a firm grasp of roles and access; actions here impact the whole system. |
05 | ACP-620: Managing Jira Projects | 🟡 06 | The Project Lens. Hands-on experience is non-negotiable. The more you've lived as a Project Lead, the more intuitive this becomes. |
04 | ACP-220: Confluence Admin | 🟡 05 | The Hidden Power. Fewer moving parts than Jira, but it reveals "invisible" capabilities that most users never see. |
03 | ACA: Cloud Foundations | 🟢 03 | The Victory Lap. Fills in the strategic product gaps that high-level admin study often misses. |
02 | ACH: Loom Fundamentals | 🟢 02 | The Eye-Opener. Reframes Loom as a unique communication tool rather than just another video replacement. |
01 | ACH: Rovo Fundamentals | 🔵 01 | The Launchpad. A fantastic, free entry point for understanding AI prompting and the Rovo ecosystem. |
6. The Horizon: What’s Next for Brovo?
Reaching Atlassian Certified Administration Expert status was a significant goal, but in this ecosystem, the finish line is always moving. The 167-day sprint may be over, but the 150% commitment to learning continues. Here is what’s on the horizon:
|  |
- Brovo’s Final Form: No technical lead is complete without the proper gear. My next 3D design project is a bespoke Atlassian-themed shield for Brovo, the 300% scale mascot.
This journey has taught me that when I ignite professional goals with personal passions, the result is supercharged creativity.
I’ll see you at Team '26!
Appendix: The 167 Day Timeline
To provide a clear picture of the pace and sequence of this journey, here is the chronological breakdown of my path from the first "deep dive" to the final certification.
Date | Milestone / Exam | Achievement |
Nov 2025 | 🚩 The Start | Journey Commences: The "All Chips In" phase begins. |
Dec 2025 | ACP-520 | Cloud Org Admin: Securing the "Keys to the Castle". |
Jan 2026 | ACP-120 | Jira Admin for Cloud: Defeating the "Final Boss". |
Feb 2026 | ACP-620 | Managing Jira Projects: Validating the "Project Lens". |
Mar 2026 | ACP-220 | Confluence Admin: Mastering the Hidden Power. |
Mar 2026 | 🏆 EXPERT | DESIGNATION: Atlassian Certified Administration Expert. |
Apr 2026 | ACA / ACH | The Victory Lap: Cloud Foundations, Loom, and Rovo Fundamentals. |
Apr 2026 | ACP-420 | JSM Projects: Completing the "Post-Game Challenge". |
Apr 2026 | 🎖️ SPECIALIST | Double Designation: Agile DevOps & ITSM Specialist reached. |
Was this helpful?
Thanks!
Ben Spillane
2 comments