Salesforce Administrator

<div class="content-intro"><p><strong>Build the Future with AspenView Technology Partners</strong></p> <p>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.</p> <p>As we continue to grow, we’re looking for exceptional people to join our team and help drive impactful change across industries.</p></div><p><strong>Why Join AspenView?</strong></p> <ul> <li> <p>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.</p> </li> </ul> <p><strong>About the Role</strong></p> <p>We are seeking a Salesforce Administrator to own the configuration, automation and operational health of an enterprise Salesforce org. This is an automation-first role: Flow and Flow Orchestration are the primary tools, and the expectation is that the holder designs automation standards for the org rather than adding one more flow to the pile. It combines build work with day-two ownership — releases, data quality, permissions and user support.</p> <p><strong>What You Will Do<br></strong><br><strong>Configuration and Automation </strong></p> <ul> <li> Design and build declarative solutions with Flow, Flow Orchestration, validation rules, custom metadata and dynamic forms</li> <li>Own the org’s automation standards: naming, entry criteria, error handling, and one-automation-per-object discipline </li> <li> Refactor or retire legacy Workflow Rules and Process Builder rather than building alongside them</li> </ul> <p><br><strong>Security and Access </strong></p> <ul> <li> Administer profiles, permission sets, permission set groups and sharing rules, and migrate off profile-based access</li> <li> Run periodic access reviews and remove the permissions nobody can justify</li> </ul> <p><strong>Data and Operational Health</strong></p> <ul> <li>Maintain data quality through duplicate rules, matching rules, validation and scheduled remediation </li> <li> Monitor scheduled jobs, storage, API consumption and limit headroom, and raise issues before they bite </li> <li> Manage releases into production including sandbox refresh and deployment validation</li> </ul> <p><strong>User Enablement</strong></p> <ul> <li>Triage and resolve user issues, and fix the cause rather than the ticket </li> <li> Build reports and dashboards that answer the question asked, and train users to self-serve</li> </ul> <p><strong>What You Bring</strong></p> <ul> <li>3+ years administering enterprise Salesforce orgs, including multi-cloud and multi-business-unit orgs</li> <li>Strong command of: <ul> <li>Flow and Flow Orchestration, including subflows, error handling and bulk-safe design</li> <li>The security and sharing model — OWD, role hierarchy, sharing rules, permission set groups, restriction rules </li> <li>Reports, dashboards, report types and Salesforce data loading tools </li> <li>Change sets and at least one source-driven deployment path such as DevOps Center or Gearset </li> </ul> </li> </ul> <ul> <li>Salesforce Certified Administrator required; Advanced Administrator and Platform App Builder preferred </li> <li> Able to read Apex well enough to know what the code in the org is doing, even if not writing it </li> <li> Evidence of having simplified an org rather than only extended one</li> </ul> <p><strong>What We're Looking For</strong></p> <p>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.<strong><br></strong></p> <ul> <li>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.</li> <li>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.</li> <li>Surfaces risk, ambiguity, and weak requirements at the moment they are noticed — not at the sprint review, and not at go-live. </li> <li>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. </li> <li>Argues from evidence and changes position on evidence. Comfortable being wrong in public, uncomfortable staying quiet</li> </ul> <p><strong>Success Indicators </strong></p> <ul> <li>Automation per object is consolidated and documented, and new automation follows the standard </li> <li> Support ticket volume falls because root causes get fixed </li> <li> Access reviews complete on schedule with exceptions closed </li> <li> Releases deploy without manual post-deployment steps</li> </ul> <p><strong>Educa