Salesforce Technical

Build the Future with AspenView Technology Partners

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.

As we continue to grow, we’re looking for exceptional people to join our team and help drive impactful change across industries.

About the Role

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.

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.

What You Will Do

Technical Leadership

• Decompose solution designs into technical tasks with clear interfaces between them
• Set and enforce the squad’s coding, testing, and review standards
• Make day-to-day technical decisions and escalate only what genuinely needs architecture input

Hands-On Delivery

• Build the hardest parts of the solution—integration layers, async frameworks, and complex Apex
• Run code review as a teaching mechanism, not a gate

Delivery Management

• Own the squad’s technical estimate and defend it with reasoning
• Manage the release: branching, environment promotion, deployment validation, and rollback planning
• Track and pay down technical debt as part of normal sprints

People & Stakeholders

• Mentor mid-level and junior engineers and make them measurably better
• Represent the squad in client technical discussions

What Success Looks Like

• The squad delivers committed scope without heroics at the end of the sprint
• Code review finds design issues rather than formatting issues
• Engineers on the squad take on work above their previous level
• Escalations to architecture are fewer and better framed