Do you know Salesforce well enough to catch a bad automation before it breaks something downstream? Can you sit with a client and figure out what they actually need, not just what they asked for? Do you like owning something end to end instead of just ticket-closing?
Then, our Senior Salesforce Admin role here at CUBE84 may interest you.
In this gig,
You're the org's daily driver
You own the day-to-day configuration of client orgs — flows, validation rules, page layouts, permission sets, approval processes. You know when declarative is the right call and when it's time to flag something to a developer instead of forcing a workaround.
You keep the data model honest
You own the security model — profiles, permission sets, sharing rules, role hierarchy — and you know why each one exists, not just how to clone it. You catch data quality issues before they turn into a client escalation, and you set up the dedup rules, validation, and reporting that keep the org clean.
You're the calm in a client's chaos
You take a client's messy ask — "can we just track this somewhere?" — and turn it into a clean requirement, a build plan, and a working solution. You know the difference between a client who needs a five-minute Loom walkthrough and one who needs a proper requirements doc.
You ship changes without breaking prod
You own release management for your orgs — sandbox to UAT to production, change sets or a proper deployment tool, and a rollback plan if something goes sideways. You test before you ship, and you document what changed and why.
You're who the junior admins call first
You review the work of junior admins before it goes near production. You catch the flow that's about to hit a recursion limit, the profile that's too permissive, the field that should've been a picklist. You explain the fix, not just make it.
You've seen more than one cloud
You move comfortably across Sales Cloud, Service Cloud, Experience Cloud, or Nonprofit Cloud depending on which client you're on, and you know enough about each to ask the right questions even outside your strongest cloud.
You ask what the data means before you touch it
Before you map a single field, you ask what the source data is actually used for, who relies on it, and what "clean" looks like to the business, not just to you. You're comfortable with Data Loader, Import Wizard, or a similar tool, and you know the difference between an insert, an update, and an upsert — but the tool is the easy part. You decide the mapping, flag the records that don't fit before they cause a problem, and take responsibility for the outcome, not just the steps.
You turn migrated data into something people can act on
Once data is in Salesforce, you understand it well enough to have an opinion on what a dashboard or report should surface from it. When something looks wrong after a load, you don't just patch the record — you check the source file, the mapping, and the load logs to find where it went wrong, and you flag it, along with what you'd do differently, instead of waiting for someone else to notice.
You leave a paper trail
You document what you build — data dictionaries, process maps, release notes — so the next person on the org (client-side or CUBE84-side) isn't reverse-engineering your work six months later.
It'll be awesome if you...
Have 5+ years of hands-on Salesforce Admin experience, owning org configuration end to end — not just ticket support (this one's non-negotiable)
Hold a Salesforce Administrator certification (Advanced Admin is a strong plus) (this one's non-negotiable)
Have solid experience with flows, validation rules, approval processes, and the security/sharing model
Have managed sandbox-to-production release cycles, including change sets or a CI/CD deployment tool
Have worked directly with clients — gathering requirements, running walkthroughs, handling the "why does it work this way?" conversation
Are comfortable reviewing and correcting the work of less experienced admins
Have owned a data migration or cleanup effort end to end, not just executed steps someone else planned, including deciding what questions to ask before touching the source data
Can explain the difference between an insert, update, and upsert, and pick the right one for the situation
Understand data well enough to suggest what a dashboard or report should track, based on what's actually in the records
More awesome, if you have
Experience across multiple Salesforce clouds (Sales, Service, Experience, Nonprofit, or CPQ)
A Platform App Builder or additional Salesforce certification
Exposure to a consulting or agency environment, juggling multiple client orgs at once
Basic familiarity with Apex or Flow-to-Apex handoff, enough to know when to loop in a developer
Experience with a dedicated migration tool (Data Loader CLI, DemandTools, or similar), not just the standard Import Wizard
Experience building or shaping report and dashboard components based on migrated or cleaned-up data
.png)
