Technical Architect- Salesforce Devops

To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months to ensure you are not duplicating efforts. Job Category Customer Success Job Details About Salesforce Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce. ROLE OVERVIEW The DevOps Architect — Migration Hub is the strategic owner of the CI/CD, environment management and release governance framework that powers all migration wave delivery across the Hub. Sitting at the intersection of platform engineering and delivery operations, this role designs and governs the DevOps infrastructure that enables concurrent migration teams — across Marketing Cloud Next, Agentforce Revenue Management, ITSM and Tableau Next tracks — to deploy, test, validate and release Salesforce configuration, code and data changes at Hub velocity. Unlike the hands-on DevOps Engineer (who operates day-to-day pipelines within a single track), the DevOps Architect operates at the Hub level — defining branching strategy, environment topology, pipeline standards, test automation frameworks, deployment governance and cross-wave dependency management that apply consistently to every track team. This role is accountable for ensuring the Hub never becomes a bottleneck — that release pipelines are fast, reliable, auditable and capable of supporting multiple concurrent go-lives within the same programme window. The DevOps Architect is also responsible for the platform development tooling contribution model — governing how Apex, LWC, Flow and integration code built by track teams is developed, reviewed, tested and promoted through Hub environments to production. RESPONSIBILITIES: S • CI/CD Pipeline Architecture — Hub Standard : Design, build and own the Hub-wide CI/CD pipeline framework using Salesforce DX, GitHub Actions and Gearset/Copado — defining the standard pipeline stages (develop → validate → test → UAT → staging → production) that apply to every migration track, wave and release. • Environment Topology Design : Design and manage the Hub environment topology — defining the number, purpose and refresh cadence of Developer, CI, SIT, UAT, Staging and Production environments across all active migration waves, balancing environment costs with delivery velocity requirements. • Branching Strategy & Version Control Governance : Define and enforce the Hub-wide Git branching strategy — including branch naming conventions, merge policies, pull request standards, conflict resolution protocols and release tagging — ensuring all Salesforce DX source code, metadata and configuration is correctly version-controlled. • Scratch Org Strategy : Design the Hub's Salesforce DX scratch org usage model — defining scratch org definitions, feature flags, shape parameters and lifecycle policies that enable track teams to develop and test in isolated, reproducible environments at scale. • Deployment Governance & Release Management : Own the release management process for all migration wave deployments — defining change freeze windows, deployment sequencing, dependency maps, rollback procedures, approval gates and production deployment runbooks used across all concurrent waves. • Test Automation Framework : Design and implement the