READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 29 of 153
Interview experiences · An applied AI
An applied AI Software Engineer interview: technical, manager, and bar-raiser rounds
The process felt high-stakes and had two technical rounds, a managerial round, and a bar-raiser-style discussion. It opened with a coding round that could eliminate me. Once I finished it, the remaining stages came quickly. After a short gap of a couple of days, I completed the next rounds in a single day. The pace left little time to decompress, and I had to stay sharp across different formats.…
Interview experiences · An applied AI
An applied AI Software Engineer interview: unclear live coding expectations
The initial screening felt normal, but the technical interview did not. I was given LeetCode-style questions, and the interviewer's behavior made the situation tense. They did not want to explain the question and expected a fully running solution while I was answering. That mismatch between the communication and the expectation put me under stress and did not feel supportive. I did not move forwa…
Interview experiences · Analog Devices
Analog Devices Software Engineer interview: a rejection for interviews that never happened
I first spoke with a recruiter about a hardware-validation role. The call was friendly and clear. We covered my background, relocation and work authorization, and my interest in hardware validation, mixed-signal systems, and test development or automation. I was told to expect a hiring-manager interview and then a longer technical panel. Neither was scheduled. I later got a rejection email that n…
Interview experiences · Analog Devices
Analog Devices Software Engineer interview: circuit-focused pressure
This interview was almost entirely about circuit-level thinking. I met a director of test engineering early, and the technical conversation centered on circuits rather than behavioral topics. The expectation seemed to be quick, precise solutions, and I felt a mistake could end my chances. Another circuit-focused discussion covered how to test whether a circuit works, then components such as capac…
Interview experiences · Analog Devices
Analog Devices Software Engineer Interview Experience: Supportive panel discussion
The interview flow was friendly and low-friction. The conversations felt welcoming from the start, without any sense that people were trying to catch me off guard. I spoke with a small panel, and the questions focused more on my background than on deep technical material. After a quick first step with a manager, I had a longer technical interview with multiple people from the group. The pace was…
Interview experiences
Analytics Engineer Interview Experience — Entry Numbering and Backfilling a Missing Date Range
I recently had an Analytics Engineer technical screen at a company and encountered a SQL + data pipeline question. Here's the approach. Table structure: entry_uuid | context_uuid | visitor_id | created_at | platform. Users can ask consecutive questions in the same chat/context. Each entry needs an entry_number indicating which entry it is within that context. How do you calculate it? The intervie…
Interview experiences · & General Intuition
& General Intuition Software Engineer Interview Experience: an uneven hiring-manager conversation
The process felt unevenly organized from the start. Communication and the collaboration vibe varied depending on the round. The part that stayed with me was a hiring-manager-style conversation that became a judgment of my career choices, rather than staying focused on fit or leadership. That did not sit well with me. I do not remember every technical detail, but the overall experience was noticea…
Interview experiences · & General Intuition
& General Intuition Software Engineer interview with AI coding round
I started with an HR call, then about a week later had a 45-minute online coding interview. That felt like the core screen: solve the problem live and explain my thinking as I went. I was then invited to the Sunnyvale office for an onsite loop. The onsite was a fuller day with a group discussion, system design, an AI-coding-style interview, and a wrap-up discussion. It tested more than one narrow…
Interview experiences · Andela Products
Andela Products Software Engineer Interview Experience: Python, React, and live coding
I began with an online Python-and-React assessment that felt like a mini project. It started with debugging, then two Python functions using real data structures rather than LeetCode-style tasks. The logic was straightforward, but I spent most of my time writing tests. The final part was a React layout, and AI use was allowed there. After passing, I had a Python-focused interview covering Python,…
Interview experiences · Andela
Andela Software Engineer Interview Experience: Practical Python and React assessment
My take-home assessment combined Python and React. It began with debugging, then two Python functions using real data structures rather than LeetCode problems. The core logic was straightforward, but I spent most of my time writing tests. The third section was a React layout, where AI use was allowed. After passing, I had a Python technical interview on fundamentals, FastAPI, and AI-related servi…
Interview experiences · Anduril Industries
Anduril Industries Software Engineer Interview Experience: automated recruiter messages and three essays
A recruiter contacted me unexpectedly with a message that felt AI-generated, and the exchange felt automated from the start. I tried several times to speak directly and move away from that phrasing, but it kept returning. She eventually sent a specific role tied to my resume that also read as though a bot had generated it, including a supposed office location in my city. After a few more chats, s…
Interview experiences · Anduril Industries
Anduril Industries Software Engineer interview experience: early recruiter screening
The process began with a quick recruiter screen that was mostly about logistics and conversation. We covered my background, past work, and interest in the role. Sometimes a small technical question came up. In one screen it was basic cantilever-beam knowledge; in another, there was no technical question at all. The recruiter also asked about fit and expectations, including team matching and motiv…
Interview experiences · Anduril
Anduril Software Engineer interview: cantilever beam questions and a nontechnical thermal screen
The recruiter screens were brief and mostly light. Technical questions did appear, but not consistently. In a screen about mechanical design, I got basic cantilever-beam questions. A separate thermal recruiter screen had no technical questions at all, which made the experience feel somewhat inconsistent from interviewer to interviewer. I did not get an offer from this stage. It felt comparatively…
Interview experiences · Anduril
Anduril Software Engineer interview: conventional flow and onsite concerns
I went through a conventional recruiter, tech-screen, and onsite flow. The questions covered data structures and algorithms, system design, and why I wanted to work at Anduril. The onsite was the main day, but the atmosphere did not match what I had hoped for. At one point, it felt like everyone was tired and the logistics were chaotic, based on how the interviewers talked about their situation.…
Interview experiences · Anduril
Anduril Software Engineer interview: C++ screen and graph clusters
I went through a familiar sequence: recruiter contact, a technical coding screen, and an on-site. In the Zoom technical round, we briefly covered my background before moving into C++. I had to read basic lines of code and explain pointers, references, lambdas, and move semantics. The second half was a programming challenge using depth-first search to identify node clusters in a graph. The on-site…
Interview experiences · Anduril
Anduril Software Engineer interview: drone equations and a demanding onsite
After an HR chat, I had a coding screen that was closer to a simulation than a standard textbook prompt. I had to calculate drone-related equations, so pattern matching was not enough to rush through it. Passing that screen led to an in-person onsite with system design, a cultural or motivational discussion, and two coding challenges. It felt difficult because the formats required both technical…
Interview experiences · Anduril
Anduril Software Engineer Interview Experience: automated recruiter messages and essays
A recruiter contacted me with a message that looked AI-generated. I asked to speak with a real person, but each reply returned to the same automated tone. She eventually gave me a "role" that also felt automated, apparently tailored from my resume and describing a city office I knew Anduril did not have. After more back-and-forth, she said she would put my resume in the system only if I wrote thr…
Interview experiences · Anduril
Anduril Software Engineer interview experience: HackerRank and ghosting
I started with a recruiter conversation that was kind and upbeat. Afterward, I received a HackerRank assignment, completed it, and waited. Then the process went quiet and I was ghosted. The positive recruiting call made the lack of any follow-up after the take-home feel especially abrupt. From what I saw, the broader process usually went from recruiter conversations to an engineering screen and t…
Interview experiences · Anduril
Anduril Software Engineer Interview Experience: Mock application work and a project presentation
My experience began with easy coordination. Reaching the recruiter and scheduling interviews was smooth. From there, the questions were tightly connected to the actual job and how effective I could be in it. I expected a typical interview structure, but it had a stronger performance element than I was used to. I had to demonstrate my abilities through mock application-style work, not just theory.…
Interview experiences · Anduril
Anduril Software Engineer Interview Experience — Onsite Coding Went Great, Then the HM's System Design Round Sank It
This role was billed as fullstack, but the interviews barely touched anything front-end related. And the final round — I got screwed over by the hiring manager. The phone screen was on 4/17. After I finished it we just chatted. The next day HR told me I passed and moved on to the onsite (VO). VO Coding 1 Question 1: a simple calculator that only needs to support addition and subtraction. ["+", 1,…
Interview experiences · Anthropic
Anthropic Data Scientist Interview Experience — A Recruiter Screen and Nonnegotiable Offer Terms
I applied online among lots of other applications, then only heard from a recruiter a month later. When I went back to look for the job description, the posting was already down... I asked her for the job description, but she didn't send it either. There were also more questions than in a typical recruiter round. Why Anthropic? Why are you a good fit? Why leave your current company? Why AI compan…
Interview experiences · Anthropic
Anthropic Interview Experience — Forced Into Single-Threaded Code, Then Rejected
I recently did a phone screen with Anthropic. I actually had a lot of goodwill toward this company going in, but the interview experience was extremely bad — I felt like the interviewer led me straight into a trap. Writing this to recap what happened, and also to ask everyone here for advice: when you run into an unprofessional interviewer during an interview, how do you save yourself? And is the…
Interview experiences · Anthropic
Anthropic Senior Software Engineer Interview Experience — Rejected After the HR Motivation Question
My process ended at the HR interview before I reached any technical interview. The recruiter asked why I wanted to choose Anthropic. After I answered, the recruiter's expression looked noncommittal. Sure enough, I received a rejection a few days later. I have ten years of experience and was interviewing for a technical role, so I was really frustrated that a poor answer to "Why Anthropic?" was en…
Interview experiences · Anthropic
Anthropic Senior+ Engineering Manager Interview Experience — Cut in the Management Style Round
I interviewed for an L6-7 EM role, in the pretrain org. The technical rounds were: project retrospective system design There were 3 non-technical rounds: management style strategy and execution culture The project retro was the only round with an actual engineering leader from the relevant area sitting in, and I felt like that one went pretty positively — they asked some pretty sharp questions. T…