TLDR
- Weeks 1-4: Trailhead Admin Beginner trail, a free Developer Edition org of your own, and a printed copy of the Administrator exam blueprint you check off as you go.
- Weeks 5-8: three portfolio projects built in that org, each with written acceptance criteria so you can prove it works instead of saying it works.
- Weeks 9-12: sit the Salesforce Certified Administrator exam, record a 10-minute walkthrough of your projects, and start applying and networking.
- Honest framing: 90 days gets you credible and demonstrable. It does not guarantee an offer. Budget 3 to 9 months of applying after you certify.
- The differentiator is not the badge count. It is being able to open an org on a screen share and walk a hiring manager through something you built and can defend.
Most "become a Salesforce admin" guides end at "get certified." That is where the actual problem starts.
There are a lot of certified admins with no professional experience, and hiring managers know it. The certificate proves you can pass a multiple-choice exam about the platform. It does not prove you can build a flow that survives contact with a real sales team. The gap between those two things is where almost every entry-level candidate gets stuck.
This plan is built to close that gap in 90 days. It assumes 10 to 15 hours a week, which is what a career-changer with a job or a recent grad with a part-time role can realistically hold. It assumes no prior Salesforce exposure. It assumes you have a laptop and nothing else.
First, the honest version of the market
You should go in with clear eyes.
The entry-level Salesforce admin market is more competitive than it was five years ago. There are more certified people, more applicants per junior req, and more hiring managers who have been burned by a certified hire that could not troubleshoot a broken flow. "Salesforce Certified Administrator" on a resume is now a filter to get past, not an advantage on its own.
At the same time, the work has not gone anywhere. Orgs are still messy, backlogs are still long, and companies still need people who understand permission models and data quality. AI tooling has taken over a slice of the routine configuration work, which changes what junior admins are hired to do. Fewer people are hired to click through 200 tickets a week. More are hired to understand the business process behind the ticket, review what automation produced, and catch the thing that is about to break. That is a better job. It is also a job that rewards judgment, which you build by building.
On money, our Salesforce admin salary guide puts the US average around $92K, with entry-level roles starting near $65K. Do not anchor on the average for your first role. Anchor on the entry band and on getting your hands on a real org.
Realistic timeline: 90 days to become credible and demonstrable. Then 3 to 9 months of applying, networking, and contract or volunteer work before a first full-time offer for most people. Anyone selling you "certified and hired in 90 days" is selling you something.
Weeks 1-4: fundamentals, your own org, and the exam blueprint
The goal for month one is not mastery. It is fluency with the vocabulary and comfort inside Setup.
Set up your practice org on day one
Before you watch a single tutorial, get a free Developer Edition org. Sign up at developer.salesforce.com. It is free, it never expires, and it is a full-featured Salesforce instance with a small data and storage allocation. This is where everything else in this plan happens.
Do this first because reading about Salesforce without an org open is close to useless. Every concept you hit for the next 12 weeks should be something you immediately go click on.
A note on Trailhead Playgrounds: they are convenient for completing modules, and they are fine for that. But build your portfolio projects in your Developer Edition org, not a Playground. You want one persistent org that tells a coherent story when you demo it.
Work the Admin Beginner trail
Start with the Admin Beginner trail on Trailhead. It covers the core object model, Setup navigation, users and profiles, standard objects, reports and dashboards, and the basics of automation. Then move into the Admin Intermediate trail for sharing, security, and more involved data management.
Two rules that make Trailhead worth the time:
- Do not click straight to the challenge. The hands-on challenges can often be solved by pattern-matching the instructions. Read the unit, then go build the thing in your own org from memory before you touch the challenge.
- Write down what you did not understand. Keep a running list. By week 4 that list is your study plan, not the modules you already found easy.
Pay particular attention to the Data Security module. Org-wide defaults, role hierarchy, sharing rules, profiles, and permission sets are the single most commonly misunderstood area for new admins, and they show up heavily on the exam and in interviews.
Map the exam blueprint
Download the official exam guide from the Salesforce Certified Administrator credential page. It lists every domain and its weighting.
Turn the blueprint into a checklist with three columns: can explain it, can build it, neither. Fill it in honestly at the end of week 2 and again at the end of week 4. Anything still in the third column by week 4 is where your study time goes.
The exam itself is 60 questions in 105 minutes, and you need 65% to pass, which is 39 correct. Roughly 6 in 10 candidates pass on their first attempt. Our breakdown of the Salesforce admin certification pass rate covers the current domain weightings and the scoring detail.
End-of-month-one checkpoint
You should be able to, without notes: create a custom object with a lookup and a master-detail relationship and explain the difference, build a report with a cross filter, create a permission set and assign it, and explain what a role hierarchy does that a profile does not.
Weeks 5-8: three portfolio projects that survive questions
This is the part almost nobody does, and it is why almost nobody stands out.
Build three projects in your Developer Edition org. For each one, write the acceptance criteria first, in a doc, before you build. Then build until every criterion passes. Then write a short readme covering the problem, the design decision you made, and one thing you would do differently at scale.
The acceptance criteria matter more than the build. They are how you demonstrate that you think like someone who ships changes into a live business, rather than someone who follows tutorials.
Project 1: a record-triggered Flow that handles a real business rule
Scenario: when an Opportunity moves to Closed Won, create a Renewal Opportunity dated 11 months out, assign it to the same owner, copy across the Account and the primary contact role, and post a Chatter update to the Account.
Acceptance criteria:
- Setting an Opportunity to Closed Won creates exactly one Renewal Opportunity. Editing and saving that same record again creates zero additional ones.
- The Renewal Opportunity carries the correct Account, Owner, Close Date, and a Stage of Prospecting.
- If the Account has no primary contact role, the Flow completes without error and logs the gap rather than failing.
- Bulk test: load 200 Opportunities to Closed Won in a single data load. All 200 produce a renewal, and no governor limit error appears in the debug log.
- The Flow has a fault path. Force a failure (for example, make a required field blank) and confirm the fault path fires and the error is captured.
- The Flow is documented: a description on the Flow itself, and named elements that a stranger can read.
That bulk test and that fault path are the difference between a tutorial flow and a flow you would let near production. In an interview, "I tested it with 200 records in a single transaction" is a sentence very few entry-level candidates can say.
Project 2: a permission and sharing model for a three-team org
Scenario: design access for a fictional company with three groups: Sales Reps, Sales Managers, and a Finance team. Reps see only their own Opportunities. Managers see their team's. Finance sees all Opportunities read-only and is the only group that can edit a custom Invoice object.
Acceptance criteria:
- Org-wide default for Opportunity is Private, and you can explain in one sentence why you did not start with Public Read Only.
- A role hierarchy exists that gives Managers visibility into their reps without any sharing rule.
- Finance access to Opportunities is granted by a criteria-based or owner-based sharing rule, not by making everyone a System Administrator.
- The Invoice object uses a permission set for edit access rather than a custom profile, and you can explain why permission sets are preferred.
- Three test users exist, one per group. You log in as each (using Login As) and confirm what they can and cannot see. Screenshot each result.
- A written access matrix: rows are objects, columns are the three groups, cells are Create, Read, Edit, Delete.
Bring that access matrix to interviews. It reads as someone who has done the work rather than someone who memorized the definition of an org-wide default.
Project 3: a data import with deduplication and a rollback plan
Scenario: import 500 Accounts and 1,500 Contacts from a messy CSV into your org, with duplicates prevented and the import reversible.
Acceptance criteria:
- The source CSV is genuinely messy on purpose: inconsistent state formats, some blank required fields, at least 20 duplicate rows, and a few records with trailing whitespace.
- You define an external ID field on Account and use Upsert so that re-running the same file does not create duplicate records. Prove it by running the file twice and showing the record count is unchanged.
- Duplicate Rules and Matching Rules are configured and actively block or flag duplicate Accounts on the website domain.
- Contacts are correctly related to their parent Accounts through the external ID rather than manual matching.
- Every failed row is captured in the error file, and you have written up what caused each category of failure.
- A rollback plan exists in writing: you captured the record IDs created, and you can demonstrate deleting exactly that set without touching pre-existing data.
Data work is unglamorous and it is a large share of what junior admins are actually asked to do. Being the candidate who talks fluently about external IDs, upsert behavior, and rollback puts you ahead of most of the field.
Optional: one superbadge
If you have spare capacity in month two, a Trailhead superbadge is worth more than a dozen ordinary badges, because superbadges are scenario-based and are not solvable by pattern-matching. The Business Administration Specialist and Security Specialist superbadges align well with this plan. Skip it if it would come at the cost of the three projects. The projects matter more.
Weeks 9-12: certify, package, and start applying
Sit the exam
Book the exam at the start of week 9 for a date near the end of week 10. A booked date changes how you study.
Use the checklist from week 4. Spend your study time on the domains where you marked "neither," and on scenario practice rather than definition recall. The exam asks what you should do in a situation, not what a term means. Before you sit, run our free Salesforce certification readiness quiz to get a score breakdown by domain and find out where you are actually weak.
If you do not pass, it is not a verdict. A significant share of candidates do not pass the first attempt. Log what you missed, study those domains for two weeks, and rebook.
Package the portfolio
Three artifacts, all of which take an afternoon:
- A 10-minute screen recording walking through all three projects. Show the org, not slides. Talk through one decision per project and one thing you would change at scale.
- A one-page project summary for each build: the scenario, the acceptance criteria, and the design decision. This is what you attach to applications.
- A LinkedIn post per project. Not for vanity. Salesforce hiring managers and consultancy recruiters genuinely read the ecosystem feed, and three build posts make you findable in a way a resume does not.
Apply, and go where the admins are
Start applying in week 11, not week 13. You will need the reps.
Look at junior admin, Salesforce coordinator, sales operations analyst, and CRM support roles. Consultancy analyst programs are often the fastest entry point because they hire for aptitude and train the platform. Our Salesforce job board lists live openings across admin, consultant, and developer roles.
At the same time, do the two things that generate opportunities outside the application pile:
- Volunteer with a nonprofit. Salesforce's nonprofit tooling is widely used and small nonprofits are chronically short on admin help. This is real production experience on a real org with real users, which is the exact line missing from your resume.
- Show up in the community. Join your local Salesforce user group and the Trailblazer Community groups for admins. Most first roles in this ecosystem come from someone who already knows your name.
If week 12 comes and nothing has landed
That is the normal case, not the failure case. Adjust like this.
Widen the target: sales ops, revenue ops, and CRM support roles all put you inside a Salesforce org, and internal moves to admin from those seats are common. Take the contract role. Take the six-month gig. Time inside a production org compounds faster than any additional certification.
And add depth in the direction the work is going. Learn how to review automation, not just build it. Learn how to read a debug log. Learn what a deployment process looks like. Those are the skills that make you useful next to AI tooling instead of interchangeable with it, and we wrote about that shift in will AI replace Salesforce admins.
Frequently asked
Do I need a computer science degree? No. Salesforce administration is configuration and business process work, not programming. Many of the strongest admins came from support, operations, or recruiting.
How much does this cost? The Developer Edition org is free. Trailhead is free. The exam is $200. That is the entire required spend. Paid practice exams are optional and worth it only if you are close to the line.
How many hours a week does the plan take? 10 to 15. You can compress it to 6 weeks at 30 hours a week if you are between jobs, but do not compress the portfolio projects. They are the part that gets you hired.
Is one certification enough to start? Yes. Get the Administrator credential, then get work. Additional certifications are worth far more once you have a real org to apply them to.
What if I fail the exam? Roughly 4 in 10 candidates do on their first try. Review your score report by domain, study those areas, rebook. It has no effect on your credential once you pass.
Related
- Salesforce admin certification pass rate and exam breakdown
- Free Salesforce certification readiness quiz
- Salesforce admin salary guide
- Salesforce job board: live admin and consultant roles
