READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 115 of 153
Interview experiences · Salesforce
Salesforce Software Engineer II Interview Experience — Recruiter Forgot About Me, Then a No-Coding Cloud Round
In April, a recruiter reached out and scheduled a video call to get a sense of my situation. They mentioned there would be a lot of openings coming after that. In June I noticed a large number of Salesforce job postings, but the recruiter had forgotten about me, so I emailed to nudge them. I was interviewing for SDE 2. Round 1: hiring manager screening. Mostly asked about my background and why I…
Interview experiences · Salesforce
Salesforce Software Engineer interview: DFS and scalable-system design
My process began with a recruiter screen and then a technical round built around a hard LeetCode-style DSA problem that leaned heavily on DFS. I spent the session working through the approach and tradeoffs while trying to keep my reasoning clear. After that, I had a high-level design interview about scalability and reliability. It pushed me beyond an immediate coding solution toward how a system…
Interview experiences · Salesforce
Salesforce Software Engineer Interview Experience — Five Onsite Rounds, Every One Circles Back to Multi-Tenancy
Sharing my interview experience with Salesforce. My impression of this company is very different from consumer-product companies: the problems themselves aren't going for difficulty, but almost every round eventually circles back to "what if this system is shared by a lot of customers." Multi-tenancy, permissions, and configurability ran through the whole interview. There was also a whole round d…
Interview experiences · Salesforce
Salesforce Software Engineer Interview Experience — Rushed Team Match, Ghosted Before the Onsite
This was a really baffling hiring process. Is Salesforce's general hire now all team-specific interviews instead of a unified track? Round 1: OA — sent later on, an online test on the HackerRank platform. If I remember right it was LeetCode-style stuff, not too hard, but the test cases were kind of annoying. After I passed, about a month later an HR person reached out — but it wasn't the general-…
Interview experiences · Salient Ai
Salient AI Senior Software Engineer Interview Experience — The Final Onsite Round Was Canceled on the Spot
Position: Senior Software Engineer, Core Product. The onsite was in San Francisco and was originally scheduled for 3 hours. Round 1: Live coding (1 hour) Practical coding, not LeetCode. It was a duplicate-files type of question: given a set of filesystem helpers, deduplicate files by their contents. The follow-ups kept digging into I/O and read optimizations. Round 2: System design (1 hour) A que…
Interview experiences · Samsara
Samsara Account Executive interview: recruiter, hiring manager, and panel final
After a quick recruiter conversation, I spoke with the hiring manager. Those early calls were information focused rather than overly formal. The recruiter set context, and the hiring manager asked about my past experience, what I wanted in a company, and whether my background matched the role. The process was organized and not overly complicated. I moved through a small number of rounds, but the…
Interview experiences · Samsara
Samsara Account Executive interview where the evaluation felt impression-based
The beginning felt fairly normal. I had a recruiter screen with basic resume questions, then spoke with the hiring manager about the role. Those early interviews were quick and structured, so I thought I was in good shape. The tone changed once I got deeper into the process. During the manager conversation, I felt as if I'd already been marked down somehow because of how I "looked the part," even…
Interview experiences · Samsara
Samsara QA Automation Engineer interview, HIL take-home project
I started with a pleasant Zoom call with the hiring manager, followed by a recruiter call that focused mostly on whether I wanted to continue. I was told the next steps would include coding and a take-home project. After I shared my availability, they scheduled four hours of interviews on one day. They didn’t explain beforehand that it would essentially function as a virtual onsite, so I tried to…
Interview experiences · Samsara
Samsara Software Engineer, HTML parsing and simple system design
After several recruiter conversations, the process moved through technical discussions, a system design exercise, and a cultural fit check. The recruiting team kept everything organized, and the interviews felt efficient and coherent. One early step was described as a quick verification call with the recruiter. The system design exercise was supposed to be simple rather than elaborate. I also got…
Interview experiences · Samsara
Samsara Software Engineer interview: a thoughtful rerouting
I began with a recruiter conversation about my background. The recruiter did not think the role I applied for was the best fit, but instead of ending the process, he suggested another position in the Routing organization. I was unsure whether I had the right skills, though the problem domain interested me enough to continue. I did not reach the next stage, but the process felt thoughtful. The rec…
Interview experiences · Samsara
Samsara Software Engineer interview: hiring manager deep dive and TPS round
My process started with an HR call about project details and what I was looking for. That quickly led into a hiring manager deep dive, which also included a TPS round within the same hour. The TPS question wasn't too difficult and didn't feel like standard LeetCode. I didn't move forward after that, but the experience was reasonably straightforward. I understood what I was being evaluated on, and…
Interview experiences · Samsara
Samsara Software Engineer interview with Level 2 and Level 3 rounds
My interview journey felt like it was built around a lot of rounds and gatekeeping. The process was described as two main stages: Level 2 first, followed by Level 3 if I cleared everything in Level 2. I was told I had to pass all the Level 2 interviews to move forward. Once I became eligible for Level 3, I would go through another set of managerial and technical rounds to finish. Even with that s…
Interview experiences · Samsara
Samsara Solutions Engineer interview: deal metrics and a take-home presentation
The process was more demanding than I expected. It went through several rounds, starting with HR and then moving into sales leadership. The overall acceptance rate felt low. They placed a lot of emphasis on showing a growth mindset, and the questions pushed me to be very specific about deal metrics. I had to prepare to go beyond surface-level answers. The interviews mixed behavioral prompts with…
Interview experiences · Samsung Austin Semiconductor
Samsung Austin Semiconductor Software Engineer interview: three-engineer panel
The process was very light and almost conversational. After a recruiter touchpoint, I had one panel interview with three engineers. There was no HR step attached to that day, no technical questions, and the atmosphere stayed relaxed. They asked behavioral questions about teamwork and my past projects. What stood out was that I was not being assessed for one narrowly defined opening. Instead, they…
Interview experiences · Samsung Electronics
Samsung Electronics Software Engineer interview: hackathon invitation and three rounds
After passing a hackathon, I was invited with a group of other candidates. The first stage took place in one day, with three back-to-back interviews. The first was technical. I solved LeetCode-style questions, one about linked lists and another based on math, and thought the assessment was fair. The second and third interviews were with two managers. They introduced the role, then asked about my…
Interview experiences · Samsung
Samsung Machine Learning Engineer Interview Experience — Panicked on a String Palindrome and Failed the Screen
I'm new to industry and to LeetCode, not a CS major, and I recently gave up on academia to try to switch into industry. I got lucky and landed a first-round interview with Samsung, one hour, with a senior staff interviewer. The whole thing was scheduled in a rush — the confirmation email with the interview link only went out the day before, and it wasn't until I saw the coding link that I realize…
Interview experiences · SAP
SAP Consultant interview experience: paper DSA and project decisions
I began with an online assessment that included an OA and two DSA-focused questions at about a medium LeetCode level. The technical interview then drew from my resume, including choices I had made in earlier projects, SQL, database management, Python, and more DSA. Next was a combined managerial and technical interview. I solved a LeetCode Hard-style DSA problem on paper, alongside behavioral and…
Interview experiences · SAP
SAP Consultant interview: Teams lag during video interview
The recruiter call went well, then I moved to a video interview on MS Teams. That conversation was frustrating because it lagged noticeably. I had not experienced that kind of Teams lag in interviews before, and it threw me off because my camera and connection worked fine in another meeting shortly afterward. The only explanation I could think of was that the HR interviewer and I were in differen…
Interview experiences · SAP Labs
SAP Labs Software Engineer interview: DSA, ABAP, and behavioral discussion
The interview began with a typical problem-solving assessment. I worked through DSA questions under constraints and had to write clear logic. One question asked for the smallest missing positive in an unsorted integer array with linear time and constant extra space. Another involved adding two numbers represented as linked lists. I then had a broader technical conversation that mixed core problem…
Interview experiences · SAP
SAP Software Engineer interview: DSA rounds and behavioral HR discussion
My loop started with an online assessment that combined role-based multiple choice questions with coding. I then had two technical rounds, followed by an HR conversation about behavior, fit, and culture. The overall difficulty felt medium: I had to stay focused, but it never became chaotic. The technical work was rooted in classic DSA and practical problem solving. One task was the first-missing-…
Interview experiences · Sargent & Lundy
Sargent & Lundy Software Engineer interview experience: a long repetitive loop
The process felt longer and less efficient than it needed to be. I had four back-to-back interviews that lasted more than 2 to 3 hours. The hiring manager, whom I expected to be on the schedule, never appeared. That made the setup feel disorganized and disrespectful. Several interviewers seemed disengaged, and the conversations had very little energy. Different people asked the same questions abo…
Interview experiences · SAS
SAS Software Engineer interview: aptitude test and two virtual rounds
After a recruiter step, I took a virtual aptitude and technical multiple-choice test. Clearing it led to the interview rounds. The first virtual technical interview had two interviewers and covered data structures and algorithms, C, memory management, and database concepts. A second virtual round mixed technical and managerial questions about my projects, DSA coding, and situational and behaviora…
Interview experiences · SAS
SAS Software Engineer interview: positive discussions, no offer
The process began with two back-to-back conversations: a 30-minute recruiter interview, then a 30-minute meeting with the hiring manager and team manager. After that, I spent almost three hours with the team and the team manager. The extended live discussion was the longest part, rather than any individual test. They asked extensively about projects on my resume and included behavioral questions.…
Interview experiences · Scale AI
Scale AI Backend Engineer Interview Experience — Full Onsite Loop with a Claude-Assisted Coding Round
I mass-applied for an infra role that sits under the ML research org. The interview process matched what other people have already posted here on the forum. Onsite loop: Task scheduler VO BQ: Standard questions, and it ended early. The highlight was during the time to ask questions back — I asked the interviewer if there was anything she didn't like about Scale AI, and she said that because of RT…