DevOps Manager

Rightsline is hiring a Dev Ops Manager, based in Toronto, to lead the team that owns our cloud platform, delivery pipelines, and production reliability across North America and Europe. You will manage and develop a team of five — a Senior Dev Ops Engineer, a Dev Ops Engineer, and two Senior Systems Engineers — and hold end-to-end accountability for the infrastructure our product runs on.

You will report to the Senior Dev Ops Architect and partner closely with Engineering, QA, Security and Compliance, and Support.

Rightsline runs a multi-region AWS platform: production in two regions serving customers in the US and the EU, twelve environments spanning developer sandbox through pre-production mirror to production, infrastructure defined in Terraform, and a templated CI/CD fleet that builds and deploys every component into each of them. The team owns our AWS accounts end to end, along with a mixed Linux and Windows server estate.

The team that runs this platform is deeply capable technically. Your mission is to pair that capability with the operational discipline of a mature platform organization: a named owner for every system and environment, infrastructure changes that land predictably and completely across all the places they belong, documentation current enough to be trusted during an incident, and a team that holds itself accountable for follow-through.

You will be accountable for the platform as a product that the rest of the company depends on — its reliability, its cost, its security posture, and how quickly engineers can get work safely into production. Success is measured by production availability and incident recovery in both regions; by environment changes that complete the first time, with a record of what changed and why;

by runbooks, diagrams, and environment inventories that are current; by disaster recovery and audit evidence produced as routine output rather than as a scramble; and by a team where ownership is unambiguous, people are growing, and commitments are met.

• Manage, coach, and develop a team of four infrastructure engineers, including senior individual contributors — people with deep expertise you will lead through judgment and clarity rather than positional authority.

• Establish unambiguous ownership: every system, environment, pipeline, and recurring operational duty has a named owner and a documented backup.

• Run the performance cycle — goals, regular one-on-ones, written feedback, and development plans calibrated against our engineering level framework — and address both strong performance and gaps directly and fairly.

• Hold the team to its commitments, and build the visibility that makes commitments legible: a single prioritized queue of work, current ticket hygiene, and clear closure on action items.

• Recruit, onboard, and retain, building enough bench depth that no system depends on one person being available.

• Own the change management process for infrastructure and environments end to end: proposal, peer review, scheduled execution, verification, and a durable record of what changed and why.

• Define and hold the line on what “done” means for environment work — the change applied consistently across every environment and region it belongs in, code and state in agreement, monitoring updated, documentation updated, and the ticket closed.

• Drive infrastructure work through version control and code review rather than console changes, and systematically close configuration drift between environments and regions.

• Make documentation a deliverable: architecture diagrams, runbooks, escalation paths, and environment inventories that an on-call engineer can rely on at three…