Salesforce — SWE Assessment: Pattern, Syllabus & Mock Test
Salesforce — SWE Assessment pattern: 2 questions in 75 minutes across 1 section. Sample questions, a preparation guide and a free timed mock.
- Pattern: Salesforce
- Duration: 75 minutes
- Questions: 2
- Timing: Free — move between sections until the paper's clock ends
- Negative marking: None
Two problems written as stories rather than puzzles. India-gated, and purely coding.
- Pure coding
- Narrative problems
- India-gated
Sections
| Section | Questions | Time | Kind | Marks each |
|---|---|---|---|---|
| Coding | 2 | 75 min | Coding | 10 |
Salesforce — SWE Assessment syllabus
Coding: Salesforce coding questions 12 problems
Instructions
Salesforce runs an India-gated HackerRank assessment: two coding problems, seventy-five minutes, no aptitude section.
- The problems read as narratives, not textbook data-structure puzzles. They describe a scenario to simulate, and an efficient solution is still required.
- The two are not worth the same. The reported split is fifty points for the first and seventy-five for the second, out of a hundred and twenty-five.
Some 2025 and 2026 drives add an AI interviewer component after this round.
How to prepare for this pattern
A guide to the Salesforce software engineering assessment pattern: two narrative coding problems in seventy-five minutes, with no aptitude section.
What the paper looks like
One section: Coding, two problems of medium difficulty in 75 minutes on a shared clock; the real assessment is India-gated and runs on HackerRank. You can move between the two problems freely. There is no aptitude section and no negative marking, and the paper is not adaptive. The problems read as narratives rather than textbook data-structure puzzles: they describe a scenario to simulate, and an efficient solution is still required. In the real assessment the two are not worth the same; the reported split is 50 points for the first and 75 for the second, out of 125. This mock marks both equally, ten marks each, graded on the test cases passed. Duration is reported as 60 minutes in 2024 and 75 in 2025, and this mock uses 75.
How to prepare, section by section
- Coding. The first skill a narrative problem tests is translation: reading a paragraph of scenario and seeing the data structure underneath it. The Simulation hub is the closest practice, since its problems are solved by doing exactly what the statement says while keeping every piece of state right. Behind the story, the usual tools are Hash Table, Sorting, Heap, Queue, Intervals and Greedy, with Arrays and Strings underneath them all. After each practice problem, write one line saying what the story reduced to, such as "a queue of events processed in time order"; that habit is what makes a real problem quick to read. The DSA roadmap covers the underlying techniques in order.
- Language. Narrative problems often mean modelling a few entities, so be comfortable defining a small class in your language; the Java, Python, C++ and JavaScript study plans all cover classes.
On the day
Read both problems fully before choosing where to start. A narrative takes longer to read than a puzzle, and misreading one rule costs more than the minutes spent reading carefully. In the real assessment the second problem is worth more, so do not let the first consume the clock: thirty-five minutes on the first leaves forty for the second. Write the rules of each scenario down as a short list before coding, then check your solution against each rule. Because marks come per test case, submit a working version early and improve it, rather than holding back an unfinished efficient one.
This mock is modelled on Salesforce's published India assessment, crowd-sourced but consistent across candidate reports; CodeKairo is not affiliated with Salesforce.
About this pattern
Crowd-sourced but consistent across several candidate threads. Duration is reported as 60 minutes in 2024 and 75 in 2025; the 50 and 75 point split is repeatedly confirmed. This paper marks both problems equally.
Modelled on the published pattern; not affiliated with Salesforce. Every sitting draws a fresh paper from the aptitude bank and the problem catalogue.