Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Aderant

Cloud Operations Support Engineer

  • Seen live on Aderant's site yesterday
  • Mid level
Pay
Not stated
Location
Auckland, New Zealand
Open for
17+ days
First seen
Oct 18, 2026
Apply on Aderant's site (opens in a new tab)

Posting record

No flags

Open 17+ days

The posting's record, oldest first
  1. Aderant's site dates the posting
  2. Ghostless first sees this listing
  3. 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 Aderant, so its true age is longer.

Last checked Nov 3, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What 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

Aderant is a global industry leading software company providing comprehensive business management solutions for law firms and other professional services organizations with a mission to help them run a better business. We are motivated by a collective desire to drive the legal industry to the forefront of innovation. With over 2,500 clients around the world, including 95 of the top AmLaw 100 firms, we are changing the outside perception of the legal sphere; where there was once resistance to modernization, we are creating a culture that embraces new ideas and technology.

At Aderant, the “A” is more than just a letter. It is a representation of how we fulfill our foundational purpose, serving our clients. It embodies our core values and reminds us that to achieve success, every day must start with the “A”. We bring the “A” to life by fostering a culture of innovation, collaboration, and personal growth. We encourage our diverse teams to bring their whole selves to work – ideas, experience, and passion – to drive our mission forward.

Our people are our strength.

Cloud Operations Engineer (Intermediate)

We're hiring for a team responsible for the reliability of our AWS and Azure environments — running and improving operational processes, monitoring infrastructure, and leading incident response. At this level you'll own operational workstreams end to end: you'll not only execute runbooks but author and refine them, drive incidents to resolution, and reduce recurring toil through automation.

Required

  • 3+ years in an operations, SRE, production support, or NOC role, including hands-on experience leading (not just participating in) incident response in a production environment
  • Solid working experience operating in AWS and Azure — IAM, compute, networking, storage, and an understanding of cost and security trade-offs (not just "basics")
  • Proficient scripting in Bash and/or PowerShell, plus Python for automation, tooling, and integrating between systems
  • Hands-on experience building and tuning observability — dashboards, alerts, and SLO/SLI-based monitoring in at least one platform (CloudWatch, Azure Monitor, Grafana, Datadog, etc.), including reducing alert noise and false positives
  • Track record of authoring and improving runbooks/SOPs, not only following them — turning repeat incidents into documented, ideally automated, resolutions
  • Experience owning incidents through their full lifecycle: triage, coordination, stakeholder comms, resolution, and driving post-incident reviews / corrective actions
  • Comfortable in a ticketing system (Jira, ServiceNow, etc.), managing SLAs, and participating in an on-call rotation
  • Strong written and verbal communication — you'll lead incident comms, run handoffs, and mentor junior engineers

Nice to have

  • Infrastructure-as-code experience (Terraform, CloudFormation, Bicep/ARM)
  • Hands-on with CI/CD platforms (Jenkins, Azure DevOps, GitHub Actions) — building or maintaining pipelines, not just triggering them
  • Container / orchestration exposure (Docker, Kubernetes, ECS/AKS)
  • Git-based workflows for version-controlling scripts, IaC, and runbooks
  • Relevant certifications (AWS SysOps Administrator / Solutions Architect Associate, AZ-104, or equivalent)

Something wrong with this posting?