Salesforce DevOps Engineer

<div class="content-intro"><p><strong>Build the Future with AspenView Technology Partners</strong></p> <p>At AspenView, we are passionate about transforming the way organizations approach technology. We specialize in creating high-performing, nearshore IT teams to help North American clients innovate faster and more efficiently.</p> <p>As we continue to grow, we’re looking for exceptional people to join our team and help drive impactful change across industries.</p></div><p><strong>Why Join AspenView?</strong></p> <p>At AspenView, we’re more than a nearshore IT partner—we’re a people-first, purpose-driven company that believes great culture drives great outcomes. We’re passionate about connecting talent and technology to deliver measurable value for clients—and meaningful career paths for our people.</p> <p>Here’s what you can expect:</p> <ul> <li>Competitive base</li> <li>Comprehensive benefits and wellness support</li> <li>Flexible work model: hybrid, remote, or in-office</li> <li>Real growth opportunities and leadership visibility</li> <li>Inclusive, respectful culture that blends U.S. innovation with Colombian heart</li> <li>A company that listens, invests in you, and celebrates wins together</li> </ul> <p><strong>About the Role</strong></p> <p>We are seeking a Salesforce DevOps Engineer to build and run the release machinery for a multi-squad Salesforce estate: source control, environment strategy, automated deployment, test automation and monitoring. DevOps is the most consistently under-resourced discipline in the Salesforce ecosystem and there are almost no dedicated practitioners, which makes it the difference between monthly releases and weekly ones.</p> <p><strong>What You Will Do</strong></p> <p class="p1"><strong>Release Engineering</strong></p> <ul> <li class="p1">Build and maintain CI/CD pipelines for Salesforce metadata using Azure DevOps, GitHub Actions, Gearset, Copado or DevOps Center</li> <li class="p1">Define branching and environment strategy across multiple squads releasing into one org</li> <li class="p1">Automate deployment validation, delta deployment and rollback</li> </ul> <p class="p1"><strong>Test and Quality Automation</strong></p> <ul> <li class="p1"><span class="s1"><span class="Apple-converted-space"> </span></span>Automate Apex test execution, static analysis with PMD or CodeScan, and metadata linting in the pipeline</li> <li class="p1">Build UI and API regression suites with Selenium, Playwright or Provar</li> <li class="p1">Gate releases on evidence rather than on sign-off alone</li> </ul> <p class="p1"><strong>Environment and Data Management</strong></p> <ul> <li class="p1">Manage sandbox strategy, refresh cadence and post-refresh automation</li> <li class="p1">Build repeatable, compliant test-data seeding — no production data in lower environments</li> </ul> <p class="p1"><strong>Monitoring and Operations</strong></p> <ul> <li class="p1">Instrument the org: event monitoring, limit consumption, async job health, integration error rates</li> <li class="p1">Run incident response for release and integration failures, and write up the causes</li> </ul> <p><strong>What You Bring</strong></p> <p><strong>Experience</strong></p> <p class="p1"><span class="s1"><span class="Apple-converted-space"> </span></span>3+ years in DevOps or platform engineering, including hands-on Salesforce release experience</p> <p class="p1"> </p> <p>Proficiency with:</p> <ul> <li class="p1"><span class="s1"><span class="Apple-converted-space"> </span></span>Salesforce CLI, sfdx source format, unlocked and second-generation packaging</li> <li class="p1">At least one Salesforce release platform: Copado, Gearset, Flosum or DevOps Center</li> <li class="p1">A general CI/CD system — Azure DevOps, GitHub Actions, GitLab CI or Jenkins</li> <li class="p1">Scripting in Bash, Python or Node for pipeline and automation work</li> <li class="p1">Test automation tooling for both Apex and UI layers</li> <li class="p1">Understanding of Salesforce metadata behaviour and why some of it deploys badly</li> <li class="p1">Experience supporting multiple squads in a shared org without blocking them</li> <li>Professional English — able to run requirement and design conversations directly with North American stakeholders</li> </ul> <p><strong>What We’re Looking For</strong></p> <p>This is a contributor role, not a task-execution role. The team already has people who deliver what they are handed. What it needs is people who question whether the right thing is being built, and say so.</p> <ul> <li class="p1">Holds a point of view and states it, including to senior stakeholders and including after a decision has been made when new evidence warrants reopening it.</li> <li class="p1">Asks why a process, data model, or delivery standard exists before extending it, rather than replicating an incumbent pattern because it is the incumbent pattern.</li> <li class="p1">Surfaces risk, ambiguity, and weak requirements at the moment they are noticed — not at the sprint review, and not at go-live.</li> <li class="p1">Works past the assigned ticket: