Salesforce Technical Architect

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 Technical Architect to own the technical integrity of a client’s Salesforce platform: integration architecture, identity, data architecture at volume, release architecture and the non-functional requirements that decide whether a solution holds up in year three. This is the scarcest role in the ecosystem, and the engagement expects the holder to make decisions rather than document options.

What You Will Do

Technical Architecture

• Own integration architecture across middleware, event bus, APIs and batch, and the contracts between them
• Design for large data volumes: skinny tables, selective indexing, archiving, and LDV-aware sharing
• Own identity and access architecture — SSO, SAML or OIDC, Connected Apps, scoped permissions

Platform Governance

• Set and police coding, packaging and metadata standards across squads
• Define the release architecture: environment strategy, branching, CI/CD, and data seeding
• Run technical design authority and hold veto on designs that create structural risk

Performance and Resilience

• Diagnose and remediate platform performance problems with evidence rather than guesswork
• Establish monitoring, alerting and observability across integrations and async processing
• Plan for failure modes: partial integration failure, governor exhaustion, API limit pressure

Enablement

• Mentor developers and solution architects and raise the technical ceiling of the team
• Represent AspenView in client technical reviews and vendor discussions

What You Bring

Experience

• 10+ years of enterprise technical delivery, including 5+ years architecting on the Salesforce Platform

Deep expertise in:

• Apex and platform limits at scale, including async framework design and LDV patterns
• Integration architecture and middleware, including MuleSoft or an equivalent iPaaS
• Identity, SSO and API security — OAuth flows, JWT, Connected Apps, Shield where applicable
• Package-based development, environment strategy and multi-squad release management
• Data architecture, master-data alignment and migration at enterprise volume
• Salesforce Certified Technical Architect, or Application Architect plus System Architect with an active CTA path, required
• Demonstrated ownership of a platform decision that proved correct under load or audit
• Experience in a regulated or high-assurance environment preferred
• 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

• Integrations degrade visibly and recoverably rather than failing silently
• Platform limits and performance are managed proactively, not discovered in production
• Multiple squads release into one org without collision
• Client technical leadership treats this role as the decision-maker on platform questions

Education

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