READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 126 of 153
Interview experiences · Amazon Web Services
Solutions Architect interview at Amazon Web Services: withdrew after technical round
I entered through a referral and passed an initial assessment. That led to a recruiter phone screen and then a technical interview, so the process moved forward quickly once I cleared the test. I withdrew after the technical round and did not experience the full multi-round loop. The early funnel felt normal: assessment, recruiter call, then technical screen. Since I chose to step away, I cannot…
Interview experiences · ServiceNow
Solutions Consultant interview at ServiceNow: positive interviews and silence
After a recruiter screen, I had a quick hiring-manager call and two peer interviews back to back. They were personable conversations about my experience, motivation, understanding of the role, and basic experience-based questions. Both peers spoke positively and pointed me toward the next stage. Then communication stopped. I followed up after about a week and again later, but received only a feed…
Interview experiences · Sopra Steria
Sopra Steria Consultant interview: follow-up silence and a revoked offer
At first, the process seemed quick and responsive. After the first stage, though, I ran into complete silence. I followed up and still received no feedback, which made me feel that I had been interviewed simply for the sake of interviewing. I also experienced another version of the same poor follow-through. It dragged on for around two months, and I was ghosted after the interviews despite my rem…
Interview experiences · Sopra Steria
Sopra Steria Software Engineer interview: one-day assessment and data tooling rounds
After the recruiter step, I went through a fast set of assessments. The first covered aptitude, general fit, and English-style screening. The second used coding-oriented multiple choice on basic DSA, SQL, and OOP concepts. It was manageable and finished within one day. In a separate role-specific track, I had two internal interviews, a client round, and a managerial round. Those conversations tes…
Interview experiences · Southern California Edison
Southern California Edison Software Engineer interview: STAR panel and electrical concepts
I started with a talent-acquisition recruiter call. Because I matched the role requirements, I moved to a four-person panel interview. They took turns asking questions, so the conversation was structured but moved quickly as each interviewer joined in. Most questions were behavioral and expected STAR-style answers. I was pressed about past experience and how I handled particular situations, with…
Interview experiences · SpaceX
SpaceX New Grad Research Scientist Interview Experience — Speculative Decoding in a 60-Minute ML Coding Round
There were two 60-minute interviews: an ML coding round and a research chat. The ML coding round asked me to implement speculative decoding. I needed to write one normal decoding function and one speculative decoding function. The speculative function had the following interface in the prompt: The test case required the speculative-decoding implementation to produce its output faster than the nor…
Interview experiences · Spacex
Spacex QA Engineer interview: electrical background and mechanical questions
The call began simply enough, but it quickly became a frustrating mismatch. The questions went beyond a general introduction. I was asked what I knew about Starship, then the conversation moved into technical fundamentals. What bothered me was how my technical background seemed to be treated as irrelevant. The role description and my coursework were in electrical engineering, yet the technical qu…
Interview experiences · Spacex
Spacex QA Engineer interview: recruiter support and onsite feedback
After a recruiter call, I went through a series of phone interviews that felt more structured than anything I had done before. There was another round with an engineer, followed by a hiring-manager call that ran about half an hour longer than I expected. That conversation stayed pretty chill, though they kept asking me to connect my background to their work. Soon after that, I was invited onsite…
Interview experiences · Spacex
Spacex Software Engineer interview: a surprise half-day panel
I started with HR, then met a hiring manager and a technical team member before what was described as an onsite. By the time I reached the panel, the process had grown into a full half-day onsite interview. What caught me off guard was the framing. It had been sold as a simple, quick chat, but it was really a technical interview. After I answered, they pushed back with follow-up questions that se…
Interview experiences · Spacex
Spacex Software Engineer interview experience
The recruiter-to-technical flow was fairly standard, but it became a full evaluation cycle. It started with HR or cultural fit, followed by technical conversations with team members. In one technical discussion, I spoke directly about prior jobs while several people listened and occasionally joined in. Later rounds demanded deeper understanding and clearer communication. The hiring manager was in…
Interview experiences · Spacex
Spacex Software Engineer interview: first-principles and hardware-focused questions
The process started with a short recruiter call about my background, then turned technical almost immediately. The next call lasted about 30 minutes and felt grounded in first principles. I answered quick checks on fundamentals such as the ideal gas law and Bernoulli's equation, then moved into structures-style questions. Even when I did fine on the equations, it seemed they wanted tight, confide…
Interview experiences · Spacex
Spacex Software Engineer interview: one-hour onsite presentation
The process moved through several technical touchpoints quickly. I had three phone interviews with different people, then reached an onsite stage that became the center of the evaluation. There, I gave a one-hour presentation on my greatest achievement. It felt fast-moving and evaluative rather than conversational. After the presentation, I was sent home right away, so I never reached the longer…
Interview experiences · Spacex
Spacex Software Engineer interview: project details and a medium coding problem
The first round began with a resume dive and moved directly into technical questions. The interviewer focused on one of my projects and pushed on the details instead of accepting the high-level story. I felt they wanted clarity on my decisions and implementation choices, and much of the discussion rested on solid C++ fundamentals. After that, the process shifted to a coding assessment after the e…
Interview experiences · Speechify
Speechify Software Engineer interview: proctored AI-assisted coding challenge
After I applied, the process moved almost immediately into an automated, AI-assisted coding challenge. It happened so fast that I felt nobody had reviewed my background first. There was no initial call. Instead, I received the challenge and had to record my screen and camera while working. The assessment lasted 90 minutes and used a company-provided codebase. I was told I could use AI tools, but…
Interview experiences · Speechify
Speechify Software Engineer interview: proctored timed assessment and screencast
The early technical step felt unusually uncomfortable because it was heavily proctored and camera-driven. I had to keep my camera on during a timed assessment, and the recording requirements made it feel more like surveillance than collaboration. It was an independent test, with no live interviewer helping while I worked. The assessment required a screencast. There were rules against AI tools and…
Interview experiences · Speechify
Speechify Software Engineer interview: refactoring and realtime AI design
I began with a recruiter conversation about my resume and the shape of the technical rounds. Soon after, I completed a 90-minute LLM-based refactoring assessment inside a full-stack app. I was given problems to fix, and although AI tools were allowed, I still had to think through the work instead of copying answers. The later formats were live and varied. In a 90-minute vibe-coding session, I rec…
Interview experiences · Spotify
Spotify Backend Engineer interview with unexpected domain questions
I started with an initial screening, which led to a technical screen divided into three parts: a discussion of my project, domain questions, and LeetCode-style coding. I expected the domain questions to relate to the project I’d discussed, but the atmosphere felt cold. During the domain section, the interviewer seemed to jump around and choose questions on the spot. I got a lot of basic, exam-lik…
Interview experiences · Spotify
Spotify Data Engineer interview: 12-minute phone screen
My process started with a recruiter chat about my background and visa status. The phone screen was pretty quick, and the scheduling felt a little chaotic. I realized the interviewer was in a rush, and the call, which was supposed to last about half an hour, ended after roughly 12 minutes. Even with the short, hurried conversation, I was selected to move on to the next round. I felt like there was…
Interview experiences · Spotify
Spotify Data Engineer interview with a demanding coding round
After a conversation with a recruiter, I had a coding-focused round that I expected to be straightforward. It turned out to be difficult. The round was with two senior engineers, and the pace felt demanding. I remember feeling that I needed to be much more fluent with interview-style practice than I actually was, and that gap made the interview harder than it should have been. I didn't receive an…
Interview experiences · Spotify
Spotify Data Scientist interview: five-week wait for feedback
My process started with a recruiter screen, followed by a technical round with two MLEs. That part was focused and direct. The final step was a behavioral interview with the hiring manager. It took about five weeks to hear back. They still came back with feedback after making a decision, which made the wait feel less abrupt than I expected. Location: United States. Overall feedback: Positive. Off…
Interview experiences · Spotify
Spotify Full Stack Engineer interview: Backend Tech Screen changed to Web Tech Screen
I had a phone screen followed by a technical interview with two senior software engineers. The interview invite initially said "Backend Tech Screen." The night before, the recruiter sent an updated invite that kept the same time. I noticed the change while checking the details, then apologized for sending too many messages. On the day of the interview, I got front-end questions instead. Only afte…
Interview experiences · Spotify
Spotify Software Engineer interview: DSA, system design, and behavioral loop
My process started with an HR screening, followed by a technical and behavioral screen with two engineers. That round used a HackerRank-style setup and included what felt like standard DSA questions. I then went through a full loop with several interview slots: two more DSA coding rounds, one system design round, and one behavioral interview. The format was methodical. Each interviewer seemed to…
Interview experiences · Spotify
Spotify Software Engineer interview with a 75-minute side-project and coding session
After speaking with a recruiter by phone, I moved into one focused interview with a senior software engineer. It lasted about 75 minutes. The format was structured: I introduced a side project, then answered technical questions based on what I'd shared, and finally did live coding in the style of classic LeetCode problems. The pacing felt fairly straightforward, but the interview was still techni…
Interview experiences · Spotify
Spotify Software Engineer interview with a difficult technical panel
My first contact was a recruiter call covering the usual basics: my background and resume, why I was interested in Spotify, why the role suited me, current compensation and expectations, work authorization and visa status, and my availability. The later interviews were noticeably harder than the early stages. I reached a technical round with a hiring panel led by a senior-level engineer, and the…