Community resources
Community resources
Community resources
The Atlassian Friend #1: A Marathon Through the Atlassian Ecosystem
When I started working with the Atlassian ecosystem back in 2011, I never imagined I’d be writing an article like this.
And if someone had told me back then that one day I’d earn every Atlassian certification available, I probably would have smiled and said they were joking.
Not because it sounded impossible.
Simply because it was never my goal.
My goal was always much simpler.
I just wanted to learn.
I’ve always been curious by nature. Every new product, every new feature, every new release felt like another opportunity to understand the ecosystem a little better.
Over the years, I started earning certifications in different areas. Some were directly related to the projects I was working on. Others came from pure curiosity. They gave me an excuse to explore parts of the platform that I probably wouldn’t have touched otherwise.
Without really planning it, one certification led to another.
Then another.
And another.
One day I stopped and realized something.
I had almost completed the entire journey without ever setting out to do it.
It was never a sprint.
It was never a personal challenge.
Looking back, it became a marathon.
More importantly, it became part of how I learn.
An Ecosystem That Never Stops Evolving
One of the things I enjoy most about working with Atlassian is that the learning never really ends.
When I started, most of my work revolved around Jira and Confluence running on Server. Since then, we’ve seen Cloud reshape the platform, Forge create entirely new possibilities, Assets become a key part of Enterprise Service Management, and more recently, tools like Loom, Rovo, and Atlassian Intelligence continue to change the way we work.
Every few months there’s something new to discover.
Sometimes it’s a feature.
Sometimes it’s a completely different way of solving a problem.
That’s what has kept me interested for more than fifteen years.
There has always been another chapter to learn.
Why I Kept Getting Certified
People occasionally ask me why I kept pursuing certifications.
The answer is actually very simple.
Because they helped me learn.
Every certification gave me a reason to go back to the documentation, revisit concepts I hadn’t looked at for years, discover capabilities I’d never used before, and spend time learning parts of the ecosystem that weren’t part of my everyday work.
Looking back, I don’t think passing the exam was ever the most important part.
The real value was everything I learned while preparing for it.
The certification was simply the outcome.
The learning was always the goal.
Understanding the Ecosystem Matters More Than Knowing the Products
If these years have taught me anything, it’s this.
Knowing a product is valuable.
Experience is invaluable.
But understanding the ecosystem is what really changes the way you solve problems.
Early in my career, I tended to think in terms of products.
“Should we use Jira?”
“Can Confluence do this?”
“What app do we need?”
Over time, my perspective changed.
Today, I try to start somewhere completely different.
I start with the problem.
Only then do I think about the technology.
Because once you understand the problem, choosing the right tool becomes much easier.
That’s where understanding the ecosystem makes all the difference.
It’s not about knowing every feature.
It’s about understanding how the different pieces fit together, when each one makes sense, and how they can work together to create something better than any individual product could on its own.
Looking back, I think that’s probably the biggest lesson all those certifications taught me.
They didn’t just help me learn individual technologies.
They helped me understand how those technologies connect.
Curiosity Is a Professional Skill
There’s something else I’ve come to appreciate over the years.
We spend a lot of time talking about technical skills, certifications, and experience.
We don’t talk nearly as much about curiosity.
I think that’s a mistake.
In an ecosystem like Atlassian, curiosity is one of the most valuable skills you can have.
It’s what makes you open the documentation just because you noticed a new feature.
It’s what makes you install something in a test environment to see how it works.
It’s what makes you spend an evening learning something you don’t need today, knowing there’s a good chance you’ll need it tomorrow.
Nobody tells you to do those things.
You do them because you genuinely want to understand.
Looking back, curiosity has probably had a bigger impact on my career than any certification ever could.
From Knowing Products to Understanding a Platform
When I started my career, I thought success was about knowing the products.
The more I learned, the more I realized that wasn’t enough.
Today, I see the Atlassian ecosystem as a platform rather than a collection of individual tools.
Jira, Confluence, Jira Service Management, Assets, Forge, Automation, Rovo… they’re all important.
But the real value isn’t in knowing each one separately.
It’s in understanding how they work together.
That’s what allows you to design better solutions.
That’s what helps you make better decisions.
And that’s what turns technology into something that creates real value for the people who use it.
For me, that’s been one of the biggest lessons of this journey.
Learning Also Means Sharing
At some point, I realized that learning was only part of the journey.
The other part was sharing what I’d learned.
The Atlassian Community has been part of my professional life almost from the beginning.
For years, I was mostly a reader.
I’d spend time reading discussions, following conversations, and learning from people who had already solved problems I hadn’t even faced yet.
Looking back, I honestly think I learned as much from the Community as I did from documentation or certification guides.
People shared ideas.
They shared mistakes.
They shared solutions.
And without realizing it, they were helping thousands of people they’d never meet.
Including me.
Eventually, I felt it was time to give something back.
In 2019, I applied to become an Atlassian Community Leader, a program that was later renamed Atlassian Champion.
I never saw it as something to collect or achieve.
To me, it simply meant becoming more involved in a community that had already given me so much.
Like many people, life interrupted that journey for a while.
The pandemic and some personal circumstances meant I stepped back from the Community for some time.
But the interest never disappeared.
In 2023, I became active again.
And in 2025, after talking with my Atlassian Community Manager, we decided to focus our efforts on supporting the Spanish-speaking community by organizing online events.
I’m genuinely excited about that.
Not because it’s about me.
Because it’s about creating more opportunities for people to learn from one another in their own language.
If this profession has taught me anything, it’s that knowledge grows when it’s shared.
That’s probably the biggest lesson the Community has given me.
Someone helped me years ago without even knowing it.
If I can do the same for someone else today, then I’m giving something back.
And that feels pretty special.
So… Are Certifications Worth It?
My answer is yes.
But probably not for the reason most people expect.
A certification doesn’t replace experience.
It doesn’t automatically make you a better administrator, consultant, or architect.
Real experience comes from working with people, understanding businesses, making difficult decisions, and learning from projects that don’t always go as planned.
Certifications offer something different.
They give you a reason to keep learning.
They encourage you to explore areas you might never look at otherwise.
And in an ecosystem that evolves as quickly as Atlassian, that’s incredibly valuable.
If your only goal is to pass an exam, you’ll probably forget most of what you studied a few months later.
If your goal is to understand the ecosystem a little better every time you learn something new, then certifications become much more than a badge.
They become part of your professional growth.
Looking Back
People sometimes ask me what it feels like to have every Atlassian certification.
Honestly?
That’s not what I think about.
When I look back, I don’t see a collection of badges.
I remember the evenings spent reading documentation.
The weekends exploring products I’d never used before.
The conversations with colleagues.
The discussions in the Community.
The projects that forced me to think differently.
The mistakes that taught me lessons no certification ever could.
That’s what stays with me.
Earning every certification was never really the destination.
It was simply the result of years spent doing something I genuinely enjoy.
Learning.
The Journey Continues
If there’s one thing I’ve learned after more than fifteen years working with Atlassian, it’s that there is no finish line.
The ecosystem will continue to evolve.
New products will appear.
Existing ones will change.
New certifications will come.
And that’s exactly how it should be.
Because that’s what keeps all of us learning.
If someone asked me today for a single piece of advice, it wouldn’t be:
“Go and get certified.”
It would be something much simpler.
Stay curious.
Understand the problem before choosing the technology.
Learn how the ecosystem fits together, not just how each product works on its own.
And whenever you learn something useful…
Share it.
Someone you’ve never met might solve a problem because you decided to write a post, answer a question, or simply share your experience.
Just like someone once did for you.
That’s probably the most valuable lesson this journey has taught me.
Certifications taught me technologies.
Understanding the Atlassian ecosystem taught me how those technologies fit together.
The Community taught me why sharing knowledge matters.
And if there’s one thought I’d like to leave you with, it’s this.
Never stop learning.
Because no matter how much experience you have, there’s always something new waiting to be discovered.
And when you can, help someone else discover it too.
Antonio Ferruz
The Atlassian Friend
Was this helpful?
Thanks!
Antonio Ferruz
5 comments