Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
AspenView Technology Partners is seeking a Salesforce Solution Architect to own the functional shape of the Salesforce estate for a client's multi-cloud environment. The role sits between business stakeholders and the delivery squad, ensuring designs survive real data volumes and user behavior across the next two releases.
Responsibilities include translating business capabilities into Salesforce solutions, deciding build versus configure versus buy versus integrate, designing data models and
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.
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:
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.
8+ years in the Salesforce ecosystem with at least 3 years designing multi-cloud solutions end to end
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
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.
The org's automation and data model stay coherent as multiple squads build in