What Salesforce is and the roles around it
Understand what Salesforce actually is (a cloud platform, not just a CRM app), how its products fit together, and which jobs exist around it, so you can pick a learning path with your eyes open.
Most people first hear of Salesforce as "a CRM". CRM means Customer Relationship Management: software that stores who your customers are, what you sold them, what they asked for and what happens next. A shop owner might do this in a notebook. A company with 5,000 salespeople needs software.
Salesforce started as a cloud CRM, which means you use it in a browser with nothing to install. Over time it grew into a platform: a place where companies also build their own apps on top of the same data, security and automation. That second part is why Salesforce has developers, not only users.
Two ways to look at Salesforce
Product versus platform
| View | What it means | Example |
|---|---|---|
| Ready-made products (clouds) | Apps for a business function that you configure | Sales Cloud tracks leads and deals; Service Cloud handles customer support cases |
| Platform | The foundation the products run on, which you can extend | A custom "Coffee Order" object, a Flow that sends an alert, an Apex trigger, a Lightning Web Component |
The products you will hear about most are Sales Cloud, Service Cloud, Marketing Cloud, Commerce Cloud and Experience Cloud (portals and websites for customers or partners). Salesforce also owns Slack, Tableau (analytics) and MuleSoft (integration), and has been adding AI features under the Agentforce name. Product names change often, so treat any list as a snapshot and check Salesforce's own site for the current one.
This track focuses on the platform, because the same skills (data model, security, Flow, Apex, LWC) apply to every cloud.
How the platform is built
Three ideas explain why Salesforce behaves the way it does.
Multitenant. Many customers share the same underlying infrastructure, like flats in one building. Each customer's data is separate, but they share the same running code. To keep one tenant from slowing down the others, Salesforce enforces governor limits: caps on how much work one piece of code can do in one go. You will meet these in the Apex lessons.
Metadata-driven. When you create an object, a field or a page layout, you are not changing the Salesforce code. You are saving a description (metadata) of your app, and the platform reads it to build the screens, database tables and APIs. That is why an admin can build a working app by clicking, with no code.
Org. An org is one customer's own copy of Salesforce: their data, settings and customisations. You will practise in your own free org (next lesson). Companies usually have a production org plus sandboxes, which are copies for building and testing safely.
Salesforce releases three major updates a year, named after seasons (Spring, Summer and Winter). Features are added automatically to your org, so release notes are worth skimming.
Clicks, then code
Salesforce teaches a habit that is also good interview advice: use clicks before code. Declarative tools (objects, fields, validation rules, Flow, reports) are built by configuring. Programmatic tools (Apex, Lightning Web Components, APIs) are built by writing code. Use the simplest tool that solves the problem, because declarative solutions are quicker to build, easier for the next person to maintain, and upgraded by Salesforce for you.
Code is for what clicks cannot do: complex logic, custom user interfaces, calling external systems and large data processing.
Which tool for which job
| Need | Usually reach for |
|---|---|
| Store a new kind of data (orders, events) | Custom object and fields |
| Stop bad data being saved | Validation rule |
| Do something automatically when a record changes | Record-triggered Flow |
| Guide a user through a form | Screen Flow |
| Show numbers to managers | Report and dashboard |
| A custom screen the standard UI cannot give | Lightning Web Component |
| Heavy logic or complex rules | Apex |
Roles in the Salesforce ecosystem
Common jobs
| Role | What they do | Skills to learn |
|---|---|---|
| Administrator | Configures and runs the org: users, security, objects, Flow, reports | Setup, data model, security, Flow, reports |
| Platform App Builder | Designs custom apps with clicks | Data model, UI, automation |
| Developer | Writes Apex, LWC and integrations; works with DevOps tools | SOQL, Apex, JavaScript, Git, Salesforce DX |
| Business Analyst | Turns business needs into requirements and user stories | Process mapping, communication, basic config |
| Consultant | Works with clients to implement a cloud (often at an IT services firm) | One cloud in depth, workshops, configuration |
| Architect | Designs large solutions: security, data volumes, integration | Years of experience across the platform |
Salesforce skills are used widely in India, in product companies, IT services firms and consultancies. Many people start as an admin or junior developer and move across. Job titles overlap a lot between companies, so read job descriptions rather than trusting titles.
How this comes up in interviews
Fresher interviews often start with plain questions: "What is Salesforce?", "What is an org?", "What does multitenant mean?", "What is the difference between declarative and programmatic development?" A good answer is short and concrete. Try this one:
"Salesforce is a cloud platform best known for CRM. Companies run it as an org, which is their own configured copy on shared multitenant infrastructure. You can build much of an app with clicks (objects, Flow, reports) and use Apex and Lightning Web Components for what clicks cannot do. Because it is shared, governor limits stop one customer's code from using too many resources."
I'm a [your background, e.g. 2nd-year B.Tech CSE student who knows Java] and I'm new to Salesforce.
Explain what [topic, e.g. an org, a sandbox, or governor limits] is, using an analogy from [a familiar area, e.g. a college or a restaurant]. Then show how it appears in a real company's Salesforce setup. Keep it under 200 words and end with one question to check my understanding.What to expect: Check the answer against Salesforce Help or Trailhead. Models sometimes mix up old and new product names or invent limits.
Try it: Find your path
Open three Salesforce job listings in India (a job site or LinkedIn). For each, write down the role title, the three skills mentioned most and whether it asks for admin, developer or consulting work. Then decide which of the roles in the table you want to aim for first and why.
Key takeaways
- Salesforce is a cloud platform: ready-made products (clouds) plus tools to build your own apps on the same foundation.
- An org is one customer's copy of Salesforce; sandboxes are safe copies for testing.
- The platform is multitenant and metadata-driven, which is why governor limits exist and why admins can build apps with clicks.
- Use clicks before code: choose the simplest tool that solves the problem.
- Main roles are admin, app builder, developer, business analyst, consultant and architect; admin skills are a strong first step.
Check yourself
Finishing the quiz marks the lesson as done.
1. What does it mean that Salesforce is "multitenant"?
2. A manager wants an email-style alert task created whenever an order's status becomes Ready. What does the "clicks before code" habit suggest?
3. Why can an admin create a working app without writing code?
4. What is a sandbox?
5. Which role mainly writes Apex and Lightning Web Components?
Saved on this device. Create a free account to keep it on every device.
Practise this with Sam
A real mock interview, out loud, with an honest scorecard. Free to start.