← Back to Directory

Salesforce interview notes, page 8 of 13

Large Enterprises

Most of these Salesforce write-ups come from Software Engineers (104), then Product Managers (6) and Backend Engineers (4). The most reported rounds are the technical phone screen (65), the system design round (31), the hiring manager screen (6) and the behavioral / leadership round (5).

121 interview notes · updated Sep 2026

Salesforce·Software Engineer·Online Assessment (OA)

Jun 2026
Salesforce gave me a frontend TypeScript exercise that covered three things at once: fixing broken snapshot tests, writing new ones, and then refactoring messy conditional logic into something cleaner. A lot to juggle in one session, and they wanted you to talk through the design thinking too.
  • You're given TypeScript code full of if/else chains and duplicated logic. Read the existing snapshot tests, identify which ones are failing, and fix them.
  • Extend the test suite to cover cases not already tested in the existing snapshots.
  • Refactor the TypeScript so that the conditional logic is replaced by a rule table lookup. Explain which design pattern this represents and why you chose it.

“The snapshot tests were actually a decent breadcrumb trail into what the code was supposed to do.”

View Post

Salesforce·Product Manager·Hiring Manager Screen

Jun 2026
Short Salesforce PM screen, basically just one strategic question about the Tableau acquisition. Nothing crazy but it's the kind of thing that trips you up if you haven't thought about it beforehand.
  • Why did Salesforce acquire Tableau?

“I fumbled this a bit.”

View Post

Salesforce·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Salesforce for a software engineer role. The whole session was built around designing a venue rental platform, which sounds straightforward until you're actually in it and realize how many moving parts they want you to reason through.
  • Design a venue and facility rental system where organizers can discover and book physical venues through different rental packages, each with its own pricing and time granularity.
  • How would you represent availability and enforce that no two bookings overlap for the same venue space?
  • Define the key APIs for listing a venue, searching available venues, creating a booking, and canceling a booking.
  • How do you scale the read-heavy search and availability path while keeping the booking write path consistent and free of double-bookings?
  • A venue has multiple independently bookable rooms. How does your schema and overlap check change, and how do you keep search efficient across all of them?
  • How would you handle a renter who starts checkout but whose payment takes 90 seconds? How do you hold the slot and what happens to competing renters during that window?
  • How would you support recurring bookings, like a club renting a hall every Tuesday for 10 weeks, including partial cancellation of a single occurrence?
  • How would you add location-based search for venues within a certain radius that meet capacity and amenity requirements, while keeping results consistent with the booking source of truth?

“Big open-ended prompt.”

View Post

Salesforce·Software Engineer·Technical Phone Screen

Jun 2026
Short Salesforce solutions architect screen, basically one question about a core platform concept. Not much to go on but it's the kind of thing that trips you up if you haven't thought about it from a business angle before.
  • Why would a company choose to use Person Accounts in Salesforce?

“I knew the surface answer but fumbled explaining the actual business reasoning.”

View Post

Salesforce·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Salesforce for a software engineer role. Two questions, both pretty standard but they pushed hard on specifics so you can't just wing it with a vague story.
  • Walk me through the most memorable or impactful bug you've dealt with at work. How did you find it, fix it, and make sure it didn't happen again?
  • Tell me about a time you had to convince someone or a team to change direction or adopt your idea. What pushback did you get and how did you bring people along?

“They kept drilling into user impact, which I wasn't fully prepared for.”

View Post

Salesforce·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a solutions architect role at Salesforce, got a technical architecture question that sounds deceptively straightforward until you're actually in the room trying to justify a design decision on the spot.
  • How would you decide whether a client should use a REST API for their integration needs?

“I jumped straight into REST vs SOAP comparisons and lost the thread a bit.”

View Post

Salesforce·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Salesforce system design round focused on a coffee-shop management system, and the SQL portion was way more intense than I expected. The interviewer kept drilling into query specifics rather than staying at the architecture level, so if you're prepping for this kind of role, brush up on your SQL before anything else.
  • Design the data model for a coffee-shop management system, covering stores, menu items, ingredients and inventory, employees, orders, customers, and loyalty programs.
  • Walk through the key APIs for this system: placing an order, updating inventory, and generating a shift schedule for employees.
  • Write a SQL query to find the top-selling menu items per store for a given time period.
  • Write a SQL query to generate low-stock alerts across all stores.
  • Write SQL to calculate employee hours worked and derive payroll figures from shift and clock-in data.
  • Write a SQL query to analyze customer loyalty cohorts, grouping customers by when they joined and tracking their behavior over time.
  • Write a SQL query to produce daily revenue rollups across all stores.
  • How would you design the reporting layer for this system? What reports matter and how would you structure them?

“I started with orders and customers because that felt natural, but I probably should've anchored on stores first since everything else hangs off that.”

View Post

Salesforce·Software Engineer·Technical Phone Screen

Jun 2026
Salesforce SWE interview that came down to a classic DP problem. Nothing too surprising but the details matter more than you'd think.
  • Given an array of distinct coin denominations and a target amount, return the minimum number of coins needed to reach that amount. Return -1 if it's not possible. Coins can be reused.

“The core insight is framing dp[i] around the amount, not some index into the coins array.”

View Post

Salesforce·Software Engineer·Recruiter / HR Screen

Jun 2026
Short Salesforce SWE interview, basically just the one motivational question from what I can tell.
  • Why do you want to work at Salesforce?

“Classic opener.”

View Post

Salesforce·Software Engineer·Technical Phone Screen

Jun 2026
Salesforce SWE interview with a tricky array permutation problem that looks straightforward until you actually try to get the edge cases right under pressure.
  • Given an array of positive integers, return the lexicographically largest permutation that is strictly smaller than the input and can be produced by swapping exactly two elements. If no such permutation exists, return the original array.

“The core scan isn't hard once you know to go right to left looking for a drop.”

View Post