Salesforce Solution 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 Solution Architect to own the functional shape of the solution across a client’s Salesforce estate: which capability is met by which cloud, what is configured, what is built, what is integrated, and what should not be done on the platform at all. The role works between business stakeholders and the delivery squad, and is accountable for designs that survive contact with real data volumes, real user behaviour and the next two releases.

What You Will Do

Solution Design

• Translate business capability requirements into a designed Salesforce solution across Sales, Service, Data 360 and connected systems
• Decide build versus configure versus buy versus integrate, and document why
•  Design the data model, sharing model and automation approach as one decision rather than three

Advisory and Governance

• Run design authority sessions and defend design decisions to senior client stakeholders
• Establish and enforce declarative and code standards so the org does not fragment across squads
• Maintain a live view of technical debt and the cost of carrying it

Delivery Support

•  Break the design into deliverable increments the squad can actually ship
• Review implementation against the design and intervene early when it drifts
• Own non-functional requirements: data volume, performance, security, auditability

Stakeholder Alignment

•  Facilitate discovery and process-mapping workshops with business and IT
• Say no to requirements that would compromise the platform, with a reasoned alternative

What You Bring

Experience

•  8+ years in the Salesforce ecosystem with at least 3 years designing multi-cloud solutions end to end

Depth across:

• Sales Cloud and Service Cloud configuration and their standard object models
• Declarative automation — Flow, Flow Orchestration, Approval Processes — and its limits
• The Salesforce sharing and visibility model, including large-org performance implications
• Integration patterns: request-reply, fire-and-forget, batch, event-driven, and middleware roles
• Data 360 and Agentforce at a design level, including where they are not yet the right answer
• Salesforce Certified Application Architect, or the constituent certifications, required
• Demonstrated experience with enterprise data migration and org consolidation or split
• Ability to produce design artefacts that a delivery team can build from: data models, sequence diagrams, integration inventories, decision logs
• Experience working inside a client’s governance process, not around it
• 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

• Designs are built as designed, and design changes during delivery are deliberate rather than reactive
• Client architecture forums accept the design without escalation
• Rework attributable to design gaps trends down release over release
• The org’s automation and data model stay coherent as multiple squads build in parallel

Education

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