Senior Salesforce DevOps Engineer

Main Skill :
Healthcare Domain Experience Mandatory , Health Cloud , Azure Devops

We are seeking an experienced Senior Salesforce Dev Ops Engineer to join a large-scale,

enterprise Salesforce delivery organization operating with 10+ POD/Scrum teams. This role is

critical to modernizing, stabilizing, and scaling our Salesforce Dev Ops practices on Azure

Dev Ops. The ideal candidate will bring deep Salesforce CI/CD expertise, strong problem-solving

skills, and a passion for engineering excellence. They will be responsible for diagnosing and

resolving significant existing challenges in our release pipeline and driving long-term

improvements across the Dev Ops lifecycle.

• Establish and enforce a reliable, automated source of truth between Salesforce orgs and the
• Design and implement processes to ensure Production org and Master branch are always in
• sync
• Eliminate code overwrite and rework caused by org/repo inconsistencies
• Architect org-from-repo deployment strategies to ensure environments are always
• created/refreshed from version-controlled source
• Redesign and optimize CI/CD pipelines to significantly reduce overall execution time
• Implement shallow clones, artifact caching, and incremental checkout strategies to address
• large repository sizes (~4.5GB)
• Introduce dedicated build agents/runners to eliminate shared-agent contention
• Optimize dependency installation, Sonar Qube, and SNYK scan execution within pipelines
• Reduce Apex test class execution time (current baseline: ~6 hours) through parallel test
• execution, test selection optimization, and test impact analysis strategies

• Design and manage Dev Ops processes supporting multiple release trains:
  Major Release (6-
• week), Short Sprint (2-week), Anytime/Micro, Hotfix, and Hypercare (1-week post-MR)
• Architect environment strategies to isolate different release streams — eliminating the risk
• of shared UAT environment conflicts across concurrent release tracks
• Establish clear environment promotion paths and minimize back-sync conflicts when
• syncing changes from Production
• Support increasing release frequency and volume with scalable, repeatable pipeline
• automation

• Design and implement automated rollback mechanisms within the pipeline to support last-
• minute release rollbacks
• Address Git cherry-pick limitations by establishing feature-branch and commit strategies
• that enable clean, isolated feature reverts
• Enable safe, low-risk hotfix and anytime deployment processes that do not disrupt ongoing
• releases
• Establish rollback runbooks and automated validation checks post-rollback
• Reduce manual bottlenecks in the pull request approval process through automation,
• tooling, and workflow improvements
• validation) to reduce dependency on manual reviewer availability
• Integrate AI-assisted or rules-based code review tools to accelerate the review cycle
• Enforce branch policies and PR standards across all POD teams