Tata Consultancy Services (TCS) is an equal prospect employer, and embraces diversity in race, nationality, ethnicity, gender, age, physical ability, neurodiversity, and sexual orientation, to create a workforce that reflects the societies we operate in. Our continued commitment to Culture and Diversity is reflected in our people stories across our workforce and implemented through equitable workplace policies and processes.
TCS is an IT services, consulting, and business solutions organization that has been partnering with many of the world’s largest businesses in their transformation journeys for over 55 years. Its consulting-led, cognitive-powered portfolio of business, technology, and engineering services and solutions is delivered through its unique Location Independent Agile™ delivery model, recognized as a benchmark of excellence in software development. TCS' proactive stance on climate change and award-winning work with communities across the world have earned it a place in leading sustainability indices such as the MSCI Global Sustainability Index and the FTSE4Good Emerging Index.
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.
Participate in the shared on-call rotation as the platform’s subject-matter escalation, and lead incident management for customer-facing eventsOwn the vendor's escalation path into Adobe: severity mapping between Adobe 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 makes those diagnosable by the service desk rather than by you.
Design and operate change management for the platform where the Git repository is production: reconcile a merge-to-main deployment model with internal change control, so that every production change carries an approved record with stalling delivery.
Owns 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 meetingTreat content publishing as a routine process: hundreds of production changes made by content authors, needing approval evidence, attribution and retention trailRepresent the platform at change advisory board, and own the freeze calendar interaction and release notesBusiness Continuity and ResilienceOwn the recovery obligation that sits internally. Adobe 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 TCS recovery surface,



each needs 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 runbookDefine 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.
Reliability & Performance EngineeringSet 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.
Tags are the dominant cause of performance regressions and are added by teams outside engineering change control; CDN egress, asset storage and processing, media delivery and any TCS-hosted APIs behind the page. Publish the reliability and performance reporting that the business, risk and technology leadership use.
Compliance and Control EvidenceEvidence controls on a platform TCS does not operate – which is harder than evidencing your own, and is where a meaningful share of the role’s effort sitsOwn log ingestion into SIEM with the agreed retention, access recertification across the repository, Adobe Admin Console, content source and CDN, and the audit evidence packSupport privacy, operational risks, control assessment and third-party risk processes with operational evidence and maintain alignment to regulatory expectations for technology, cyber and third

📌 Site Reliability Engineering I (Canada)
🏢 TATA Consultancy Services
📍 Canada