18 Nov
|
Astra North Infoteck
|
Winnipeg
18 Nov
Astra North Infoteck
Winnipeg
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
📌 Adobe Site Reliability Engineer (Winnipeg)
🏢 Astra North Infoteck
📍 Winnipeg