Technical Architect- Salesforce Devops

Job description

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 Hub-wide automated test suite — including Apex test class standards, code coverage requirements, UI automation (LWC Jest, Selenium), data validation scripts and post-deployment smoke tests — integrated into every CI/CD pipeline stage. Static Code Analysis & Quality Gates: Implement and maintain static code analysis tooling (PMD, Salesforce Code Analyser, ESLint) as mandatory quality gates within the Hub pipeline — enforcing Apex best practices, Governor Limit awareness, LWC standards and security vulnerability detection before any code progresses to UAT. Multi-Org & Multi-Track Pipeline Management: Manage the complexity of concurrent multi-org pipelines across 4–5 active migration tracks — designing dependency management, cross-track metadata conflict resolution and coordinated deployment sequencing for shared Salesforce org components. Data Migration Pipeline Integration: Integrate data migration pipeline execution (ETL job scheduling, bulk load sequencing, reconciliation validation) into the Hub CI/CD framework — ensuring data migration jobs are tracked, versioned, automated and auditable alongside metadata deployments. Secrets & Credential Management: Design and enforce secure secrets management for all Hub environments — including connected app credentials, API keys, org authentication certificates, ETL connection credentials and third-party integration tokens using vault-based or CI/CD-native secrets management. Monitoring & Observability: Design the Hub's deployment monitoring and observability framework — including pipeline run dashboards, deployment success/failure metrics, apex test trend monitoring, environment health checks and post-deployment alert routing for track teams and programme leadership. DevOps Engineer Mentoring & Standards: Act as the technical lead and mentor for DevOps Engineers embedded in each migration track — setting development standards, reviewing pipeline configurations, conducting DevOps design reviews and ensuring consistent tooling adoption across all track teams. Platform Development Contribution: Design and build reusable Salesforce platform components for Hub DevOps tooling — including LWC-based deployment dashboards, Apex utilities for automated org health checks, custom metadata-driven pipeline configuration frameworks and Salesforce Flow automations for release approval workflows. Continuous Improvement — Hub Feedback: Capture DevOps lessons learned after every migration wave — pipeline failures, deployment blockers, environment contention, test coverage gaps Tooling Evaluation & Adoption: Evaluate and recommend new DevOps tooling, Salesforce release management platforms and automation frameworks — maintaining the Hub's DevOps toolkit at the leading edge of Salesforce delivery practice. CORE TECHNICAL SKILLS — MUST HAVE Salesforce DX & Source-Driven Development: Expert knowledge of Salesforce DX — scratch org management, SFDX project structure, package development model (unlocked packages, managed packages), metadata API formats and CLI operations for automated deployments. CI/CD Pipeline Engineering: Hands-on expertise building and maintaining CI/CD pipelines for Salesforce deployments — using GitHub Actions, GitLab CI, Azure DevOps or CircleCI combined with Gearset, Copado or custom SFDX scripting for automated validate-test-deploy workflows. Gearset or Copado: Deep practical experience with at least one enterprise Salesforce release management platform — Gearset or Copado — including pipeline configuration, org comparison, deployment validation, rollback management and test execution integration. Git & Branching Strategy: Expert-level Git proficiency — branching model design (GitFlow, trunk-based, environment-branching), merge policy enforcement, PR review standards, release tagging and conflict resolution for Salesforce metadata and Apex code repositories. Salesforce Environment Management: Proven ability to design and manage multi-org environment topologies for large programme delivery — including sandbox refresh automation, org dependency mapping, data masking for lower environments and environment capacity planning. Apex & Platform Development: Strong Apex development skills — Triggers, Batch