You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Early Window: Closes in
Company hidden

Senior Atlassian Cloud Engineer

  • Remote
  • 6+ years

Salary

Not stated

Similar roles pay €65K - 90K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The team builds and improves the platforms employees use to collaborate and get support, with Jira Service Management (JSM) as the main focus.

You will own solutions that make service delivery simpler, automate manual work, and improve how employees experience support.

The role covers Jira Cloud and Confluence as well, with a focus on security, reliability, and governance across the Atlassian setup.

You will work with Engineering, Corporate IT, Security, and other stakeholders to turn complicated needs into maintainable solutions, from first discovery through rollout and ongoing operation.

The company publishes its Engineering Career Framework openly, describing expectations at each career level.

Responsibilities

  • Design, build, and keep improving JSM features that make employee support quicker and more useful.
  • Build scalable service workflows, portals, queues, SLAs, and automation covering incident, request, problem, and change management.
  • Create secure, maintainable integrations between Atlassian Cloud and enterprise systems using APIs, webhooks, and scripts.
  • Improve employee self-service through Confluence knowledge bases, Rovo, and AI-driven support tools.
  • Develop JSM Assets and configuration management so data is cleaner, assets are easier to see, and service delivery improves.
  • Tighten governance, access control, security, and reliability across Jira Cloud, JSM, and Confluence, while cutting configuration complexity and technical debt.
  • Work with teams to define requirements, weigh technical trade-offs, and deliver projects through rollout and support.
  • Write reusable configuration patterns, documentation, and runbooks, and use operational metrics and employee feedback to decide what to improve.
  • Take on on-call duty occasionally when bugs, outages, or other operational issues need attention, to keep the experience stable and high quality for customers.

Requirements

  • 9+ years of relevant experience in enterprise Atlassian platform administration, engineering, or similar technical work.
  • Deep knowledge of Jira Cloud and Jira Service Management, including configuration, permissions, governance, and troubleshooting.
  • Proven experience designing and implementing JSM workflows, service portals, queues, SLAs, and automation.
  • Experience building and maintaining integrations with REST APIs, webhooks, and scripting.
  • Solid understanding of SaaS security, access management, and operational reliability.
  • A record of solving unclear technical problems, making sound design choices, and owning complex projects through to delivery on your own.
  • Strong written and spoken communication, with the ability to document technical solutions and work with both technical and non-technical colleagues.
  • Optional: experience leading large JSM implementations or service management transformation programs.
  • Optional: experience with JSM Assets and configuration management databases (CMDBs).
  • Optional: familiarity with ServiceNow or similar enterprise IT service management platforms.
  • Optional: experience with Rovo, AI agents, or AI-powered service workflows.
  • Optional: experience with Python, Groovy, JavaScript, or ScriptRunner.
  • Optional: experience connecting Atlassian products with Slack, identity providers, endpoint management tools, or monitoring platforms.
  • Optional: experience building Confluence knowledge bases and linking them into employee self-service.
  • The company's durable skills framework, built around AI fluency as a way to strengthen human judgment, covers four areas: awareness (understanding yourself and others), judgment (evaluating information and deciding in complex situations), adaptability (learning and staying effective through change), and connection (communicating, collaborating, and building trust).
  • A blog post from the Chief People Officer, Melanie Rosenwasser, explains why these skills matter and what the data shows about thriving through change.

Conditions

Location: Poland.

Pay range: 255 000 zł to 345 000 zł PLN.

Where you’d work

Fully remote

You can work from

  • Europe
  • Poland

About the company

Company hidden

  • Industry: SaaS

Your chances

Still hiring, not crowded yet, and you'd be among the first.

  • 15 checks run
  • 5 good signs
  • 0 red flags

Still hiring?

10 checks

Actively hiring

In its favour2

  • Still on the company's own careers site, checked 1 h agoModerate evidence
  • Found in the last 48 hours, before the big job boardsModerate evidence

How crowded?

5 checks

Low

In its favour3

  • In its Early Window: not on the big job boards yetStrong evidence
  • Asks for 9+ years: a narrow poolModerate evidence
  • Remote within Poland onlySlight evidence

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details11 facts · Role, Location, Compensation, Company
Tech stack
  • Python
  • JavaScript
Seniority
Senior
Industry
SaaS
Specialty
DevOps
Region
Europe
Pay period
Annual
Show 5 more factsShow less

Role

Category
DevOps & Infrastructure
Specialty
DevOps
Seniority
Senior
Experience
9+ years
Tech stack
  • Python
  • JavaScript

Location

Work model
Remote
Region
Europe
Remote from
  • Europe

Compensation

Salary
Salary by agreement
Pay period
Annual

Company

Industry
SaaS

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason