Salesforce Developer

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.

Why Join AspenView?

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.

Here’s what you can expect:

• Competitive base
• Comprehensive benefits and wellness support
• Flexible work model: hybrid, remote, or in-office
• Real growth opportunities and leadership visibility
• Inclusive, respectful culture that blends U.S. innovation with Colombian heart
• A company that listens, invests in you, and celebrates wins together

About the Role

We are seeking a Salesforce Developer to build and extend custom functionality on enterprise Salesforce orgs where declarative configuration has reached its limit. The role writes Apex and Lightning Web Components, designs integrations to surrounding enterprise systems, and holds the line on test coverage, governor-limit discipline and release hygiene. It sits inside a delivery squad alongside admins, business analysts and an architect, and is expected to push back on requirements that would be better solved with configuration than with code.

What You Will Do

Platform Development

• Build Apex triggers, batch, queueable and scheduled classes against a documented trigger framework rather than one class per object
• Develop Lightning Web Components, and extend Aura or Visualforce only where the existing estate requires it 
• Choose configuration over code where Flow, validation rules or custom metadata will do the job, and say so when a requirement does not warrant Apex

Integration

• Build and consume REST and SOAP services using Named Credentials and External Services
• Implement event-driven integration with Platform Events, Change Data Capture and Pub/Sub API 
• Handle retry, idempotency and error surfacing so failed integrations are visible rather than silent