Remote Lead DevOps Engineer (Toronto)

Remote Lead DevOps Engineer (Toronto)

03 Oct
|
Rightsline
|
Toronto

03 Oct

Rightsline

Toronto

Rightsline is hiring a DevOps 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 DevOps Engineer, a DevOps 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 DevOps 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. by runbooks, diagrams, and environment inventories that are current; 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. 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 in the morning. Own incident practice — on-call rotation, severity definitions, blameless postmortems,



and remediation items that are tracked to closure. Own our AWS accounts outright — account structure and organization, IAM and access boundaries, service quotas, networking, billing and tagging, and the guardrails that keep each account consistent with the next.

Own everything running in those accounts across both regions — containerized services, load balancing, relational databases, search, messaging, and serverless components — including capacity, performance, patching, and security posture.

Own the server estate on both Linux and Windows: build standards, configuration management, patching cadence, hardening, and lifecycle, so neither platform becomes the one nobody wants to touch.

Own infrastructure as code in Terraform: module design, environment composition, state management, and the review standards that keep it maintainable as the fleet grows. Own the CI/CD estate — a templated pipeline-per-component-per-environment fleet across twelve environments and two regions — along with the release promotion model and production approval gates. Own observability and log management so that alerts are actionable, noise is low, and the data needed to investigate an issue is still there when the question gets asked.

Partner with Engineering to reduce deployment risk and shorten lead time to production, and with QA on environment availability, parity, and refresh. Own availability and performance objectives for production in both regions, and the monitoring that demonstrates they are being met. Partner with Security on hardening, secrets management, remediation timelines, and audit readiness, and keep our EU data residency commitments intact.

Act as the escalation point for infrastructure issues affecting customers, communicating status credibly to engineering leadership and, when needed, to customers. Coordinate effectively with engineering colleagues in the United States and India, including planning work and releases across time zones. 7+ years in DevOps, SRE, or infrastructure engineering, including 2+ years directly managing a DevOps or infrastructure team, with hiring, performance, and development responsibility.



Management experience specifically in this space is required — leading infrastructure engineers is a different job from leading application developers. ~ Experience leading senior engineers and architects — specialists who know their domains better than you do — and a track record of earning their trust. ~ A demonstrated record of introducing process rigor to a technically strong team without slowing it down: change management, documentation standards, and on-call and incident practice that the team genuinely adopted and sustained. ~ Deep hands-on AWS experience, including account-level ownership: organizations and account structure, IAM, networking and load balancing, container orchestration, relational databases, and multi-region architecture. ~ Working fluency across both Linux and Windows Server — you can hold a credible technical conversation about either, and you understand what it takes to keep a mixed estate patched, hardened, and consistent. ~ Ownership of production CI/CD (AWS CodePipeline and CodeBuild, Spinnaker, GitHub Actions, or comparable), including release promotion and approval gates. ~ Experience operating under an audit framework such as SOC 2, PCI DSS, or ISO 27001, and owning disaster recovery testing rather than just participating in it. ~ Bachelor's degree in Computer Science or a related field, or equivalent practical experience.

Multi-tenant SaaS at scale, particularly with EU data residency requirements. NET application hosting. Windows-side depth — Active Directory, IIS, Group Policy — alongside Linux administration. Kubernetes, and infrastructure-code quality tooling such as Terratest, Checkov, or policy-as-code.

AWS certification (Solutions Architect Professional or DevOps Engineer Professional).

Experience integrating AI-assisted development tooling into delivery pipelines and the guardrails that requires. Based in Toronto, Canada, in a hybrid arrangement — our Toronto office is available to you, with the flexibility to work from home. Regular overlap with engineering colleagues in the United States and India.

Participation in escalation coverage, and occasional planned off-hours work for releases, migrations, and disaster recovery testing. That means staying flexible, letting go of what isn't working, and treating uncertainty as chance rather than obstacle. Your customers count on you.

We do not discriminate against any employee or applicant for employment because of race, color, sex, age, national origin, religion, sexual orientation, disability, gender identity and/or expression.

📌 Remote Lead DevOps Engineer (Toronto)
🏢 Rightsline
📍 Toronto

Reply to this offer

Impress this employer describing Your skills and abilities, fill out the form below and leave Your personal touch in the presentation letter.

Subscribe to this job alert:

Get the latest job offers by email for: remote lead devops engineer (toronto) / toronto

Subscribe to this job alert:

Get the latest job offers by email for: remote lead devops engineer (toronto) / toronto