READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 131 of 153
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: sliding window and rate limiter
My process began with an online assessment containing two coding problems. One was a relatively approachable sliding-window task, while the other used binary search. I then had a live coding interview where I implemented a queue with two stacks, a clear test of data-structure thinking. Later rounds stayed DSA focused. I worked through string and subarray logic, then another round on designing rat…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: streaming design and manager rounds
The process was simple in structure but hard in content. After initial setup, I had three rounds: a system-design interview followed by two managerial rounds. For system design, I was asked to design a streaming application like a major video platform. I had to explain how the system would work at scale and discuss architectural trade-offs. The later managerial discussions focused on how I work a…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: three-month loop to offer
After an online assessment and recruiter call, I was scheduled for an onsite-style loop. From assessment to decision, the process took around three months. The evaluation was split among multiple interviewers and felt consistent and deliberate. The onsite loop ran in one stretch. I had a bar-raiser round, a DSA-heavy round, and a low-level design round. Each interview lasted about an hour. The su…
Interview experiences · Supermicro
Supermicro Network Engineer interview experience: opaque asynchronous tasks
My application process was unusual. After I applied, I did online tasks that involved watching videos and answering questions instead of going through a normal back-and-forth interview. At the time, I was not clearly told what that process represented. A few days after I finished, I received an email saying I had been successful, but it did not explain much about what had happened behind the scen…
Interview experiences · Supermicro
Supermicro Software Engineer interview: assessment test cases and behavioral follow-ups
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,…
Interview experiences · Supermicro
Supermicro Software Engineer interview: Bar Raiser depth
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…
Interview experiences · Supermicro
Supermicro Software Engineer interview: brain-teaser screening
The process began with online assessments that did not feel related to the role. The recruitment quizzes leaned on strange puzzle-like brain teasers, and I felt they wasted my time because I was not being hired to solve riddles. After the assessment, the follow-through varied. In one thread, I had a couple of interviews: one structured round and one more conversational interview with normal quest…
Interview experiences · Supermicro
Supermicro Software Engineer interview: delayed OA-to-onsite process
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…
Interview experiences · Supermicro
Supermicro Software Engineer interview experience: Amazon-style loop and leadership prompts
After applying, I completed an online assessment and then entered an Amazon-style loop. The day felt like a marathon, with multiple back-to-back rounds and different interviewers. Coding, behavioral questions, and leadership-principles prompts were mixed together. DSA was at the center early on, followed by more engineering-judgment conversations that asked me to connect past work with particular…
Interview experiences · Supermicro
Supermicro Software Engineer interview experience: coding, design, and bar-raiser loop
My path followed a formal Amazon-style interview loop after I applied, rather than a quick conversation. It was intense because it combined deep coding, several system-design discussions, object-oriented design, and a bar-raiser focus on leadership principles. The coding questions ranged from medium to hard. I was expected to find an optimal solution, explain my reasoning, cover time and space co…
Interview experiences · Supermicro
Supermicro Software Engineer Interview Experience: Full-stack debugging assessment
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…
Interview experiences · Supermicro
Supermicro Software Engineer interview experience: grid paths and RAG
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…
Interview experiences · Supermicro
Supermicro Software Engineer interview experience: misaligned hypothetical questions
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…
Interview experiences · Supermicro
Supermicro Software Engineer Interview Experience: no-show and disputed blacklisting
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…
Interview experiences · Supermicro
Supermicro Software Engineer interview: LRU cache and eviction
A recruiter reached out and scheduled an onsite loop after an initial step. What surprised me was the length of the phone screen. It went deeply into implementation instead of staying at a broad fit level. I was pressed on an LRU cache, including a hashmap with a doubly linked list and a clear explanation of eviction behavior. Because I had practiced system-design-style examples, I felt more comf…
Interview experiences · Supermicro
Supermicro Software Engineer interview: medium coding questions under pressure
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…
Interview experiences · Supermicro
Supermicro Software Engineer interview: patient two-question DSA screen
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…
Interview experiences · Supermicro
Supermicro Software Engineer interview: strings, priority queues and object-oriented design
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…
Interview experiences · Supermicro
Supermicro Software Engineer interview: take-home coding and two design questions
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…
Interview experiences · Supio
Supio Software Engineer Interview Experience — One Hour Live-Debugging Their AI Chat Codebase
A personal injury law AI startup in Seattle. One hour of debugging. The interviewer emails you a source code repository, you run it locally yourself, and fix the issues. You need to be reasonably familiar with how to work with some AI APIs. It's a chat interface. Bug 1: the console showed "API key invalid." The cause: a wrong API key. Bug 2: after sending a request in the chat box, the response t…
Interview experiences · Susquehanna International Group
Susquehanna International Group Quantitative Analyst interview: CodeSignal, Bayes and expected value
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…
Interview experiences · Susquehanna International Group
Susquehanna International Group Quantitative Analyst interview: optimization and timed assessments
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…
Interview experiences · Susquehanna International Group
Susquehanna International Group Quantitative Analyst interview: probability and coding
I had an OA first, then quick interviews combining probability with coding and problem solving. The technical portions did not seem impossibly hard, but they could be tricky. The challenge was staying consistent instead of getting stuck on one question. The follow-up conversations were smooth and interviewer-friendly, with HR reaching out quickly after positive feedback. One interview was casual,…
Interview experiences · Susquehanna International Group
Susquehanna International Group Quantitative Analyst interview: rushed probability questions before a mixed interview
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…