Find a lesson, question or project

Start typing to search published content and planned structures.

↑ ↓ moveEnter openEsc close

Salesforce interview research

Candidate accounts · 1 scoped account · 6 reported questions/topics

Snapshot: 1 October 2026 · Software/backend focus · No live fetching

Self-reported accounts, not employer-confirmed. Preserve the stated role, team and location; this sample does not establish company-wide patterns or question frequency.

Questions people reported

Named problems, reported variants and broad topics are different kinds of evidence. Related practice links are not proof that the exact problem was asked. Some prompts were withheld; we do not invent their details.

Topics in these accounts: Coding

MTS · candidate reported 3 years of experience; Bengaluru, India

6 Jun 2026 · Interview date

Read the original candidate account

This hiring drive included assessment, screening, two onsite coding rounds and a hiring-manager discussion. The candidate explicitly reported no dedicated LLD or system-design round.

Scope and source limitations

Keep this employer-specific role, date and region scope. Candidate reports are self-reported, not employer-confirmed.

This account was retained from the existing reviewed dataset and was not fully reread in the 1 October research pass.

  • Good Ways to Split an Array

    Coding · Reported topic

    Count three-part contiguous splits satisfying S2 ≤ S1 + S3.

  • ATM Queue

    Coding · Reported topic

    Find the exit order when unfinished withdrawals return to the queue.

  • String permutation counting

    Coding · Reported topic

    The author did not remember the exact statement.

  • Minimize array sum with K halvings

    Coding · Reported topic

    Repeatedly halve an element; the candidate used a max heap.

  • Constant-time insert, delete and random selection

    Coding · Reported topic

    Random selection must give elements equal probability.

    Related practice: Insert Delete GetRandom O(1)

  • Coin Change II

    Coding · Named problem

    The report links this exact problem.

    Named problem: Coin Change II

Additional independent, matching role/level/region reports are needed before claiming recurring patterns.

A suggested 14-day preparation plan

Authored practice, not the company’s syllabus. This general track is an editorial starting point, not a pattern inferred from all these reports. Confirm the format with your recruiter and adapt it to your actual level.

Algorithm reasoning

Prioritize invariants, traversal, hashing, heaps and changed-constraint follow-ups. Keep practical coding and design practice too.

  • Days 1–2: diagnose gaps with arrays/hashing and a graph exercise.
  • Days 3–5: traversal, dependencies, heaps and binary-search invariants.
  • Days 6–7: DP/backtracking; state, recurrence and edge-case tests.
  • Days 8–9: a timed coding mock with two follow-ups and a dry run.
  • Days 10–11: one executable design exercise and one service-design mock.
  • Days 12–14: project stories, a full mixed mock and targeted revision.
Practise an original design exercise

Design a multi-tenant customer-record API with access controls.

This exercise is written for practice, not reported by a candidate. Define requirements, implement the smallest useful version, then test concurrency, retries and failure recovery where relevant.

Customize a timed role/level prep brief

The timed brief uses a narrower, date/level-filtered dataset. Broader accounts on this page are deliberately not substituted into those filters.

How this research was collected

Public candidate accounts, official guides and original editorial practice are kept separate. We did not copy paid question banks or scrape all of the internet. Cross-posts are not independent evidence; one source can describe more than one company. Unknown or index-only dates are not used to claim recency. Future expansion needs permitted fetching, deduplication and metadata review; this version remains a static snapshot.