Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
AspenView Technology Partners is hiring a Salesforce Technical Architect to own the technical integrity of a Salesforce platform for client engagements. You will lead integration architecture across middleware, identity, data architecture at volume, and release architecture, driving non-functional requirements and architectural decisions.
The role demands deep expertise in Apex, iPaaS, SSO/OIDC, and platform governance, with a focus on scalable data handling, security, and performance.
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.
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.
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.
Bachelor's degree in Computer Science, Software Engineering, Information Systems, or a related field - or equivalent experience
A