Salesforce is the global leader in cloud CRM and AI-powered customer platforms - Einstein, Agentforce, and Data Cloud sit at the center of its product story. Founded in 1999 in San Francisco, with India engineering hubs in Hyderabad, Bengaluru, and Mumbai hiring AMTS / Software Engineer talent through Futureforce and campus drives.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Salesforce is a product-engineering bar with a values tax. Meeting CGPA only gets you into the funnel - the HackerRank OA and interview depth decide offers.
Academic requirements
Marks: 7.0+ CGPA commonly cited; 7.5+ on many 2026 AMTS drives
Degree: B.Tech / B.E. / M.Tech / MCA (or as per notice)
Year of Study: Final-year students and recent graduates
Backlogs: No active backlogs preferred / as printed in JD
Branch & skills
Preferred: CS / IT and related streams
Also compete: Other branches with proven coding depth
Languages: Java, Python, C++
Focus: Timed DSA, OOP, light SaaS design, project ownership
Minimum CGPA required (candidate-reported): 7.0+ CGPA commonly cited, with 7.5+ on many 2026 AMTS drives. Treat this as a shortlisting floor when printed - Salesforce still filters heavily on assessment and interview performance. Recent-cycle chatter is stable enough that you do not need separate 2025 vs 2026 eligibility FAQs - verify the notice in front of you.
| Academic Level | Typical floor (candidate-reported) | Notes |
|---|---|---|
| Graduation | 7.0+ commonly; 7.5+ on many AMTS JDs | Confirm on campus JD / careers post |
| 10th / 12th | Often aligned when the JD lists all three | Consistency across years matters |
| Backlogs | Usually none active at joining | Offer-stage verification |
Good fit: You triage HackerRank problems in three minutes, write custom tests before submit, can defend one project with metrics, and have real STAR stories for Trust and Customer Success - not slogan bingo. Internships help; a measurable personal project beats a vague CRM buzzword resume.
Harder path: You confuse SWE OA with Admin certification prep; you over-invest in the hardest graph while an easy array case fails; your Why Salesforce is “brand + CTC.” Values rounds are real interviews.
Branch myth: Non-CS students clear AMTS when DSA is real and the JD allows related streams. Branch does not replace hidden-test discipline.
Locations: Hyderabad, Bengaluru, and Mumbai dominate India engineering chatter. Say constraints early.
Futureforce path: Early-career / campus-adjacent programs feed AMTS pipelines. Same OA bar - Futureforce is a channel, not a shortcut past coding.
Cert theater warning: Trailhead badges are fine for Admin paths. For AMTS SWE, a wall of badges with a weak OA is still a reject.
Download 2026 Salesforce placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Salesforce does not publish one permanent official paper. Previous-year style practice targets the HackerRank OA and early technical rounds - medium-hard DSA with hidden tests - not Apex trivia.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed DSA correctness under HackerRank constraints |
| Technical interviews | Live coding + complexity + project depth |
| Values / behavioral | STAR stories mapped to Salesforce values |
| HM / HR | Why Salesforce, location, offer logistics |
How to use a paper: time the full window; mark guessed items; rewrite anything that would fail hidden tests; log misses by pattern. Three reviewed papers beat ten skimmed ones.
Year-page cheat sheet:
| Year pack | Use it for |
|---|---|
| 2024 | Baseline OA themes |
| 2025 | Updated mixes and pattern notes |
| 2026 | Expected HackerRank pattern + AMTS focus |
Campus and Futureforce hiring often clusters around placement season; off-campus AMTS openings also appear year-round on Salesforce Careers. Same coding bar either way.
Campus / Futureforce
College placement cells and Futureforce early-career programs - PPT, then OA and interviews.
Online applications
Apply on Salesforce Careers for AMTS / Software Engineer and related early-career roles.
Referrals
Employee referrals improve resume visibility; the OA bar stays the same.
Resume screening - Academics, projects, internships; CGPA/backlog rules from the JD.
Online assessment (~75-120 min) - Usually HackerRank. Commonly 1-3 medium-hard DSA problems; some drives add CS MCQs. Languages: Java, Python, C++. Hidden tests and timeouts reject more candidates than “unknown topics.”
| Section | Questions | Time | Difficulty | Focus |
|---|---|---|---|---|
| Coding problem 1 | 1 | 30-45 min | Medium | Arrays, strings, hashing, two pointers |
| Coding problem 2 | 1 | 35-50 min | Medium-Hard | Trees, graphs, heaps, DP |
| Optional third / harder variant | 0-1 | Remaining | Harder | Constraint escalation |
| CS MCQs (if present) | Varies | Shared window | Easy-Medium | OOP, DBMS, OS, complexity |
Technical interview 1 (45-60 min) - Live coding, approach-first narration, edge cases, complexity.
Technical interview 2-3 (45-60 min each) - Harder DSA or multi-part problems, project deep-dive, light SaaS/CRM design (APIs, multi-tenancy, notifications), OOP/SQL follow-ups.
Values / behavioral (30-45 min) - Trust, Customer Success, Innovation, Equality, Sustainability with real STAR stakes.
Hiring manager / HR (30-45 min) - Role fit, Why Salesforce, location (Hyderabad / Bengaluru / Mumbai), compensation and joining.
Often 2-6 weeks for campus / Futureforce batches (off-campus can stretch longer).
| Phase | Duration | Key activities |
|---|---|---|
| Resume screening | 3-14 days | Campus shortlist / portal review |
| Online assessment | 1 day | Timed HackerRank DSA |
| Interview scheduling | 2-7 days | Technical loop coordination |
| Technical rounds | 1-2 weeks | 2-3 interviews |
| Values + HM/HR | 3-10 days | Culture fit, CTC, location |
If you only remember three numbers: HackerRank OA first, values round is real, fresher CTC band ₹25-40 LPA (candidate-reported).
Practice 25-35 minute sketches:
Weak: “I believe in customer success and teamwork.” Stronger: Situation with a real user/customer stake, the trade-off you refused, the outcome, and what you would institutionalize next time. Map explicitly to Trust or Customer Success.
Prepare 8-10 STAR stories covering Trust, Customer Success, Innovation, Equality, and Sustainability. Rehearse out loud - values rounds punish reading essays.
Most people treat values as “HR fluff after the hard part.” At Salesforce, Trust and Customer Success stories are graded. If your only prep is DSA, you can clear OA and still stall when asked for a time you protected user trust. Write stories from real college projects, internships, or club work - inventing ethics theater is obvious.
Practice format: 90 seconds spoken, then a friend asks “what would you do differently?” If you cannot answer without slogans, rewrite the story.
You do not need Platform App Builder for AMTS SWE. You do need enough product vocabulary to sound specific:
Pick one line that matches your interests and prepare a 30-second engineering angle (multi-tenancy, API limits, notification reliability, inference latency, trust). That beats Wikipedia recitation.
Java is common on invites. Watch:
If you are Python-first, still learn to read Java snippets for interview discussion - some interviewers switch languages mid-loop.
2024: HackerRank coding-first OAs, 2-3 technicals, managerial/values, HR; packages in the ₹25-40 LPA fresher chatter band; some SDE stories citing ~₹35 LPA.
2025: same skeleton; more AI vocabulary in Why Salesforce; OA still DSA; intern paths with stipends near ₹1.1 lakh/month in some reports.
2026 implication: keep medium-hard DSA sharp, practice HackerRank UI, build values STAR early (not the night before), and add one Agentforce/Data Cloud talking point for HR.
Practice banks include first non-repeating character, merge lists, Kadane, cycle detection, anagrams, BST validate, top-k words, decode string, interval free time - treat as families, not prophecy.
Reply professionally, confirm slots, start mocks within 48 hours. Re-read resume as an interviewer would. Rebuild project demo with metrics. Draft values stories you can speak, not read. If rounds span multiple days, protect sleep - cognitive fatigue fails strong coders.
Weak: “I built a CRM clone.” Stronger: “I modeled accounts and opportunities with clear ownership rules, added rate-limited webhooks for status changes, and cut duplicate notifications by introducing an idempotency key - duplicate rate dropped from X% to Y% in staging.”
Weak: “I know Salesforce.” Stronger: “I’m excited about Agentforce-style assistants, but I’m applying as an AMTS engineer - my proof is timed DSA and a multi-tenant side project, not Admin clicks.”
Campus PPT weeks feel intense - use peer mock partners. Futureforce timelines can be clearer but still competitive. Careers applications without referrals may sit longer; a tight resume with 2-3 defensible projects helps more than a generic “passionate about CRM” summary.
Do not over-invest here relative to OA mocks - but do not arrive blank when MCQs or follow-ups appear.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a Salesforce invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Salesforce sits around ₹25-40 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): From student reports for 2026: many campus and Futureforce AMTS drives cite 7.0+ CGPA generally, with a large share of AMTS notices listing 7.5+ CGPA and no active backlogs. Degree typically B.Tech/B.E./M.Tech/MCA. Strong timed DSA matters as much as academics. Verify your campus JD or Salesforce Careers posting.
What you are training for: Resume/campus shortlist → HackerRank-style OA (~75-120 min, 1-3 medium-hard DSA, sometimes CS MCQs) → 2-3 technical interviews → Values/behavioral → Hiring Manager/HR. Timeline often 2-6 weeks for campus/Futureforce batches.
Short version of the prep split: Master the HackerRank OA with timed medium-hard DSA (~60% prep), run full OA mocks (~15%), prepare STAR stories mapped to Salesforce values (~15%), and revise OOP/SQL/OS plus one CRM/SaaS design prompt (~10%). Use papers and mocks on this site.
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the Salesforce previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Salesforce drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Salesforce usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Salesforce?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Salesforce-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the Salesforce story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Salesforce papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Salesforce papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Salesforce-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Salesforce paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Salesforce. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Salesforce, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Salesforce mistakes, you are collecting content, not preparing.
Sit one more mixed Salesforce set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Sit one more mixed Salesforce set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Sit one more mixed Salesforce set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Random Salesforce problems feel productive. Timed mocks are what move the needle. If you only have an hour tonight, sit 40 minutes of a previous-year Salesforce set and spend 20 minutes on the three misses. That loop beats an untimed 8-problem grind you will not remember tomorrow.
Do not reread the whole Salesforce hub. Skim eligibility once, open your error log, and recast the two STAR stories you will actually say. If the drive names an OA platform, click around it for five minutes so login panic is not your first round.
One useful Salesforce drill: you set a 25-minute timer, your friend picks a question from this site, you talk the approach before typing. Swap. You will hear the holes an interviewer hears. Do this twice a week in the last fortnight, not every night.
Trust the JD and the mailer. This Salesforce page is compiled from candidate-reported patterns. When a number conflicts (CGPA floor, duration, role name), write the JD number on your notes and keep practising the skills that still overlap.
Between OA and interview, most people either panic-revise everything or do nothing. Pick three Salesforce topics from your weakest mock, one project diagram, and two behavioral stories. That is a better 48 hours than a new 200-problem list.
| Band | Typical CTC (from student reports) | Notes |
|---|---|---|
| AMTS / SWE fresher | ₹25-40 LPA | Campus / Futureforce; varies by city and equity |
| Early career (~0-2 yrs) | Often above fresher band | Intern converts / lateral; team-dependent |
Confirm base / bonus / RSU split on the written offer. Commonly discussed benefits: health coverage, Trailhead learning culture, wellness programs, and city-dependent hybrid norms.
How to read the band: ₹25-40 LPA is the AMTS/SWE fresher range students most often cite. Exact splits vary. Intern stipends (students have cited ~₹1.1 lakh/month in some SDE intern stories) are separate from FTE letters - read terms carefully.
Growth: AMTS → higher IC levels vary by org. Platform vs industry cloud vs AI-feature teams feel different - ask what you would build in year one.
Pay compare chatter: often between Oracle-like enterprise bands and top FAANG chatter, competitive among cloud CRM product roles. Still choose by product and letter.
“I have 7.2 but JD says 7.5.” You may be out on paper - ask the placement cell; do not invent eligibility.
“I only have Admin Trailhead badges.” Fine as extras; they do not replace OA coding.
“I hate behavioral interviews.” Then Salesforce is a rough target - values rounds are non-optional on many loops.
“I’m open to Hyderabad only.” Say so early; Bengaluru/Mumbai may appear on offers.
“Can referrals skip OA?” Visibility improves; coding bar stays.
Campus: PPT, reserved energy, season timelines, peer pressure useful for mocks.
Futureforce: structured early-career channel; still OA + interviews.
Careers off-campus: more calendar flexibility; slower responses; denser pools.
Technical content does not soften because the channel sounds friendlier.
Reread AMTS vs SWE title, base/bonus/RSU, location, hybrid norms, joining date, BGV docs, intern convert clauses if any. Celebrate after signatures. Ask about team domain so you know whether year one is platform plumbing or product features.
| Value | Story prompt | What interviewers listen for |
|---|---|---|
| Trust | Protected user data / refused a shady shortcut | Stakes, trade-off, outcome |
| Customer Success | Unblocked a user/customer under pressure | Impact beyond your ego |
| Innovation | Shipped a meaningful technical improvement | Alternatives considered |
| Equality | Included quieter teammates / fair credit | Specific behaviors |
| Sustainability | Reduced waste (compute, process, or literal) | Pragmatism, not slogans |
You will not be asked all five every time - but arriving with only one story is risky. Rotate practice so each value gets airtime weekly.
After a 30-minute sketch, score yourself 0-2 on each:
A 10+ score is interview-ready for fresher depth. Below 6 means more drills, not more blogs.
Active backlogs: treat as hard stops on many AMTS JDs. Cleared historical backlogs: prepare a one-line ownership answer. Gap years: own briefly and pivot to skills. Non-CS branches: compete when JD allows and DSA is real - do not rely on WhatsApp forwards for eligibility.
If Adobe, Oracle, and Salesforce drives collide in one month, protect a shared morning DSA block, then alternate evening specialties (design / SQL / values). Burning out on three companies’ PDF archives helps none of them. Two excellent mocks beat ten unread downloads every time.
Net for 2026: do not wait for a pattern rumor. Double down on timed DSA, hidden-test discipline, and values STAR stories with stakes. Calendar length matters; fundamentals decide.
Also expect more Agentforce vocabulary in HR prep notes. You do not need a research paper - you need one concrete sentence on how AI agents help customers without breaking trust or latency budgets.
If your college gets a Salesforce PPT with two weeks’ notice, freeze new topics and run OA mocks + STAR repair only. If you have three months, follow the 8-12 week plans.
Record yourself answering Why Salesforce and one Trust story on your phone. Playback once. Cringe is useful - fix filler words, add a metric, cut slogans. Then stop recording and sleep. Over-rehearsing until you sound robotic is a real failure mode; aim for natural specificity.
Also reread the JD for location and role title so HM/HR logistics answers are consistent with what you already told technical interviewers. Contradictions on relocation kill late-stage loops more often than students expect.
Yes. Free Salesforce placement papers PDF and previous-year style OA/interview practice (2024-2026) on this site - no registration. Start with the 2026 PDF and the archive. Papers train patterns; they are not leaked live exams.
Shortlist → HackerRank-style OA → 2-3 technical interviews → Values/behavioral → HM/HR. Often 2-6 weeks for campus/Futureforce batches.
Typical fresher loop includes OA, 2-3 technicals, values, and HM/HR. Some drives merge rounds. Follow your schedule.
HackerRank-style, ~75-120 minutes, 1-3 medium-hard DSA, sometimes CS MCQs. Languages Java/Python/C++. Hidden tests decide advancement. Clearing OA only shortlists you.
Salesforce’s early-career / campus-adjacent hiring channel that feeds AMTS and related roles. Expect the same coding bar as other fresher loops - Futureforce is access, not a free pass.
A real culture round on Trust, Customer Success, Innovation, Equality, and Sustainability. Use STAR stories with stakes - customer impact, ethical trade-offs, inclusive teamwork.
No for most AMTS SWE paths. Prioritize DSA and coding. Admin/declarative skills matter more for Admin or specialized consultant paths.
Map 8-10 STAR stories to the five values; practice Why Salesforce with CRM/Einstein/Agentforce/Data Cloud specifics. Bank: HR interview questions.
Common reports: 7.0+ general floor; 7.5+ on many 2026 AMTS drives; B.Tech/B.E./M.Tech/MCA; no active backlogs preferred. Notifications override blogs.
Any of Java, Python, or C++ you can debug live. Java is frequently reported on HackerRank invites.
It matches many printed floors, but OA hidden tests still decide shortlists. Skills convert offers; CGPA only opens the door.
From student reports AMTS / SWE band around ₹25-40 LPA as of August 2026. Offer letter wins.
Associate Member of Technical Staff - primary fresher/early-career engineering title for many India loops. Selected via OA + technical + values + HM/HR.
~60% DSA, ~15% OA mocks, ~15% values STAR, ~10% CS/design. Details: preparation guide.
Salesforce: CRM + AI agents; values-heavy loop; fresher CTC often ₹25-40 LPA. Adobe: Creative/Experience Cloud craft. Oracle: Databases/cloud scale and SQL depth. Choose by product fit and written offer.
Correctness first on the OA, DSA error log, one CRM/SaaS design prompt, and STAR stories mapped to Salesforce values - not generic HR answers.
The OA is the steepest filter for most candidates - hidden tests and triage mistakes sink otherwise-strong profiles. Values rounds are medium if your stories are real. Beatable with timed mocks and deliberate STAR practice.
Aim for at least 8-12 timed full OA mocks matching your invite length, plus ongoing pattern drills. Review every miss into an error log. If MCQs appear on your invite, include mixed papers - not coding-only mocks.
Salesforce: CRM + AI agents; values-heavy loop; fresher CTC often ₹25-40 LPA. ServiceNow: enterprise workflow platforms. Microsoft: broader cloud/productivity engineering, often higher fresher bands in chatter. Choose by product interest and written offer.
Usually not as the OA focus for AMTS coding paths - DSA dominates. Some role-dependent interviews may touch platform concepts later. Do not skip DSA to memorize Apex syntax for a standard SWE OA.
“I wasted 40 minutes on the hard graph problem and failed an easy array case I never opened.” Next mock I triaged in three minutes - that mattered more than another course.” - anonymized 2025 AMTS composite
Successful prep patterns: timed OA mocks, custom tests before submit, one project story with metrics/trade-offs, and values answers that sound like real work. Round-by-round stories: Salesforce interview experience.
Other write-ups also describe SDE selects with 90-minute HackerRank sets (arrays/trees/DP), then technical rounds on graphs/strings and light design (URL shortener style), plus managerial/values fit - packages cited around ₹35 LPA in one 2024 SDE story. Intern paths report stipends near ₹1.1 lakh/month in some write-ups. Treat each story as a vibe check, not a fixed paper.
What to steal: triage early; never skip easy cases; prepare values STAR before the loop starts; answer Why Salesforce with product specifics; return to timed mocks on this site instead of hoarding PDFs.
If you interview this month: map your invite to the practice map, run two full HackerRank-style mocks, and rehearse three values stories nightly. Execution beats archive collecting.
Post a short dated note: OA duration, languages, whether MCQs appeared, values question themes, and what you would redo. Specifics help the next batch more than motivational paragraphs.
Bottom line for juniors: Salesforce fresher hiring is beatable if you treat HackerRank correctness and values storytelling as first-class skills beside DSA theory. Triage early, test before submit, and bring STAR stories with stakes - that unglamorous combo clears more AMTS offers than last-minute cert binges.
Keep the loop boring and consistent: timed coding, spoken values stories, one CRM design sketch a week, sleep. That clears more offers than unread PDF collections.
Students targeting Salesforce alongside Adobe/Oracle should share a DSA core, then branch evenings: values STAR + HackerRank triage for Salesforce, design sketches for Adobe, SQL/schema for Oracle.
Another pattern from campus/off-campus composites: candidates who cleared emphasize paced HackerRank filters where easy marks disappear if you over-invest in one hard item. After OA, interviewers dig into one resume project and expect Salesforce values language - not generic “hard worker” answers.
Successful AMTS candidates emphasize:
If you interview this month: print your invite sections, map them to the practice map, schedule two full mocks, and rehearse values stories nightly. Do not collect five more PDFs. Execution beats archive hoarding.
That clarity - triage, tests, values, product-specific motivation - is the whole game for fresher Salesforce loops in 2026.
Keep showing up for the boring reps. Salesforce will not ask whether you watched twenty CRM explainers - it will ask whether your code passes hidden tests and whether your values stories sound like a person who has actually worked with other humans. That is the bar. Clear it deliberately.
On this site, use the nested OA, coding, and interview pages when you need drills; return here when you need the map for Salesforce AMTS prep in 2026.
Review your error log the morning of the test, not a new textbook chapter.
When in doubt, invest the next hour in a timed mock rather than another article about culture. Offers come from execution under a clock, not from perfect notes sitting unread on your desktop. Start the mock now; review every mistake carefully the same day while the attempt is still fresh.
