Salesforce Technical Lead

<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>About the Role</strong></p> <p>We are seeking a Salesforce Technical Lead to run the technical side of a delivery squad: breaking design into work, setting the standards the squad builds to, reviewing what comes out, and making the calls that do not need an architect. This is a hands-on role—roughly half of your week is spent building—and it is the role that allows a pod to deliver without a full-time architect attached.</p> <p>This is a full-time, remote position delivered from AspenView’s Latin American delivery centers into a North American client team. You will work the client’s core business hours with substantial time-zone overlap, operating as part of the client’s squad under AspenView delivery leadership.</p> <p><strong>What You Will Do</strong></p> <p><strong>Technical Leadership</strong></p> <ul> <li>Decompose solution designs into technical tasks with clear interfaces between them</li> <li>Set and enforce the squad’s coding, testing, and review standards</li> <li>Make day-to-day technical decisions and escalate only what genuinely needs architecture input</li> </ul> <p><strong>Hands-On Delivery</strong></p> <ul> <li>Build the hardest parts of the solution—integration layers, async frameworks, and complex Apex</li> <li>Run code review as a teaching mechanism, not a gate</li> </ul> <p><strong>Delivery Management</strong></p> <ul> <li>Own the squad’s technical estimate and defend it with reasoning</li> <li>Manage the release: branching, environment promotion, deployment validation, and rollback planning</li> <li>Track and pay down technical debt as part of normal sprints</li> </ul> <p><strong>People & Stakeholders</strong></p> <ul> <li>Mentor mid-level and junior engineers and make them measurably better</li> <li>Represent the squad in client technical discussions</li> </ul> <p><strong>What Success Looks Like</strong></p> <ul> <li>The squad delivers committed scope without heroics at the end of the sprint</li> <li>Code review finds design issues rather than formatting issues</li> <li>Engineers on the squad take on work above their previous level</li> <li>Escalations to architecture are fewer and better framed</li> </ul> <p><strong>What You Bring</strong></p> <p><strong>Education</strong></p> <ul> <li>Bachelor’s degree in Computer Science, Software Engineering, or a related field—or equivalent experience</li> </ul> <p><strong>Experience</strong></p> <ul> <li>7+ years building on Salesforce, including 2+ years leading a delivery squad</li> <li>Experience estimating and committing to delivery scope, and being held to it</li> <li>Track record of raising the technical standard of a team, with specifics</li> <li>Professional English—able to run requirement and design conversations directly with North American stakeholders</li> </ul> <p><strong>Technical Expertise</strong></p> <ul> <li>Apex at depth—async patterns, trigger frameworks, bulkification, and governor limits</li> <li>Lightning Web Components (LWC) and modern front-end practice on the platform</li> <li>Integration patterns and hands-on experience with at least one middleware or iPaaS platform</li> <li>Git branching strategy, CI/CD, and package-based development</li> </ul> <p><strong>Certifications</strong></p> <ul> <li>Salesforce Certified Platform Developer II, or Platform Developer I with equivalent demonstrated depth</li> </ul> <p><strong>Soft Skills</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>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>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>Surfaces risk, ambiguity, and weak requirements at the moment they are noticed—not at the sprint review, and not at go-live</li> <li>Works past the assigned ticket: proposes better approaches, improves what sits around the work, and leaves the team’s practice stronger than it was found</li> <li>Argues from evidence and changes position on evidence—comfortable being wrong in public, uncomfortable staying quiet</li> </ul><div class="content-conclusion"><p><strong>Visa Sponsorship</strong></p> <p>AspenView does not sponsor employment visas for this role. Applicants must be permanently authorized to work in their country of residence and must not