Salesforce Developer

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

Quality and Release 

• Write meaningful Apex tests with real assertions, not coverage padding
• Work source-driven with Salesforce CLI, scratch orgs and unlocked or second-generation packages
•  Deploy through CI using Azure DevOps, GitHub Actions or DevOps Center, and keep the pipeline green

Collaboration

• Review peers' code and accept review on your own
• Work with the architect on design decisions before building, and translate analyst requirements into technical designs, flagging the gaps in them
  
  

What You Bring

Experience

• 3+ years building on the Salesforce Platform, including production releases in an Agile delivery team
• Proficiency with:

• • Apex — asynchronous patterns, bulkification, governor limits, large data volumes
  • Lightning Web Components, Lightning Data Service, and the Salesforce UI API
  • SOQL and SOSL, including selective query design against multi-million-record objects
  • Flow and Flow Orchestration, as a first-choice tool rather than a fallback
  • Salesforce CLI, sfdx source format, scratch orgs, and package-based development
• Integration experience across REST, SOAP, Platform Events and middleware, with an understanding of when
  the integration belongs outside the platform
• Salesforce Certified Platform Developer I required; Platform Developer II preferred
•  Working knowledge of the Salesforce security model: sharing, FLS and CRUD enforcement in Apex
•  Git-based branching, code review, and static analysis such as PMD or CodeScan
•  Professional English — able to run requirement and design conversations directly with North American
  stakeholders

What We’re Looking For

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.

• 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. 
• 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. 
• Surfaces risk, ambiguity, and weak requirements at the moment they are noticed — not at the sprint review, and not at go-live. 
• 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. 
• Argues from evidence and changes position on evidence. Comfortable being wrong in public, uncomfortable staying quiet. 

Success Indicators

• Custom code volume falls or holds flat while delivered functionality grows, because configuration is used where it fits
• Releases go out without rollback, and failed integrations are detected by monitoring rather than by users
• Apex tests catch real regressions, evidenced by defects found in CI rather than in UAT
• Other developers on the squad adopt the patterns this role establishes

Education

• Bachelor’s degree in Computer Science, Software Engineering, Information Systems, or a related field — or equivalent experience