The hiring process
| Round | Format | What's tested |
|---|---|---|
| Online Assessment (HackerRank/CodeSignal) | ~60 min | DSA filter on medium problems |
| Technical Coding Round 1 | ~45-60 min | Live DSA with an engineer |
| Technical Coding Round 2 | ~45-60 min | Second DSA round, harder or applied |
| System Design (HLD) | ~45-60 min | CRM-scale architecture and data |
| Hiring Manager Round | ~45 min | Production judgment and team fit |
Process and cutoffs vary by drive/team and change over time — confirm on the official careers page.
Round-by-round: exactly what's asked & how to prepare
Online Assessment (HackerRank/CodeSignal)
~60 minA timed OA with 2-3 problems that must be solved cleanly. It's a genuine filter: partial solutions rarely pass. Expect array/string/hashing-heavy problems solvable in the time limit.
- Hash-map frequency and grouping problems
- Two-pointer or sliding-window on arrays/strings
- Interval or sorting-based logic
- Basic graph traversal (BFS/DFS)
- String parsing with tricky edge cases
- Master sliding window, two pointers, and hash maps (NeetCode 150, free)
- Do timed HackerRank sets to build submission speed
- Practice handling all edge cases before submitting
- Review complexity analysis so you pick the right approach fast
- Running out of time by over-thinking problem one
- Submitting code that fails hidden edge cases
- Not reading constraints to gauge required complexity
- All test cases passing within time
- Efficient approach chosen quickly
- Clean, readable submission
Technical Coding Round 1
~45-60 minA live medium problem, often on graphs, stacks, or two-pointer patterns. The interviewer probes your reasoning, complexity, and edge-case handling as you code.
- Graph connectivity or shortest-path variant
- Stack-based parsing or monotonic stack
- Two-pointer on sorted data
- Tree traversal with a twist
- Hash-map design problem
- Practice graphs and stacks specifically (they recur)
- Rehearse thinking out loud while coding
- Prepare a clear edge-case + complexity closing routine
- Do mock interviews on Pramp or interviewing.io (free tiers)
- Silent coding with no narration
- Skipping complexity discussion
- Not verifying with a test case
- Clear articulation of approach and trade-offs
- Correct complexity analysis
- Clean, bug-free implementation
Technical Coding Round 2
~45-60 minA second coding round, sometimes slightly harder or more applied, occasionally touching object modeling. Consistency across both coding rounds is what advances you.
- Medium-plus DP or greedy problem
- Design a small in-memory structure with operations
- Graph problem framed around entity relationships
- String matching or transformation
- Follow-up extending the base problem
- Add DP and greedy patterns to your rotation
- Practice extending solutions when constraints change
- Time-box getting to a working solution, then optimize
- Review your OA/round-1 mistakes and drill them
- Freezing on a harder variant instead of stating a brute force first
- Inconsistent performance vs round one
- Poor code hygiene under pressure
- Stable performance matching round one
- Ability to start simple and improve
- Adapts cleanly to follow-ups
System Design (HLD)
~45-60 minFor MTS and above, a design round often anchored in Salesforce's domain: syncing millions of CRM records reliably, deduplication, event-driven notifications, and consistent search indexing. You scope, architect, and defend trade-offs.
- Design a contact/account dedup and merge system
- Event-driven notification pipeline at scale
- Consistent search indexing over CRM data
- Multi-tenant data isolation and sharding
- Reliable sync between systems with retries
- Study multi-tenancy, sharding, and event queues
- Learn dedup/merge and idempotency patterns
- Practice with system-design-primer (free)
- Do 2 mock designs framed around data sync/search
- Ignoring multi-tenancy and data isolation
- No plan for consistency or retries
- Diving into detail before scoping requirements
- Domain-relevant, reasoned architecture
- Explicit consistency and failure handling
- Clear trade-off communication
Hiring Manager Round
~45 minA conversation with the hiring manager going deep on how you debug production systems, maintain services, and collaborate. Behavioral questions map loosely to Salesforce's values.
- How you'd debug a live production incident
- Owning long-term service health and upkeep
- A hard technical decision and its trade-offs
- Working across teams under conflicting priorities
- Why Salesforce and this team
- Prepare an on-call/incident story with concrete steps
- Have 4-5 STAR stories ready
- Read about Salesforce's V2MOM and values
- Prepare specific questions about the team's systems
- Hand-wavy incident-debugging answers
- No concrete ownership examples
- Generic motivation with no research
- Structured, methodical debugging reasoning
- Real ownership of service reliability
- Collaborative, low-ego communication
What to master
- Arrays, strings, hashing
- Sliding window and two pointers
- Graphs (BFS/DFS, connectivity)
- Stacks and queues
- Dynamic programming and greedy basics
- Multi-tenancy, sharding, event queues
- Dedup/idempotency and search indexing
- Production debugging and STAR stories
Eligibility
SWE/MTS and above; system design and hiring-manager rounds appear once both coding rounds are cleared and scale with level.
Salesforce SWE salary & compensation (2026)
Competitive comp; RSU refreshers plus bonus; India (Hyderabad/Bengaluru) growing.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| AMTS (SWE) | 0–2 yrs | ₹22–38 LPA | $150K–195K | base + RSUs + ~10% bonus |
| MTS | 2–4 yrs | ₹38–65 LPA | $195K–270K | stock + bonus grow |
| SMTS (Senior) | 4–8 yrs | ₹65–115 LPA | $280K–390K | RSU share rises |
| Lead MTS | 8–12 yrs | ₹115–190 LPA | $400K–560K | equity-heavy; higher bonus target |
| Principal MTS | 12+ yrs | ₹190–320 LPA | $560K–780K | large refreshers |
How the package is structured
- US split ~ base 55–62%, RSUs 25–35%, bonus 10–15%
- Annual RSU refreshers; bonus scaled by company + individual performance
- India comp ~ 40–50% of US at same level
- SMTS is the common senior terminal level; Lead/Principal are steep jumps
Indicative 2026 market ranges aggregated from public sources (levels.fyi, Glassdoor, AmbitionBox, candidate reports). Compensation varies widely by location, team, level calibration, and negotiation — use these as directional benchmarks, not guarantees.
Your prep plan
- Days 1-3: Master arrays/strings/hashing + timed OA sets
- Days 4-6: Graphs and stacks deep practice
- Days 7-8: DP/greedy medium problems
- Days 9-11: System design on data sync/dedup/search
- Days 12-13: STAR + production-debugging stories
- Day 14: Full mock loop and review
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview.
Get my personalized planFrequently asked questions
How hard is the OA filter?
It's a real gate. You generally need clean, fully-passing solutions to 2-3 medium problems, so practice under time pressure.
What DSA topics matter most?
Arrays, strings, hashing, sliding window, two pointers, and graphs come up most; stacks and DP appear in the harder round.
Is system design needed for entry-level?
For MTS and above it's standard; more junior loops may be coding-heavy with lighter design. It scales with level.
What is the hiring-manager round really testing?
Practical judgment: how you debug production, keep services healthy, and collaborate. Bring concrete, structured examples.
What is V2MOM and should I know it?
It's Salesforce's planning framework (Vision, Values, Methods, Obstacles, Measures). Knowing it signals cultural awareness in the HM round.
How long does the process take?
Usually about 2-4 weeks, faster or slower depending on scheduling and level.