Atlassian Journey

[#1]

From Data Center to What’s Next? A Reflection from an Atlassian Engineer

I never imagined that one line in a job description would make me question my career "Atlassian Cloud experience required". 

Like many engineers, I’ve spent years working with Jira, Confluence and Bitbucket Data Center. I’ve designed and supported enterprise platforms, implemented governance frameworks, introduced security guardrails, configured SSO, managed risk and controls, addressed vulnerabilities, performed upgrades, and helped organisations keep business-critical systems running.

But recently, as part of career transition, organisation structure changes, while applying for new roles, I’ve noticed a clear trend. Almost every opportunity asks for Atlassian Cloud experience. Not as a nice-to-have, but as a baseline expectation.

It made me stop and think.

Has my experience suddenly become less valuable?

Or am I simply telling the wrong story?

More Than a Jira/Confluence Administrator

One thing I’ve realised is that many of us unintentionally define ourselves by the products we support.

We say we’re Jira administrators or Confluence administrators.

But when I look back over my career, that’s only a small part of the story.

The real work has never been about clicking through administration screens.

It’s been about solving business problems.

It’s about designing platforms that thousands of people rely on every day. It’s about protecting critical systems through governance and security. It’s about making sure the right people have the right access, ensuring upgrades don’t disrupt the business, implementing controls that satisfy auditors, automating repetitive tasks, and working with stakeholders across security, infrastructure and software engineering teams.

Those aren’t just Atlassian skills. They’re engineering skills.

The Platform May Change, but the Principles Don’t

Cloud is undoubtedly the future for many organisations.

The way we manage Atlassian products is changing, and there’s no point pretending otherwise.

Infrastructure management is reducing.

Managed services are replacing manual administration.

Automation is becoming easier.

Artificial intelligence is beginning to change how administrators work.

That’s not something to fear.

It’s something to prepare for.

The fundamentals remain the same:

• Secure the platform.
• Govern access.
• Enable collaboration.
• Automate repetitive work.
• Reduce operational risk.
• Support the people who depend on the platform.

Whether those responsibilities exist in a Data Center deployment or a Cloud service, they’re still the responsibilities of a good engineer.

The Experience Gap

There’s another challenge that I suspect many experienced professionals share.

How do you gain commercial Cloud experience when most organisations only want to hire people who already have it?

It’s a familiar cycle.

No experience means fewer opportunities.

Fewer opportunities mean less experience.

The answer probably isn’t to wait for someone to give us permission.

It’s to become curious.

Set up a Cloud environment.

Learn Atlassian Administration in Cloud.

Explore Automation for Jira.

Experiment with APIs.

Understand the differences between Data Center and Cloud.

Read migration guides.

Build things.

Document what you learn.

None of this replaces commercial experience, but it demonstrates something just as important: the initiative.

Technology has always rewarded people who are willing to learn before they’re asked to.

Staying Curious Matters More Than Staying Comfortable

One lesson I’ve learned throughout my career is that technology never stands still.

Years ago we were discussing server deployments.

Then came Data Center.

Now we’re talking about Cloud, platform engineering, AI-assisted administration and intelligent automation.

Five years from now, the conversation will probably be different again.

The engineers who thrive won’t necessarily be the ones who know today’s technology the best.

They’ll be the ones who never stop learning.

That’s the mindset I’m choosing to adopt.

Not because I have to.

Because it’s part of being an engineer.

Looking Beyond the Atlassian Ecosystem

Another thought I’ve been reflecting on is whether we should define our careers around a single vendor at all.

The skills many of us have developed—governance, application security, identity and access management, integrations, automation, risk management and stakeholder communication—are valuable well beyond the Atlassian ecosystem.

Perhaps the future isn’t simply becoming an Atlassian Cloud Engineer.

Perhaps it’s becoming a Platform Engineer.

Or moving into Application Security.

Or Identity and Access Management.

Or DevSecOps.

Or Enterprise Architecture.

Technology changes.

The ability to solve problems doesn’t.

Next Chapter

I’m still on this journey. Looking for that silver lining. 

I don’t have years of commercial Atlassian Cloud experience.

What I do have is years of experience building secure, resilient and well-governed enterprise platforms.

I’m investing time in understanding Cloud, broadening my technical skills, exploring automation, learning more about AI, and keeping an open mind about where my career could go next.

If Data Center has taught me anything, it’s that no technology lasts forever.

What lasts is the willingness to learn, adapt and stay curious.

I’d Love to Hear Your Thoughts

If you’re an Atlassian professional, I’m genuinely interested in hearing how you’re approaching the next stage of your career.

Expanding into platform engineering?

Moving towards security or DevSecOps?

Or are you finding opportunities beyond the Atlassian ecosystem?

I don’t think there’s a single right answer.

But I do think this is a conversation worth having.

Because while products evolve, the engineering community that supports them evolves too.

With Love 

Viswa