READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 130 of 153
Interview experiences · Stubhub
Stubhub Software Engineer interview: Codility, CodeSignal, and resume-based technical screen
The process moved quickly into online testing and stopped just as fast. I took a Codility-style assessment with a limited time window and submitted everything before time ran out, but I never heard back. At another stage, I completed a CodeSignal assessment with several LeetCode-style questions. The focus was on getting working solutions rather than writing the most elegant algorithms. I ran out…
Interview experiences · Stubhub
Stubhub Software Engineer interview: OOP, a project deep dive, and final presentation
I started with a short recruiter call covering background and fit. About a week later, I had a technical interview on OOP: building classes and implementing methods tied to them. The pace was manageable, and the questions were not overly tricky. The final stage had three back-to-back interviews. First was a 30-minute conversation with a software engineer on the team. Then I had a one-hour project…
Interview experiences · Stubhub
Stubhub Software Engineer interview: six-year requirement for the senior SWE track
I reached out through LinkedIn and eventually connected with the company. The process started normally, but I soon learned that senior-level roles required six or more years of experience. I considered myself a senior engineer, but I didn’t meet the experience requirement for the senior SWE track. Because of that policy, I didn’t move forward and withdrew from the process. The hard cutoff felt ol…
Interview experiences · Stubhub
Stubhub Software Engineer interview with a 75-minute pair programming round
My interview process started with an HR behavioral round, followed by a CodeSignal assessment and then a face-to-face technical sequence. The technical portion included a 75-minute pair programming round and a system design round. The process ended after the system design interview, and I was rejected at that final technical stage. It felt like a typical multi-round pipeline, but the rejection se…
Interview experiences · Stubhub
Stubhub Software Engineer interview with a shortened project deep dive
I started with a recruiter screen that already felt off. There was a missed call, and after I reached back out, I waited about two weeks just to hear about moving to the next round. When I was scheduled for the hiring manager interview, the hiring manager I was connected with didn't match what the email said. The project deep dive also didn't match the schedule. It was supposed to last 45 minutes…
Interview experiences · Stubhub
Stubhub Software Engineer interview with no clear decision
I didn't get much information from StubHub during the interview loop. After I completed the process, they didn't seem to communicate a clear decision either way. About two weeks later, I received a survey asking me to rate the interview. The experience left me uneasy. The interview itself wasn't especially brutal, but the recruiting process didn't feel appropriate for the time and effort it requi…
Interview experiences · Stubhub
Stubhub Software Engineer interview with repeated scheduling problems
The process started with scheduling, and it quickly became clear that it wasn't being handled with much care. The recruiter didn't show up for the originally scheduled interview at all. After I reached out to reschedule, I didn't get a real response. I joined the rescheduled call anyway, only for the recruiter to arrive late and act as if the situation was an inconvenience rather than something t…
Interview experiences · Sunrise
Sunrise Software Engineer Interview Experience — Nine or Ten Rounds in One Chicago Onsite
You have to go to Chicago in person — I'm sick of it. The whole trip was a terrible experience. The interview process was long and painful, and after each round they'd ghost you for a month. But then when HR finally reached back out a month later, you had to give them a firm availability within a single day. The company's culture and technical bar didn't impress me either. They seem to have very…
Interview experiences · Sunrun
Sunrun Account Executive interview: onboarding expectations shifted
The timeline and expectations felt inconsistent from the start. I was told onboarding and scheduling would be simple and that I would be placed at one site, but after onboarding I had to travel to another county for a team meeting and visit several sites instead of the one where I applied. The training ramp also took much longer than I expected because of extensive paperwork and back-and-forth. S…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: a large project with about an hour to work
After the early screening and assessment, the process became a run of back-to-back rounds that mixed behavioral and technical questions. It felt harsher than the interviews I was used to. They gave about an hour for a large project, which felt more like a stress test than a normal interview. I had to work through DSA problems while also talking about design. System design became important late in…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: AI-assisted website bug fix
The online assessment had four parts. It opened with a medium-to-hard DSA problem, followed by a work simulation where I fixed a website bug using AI. The remaining sections were behavioral questions. Later stages also leaned heavily on personal experience rather than being a pure coding showcase. The AI-assisted simulation was the surprising part because AI was part of how they expected the task…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: coding, GenAI, and leadership evaluation
After an initial campus-style screen, I started with an OA and waited a while for the next steps. Once I cleared it, the process moved through timed rounds that combined coding, role-specific evaluation, and behavioral work. The first round was a 1-hour virtual interview on a live coding platform. After a brief introduction, I chose C++ when asked which language I preferred. The coding problems i…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: demanding DSA and graph rounds
After the recruiter stage, I had back-to-back technical interviews for what was presented as an entry-level Software Engineer role. I found them brutally hard. I answered what I could and felt I was solving problems and communicating reasonably well, but I was rejected. The standard seemed extremely high and unforgiving. DSA came up repeatedly in the later rounds. One included graph algorithms an…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: distracted interviewer
The conversation itself felt straightforward, but the tone made it awkward. The interviewer seemed distracted, almost as if they were reading from a prepared list. The focus was on my experience, projects, and technical work, with questions that probed more refined knowledge. There was not much improvised back-and-forth in how the questions were delivered. I had to keep my answers organized and s…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: DSA and leadership principles
My path started with an online assessment that paired a live DSA problem with Amazon work-style questions tied to leadership principles. In the coding portion, I was assessed on my problem-solving approach, correctness, and time and space complexity. The behavioral questions used “tell me about a time” situations and expected STAR-style answers around themes such as ownership, bias for action, an…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: edit distance, Locker design, and offer
During the coding round, I realized the problem was the same edit-distance question I had practiced shortly before. I then had a system design discussion about Amazon Locker, where I reasoned through components and customer flows. The last round used behavioral questions tied to leadership principles. I had to connect examples to specific principles and explain my actions and results. The process…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview experience
The process began with an online assessment that combined behavioral prompts tied to Amazon-style Leadership Principles with a separate coding section. After clearing it, I moved to the in-person stage. My first interview was with the hiring manager and was strongly behavioral. I discussed my background and projects and answered Leadership-Principle questions about specific situations. Near the e…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer Interview Experience: DSA and unstable interviewer connection
I had four rounds, and each mixed some behavioral or Leadership Principles discussion with technical content. DSA appeared often across the loop. The process mostly felt fair, but one round was disrupted by the interviewer's connectivity problems and their apparent uncertainty about the DSA problem. I was trying to reason through the solution while navigating an unstable setup. The remaining roun…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview experience: full DSA and design loop
The interview felt like a full Amazon-style loop, with several layers of depth in each technical conversation. I began with LeetCode-style coding: two DSA problems, one medium and one hard. For both, I needed an optimal solution, an explanation of my reasoning, time and space complexity analysis, and edge-case handling. The interviewer kept asking about alternative approaches and trade-offs. Then…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer Interview Experience: Repository debugging home test
Before the live loop, I had a two-part home test. A HackerRank/LeetCode-style prompt took about 40 minutes, then I debugged a full-stack app repository where one API call did not work as expected. I had to trace the problem and fix it until all tests passed. It felt more like real engineering than a clean algorithm exercise, with repeated context switching among reading code, reproducing the fail…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: graphs, trees and a bar-raiser round
The loop ran over a couple of days with back-to-back rounds that mixed behavioral prompts and technical depth. In one virtual session, I was asked about data-center-style work. The panel seemed to include people from manager through principal and staff roles. The technical questions covered strings, graph and array problems, linked lists, and binary search trees. One round focused on graphs and a…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: leadership in technical rounds
My loop blended leadership principles directly into technical interviews. The first technical conversation combined troubleshooting and GenAI fluency with prompts about Bias for Action. It was clear that behavior and engineering were not being treated as separate subjects. The next technical round focused on coding problems with leadership themes such as Deliver Results. A hiring-manager-style co…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: live coding and system design
I began with a recruiter phone screen about my resume and experience. Then I had a technical video interview with a senior engineer that lasted about an hour. After a quick introduction, I completed a live coding challenge in a shared editor. The discussion then moved into system-design fundamentals and my past projects. The challenge was being clear while coding live and then explaining design-l…
Interview experiences · Super Micro Computer
Super Micro Computer Software Engineer interview: pleasant but uncertain pacing
The people I spoke with at Super Micro Computer were nice, and once the process started, communication moved toward decisions quickly. The overall path was not laid out efficiently, though, and I still felt that the company took its time advancing me. The final stage had multiple interviews on engineering fundamentals related to the role. The questions were not unfair, but different interviewers…