Career tracks
One shared ladder for the whole ecosystem
Job titles in the Salesforce world are wildly inconsistent — a “Senior Consultant” at one company can be a “Developer” at another. This site harmonizes them into five parallel career tracks with four levels each, so members, companies and recruiters can compare experience on the same scale. The levels compare scope and experience, never rank: an L3 administrator and an L3 developer are peers.
Built from the data you enter
Your place on the ladder is not assigned by us — it comes from your own profile. The calculated match reads the job titles in your work history and the Salesforce roles you have chosen, weighs your most recent role the most, and places you on the track and level your experience supports. You can always set your own choice instead, and you can improve the match by keeping your timeline and roles up to date.
The Salesforce ecosystem has five parallel career tracks. The administrator track masters the platform without code — declarative configuration, security and data. The developer track builds with code — Apex, Lightning Web Components and APIs. The architect track designs across both — end-to-end solution architecture, integration and governance. The leadership track owns value, teams, budgets and business outcomes. The business analyst track defines the business problem, requirements, process and adoption before and throughout delivery. Most members sit in one track; some work across two.
Each track answers a fundamentally different driving question.
| Track | Driving question | Core deliverables |
|---|---|---|
| Business Analyst | “What business problem are we solving, and how should the process work?” | Process maps, user stories, solution blueprints, UAT and adoption plans |
| Administrator | “How do we configure this cleanly and keep the org running?” | Flows, permissions, hygiene and user enablement |
| Developer | “How do we engineer this programmatically?” | Apex, LWC, APIs, CI/CD and unit tests |
| Architect | “How should this be structured across systems and at scale?” | System landscape, data strategy, governance and trade-offs |
| Leadership | “Why are we building this, what is the business ROI, and who will deliver it?” | Roadmap, budget, vendor management, team capacity and stakeholder buy-in |
The five tracks run in parallel — the levels compare scope and experience, not rank.
No Apex or code required. Focus: declarative architecture (Flows), security and access controls, data integrity, user operations, release management and platform hygiene.
| Level | Title | Experience | Core competencies | Certifications |
|---|---|---|---|---|
| L1 | Junior / Associate Administrator | 0–2 years |
|
|
| L2 | Salesforce Administrator | 2–4 years |
|
|
| L3 | Senior Administrator | 4–7 years |
|
|
| L4 | Lead Administrator / Platform Owner | 7+ years |
|
|
Custom software development: Apex backend, Lightning Web Components frontend, API integrations, DevOps pipelines and unit testing.
| Level | Title | Experience | Core competencies | Certifications |
|---|---|---|---|---|
| L1 | Junior / Associate Developer | 0–2 years |
|
|
| L2 | Salesforce Developer | 2–4 years |
|
|
| L3 | Senior Developer | 4–8 years |
|
|
| L4 | Lead / Staff Developer | 8+ years |
|
|
Its own track, not a senior developer with another title. Focus: end-to-end solution design, data and security models, integration strategy, multi-cloud governance and technical risk. Fed by both the administrator and developer tracks — and certified separately by Salesforce.
| Level | Title | Experience | Core competencies | Certifications |
|---|---|---|---|---|
| L1 | Associate Solution Architect | 2–5 years |
|
|
| L2 | Solution Architect | 5–8 years |
|
|
| L3 | Senior / Lead Solution Architect | 8–12 years |
|
|
| L4 | Certified Technical Architect (CTA) | 10+ years |
|
|
Its own track, not simply a promotion from a technical role. Focus: business value, roadmap, investment, delivery accountability, team capacity, vendor management and stakeholder alignment. Leaders may come from any of the other three tracks.
| Level | Title | Experience | Core competencies | Certifications |
|---|---|---|---|---|
| L1 | Team Lead / Delivery Lead | 4–7 years |
|
|
| L2 | Salesforce Delivery Manager | 6–10 years |
|
|
| L3 | Program Director / Head of Platform | 9–15 years |
|
|
| L4 | VP / Director of CRM & Digital Transformation | 12+ years |
|
|
Its own track, not another name for administration. Focus: discovery, business process design, requirements, solution shaping, user acceptance, adoption and measurable outcomes. Business analysts connect business users with administrators, developers, architects and delivery leaders.
| Level | Title | Experience | Core competencies | Certifications |
|---|---|---|---|---|
| L1 | Junior Business Analyst | 0–2 years |
|
|
| L2 | Salesforce Business Analyst | 2–5 years |
|
|
| L3 | Senior Business Analyst / Product Owner | 5–9 years |
|
|
| L4 | Lead Business Analyst / Business Architect | 9+ years |
|
|
From the administrator track: senior administrators who master cross-cloud design move toward the Solution Architect path — extending declarative mastery into end-to-end application architecture.
From the developer track: senior developers who master integration, identity and lifecycle governance move toward the System Architect path — extending engineering into enterprise-scale design.
Where the paths converge: the Certified Technical Architect (CTA) — the highest Salesforce credential — sits at the top of both bridges, requiring mastery across data, security, integration and multi-org strategy.
From the business analyst track: lead business analysts who master cross-cloud solution shaping, data, security and integration trade-offs can move toward Solution or Business Architecture while retaining a business-outcome perspective.
Where the handoff happens: when business logic exceeds what declarative Flows can handle — high-volume transaction processing, custom API endpoints, complex algorithms, or custom UI beyond standard Lightning pages — the work moves from Administrator to Developer.
Complementary, not hierarchical: a Lead Administrator is not “below” a Senior Developer — the tracks hold distinct, parallel expertise. Enterprises rely on senior administrators to prevent unnecessary custom code and its maintenance overhead.
Architecture caps both: the architect track is a third discipline, not a promotion. Solution and Technical Architects step back from hands-on delivery to own design, governance and risk across everything the other two tracks build.
Leadership owns the outcome: leadership does not replace technical authority. It owns why the work matters, who will deliver it, what it costs and whether the program realizes business value.
Business analysts define the need: business analysts own discovery, requirements, process design and adoption; administrators and developers own the configured or coded implementation, while architects govern the solution across systems.
| Dimension | Developer Track | Architect Track |
|---|---|---|
| Primary question | “How do we engineer this component cleanly and reliably?” | “Should we build this, configure it, or buy an external service?” |
| Deliverables | Apex classes, Lightning Web Components, unit tests, pull requests. | Architecture diagrams, trade-off matrices, governance frameworks, data models. |
| Scope | Single org, sprint backlog, one specific technical workstream. | Multi-org, multi-cloud, cross-system enterprise landscape. |
| Accountability | Code quality, test coverage, execution performance. | Long-term technical debt, risk, scalability and system cost. |