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
- Supermicro Software Engineer Interview Experience: Full-stack debugging assessmentSupermicro · Software Engineer · Jul 2026
I had an online HackerRank/LeetCode-style prompt under a tight window, immediately followed by a full-stack repository debugging task. An API call did not behave as expected, and I had to diagnose and patch it until every test passed. The difficulty came from the number of moving pieces rather than the algorithm alone. In versions of this assessment style, there was also a work simulation where I…
- Supermicro Software Engineer interview experience: grid paths and RAGSupermicro · Software Engineer · Online Assessment · Jul 2026Rejected
For my Amazon Supermicro Software Engineer track, the process began with an OA combining coding and work simulation. The workstyle assessment used Leadership Principles situations, with additional feedback and workstyle components. I then progressed to virtual interviews of about an hour each. The first interview opened with a brief introduction and language check; I chose C++. I worked on grid a…
- Supermicro Software Engineer interview experience: misaligned hypothetical questionsSupermicro · Software Engineer · Jul 2026
The interview felt misaligned with the job. It lasted about an hour, but the questions were mostly hypothetical scenarios that did not reflect my current role and seemed aimed at a different domain. Instead of discussing day-to-day software work or my approach to it, the conversation focused on structural or mechanical topics and knowledge of proprietary information in a growing industry. It did…
- Supermicro Software Engineer Interview Experience: no-show and disputed blacklistingSupermicro · Software Engineer · Jul 2026
The process went wrong before it could really begin. An interviewer did not show up for my scheduled meeting. I contacted the recruiter and recruiting team with evidence that I was present and ready. Even so, I was blamed for missing the interview. After I declined to reschedule because of what happened, I felt shut out, and I was told I was effectively blacklisted. I received no meaningful inter…
- Supermicro Software Engineer interview: assessment test cases and behavioral follow-upsSupermicro · Software Engineer · Online Assessment · Jul 2026
After applying, I completed an online assessment with four test cases in the first part and seven in the second. Then came coding and leadership-focused interviews. One coding round covered graphs and arrays, another covered linked lists and binary search trees, and the bar-raiser felt harder than the earlier rounds. I also heard another version of the overall flow: an OA with two coding pieces,…
- Supermicro Software Engineer interview: Bar Raiser depthSupermicro · Software Engineer · HR Screen · Jul 2026
My loop started with a recruiter screen and a small set of structured technical rounds. The first technical round combined troubleshooting with Bias for Action and GenAI fluency. The next turned to coding problem solving, where I needed to solve a technical prompt and keep my output clear. Then came a hiring-manager-style round on Earn Trust, Learn and Be Curious, and Operational Excellence. The…
- Supermicro Software Engineer interview: delayed OA-to-onsite processSupermicro · Software Engineer · Online Assessment · Jul 2026Rejected
After my initial OA, I waited a long time before hearing about an in-person onsite. Once the onsite finally happened, the later stages were a short back-to-back sequence with SWE rounds and a managerial discussion. The application kept moving slowly, and HR was not consistently responsive. Even when I followed up, replies arrived late. That uneven communication affected my confidence more than th…
- Supermicro Software Engineer interview: medium coding questions under pressureSupermicro · Software Engineer · Technical Screen · Jul 2026
My interview opened with a basic introduction and then went directly to two medium-level LeetCode questions. One was a balloon-bursting-style problem, and the other involved tree path sum. The difficulty felt easy, but I still choked during the session. There was little beyond the usual expectation that I reason through the approach and implement it. The larger problem was performing under pressu…
- Supermicro Software Engineer interview: patient two-question DSA screenSupermicro · Software Engineer · Technical Screen · Jul 2026Offer
After a recruiter touchpoint, I had a focused technical screen. It opened with a quick introduction and went straight into two DSA questions: a binary-tree problem and a LeetCode-medium style problem. It felt like they were checking a specific spread of DSA knowledge, almost as if the questions mapped to a known curriculum. The pace was thorough and tightly scheduled, with back-to-back interactio…
- Supermicro Software Engineer interview: strings, priority queues and object-oriented designSupermicro · Software Engineer · Technical Screen · Jul 2026
This was a multi-round loop with an Amazon-style level of intensity. Behavioral and technical questions were mixed together, and the bar felt high. One round probed leadership, while another used more conventional interview topics. I saw strings, priority queues, and object-oriented design, plus a round that was entirely behavioral. The time pressure made the whole thing feel like a test of wheth…
- Supermicro Software Engineer interview: take-home coding and two design questionsSupermicro · Software Engineer · Take-home Project · Jul 2026
Recruiter coordination led to a structured process over a couple of days. The questions mixed situations and behavioral discussion, so fit and communication mattered as much as technical depth. After the initial screen, I completed a take-home LeetCode-style assessment and a live coding interview. Then I had a system-design round with two design questions and a behavioral interview about collabor…
- Susquehanna International Group Quantitative Analyst interview: CodeSignal, Bayes and expected valueSusquehanna International Group · Quantitative Analyst · Online Assessment · Jul 2026
I began with a structured math screen: a timed CodeSignal assessment with programming and algorithmic problems that also demanded test-style problem solving under pressure. The later interviews stayed focused on probability and clean reasoning. Interviewers wanted to hear how I thought, not only the answer. The math covered Bayes' rule, combinatorics, expected-value questions, and puzzle-like rea…
- Susquehanna International Group Quantitative Analyst interview: optimization and timed assessmentsSusquehanna International Group · Quantitative Analyst · Online Assessment · Jul 2026Rejected
The assessments made runtime and optimization as important as getting the answer right. I took an OA and then a general coding assessment covering hash maps, binary search, queues and heap operations. The questions became harder as I went, so I needed to finish the early ones quickly enough to leave time for the later work. One later problem hit a runtime limit, and I had to improve my first solu…
- Susquehanna International Group Quantitative Analyst interview: rushed probability questions before a mixed interviewSusquehanna International Group · Quantitative Analyst · Online Assessment · Jul 2026
After a recruiter call, I entered a timed, math-heavy process that felt focused on probability from the start. The next step was an online assessment made up mostly of probability questions, and it got harder as I went. I did not manage my time as well as I should have, so I rushed the last few questions just as the difficulty increased. Soon after, I had another interview that mixed behavioral a…
- Susquehanna International Group Quantitative Analyst interview: timed probability and logicSusquehanna International Group · Quantitative Analyst · Intern · Online Assessment · Jul 2026Rejected
I applied for a quant internship and received the online assessment almost immediately. I had about an hour for probability and logic questions. They weren't brutally difficult, but preparation mattered if I wanted to work quickly and keep the reasoning straight. It felt like a check of fundamentals and composure. I don't have a long sequence of later rounds to describe. Probability and logic wer…
- Susquehanna International Group Software Engineer interview: CodeSignal DSASusquehanna International Group · Software Engineer · Online Assessment · Jul 2026
The process was compact: a CodeSignal coding assessment, then recruiter and technical interviews. The main technical checkpoint was a DSA-focused CodeSignal set with multiple questions. It felt designed to see how I handled structured algorithm problems within the platform's constraints. After the assessment, I had an HR interview and a technical interview with deeper discussion and coding-style…
- Susquehanna International Group Software Engineer month-long processSusquehanna International Group · Software Engineer · Technical Screen · Jul 2026
Scheduling was deliberate from the beginning. After recruiter contact, I had a technical screen and then a technical-plus-design round, with recruiter preparation and follow-up calls around the interviews. The in-person stage also included fit and experience conversations, and I appreciated the communication and feedback throughout. The process lasted more than a month, with rounds about one to t…
- Swiggy Software Engineer interview: DSA, LLD, and system designSwiggy · Software Engineer · Technical Screen · Jul 2026
I went through a straightforward Swiggy loop that flowed smoothly. After the recruiter touchpoint, I had two rounds: a coding interview on DSA and LLD-style patterns, then a system design round with an engineering manager. The difficulty felt average. The DSA and LLD portion was standard enough that I was not completely thrown off, and the system design discussion felt manageable but thoughtful r…
- Symbotic Robotics Engineer interview: positive signals and vague closureSymbotic · Robotics Engineer · HR Screen · Jul 2026Rejected
My process started normally with an HR phone screen that went well, followed by a video call with the hiring manager. That conversation felt dry rather than warm, and it did not seem to build toward a decision. I asked for an update soon after but heard nothing, then eventually received a Workday-style email saying they were moving forward with other candidates. On another attempt, the sequence w…
- Symbotic Software Engineer interview: long wait after final roundsSymbotic · Software Engineer · Onsite · Jul 2026No response
I began with a Microsoft Teams recruiter screen. The recruiter explained the role and reviewed my resume, and the follow-up interviews stayed close to my background: basic behavioral questions, what I had done before, and what I could bring to the team. There were several conversations, including an on-site element and a final director discussion that was presented as time for my questions. The p…
- Synechron Software Engineer interview: interruptions and rushed technical screeningSynechron · Software Engineer · Technical Screen · Jul 2026Rejected
My first interview left me rattled. The interviewer repeatedly cut me off and moved to the next question before I'd finished. I felt interrupted more than assessed. A later screening was even more rushed. A short phone call led to a technical screen where the questions came too quickly for me to think them through. When I asked for clarification, I didn't feel the interviewer slowed down or helpe…
- Syntes Software Engineer interview: friendly start, no follow-throughSyntes · Software Engineer · HR Screen · Jul 2026No response
The first thing that stood out was the lack of clarity once I finally had a chance to interview. Recruiters were direct when they reached out, but they gave little information about the process length and I received no updates afterward. In a separate attempt, I was contacted after applying for an assessment path. There was a quick phone call about my background and fit, with the hiring manager c…
- Syntes Software Engineer interview: relaxed half-day panel sessionSyntes · Software Engineer · Jul 2026
Recruiter outreach came first, and they connected me with the team. The atmosphere was easygoing, and everyone felt friendlier than the people I had met at other European pharma companies. The process moved quickly into two rounds: a short call with the hiring manager, then, about a week later, a half-day in-person session. That session consisted of several panel-style conversations. Most intervi…
- Syntes Software Engineer interview: two virtual discussions with hiring decision-makersSyntes · Software Engineer · Other · Jul 2026
Both interviews were virtual and felt closely connected to the hiring decision. In the first video call, I spoke with the person directly involved in deciding who to hire. The second brought in additional team members for more of a panel discussion. We mainly talked about my background. In the second round, it felt like several people were considering my answers from different perspectives at onc…
- Sysco Account Executive interview with no follow-upSysco · Account Executive · Online Assessment · Jul 2026No response
After completing interview steps, I never got real closure. Things initially seemed promising, but the follow-up did not come. I kept reaching out and was left wondering whether I had been passed over or simply forgotten. In one case, I was told I had made it through, then there was no second round and no explanation. In another, the process ended after an online assessment and a video interview…
- T Mobile Us Account Executive interview: sales scenarios and mixed outcomesT Mobile Us · Account Executive · Onsite · Jul 2026Offer
After a recruiter contacted me, I had an early screen to confirm my background, availability, and interest in the role. The discussion was practical: why I wanted the role, my sales experience, and how my goals matched the business. I kept it conversational and used real examples rather than trying to sound overly polished. A little later, I met with managers, usually in one main in-person conver…
- T-Mobile Account Executive interview: behavioral sales conversations and inconsistent follow-upT-Mobile · Account Executive · Onsite · Jul 2026Offer
After I applied, the process moved smoothly and did not feel drawn out. I started with a phone check-in to confirm my background, availability, and interest. I discussed examples from my sales experience, then had live conversations with managers, typically face to face or as a virtual onsite. The conversations were more relaxed than intimidating and leaned on behavioral examples: customers, cowo…
- Tanium Software Engineer interview: recruiter silence and canceled technical interviewsTanium · Software Engineer · HR Screen · Jul 2026
The start was discouraging. Two recruiters contacted me on LinkedIn and asked for my resume and contact details. One disappeared entirely. The other said the role was not live yet and should open the following week. That week passed without a response or a job posting. I followed up anyway and got nothing back. After they had confirmed the outreach was real, the lack of basic professional courtes…
- Target Account Executive interview experienceTarget · Account Executive · Other · Jul 2026Withdrew
I had a short in-person interview about customers and availability. The questions focused on how I would handle common shopping situations and help customers, not technical material. I also received a quick explanation of the position. I later had a manager-led in-person interview with a manager and assistant manager. They asked about my availability and customer interactions. The follow-up was t…
- Target Account Executive interview: communication and difficult stakeholdersTarget · Account Executive · Other · Jul 2026Offer
The interview used structured questions about how I work. I described cross-functional work, communication challenges, difficult stakeholders, problem solving and managing expectations. The prompts were straightforward and related to situations I'd discussed in previous roles. They were specific enough that I could see the focus was on my thinking and how I explained decisions. I didn't end up ta…