Salesforce Backend Engineer interview questions

4 Backend Engineers have shared notes from their Salesforce interviews, with the questions they were asked in each round. That is 3% of the 121 Salesforce interview notes on Screna AI.

4 Backend Engineer interview notes

Salesforce·Backend Engineer·Onsite - System Design / Architecture

Jul 2026
Salesforce backend round, one big system design question about elevators. Felt like a classic OOP design problem but with enough scheduling complexity to keep you on your toes for the full hour.
  • Design an object-oriented elevator control system for a building with multiple floors and multiple elevators. The system should handle hall requests from floors, cabin requests from inside elevators, track elevator state, assign requests to elevators, and schedule movement efficiently.

“Spent the first few minutes just listing classes out loud, ElevatorCar, FloorRequest, Dispatcher, Door, that kind of thing.”

View Post

Salesforce·Backend Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Salesforce for a backend engineer role, focused entirely on building the analytics backend for a ChatGPT-style product. No UI, no model internals, just the data pipeline and serving layer. Pretty meaty question that covered a lot of ground.
  • Design the analytics backend for a ChatGPT-like product. You need to cover what metrics to track, how to ingest data from upstream services, how to store and aggregate it, and how to serve dashboard queries efficiently.
  • How would you design the ingestion pipeline from upstream services like chat sessions, message-level events, and user accounts into your analytics store?
  • What slicing dimensions would you expose on the dashboard, and how do you handle the trade-off between query freshness and storage or compute cost?
  • How would you handle PII and data governance concerns in this analytics pipeline?

“This is a big open-ended question and I spent probably too long on the metrics enumeration part before getting to the architecture.”

View Post

Salesforce·Backend Engineer·Onsite - System Design / Architecture

May 2026
Salesforce backend engineering interview that was basically one long system design session focused on building an analytics platform for a ChatGPT-style product. The scope was pretty wide and I kept second-guessing how deep to go on each piece.
  • Design the backend of an internal analytics system for a conversational AI product. The system should collect data from production databases and service logs, compute product and reliability metrics, and serve those metrics to a dashboard used by PMs and engineers.
  • How would you ingest data from existing production services without putting extra load on those primary databases?
  • What event and metric schemas would you use for this kind of analytics platform?
  • How would you support both near-real-time metrics and historical analysis within the same system?
  • Walk through how you'd compute metrics like daily active users, conversation counts, request volume, latency percentiles, token usage, and error rates.
  • How would you design the system to slice metrics by dimensions such as time, model version, region, platform, and user segment?
  • How would you handle data freshness, correctness, deduplication, and backfills in this system?
  • How would you address privacy, access control, and operational monitoring for this analytics platform?
  • What does the API or query layer look like that a dashboard backend would call to retrieve metrics?

“This is a big one.”

View Post

Salesforce·Backend Engineer·Technical Phone Screen

May 2026
Salesforce backend round, one algorithmic problem the whole time. Pretty standard greedy/heap territory but I fumbled the implementation details more than I'd like to admit.
  • Given a list of events each with a start and end day, find the maximum number of events you can attend if you can only attend one per day.

“I knew the greedy angle pretty quickly: sort by start day, use a min-heap keyed by end day, iterate day by day and always pick the event expiring soonest.”

View Post