Adobe Site Reliability Engineer - Content Delivery Network

Astra-North Infoteck Inc.

Toronto

On-site

CAD 130,000 - 190,000

Full time

14 days+

A complete application in a minute

Tailored resume and cover letter, ready to send.

Get past ATS filters

Job summary

Astra-North Infoteck Inc. is looking for a Senior Site Reliability Engineer to own end-to-end CDN performance, monitoring, and incident management for our content delivery network.

You will design robust release controls, runbooks, and DR exercises to ensure platform resilience. You will collaborate with cross-functional teams to maintain high availability, optimize performance, and implement observability across real user and synthetic monitoring.

Qualifications

  • Substantial hands-on experience operating a high-traffic public website behind an enterprise CDN.
  • Depth in CDN configuration – origin and cache behaviour, invalidation, edge logic, TLS and DNS.
  • Experience with web application firewall tuning for production-like traffic.
  • Strong observability practice: SLOs, error budgets, logs, RUM and synthetic monitoring.

Responsibilities

  • Own end-to-end monitoring of CDN surfaces, DNS, certificates, cache health and third-party integrations.
  • Design and operate change management and release pipelines with evidence and controls.
  • Lead incident management for customer-facing events and vendor escalations.
  • Develop and maintain an automated disaster recovery and recovery testing program.
  • Publish reliability and performance reports for business and technology leadership.

Skills

CDN configuration
Observability
Incident command
SRE/DevOps
CI/CD
Release engineering
Web performance
TLS/DNS
Vendor management

Tools

Akamai
Cloudflare
Git-based deployments
SIEM

Job description

Adobe Site Reliability Engineer - Content Delivery Network

Senior Site Reliability Engineer - AEM - Content Delivery Network

Toronto- 4 Days WFO

ABOUT THE ROLE
  • Own end-to-end monitoring of the controlled surface: CDNand edge configuration, DNS, certificates, cache and invalidation health, andevery 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 banknetwork, per template, per language, because internal-only monitoring cannotsee the CDN, DNS and certificate failures this architecture is most exposed to.
  • Run smoke testing of dependent interfaces on every changeand maintain the automation packs that do it.
  • Participate in the shared on-call rotation as theplatform’s subject-matter escalation, and lead incident management forcustomer-facing events.
  • Own the vendor's escalation path: severity mapping betweenvendor and internal incident scales, named contacts, evidence capture, andholding the vendor to its commitment during an event.
  • Handle a class of incident that does not exist ontraditional platforms – content published but not visible, invalidationfailure, and authoring-source outages – and make those diagnosable by theservice desk rather than by you.
2. Change and Release Reliability
  • Design and operate change management for the platformwhere the Git repository is production: reconcile a merge-to-main deploymentmodel with change control, so that every production change carries an approvedrecord with stalling delivery.
  • Own the release pipeline as a production control – branchprotection, required checks, lint, performance, and secret-screening gates –and the evidence that they are enforced.
  • Own rollback: revert, republish and purge, rehearsed endto end with a measured recovery time and a named authority who can call itwithout convening a meeting.
  • Treat content publishing as a routine process: hundreds ofproduction changes made by content authors, needing approval evidence,attribution and retention trail.
  • Represent the platform at change advisory board, and ownthe freeze calendar interaction and release notes.
3. Business Continuity and Resilience
  • Own the recovery obligation. The vendor operates deliveryresiliently, but customers restore their own content from source versionhistory rather than vendor backups – so the content source, the Git repositoryand the CDN configuration are the recovery surface, each needing a testedrestore.
  • Hold CDN and edge configuration as code so that a lost orcorrupted property is a redeploy rather than an outage with no runbook.
  • Define RTO and RPO with the business against theapplication criticality tier, document the DR exercise plan, and execute thetesting – including failure modes you can actually cause: certificate expiry,invalidation failure, WAF misconfiguration, content source unavailability, andrepository compromise.
  • Maintain the operational resilience evidence a regulatorexpects for a material third-party technology arrangement, and keep theplatform exit and portability plan current.
4. Reliability & Performance Engineering
  • Set and defend service level objectives for bothavailability and page performance. Define Core Web Vitals thresholds pertemplate, run them on an error budget, and report against them.
  • Build the observability practice from the telemetry thatexists; real user monitoring on the production domains, CDN access logsstreamed to enterprise SIEM as the log source of record, and externalsynthetics. There is no origin server log – designing around that constraint ispart of the job.
  • Own third-party scripts and tag governance as areliability control. Tags are the dominant cause of performance regressionsandae are added by teams outside engineering change control; you will define theapproval 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 thepage. Capacity planning here is a financial operations discipline, not aserver-sized one.
  • Publish the reliability and performance reporting that thebusiness, risk and technology leadership use.
5. Compliance and Control Evidence
  • Evidence controls on a platform the organization does notoperate – which is harder than evidencing your own, and is where a meaningfulshare of the role’s effort sits.
  • Own log ingestion into SIEM with the agreed retention,access recertification across the repository, admin console, content source andCDN, and the audit evidence pack.
  • Support privacy, operational risks, control assessment andthird-party risk processes with operational evidence and maintain alignment toregulatory expectations for technology, cyber and third-party risks.
  • Keep the configuration management database, support modeland assignment groups accurate as the platform estate grows.
WHAT WILL YOU DO?

This is a build-then-run role. Roughly half of the firstyear is establishing a reliability practice that does not exist yet.

  • The observability stack: Real User Monitoring, Core WebVitals dashboards and alerting, CDN log ingestion, and external synthetics.
  • CDN and Edge configuration as Code, with a tested restore.
  • The operations runbook, incident playbook, operationallevel agreement and vendor escalation matrix.
  • The change model that reconciles Git-based deployments andcontinuous content publishing with change controls.
  • The first disaster recovery exercise and the firstrehearsed, measured rollback.
  • Service level objectives agreed with the business, and thereporting that holds the platform to them.
WHAT DO YOU NEED TO SUCCEED?
Must have
  • Substantial hands-on experience operating a high-trafficpublic website behind an enterprise content delivery network. Depth in CDNconfiguration – origin and cache behaviour, invalidation, edge logic, TLS andDNS – is the single most important qualification. Akamai and Cloudflareexperience is an advantage.
  • Practical web application firewall experience, includingtuning false positives against production-like traffic before enforcement, andbot management that protects the site without blocking the crawlers you need.
  • A real observability practice: defining service levelobjectives and error budgets, and building monitoring from log, real-user andsynthetic sources rather than from an agent on a server.
  • Web performance engineering – Core Web Vitals, load andrendering behaviour, and the ability to read a waterfall and attribute aregression to a specific script.
  • Git-based release engineering and CI/CD as a productioncontrol, including infrastructure and configuration as code.
  • Incident command on customer-facing services, and thediscipline to produce evidence during an event, not after it.
  • Working effectively in a regulated environment – changecontrol, audit evidence, access management and third-party risk – withouttreating it as an obstacle.
Nice-to-have
  • Experience operating a vendor-run or SaaS-deliveredplatform, where reliability means instrumenting, escalating and holding asupplier accountable rather than fixing the tier yourself.
  • Adobe Experience Manager exposure, particularly EdgeDelivery Services and Assets as a Cloud Service.
  • Financial services or another regulated sector.
  • Bilingual delivery – operating a site that must meet thesame standard in English and French.
  • Accessibility and Search Engine Optimization literacysufficient to recognize when a reliability decision creates a compliance ordiscoverability problem.
Get your free, confidential resume review.

or drag and drop your file here.

Similar jobs

Similar jobs worth comparing

Adobe Site Reliability Engineer - Content Delivery Network
Adobe Site Reliability Engineer - Content Delivery Network

Astra-North Infoteck Inc. • Toronto

On-site
CAD 120,000 - 180,000
Adobe Site Reliability Engineer
Adobe Site Reliability Engineer

Tata Consultancy Services Limited • Toronto

On-site
CAD 120,000 - 180,000
Senior Site Reliability Engineer – Adobe Cloud & Edge Delivery
Senior Site Reliability Engineer – Adobe Cloud & Edge Delivery

n2psystems • Toronto

Hybrid
CAD 120,000 - 160,000
Senior Customer Engineer - Toronto Canada
Senior Customer Engineer - Toronto Canada

Cloudflare, Inc. • Toronto

Hybrid
CAD 130,000 - 190,000
Senior Site Reliability Engineer
Senior Site Reliability Engineer

Compunnel Inc. • Montreal

On-site
CAD 100,000 - 130,000
Senior DevSecOps & Cloud Security Engineer (PL7326)
Senior DevSecOps & Cloud Security Engineer (PL7326)

Paralucent • Toronto

On-site
CAD 130,000 - 170,000
Forward Deployment Engineer
Forward Deployment Engineer

Urban Ridge Supplies • Mississauga

On-site
CAD 140,000 - 185,000
Senior Observability Engineer
Senior Observability Engineer

Astra-North Infoteck Inc. • Montreal

Hybrid
CAD 90,000 - 130,000
Service Reliability Engineer
Service Reliability Engineer

Deliverect • Toronto

On-site
CAD 90,000 - 130,000
RQ00831 - DevOPS/Cloud Engineer - Senior
RQ00831 - DevOPS/Cloud Engineer - Senior

Maarut • Toronto

On-site
CAD 120,000 - 150,000