real interview stories, told over a cup of tea ♡
Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
3935 results
- Same OA, Now Cruise-Themed Instead of SuperheroesCapital One · Data Analyst · Online Assessment · Jul 2026
I noticed there isn't much here about this OA, and I just finished mine, so I wanted to share. The two Canada-version posts from 2024 are completely outdated now — what's being tested currently is very similar to another report I found. Basically the approach for every question is the same, except it's no longer about superheroes, it's about cruises now. There are 12 questions total, but the firs…
- Samsara Account Executive interview: recruiter, hiring manager, and panel finalSamsara · Account Executive · HR Screen · Jul 2026
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…
- Samsara Software Engineer interview: a thoughtful reroutingSamsara · Software Engineer · HR Screen · Jul 2026Rejected
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…
- Samsung Austin Semiconductor Software Engineer interview: three-engineer panelSamsung Austin Semiconductor · Software Engineer · Technical Screen · Jul 2026Offer
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…
- Samsung Electronics Software Engineer interview: hackathon invitation and three roundsSamsung Electronics · Software Engineer · Technical Screen · Jul 2026Offer
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…
- SAP Consultant interview experience: paper DSA and project decisionsSAP · Consultant · Online Assessment · Jul 2026Offer
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…
- SAP Consultant interview: Teams lag during video interviewSAP · Consultant · HR Screen · Jul 2026
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…
- SAP Labs Software Engineer interview: DSA, ABAP, and behavioral discussionSAP Labs · Software Engineer · Technical Screen · Jul 2026
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…
- SAP Software Engineer interview: DSA rounds and behavioral HR discussionSAP · Software Engineer · Online Assessment · Jul 2026
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-…
- Sargent & Lundy Software Engineer interview experience: a long repetitive loopSargent & Lundy · Software Engineer · Jul 2026
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…
- SAS Software Engineer interview: aptitude test and two virtual roundsSAS · Software Engineer · Online Assessment · Jul 2026
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…
- SAS Software Engineer interview: positive discussions, no offerSAS · Software Engineer · HR Screen · Jul 2026
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.…
- Scale Product Manager interview: AI product cases and fitScale · Product Manager · Technical Screen · Jul 2026
After a recruiter call, I entered a product-focused process that lasted several weeks. It combined behavioral questions with product-sense work. The work was AI-focused, and the cases asked for broad thinking with room to shape an approach. The live interviews involved several people and tested different aspects of my thinking. Some conversations were about product sense and design, while others…
- Schneider Electric Software Engineer Interview Experience: quick technical and manager processSchneider Electric · Software Engineer · HR Screen · Jul 2026
After a recruiter call, the process moved quickly through two interviews with a hiring manager and a final recruiter conversation about the offer and next steps. The organization made it feel low-stress, and I liked how friendly the panelists were. There was a technical round and a managerial round. I discussed my background, why I applied, and technical questions that did not feel designed as tr…
- Schneider Electric Software Engineer interview: Distribution Center digitizationSchneider Electric · Software Engineer · Onsite · Jul 2026Offer
I met a panel of two managers and an HR representative in a conference room in Athens. After introducing myself, I described projects I'd led during internships and contract work. We then discussed logistics and processes, particularly how I'd digitize work in a Distribution Center. They asked about my strategy for implementing advanced digitization. The questions felt practical, and I appreciate…
- Schweitzer Engineering Laboratories Software Engineer interview: C and C++ pressureSchweitzer Engineering Laboratories · Software Engineer · Technical Screen · Jul 2026
The interview felt like it went well overall, though there were a couple of genuinely tricky moments that made it sharper than a typical screen. In the behavioral portion, a few questions did not come as easily as I wanted, even though I think I handled most of them. Most of the technical questions came back to coding concepts and problem-solving, with C and C++ as the language focus. That mix of…
- Schweitzer Engineering Laboratories Software Engineer interview: embedded depthSchweitzer Engineering Laboratories · Software Engineer · Jul 2026
The questions were described as easy, but the interview was not superficial. It required low-level embedded-system design and programming knowledge, and I felt the details could catch someone who skimmed. I had a good conversation with the panel and felt they were exploring whether I understood the material deeply. Even answers I thought were correct led to follow-ups on important details, which…
- Scientific Research Research Scientist interview: prolonged silence after onsiteScientific Research · Research Scientist · HR Screen · Jul 2026
The process took much longer than I thought it should. After an initial phone screen and an interview with the hiring manager, I eventually had an onsite stage, but the timeline extended beyond three months. While I waited, both the manager and recruiter were essentially unreachable, and it felt as if the process had paused. The interviews themselves were not my main concern. Once I was left in l…
- Scientific Research Software Engineer interview: CAPA panelScientific Research · Software Engineer · HR Screen · Jul 2026Rejected
After applying online, I first spoke with a recruiter about the role and my background. That conversation was focused on fit and helped set expectations for what the hiring team cared about. Soon after, I had a panel-style interview that combined technical and situational discussion. Even when the topics became specific, the tone was conversational. The technical discussion centered on my CAPA-st…
- Scientific Research Software Engineer pressure coding interview experienceScientific Research · Software Engineer · Technical Screen · Jul 2026
My process started with a recruiter call and quickly became structured technical conversations. I was usually asked to walk through my resume and projects, then they dug into what I had actually done. Sometimes the prompts were straightforward about systems; sometimes they were scenarios meant to test how I reasoned. One round combined leadership-style discussion with coding. I had to explain my…
- Scotiabank Financial Analyst interview: one-hour branch-manager roundScotiabank · Financial Analyst · HR Screen · Jul 2026Offer
After I applied and was shortlisted, I had a preliminary recruiter-style call that felt more like an eligibility and fit check than a deep interview. About a week later, I had the main round with branch managers, including one person who was also the team manager. The conversation lasted roughly an hour, and fortunately there were no further interviews. Most of the discussion was about my backgro…
- Scotiabank Financial Analyst interview: Superday valuation questionsScotiabank · Financial Analyst · Other · Jul 2026
The process felt more like interview school than a casual screen. The first round combined behavioral and technical questions, and the Superday was a series of short back-to-back conversations. Some interviewers wanted role-specific technical knowledge while others stayed behavioral, but all of it tested whether I understood the market instead of just definitions. I was pushed on a stock pitch, i…
- Scotiabank Software Engineer interview: late start and unclear Python exerciseScotiabank · Software Engineer · Technical Screen · Jul 2026
I joined the Scotiabank interview five minutes early, but the main interviewer arrived about 20 minutes late. Once it began, I gave detailed answers and explained the business reasons behind choices in my past projects. I felt some answers were judged through assumptions that did not match the context I was trying to clarify. I was also frustrated by the implication that I relied on AI tools, bec…
- Scotiabank Software Engineer interview: practical SQL and Python discussionScotiabank · Software Engineer · HR Screen · Jul 2026
After a recruiter screening phone call, I had a technical round with three interviewers. It felt straightforward and seemed more about getting a read on me than catching me off guard. The conversation included SQL, Python, and other general technical questions. It did not feel like a heavy algorithm gauntlet. The questions stayed grounded in practical language and query knowledge. Overall, it fel…
- SentinelOne Software Engineer interview: fast online technical pairSentinelOne · Software Engineer · Technical Screen · Jul 2026
After a recruiter reached out, I shared my availability and received invitations quickly. The process moved fast and felt straightforward. I first spoke with the recruiter, then completed the technical part online in English. There were two back-to-back video technical interviews. The first covered conventional programming, including coding fundamentals and problem solving. The second moved to sy…
- ServiceNow QA Engineer interview: easy coding and project discussionServiceNow · QA Engineer · Technical Screen · Jul 2026
The online interview felt straightforward and easier than I had expected. The coding portion involved stack and dynamic-programming ideas, including next greater element and a buy-and-sell-stocks problem. The conversation then moved to my project, where I explained my testing approach and how I verified the work. That set the tone for the rest of the call. It was a smooth, low-pressure discussion…
- ServiceNow Software Engineer Interview Experience: Interrupted technical screenServiceNow · Software Engineer · Jul 2026
The interview was tougher than it first appeared. I got an array problem that combined stack and queue ideas, and struggled to see how the structures were meant to connect. The flow worsened when the interviewer turned off the camera and left during the interview. I tried to get their attention, but was left waiting without real-time feedback. I got through the session but did not receive an offe…
- ServiceNow Software Engineer interview: positive start, months of silenceServiceNow · Software Engineer · Jul 2026No response
I applied online, spoke first with a recruiter, and then had a video conversation with the hiring manager. During that call, I was told my skills matched what they wanted. Then I heard nothing for months. Eventually I received an automated rejection while the role kept appearing again. The recruiter also stopped responding after I reached out twice. It was frustrating because the process seemed t…
- ServiceTitan Account Executive interview: repeated communication failuresServiceTitan · Account Executive · HR Screen · Jul 2026Rejected
The first recruiter screen went smoothly. The recruiter seemed engaged and said next steps with the hiring manager would be scheduled. Then I heard nothing for about two weeks. I emailed twice, and only after I included the hiring manager did I receive a rejection. It was especially frustrating because this was not my first experience with the company, and I felt my time was not being respected.…
- ServiceTitan Customer Success Engineer interview: recruiter silenceServiceTitan · Customer Success Engineer · HR Screen · Jul 2026No response
After I applied, I had an initial recruiter screen and the process seemed to be moving. Then I received an automated rejection. Later, the recruiter contacted me personally and asked for a call about an update. I replied promptly and followed up again that day, but heard nothing. Days later I tried again and still received no response. The silence was especially disappointing because the recruite…
