Senior Site Reliability Engineer

Senior Site Reliability Engineer - AEM - Content Delivery Network

Toronto – 4 Days WFO

Salary: CA$133,200.00 yearly

Full-time

ABOUT THE ROLE

Own end-to-end monitoring of the controlled surface: CDN and edge configuration, DNS, certificates, cache and invalidation health, and every third‑party integration on the page – Search, Consent Management, Analytics, Personalization and AI services and many more to come.

• Build and run synthetic monitoring from outside the bank network, per template, per language, because internal-only monitoring cannot see the CDN, DNS and certificate failures this architecture is most exposed to.
• Run smoke testing of dependent interfaces on every change and maintain the automation packs that do it.
• Participate in the shared on-call rotation as the platform’s subject‑matter escalation, and lead incident management for customer-facing events.
• Own the vendor's escalation path: severity mapping between vendor and internal incident scales, named contacts, evidence capture, and holding the vendor to its commitment during an event.
• Handle a class of incident that does not exist on traditional platforms – content published but not visible, invalidation failure, and authoring‑source outages – and make those diagnosable by the service desk rather than by you.

2. Change and Release Reliability

• Design and operate change management for the platform where the Git repository is production: reconcile a merge-to-main deployment model with change control, so that every production change carries an approved record with stalling delivery.
• Own the release pipeline as a production control – branch protection, required checks, lint, performance, and secret‑screening gates – and the evidence that they are enforced.
• Own rollback: revert, republish and purge, rehearsed end to end with a measured recovery time and a named authority who can call it without convening a meeting.
• Treat content publishing as a routine process: hundreds of production changes made by content authors, needing approval evidence, attribution and retention trail.
• Represent the platform at change advisory board, and own the freeze calendar interaction and release notes.

3. Business Continuity and Resilience

• Own the recovery obligation. The vendor operates delivery resiliently, but customers restore their own content from source version history rather than vendor backups – so the content source, the Git repository and the CDN configuration are the recovery surface, each needing a tested restore.
• Hold CDN and edge configuration as code so that a lost or corrupted property is a redeploy rather than an outage with no runbook.
• Define RTO and RPO with the business against the application criticality tier, document the DR exercise plan, and execute the testing – including failure modes you can actually cause: certificate expiry, invalidation failure, WAF misconfiguration, content source unavailability, and repository compromise.
• Maintain the operational resilience evidence a regulator expects for a material third‑party technology arrangement, and keep the platform exit and portability plan current.

4. Reliability & Performance Engineering

• Set and defend service level objectives for both availability and page performance. Define Core Web Vitals thresholds per template, run them on an error budget, and report against them.
• Build the observability practice from the telemetry that exists; real user monitoring on the production domains, CDN access logs streamed to enterprise SIEM as the log source of record, and external synthetics. There is no origin server log – designing around that constraint is part of the job.
• Own third-party scripts and tag governance as a reliability control. Tags are the dominant cause of performance regressions and are added by teams outside engineering change control; you will define the approval route, measure each tag’s cost and enforce the budget.
• Own capacity and cost where they still exist: CDN egress, asset storage and processing, media delivery and any hosted APIs behind the page. Capacity planning here is a financial operations discipline, not a server-sized one.
• Publish the reliability and performance reporting that the business, risk and technology leadership use.

5. Compliance and Control Evidence

• Evidence controls on a platform the organization does not operate – which is harder than evidencing your own, and is where a meaningful share of the role’s effort sits.
• Own log ingestion into SIEM with the agreed retention, access recertification across the repository, admin console, content source and CDN, and the audit evidence pack.
• Support privacy, operational risks, control assessment and third‑p