Posting record
Open 12+ days
- Phizenix's site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Phizenix, so its true age is longer.
Last checked Nov 4, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat the posting discloses
Not stated: Pay, real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Some employers add pay only on their own site. Check the original posting before you rule it out.
Skills mentioned
About the role
We are hiring an Atlassian Cloud Migration Engineer to help a client move Jira and Confluence from Server/Data Center to Atlassian Cloud. You will lead key workstreams and remediate the client's ScriptRunner scripts for Cloud.
What you'll do
Plan and run migrations using JCMA and CCMA, from test runs through cutover.
- Inventory ScriptRunner scripts, then retire them, replace them with Jira Automation, or rewrite them for ScriptRunner for Cloud.
- Work directly with client stakeholders on UAT, cutover and handover.
What you need
- A key role on multiple Atlassian Cloud migrations.
- Advanced, hands-on ScriptRunner for Cloud remediation experience.
- Strong Groovy scripting and Jira administration skills.
- Clear client-facing communication.
Nice to have: Jira Automation, Forge, JSM migrations and Atlassian certifications such as ACP-120.
Something wrong with this posting?