Sam's Club Software Engineer Interview Questions
& Process

The interview process kicked off okay, but then we hit the system design part. First up was a phone call, which went fine. Then, a coding round with some technical questions and an easy LeetCode-style problem. The third round was about Salesforce technical stuff and included another coding problem—fair and relevant, all in all. But man, that last round, the system design interview, was a letdown. The interviewer cut me off mid-introduction. My background is clearly Salesforce development, yet he dove straight into Docker system design questions. It felt totally off for this role. Honestly, it felt like he'd already decided to pass, without even checking my experience. It’s super important that interviewers know the domain they're testing. This guy clearly didn't know Salesforce, making the whole thing feel unfair and pointless.

The interview process had two rounds: a coding round and a design round. The coding round used Java and wasn't like Leetcode, it was meant to mimic actual work with changing requirements. The design round asked a system design question which I wasn't ready for.

I applied through the careers site and a recruiter got in touch. After that, I had to do an online coding test on Hackerearth with 10 questions: 3 coding problems to solve and 7 multiple-choice ones about code outcomes or finding bugs. Since I did well, I got a phone screen with two principal engineers that lasted about an hour, where I had to code data structures and algorithms. Then, I had another phone screen with two more senior team members, and we coded again on a shared screen. After that, I was invited for an onsite interview which had about 4-5 rounds, each with two interviewers. These rounds included whiteboarding and situational/behavioral questions. The HR contacted me within a couple of days with an offer, which I negotiated and accepted.