M02 — Discover Salesforce Roles and Careers
One of the traps when you start is thinking that “working in Salesforce” means one single thing. It does not.
Some roles are more functional, some more technical, some more analytical, some more commercial, some closer to processes, some closer to customers and some closer to code. Each one rewards different strengths.
If you come from another sector, this matters. Your previous experience can give you clues about where you may fit better, but you need to understand the options before choosing your first door.
Do not choose by hype. Choose by fit.
There is one distinction worth understanding early: your professional role and your certification are not the same thing.
A certification gives you a base to defend conversations. Your role depends on the project, the company, your experience and the responsibilities you end up taking on.
In a large company, responsibilities may be more separated: administrator, business analyst, consultant, project manager, developer, architect… In a medium consulting firm, however, one person often becomes quite multi-role. You may touch analysis, configuration, client meetings, documentation, testing, training and follow-up.
That does not mean improvising. It means your base must be solid.
And for a career changer, the most realistic base is usually Admin.
Salesforce Administrator
Admins configure and maintain the platform: users, permissions, objects, fields, layouts, reports, dashboards and automations.
From the outside, it can look like a buttons role. From the inside, it feels different.
Creating a field is easy. Knowing whether that field should exist, who should see it, how it affects data, reporting, security, process and maintenance… that is where judgment begins.
That line separates someone who only knows how to touch the tool from someone who is starting to think like a consultant.
If you come from outside the sector, your first opportunity will probably be close to administering, maintaining or improving existing orgs. It does not sound epic, but it is a very real entry point. And a very good school.
Functional Consultant
Functional consultants connect business needs with Salesforce solutions.
They listen, ask, structure, spot gaps, translate conversations into requirements and help turn them into configuration, processes or functional design.
It is not a “less technical” role. It is technical in another way. It requires understanding the platform, but also business, people, priorities, constraints, adoption and internal politics. Yes, politics. That comes in the package too, even if nobody puts it in Trailhead.
If you come from sales, operations, consulting, projects, account management or client-facing work, this may be a strong fit.
Business Analyst
Business Analysts help the team understand the problem better before anything gets built.
They document processes, gather requirements, find friction points, structure conversations and turn chaos into clarity.
It may sound less “Salesforce” from the outside, but in real projects it is huge. Building the wrong thing with confidence is still building the wrong thing.
A good BA stops the team from building nonsense with confidence.
And that, funny as it sounds, saves money.
Developer
Developers work with code: Apex, Lightning Web Components, integrations and custom logic.
It is a strong path if you come from software or deliberately want to move toward programming. But it is not mandatory to enter Salesforce.
Moving into tech does not automatically mean becoming a developer.
If you are a senior career changer from business, this is probably not your initial war. Not because you cannot learn, but because you would be competing with people who already come from IT, with years of technical base and much more traction on that side.
Do not compete where you are weak out of pride. Enter where you can become strong.
Solution Architect
Architects design full solutions: products, data, security, integrations, scalability and high-impact decisions.
It is a useful reference point to understand where a career can grow, but it is not usually an entry point.
Architecture is far away. Developer is on the other side of the street if you do not come from code. Your first focus should be building base, judgment and credibility.
Roles and certifications are not the same
This idea matters:
You may have the Admin certification and end up doing Admin, BA, functional consultant or even project coordination tasks depending on your experience and context.
The certification does not decide everything. It gives you language, base and initial legitimacy.
Experience and the project decide the real role you occupy.
That is why you should not obsess over the perfect label. You should understand what problems each role solves and where you can bring more value.
Quick map
| Role | Focus | If you come from… | Common risk |
|---|---|---|---|
| Administrator | Platform configuration, operations and maintenance | Administration, support, operations, business | Thinking it is only buttons |
| Functional Consultant | Business-to-Salesforce translation | Sales, consulting, projects, operations | Thinking it is “less technical” |
| Business Analyst | Process and requirement clarity | Management, training, analysis, client work | Thinking it is not a Salesforce role |
| Developer | Code, components and integrations | IT, software, programming | Thinking everyone must start here |
| Solution Architect | End-to-end solution design | Senior project experience | Treating it as an entry-level goal |
Before moving on
Pick two roles that feel close and read two real job descriptions for each.
Write down:
- skills that repeat;
- business problems that appear;
- parts that connect with your background;
- parts that still feel far away.
The important question is not “which role sounds more impressive?”.
The better question is: “which first role could I explain with more credibility?”.