Salesforce Developer Roadmap 2026: 12-Month Plan
7 min read ยท 2026-10-08
The salesforce developer roadmap 2026 has six phases. You learn the platform like an admin, automate with Flow, write Apex and SOQL, build Lightning Web Components, connect systems and add Agentforce, then pass Platform Developer I and apply. Plan on 9 to 12 months at about 10 hours a week. That is an estimate. It gets shorter if you already code or already work as an admin.
Each phase ends with a project you build in a free Developer Edition org, plus a milestone you can check. You can follow the roadmap alone, and you can also show it to a manager or recruiter to prove where you stand.
The roadmap at a glance
Goal: Go from no Salesforce experience to a certified Platform Developer who can build, test and deploy Apex and LWC solutions. Duration: 9 to 12 months, part time
Platform and Admin Basics (Months 1-2)
Learn how a Salesforce org is configured before you write any code.
- Create a free Developer Edition org and finish the Admin Beginner trails on Trailhead.
- Build custom objects, fields, lookup and master-detail relationships, record types and page layouts.
- Set up profiles, permission sets, roles and sharing rules for one realistic team.
- Build reports and dashboards that answer three business questions from your org's data.
Milestone: A small custom app with related objects, a working security model and one dashboard.
Flow and Declarative Automation (Months 2-3)
Automate processes with clicks first. That way you learn when code is really needed.
- Build record-triggered, screen and scheduled flows in Flow Builder.
- Use validation rules, formula fields and roll-up summaries.
- Debug a flow and write down the order of execution when a record is saved.
- Rebuild one old manual process as a flow, either from your own job or from a Trailhead scenario.
Milestone: A full lead-to-opportunity process automated with flows and validation rules only.
Apex and SOQL (Months 3-6)
Write server-side logic that stays inside platform limits.
- Learn Apex classes, collections, exceptions and object-oriented patterns.
- Write SOQL and SOSL queries, including relationship and aggregate queries.
- Build bulk-safe triggers with one trigger per object and a handler class.
- Use Queueable, Batch and Scheduled Apex for heavy or delayed work.
- Write test classes that assert real outcomes for single records, bulk loads and users without permission.
Milestone: A trigger framework that processes 200 records in one transaction and passes all its tests.
Lightning Web Components (Months 6-8)
Build modern user interfaces on the platform.
- Refresh modern JavaScript: modules, promises, async and await, array methods.
- Build components with templates, reactive properties, events and composition.
- Read and write data with Lightning Data Service, wire adapters and Apex methods.
- Style with the Salesforce Lightning Design System and test with Jest.
Milestone: An LWC on a record page that reads and updates records through Apex.
Integrations, DevOps and Agentforce (Months 8-10)
Connect Salesforce to other systems, ship changes safely and get familiar with AI agents.
- Call an external REST API from Apex with Named Credentials.
- Expose a custom Apex REST endpoint and use platform events for one event-driven flow.
- Work with Salesforce CLI, VS Code and scratch orgs, and keep every change in Git.
- Finish the Agentforce modules on Trailhead and expose one Apex invocable method as an agent action.
Milestone: Your org talks to a public API, and all its metadata deploys from a Git repository.
Certification and First Role (Months 10-12)
Prove your skills and get your first developer work.
- Pass the Administrator certification if you skipped it earlier.
- Prepare for Platform Developer I with timed practice exams and the official exam guide.
- Publish two or three portfolio projects, each with a repo, a short demo video and notes on your design choices.
- Join Trailblazer Community groups and apply to consulting partners and in-house Salesforce teams.
Milestone: Platform Developer I passed and first interviews booked.
Admin First or Developer Directly: How to Choose
Where you start depends on what you already know. The platform rewards a "clicks before code" habit, and interviewers often ask when you would pick a flow over a trigger. Whatever your background, you can't answer that without admin knowledge.
All three paths below use the same salesforce admin and developer roadmap. Only the time you spend on each phase changes. Pick your path:
- Complete beginner, no code, starting from scratch: follow every phase in order. Take the Administrator certification around month 3. If you have never coded, learn basic JavaScript before Apex.
- Salesforce admin moving to development: skim phases 1 and 2, then spend your time on Apex, testing and LWC. You can often finish in 6 to 8 months.
- Developer from Java, C# or JavaScript: Apex syntax will feel familiar. Spend phase 1 on the data model and sharing rules, because that is where experienced coders struggle most. Then move fast through Apex.
Salesforce Developer Certification Roadmap
The usual order is Administrator, then Platform App Builder, then Platform Developer I. Salesforce sets no official prerequisite for PD1. Salesforce Ben still advises getting Admin and Platform App Builder first, plus about two years in the ecosystem. If you come in without that background, plan more prep time.
The fee, length and retake rules can change, so check them on the official exam page before you book. After PD1, common next steps are Platform Developer II or a specialist track. For a Salesforce Marketing Cloud developer roadmap, add AMPscript, SQL for data extensions and server-side JavaScript after phase 3, and aim for the Marketing Cloud Developer certification.
Platform Developer I has 60 multiple-choice or multiple-select questions, and you need 68% to pass. According to Salesforce Ben, the questions are split like this:
- Process Automation and Logic: 30%
- User Interface: 25%
- Developer Fundamentals: 23%
- Testing, Debugging and Deployment: 22%
Governor Limits, Bulkification and Test Coverage
Salesforce is multi-tenant. Every transaction runs under strict limits on queries, DML statements, CPU time and memory. The classic beginner bug is a query inside a loop: it works with one test record, then fails when a data import fires the trigger on hundreds of records.
Unit tests must cover at least 75% of your Apex code before you can deploy to production, and every trigger needs some coverage. Salesforce's own guidance says to aim at covering every use case, not just at reaching that percentage.
- Query once: collect IDs in a set, then run one SOQL query outside the loop.
- Use maps: key results by ID for fast lookups.
- DML once: gather changes in a list and update them in one statement.
- Go async: move callouts and large jobs to Queueable or Batch Apex.
What AI Changes for Salesforce Developers in 2026
The role is changing. Writing basic code takes up less of the job. More of it goes into Agentforce, data, integrations and architecture.
In practice, that makes phases 3 and 5 more important. AI can draft an Apex class, but you still have to check it for limits, security and tests. Salesforce also ships three major releases a year (Spring, Summer and Winter), so set aside a few hours after each one to read the release notes. That is the realistic answer to "salesforce roadmap 2026": the platform changes with every release, and your plan has to keep up.
Turn It Into a Salesforce Developer Roadmap Template You Can Present
If your manager or a training budget pays for your upskilling, a one-page plan gets approved faster than a list of courses. Give each phase five columns: phase, weeks, training resource, deliverable and exit criterion. In Excel or Google Sheets, one row per phase is enough. Save it as a PDF to share.
Make the exit criteria checkable. "Learn Apex" is too vague. "Trigger framework passes bulk tests in a dev org" is something you can show. Add a review date every quarter. A recruiter reading the same plan sees a concrete Salesforce developer training path with finished projects, and that counts for more than a list of badges.
Common mistakes to avoid
- Writing Apex for problems Flow already solves. Default to declarative tools, and only use code when logic, volume or integration needs it.
- Putting SOQL or DML inside loops. Bulkify every trigger and test it with a large data load.
- Writing tests only to hit coverage. Assert real outcomes, and test bulk, negative and permission cases.
- Ignoring the sharing model. Enforce sharing and field-level security in your Apex on purpose.
- Pasting AI-generated code without reading it. Review every line for limits and security before it goes into Git.
- Collecting badges without building anything original. Turn each phase into a documented portfolio project.
Frequently asked questions
How long does it take to become a Salesforce developer from scratch?
Most estimates say 6 to 12 months to be job ready, but this is an estimate, not a guarantee. This roadmap assumes 9 to 12 months at about 10 hours a week. Admin or programming experience shortens it a lot.
Should I get the Admin certification before Platform Developer I?
It isn't required, but it is the common route. Admin knowledge of objects, security and Flow comes up in PD1 questions and in interviews. Many employers also ask for both certifications.
Can you pass Platform Developer I without coding experience?
Yes, but plan more time for phase 3 and learn basic JavaScript or Java first. The exam tests Apex, SOQL, LWC and testing, and those are hard to learn from theory alone. Building the phase projects is the best preparation.
Is Salesforce development still worth learning with AI tools in 2026?
The work isn't going away. It is moving toward Agentforce, data, integrations and architecture. Developers who understand limits, security and testing are the ones who can check what AI produces, so build those skills first.
Should I learn Aura or Lightning Web Components?
Build new components in Lightning Web Components, the standards-based framework Salesforce recommends. Aura still runs in older orgs, so learn to read it for maintenance work. Good JavaScript makes LWC much easier.