Real, anonymous reports from people who interviewed for Backend Engineer at Salesforce, newest first and distilled into what to expect across the loop.
Get your personalized Salesforce Backend Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My process started off pretty normally, and the recruiter vibe was professional. I moved into technical rounds that were grounded in classic CS and data-structures thinking, and the interviews felt mostly standard until the programming question hit.
That programming portion was brutally hard for me—easily the hardest I’d ever seen in an interview. I had about an hour to work, but I still couldn’t get to a working solution during the time, and the conversation didn’t turn into a rescue—just a tough prompt and a lot of pressure. Before that, I was also grilled on my CV projects and had to navigate core computer science concepts, including how Git works on the backend, and then translate that theory into a DSA-style problem.
9 months ago
I went through a fairly direct process for a Lead Software Engineer role focused on backend distributed systems. The recruiter reached out first, and then I took a proctored HackerRank screening with two questions to complete in 75 minutes. Both problems were described to me as LeetCode-medium level, and it felt like a real test of whether I could stay sharp under timed constraints.
After that, the flow moved into a separate DSA round. The overall setup was simple—one major timed screening followed by another technical round—so I could tell they were optimizing for fundamentals and clean problem-solving rather than a long chain of interviews.
9 months ago
I took an online assessment for an SMTS Backend role, and it was done via HackerRank through the careers portal. The test had two coding questions to …
Unlock every Backend Engineer interview experience
