Salesforce Admin vs. Consultant vs. Architect: What Recruiters Need to Know

A recruiter presented me for a "Senior Admin" role last month. I am a 13x certified Architect. The salary was $40K below my range. The job involved resetting passwords and running reports.

This happens constantly. Not because recruiters are malicious. Nobody taught them that "Salesforce professional" covers at least four completely different roles at four completely different price points, solving four completely different kinds of problems.

Here is the breakdown that should have existed years ago.

The Four Tiers

Administrator ($70K-$110K, 1-5 years typical): Configures the platform using clicks, not code. Manages users, security, reports, dashboards, and automations (Flows). Day-to-day operators. They answer: "How do I build this in Salesforce?"

Developer ($100K-$150K, 2-8 years typical): Writes custom code: Apex, Lightning Web Components, Visualforce, API integrations. Builds what configuration cannot. They answer: "How do I code this for Salesforce?"

Consultant ($100K-$140K, 3-8 years typical): Gathers business requirements, designs solutions, manages implementations. Sits between business stakeholders and technical teams. Needs both technical depth and communication skills. They answer: "What should we build and why?"

Architect ($140K-$200K+, 5-15 years typical): Designs overall technical strategy across entire Salesforce environments. Data models, integration patterns, security architecture, platform governance. They answer: "How should the whole system work together?"

What Each Role Touches Daily

Admins live in Setup: Flow Builder, Report Builder, Data Loader, user management. Their output is configured features, reports, and Flows. They talk to end users and managers.

Developers live in VS Code: Apex classes, triggers, LWC components, test classes, GitHub. Their output is custom code, API integrations, and deployed packages. They talk to other developers and tech leads.

Consultants live in documents: Google Docs, Lucidchart, Jira, presentations. Their output is functional specs, solution designs, and training materials. They talk to business stakeholders and project managers.

Architects live in diagrams: ERD tools, integration architecture documents, governance frameworks. Their output is architecture decisions, data models, and technical strategy. They talk to CTOs, project sponsors, and vendor teams.

Task Complexity by Role

Simple work: Admin handles user setup and reports. Consultant documents requirements. Architect reviews existing architecture.

Moderate work: Admin builds Flows and approval processes. Consultant leads discovery sessions and writes specs. Architect designs data models for new features.

Complex work: Admin builds multi-object Flows with error handling. Consultant runs full lifecycle implementations with change management. Architect creates multi-org strategy and enterprise integration architecture.

Do not assign: Admins should not write custom code or design system architecture. Consultants should not write Apex. Architects should not handle day-to-day configuration or user support. Misassigning complexity is how projects fail and placements go bad.

When to Present Up or Down

Admin for Consultant role: Works if 3+ years, client-facing experience, and demonstrated requirements gathering skills. Does not work if the candidate has only done internal admin work.

Consultant for Architect role: Works if 5+ years, multi-org experience, and integration or data model design. Does not work with only single-org implementations.

Developer for Consultant role: Rarely works. Developers and consultants solve different types of problems with different skill sets. Strong communication skills in a developer are the exception.

Architect for Consultant role: Works if the candidate wants to step back (lifestyle change, travel reduction). Architecture skills translate downward cleanly. Expect pushback on rate.

How to Tell If Someone Is Lying About Their Role Level

For Admin candidates: "What happens when you deploy a Flow from sandbox to production?" Real: Describes change set or Salesforce DX deployment. Notes Flow must be activated separately in production. Mentions checking for conflicting automations. Fabricated: Cannot describe the deployment process, or says "I built everything directly in production." Building in production signals no professional deployment standards.

For Consultant candidates: "Walk me through a discovery session you led." Real: Describes specific questions asked: business problem, users, current process, success criteria. Names the stakeholders and the deliverable (requirements doc, process map, user stories). Fabricated: "I gathered requirements" without describing the process, the questions, or the output. Consultants who have led discovery can reconstruct the conversation. Those who only observed cannot.

For Architect candidates: "You inherit an org with 400 custom objects and 200 Flows. Where do you start?" Real: Systematic assessment: audit automation inventory, map object relationships, identify technical debt, review governor limit usage, assess security model. Prioritizes risk (what could break) before optimization (what could be better). Fabricated: "I would clean it up" or "I would start rebuilding." An architect does not start building. An architect starts assessing. The instinct to understand before acting is what separates architects from everyone else.

Quick Reference

	Admin	Developer	Consultant	Architect
Salary	$70-110K	$100-150K	$100-140K	$140-200K+
Key Cert	Admin/Adv Admin	Platform Dev I/II	Cloud Consultant	Architect certs
Client-Facing?	Sometimes	Rarely	Always	Always
Codes?	No	Yes	Sometimes	Sometimes
Designs Systems?	No	No	Partially	Yes

Part 8 of a 10-part series. Previously: Nonprofit Cloud Screening Guide. Next: Certification Decoder

---

Jeremy Carmona is a 13x Salesforce certified architect, founder of Clear Concise Consulting, and adjunct instructor at NYU Tandon School of Engineering.

Free Download of Salesforce Admin vs. Consultant vs. Architect Guide