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
- Anduril Software Engineer interview experience: HackerRank and ghostingAnduril · Software Engineer · Take-home Project · Jul 2026No response
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…
- Anduril Software Engineer Interview Experience: Mock application work and a project presentationAnduril · Software Engineer · HR Screen · Jul 2026
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.…
- Anduril Software Engineer interview: C++ screen and graph clustersAnduril · Software Engineer · HR Screen · Jul 2026
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…
- Anduril Software Engineer interview: cantilever beam questions and a nontechnical thermal screenAnduril · Software Engineer · Jul 2026
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…
- Anduril Software Engineer interview: conventional flow and onsite concernsAnduril · Software Engineer · Technical Screen · Jul 2026
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.…
- Anduril Software Engineer interview: drone equations and a demanding onsiteAnduril · Software Engineer · Jul 2026
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…
- Apexon Software Engineer interview: Java questions and platform assessmentApexon · Software Engineer · Online Assessment · Jul 2026
I went to Apexon for a Java-engineer-style interview and waited a long time before it began. When it finally started, it felt rushed and focused on Java fundamentals and fast coding. I solved a problem about printing pairs such as (x, 2x) from an array, then worked with Java Streams to filter and transform strings. I was also asked about daemon threads. The conversation ended abruptly, leaving li…
- Appian Software Engineer interview: immediate automated rejectionsAppian · Software Engineer · Jul 2026Rejected
About an hour after I applied online, I received an automatic rejection. I never spoke with anyone at the company, and it did not appear that my resume had been reviewed. The same role kept being reposted. When I tried again later, I received another automatic rejection without a recruiter call. That made the experience feel less like active hiring and more like resume harvesting, at least from m…
- Apple Machine Learning Engineer interview: smooth and rushed flowsApple · Machine Learning Engineer · Technical Screen · Jul 2026Offer
My smoother interviews began with a technical phone screen, then a comfortable, practical DSA-style round. It included a regression-model critique and a subset-sum-style problem. I had recently worked through similar problems, so those patterns were already familiar. I then had a codebase-style evaluation around PDF evaluation logic. The structure felt familiar because I had previously reviewed t…
- Apple Software Engineer interview with a full-day final round of eight conversationsApple · Software Engineer · Jul 2026
The interview cycle was organized but intense. I had four rounds overall, and the final one was a full day with around eight separate interviews running back to back. There were a lot of technical and behavioral questions, and the main demand was sustained focus. Before that full-day round, I had conversations about my background and projects. They started with my CV, then moved into targeted tec…
- Apple Software Engineer interview: CMOS logic and architecture reasoningApple · Software Engineer · Technical Screen · Jul 2026
After a recruiter chat, I moved through structured rounds that felt focused and practical. The first round asked me to explain core flow stages end to end, tying each stage's inputs to its purpose. The questions soon became more specific, including level shifting, isolation cells, and how CMOS logic works for an inverter. The virtual onsite was about how I approached an engineering problem, not j…
- Apple Software Engineer interview: design challenge decisionApple · Software Engineer · Other · Jul 2026Rejected
HR outreach quickly led to an hour-long hiring-manager conversation about my background, technical topics, and design. I did not feel especially strong in those answers, but I still advanced to a design challenge. The cycle ended after I submitted that work. I was rejected after the design challenge, without a long back-and-forth. What surprised me was how quickly the process moved from conversat…
- Apple Software Engineer interview: onsite assignment and presentationApple · Software Engineer · Onsite · Jul 2026Rejected
Recruiter outreach moved quickly into a multi-step process that felt smooth even though it was complex. I went through several rounds with different interviewers, each focused on how I would operate in the role rather than on curveballs. The HR touchpoints clearly explained what each stage would test. I had an onsite-style experience with an assignment and a presentation at the end, which made th…
- Apple Software Engineer interview: technical depth and uncomfortable toneApple · Software Engineer · Other · Jul 2026
The overall cycle was technically heavy and thorough. I had multiple rounds with mostly professional, fair questions about heat transfer, fluid mechanics, and thermodynamics. I was expected to show understanding even when the questions became specific. Two rounds felt different. Those interviewers kept adding follow-ups until they found something I could not answer, and some questions required de…
- Apple Software Engineer interview: timing, circuits, and coding under pressureApple · Software Engineer · Technical Screen · Jul 2026Offer
The process was long and kept expanding. I had multiple roughly one-hour interviews, and the volume itself made it intense. Technical questions covered setup and hold timing, transistor and diode behavior, logic reasoning, and at least one coding round with medium LeetCode-style problems such as string compression and an LRU cache. The mix of coding and hardware-timing questions tested both reaso…
- Apple Software Engineer interview: verification and timing closureApple · Software Engineer · Technical Screen · Jul 2026
The process began with a short phone call where I was walked through the overall structure. The later rounds centered on my resume and projects, then moved straight into hardware verification and design. The technical range ran from basic material to SVA constraints, UVM, and handshake-style interactions. A later round was even more focused on code and timing logic. We covered DFT fundamentals, e…
- Applied Materials Software Engineer interview with a calm technical and behavioral processApplied Materials · Software Engineer · Jul 2026
I had a calmer, low-stress process overall because the people running it were accommodating. The recruiter and interviewers were helpful, and the process felt like it was moving forward instead of dragging. I didn't feel anxious as it went on, and the tone matched how they treated me as an applicant. The interviews began with the usual conversation about my background, why I wanted the role, and…
- Applied Medical Software Engineer interview: resume-based panelApplied Medical · Software Engineer · Other · Jul 2026
I started with a recruiter phone screen about my background, why I wanted the company and role, school, and prior work. About a week later, I met an engineering manager and several engineers from the team in an in-person panel. That panel stayed close to my resume and projects. The follow-ups asked for specifics about what I had done and how I approached the work. It was less puzzle heavy than ma…
- Aptean Software Engineer interview: manual testing and SQL scenariosAptean · Software Engineer · Technical Screen · Jul 2026Offer
I went through a focused two-round process built around manual testing. The technical discussions covered SDLC and STLC, how I design test cases, and the defect life cycle from discovery to closure. I also worked with SQL queries and explained my approach to scenario-based testing questions. They kept probing for practical knowledge rather than memorized definitions: how I solve problems and whet…
- Arcesium Software Engineer online assessment with negative marking and coding questionsArcesium · Software Engineer · Online Assessment · Jul 2026
My process started with an online assessment that lasted about 80 minutes. The first 15 minutes were a technical multiple-choice section with negative marking, so every guess felt costly. Next came assessment-style questions where I had to read a code snippet and choose the correct output. Then there were two coding questions. The assessment was split into clear sections: MCQs to filter quickly,…
- Arch Global Services Philippines Software Engineer Interview Experience: project depth to HR logisticsArch Global Services Philippines · Software Engineer · HR Screen · Jul 2026Offer
After a recruiter call and shortlisting-style contact, I had an hour-long technical interview about my project and technical depth. It felt more like a discussion of real work and core principles than a string of unrelated facts. Later, a developer-background interview covered coding, problem solving, situations, and project details. The manager round moved into architecture and design tradeoffs,…
- Arctic Wolf Software Engineer interview: two coding questions in forty minutesArctic Wolf · Software Engineer · Onsite · Jul 2026
I expected a more hands-on process, but the first interview stayed fairly high level. I was invited to the office, where most of the panel was in the room even though one interviewer joined remotely. We spent most of the time on my past experience, how I had handled problems on earlier projects, and how I explained my reasoning. There was no coding exercise or deep implementation discussion. A la…
- Arista Networks Software Engineer linked-list and tree interview experienceArista Networks · Software Engineer · Technical Screen · Jul 2026
After recruiter outreach, I had a DSA-heavy technical interview about linked lists and trees. The interview focused on how I reasoned about memory and pointers, not only whether I reached the final code. It lasted about an hour, and the interviewer was chill. I had to explain storage and memory use while building or tracing a solution, then answer follow-ups on traversal and pointer behavior. In…
- Arista Networks Software Engineer live coding interviewArista Networks · Software Engineer · Technical Screen · Jul 2026
The process felt simple and organized. After a short recruiter-style beginning, I entered live technical rounds. A few people took turns asking questions while I worked in real time. The session lasted about an hour and combined behavioral questions grounded in my resume with one LeetCode-style problem. I also went through a similar three-step process in which every stage involved live coding. Th…
- Aristocrat Software Engineer interview: testing, SQL, and Linux basicsAristocrat · Software Engineer · Technical Screen · Jul 2026
After recruiter outreach, I had a focused technical conversation. It combined situational scenarios with testing knowledge, SQL query fundamentals, Linux commands, and different types of testing. A recurring question was how I would contribute to the company, framed through basic testing practices. The difficulty felt average, and the process matched the work the role appeared to involve. I felt…
- Arm Software Engineer interview: presentation, programming and technical depthArm · Software Engineer · Technical Screen · Jul 2026
The process moved quickly from a recruiter call into a technical screen. I spoke with a hiring-manager-style interviewer, then had several technical interviews. One round combined a presentation and a programming test. The sessions generally moved from my background and previous work into theory, data structures, algorithms and coding. The interviews were structured but challenging, with both tec…
- Arrive Logistics Account Executive interview: onsite rep shadowingArrive Logistics · Account Executive · Onsite · Jul 2026Offer
Recruiting contact moved quickly into a small sequence of interviews, and I never felt like I was walking in blind. Early conversations with the recruiter covered my background, why I was interested in sales, and a deeper walkthrough of the role and company. I had a clear contact person and fast communication about scheduling and next steps. Onsite, I toured the facility and shadowed an experienc…
- Ascendion Software Engineer interview: fair project questions followed by silenceAscendion · Software Engineer · Jul 2026No response
After a recruiter call that pressed for immediate availability, I interviewed that same afternoon. Later, I was told to be ready for a final round in June, so I waited for the next update. What followed was a long silence. After the final-round readiness message, I did not get meaningful updates, and by late July the process still felt unresolved. The uncertainty weighed on me because it gave me…
- ASM Software Engineer interview: resume presentation and CS fundamentalsASM · Software Engineer · HR Screen · Jul 2026
After a quick recruiter touchpoint, I had a 60-minute Teams interview with two senior software engineers. We began with my resume and projects, including questions about what I had built and how I approached it. Then we covered several straightforward CS fundamentals and finished with a manageable coding challenge. Later rounds followed a similar pattern: a short presentation about my work, follo…
- ASML Software Engineer interview: a single-attempt HireVue video screenASML · Software Engineer · HR Screen · Jul 2026
I started with a HireVue video round where I recorded answers to a few prompts on my own time. It was straightforward and low stakes, mostly common questions about me rather than deep technical material. The unusual part was talking to a camera instead of a person, but the questions did not ask for anything unexpected. The format was consistent: short preparation, a brief response window, and one…
