Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

4433 stories

Likes earn the author +10 XP for the first 3 likes each day

BoeingSoftware Engineer
Reported Apr 2026

Boeing Software Engineer interview with a one-hour behavioral panel

Recruiter outreach led to a virtual interview with several hiring managers. The conversation was heavily behavioral and lasted about an hour. They asked about my background, what I'd done before, and how my experience could benefit the company. I was repeatedly asked to explain my past work clearly instead of simply naming projects. It started with the usual "tell me about yourself" question, the…

OfferOther0
CanonicalSoftware Engineer
Reported Apr 2026

Canonical Software Engineer interview spanning React, C++, Linux, and full-stack JavaScript

I interviewed for a Software Engineer role through a multi-interview, all-technical process. It moved from front-end topics into broader full-stack engineering, including Linux and open source. In the front-end interview, I was asked about React and general front-end topics. The systems and programming interview shifted to C++ and Linux. Another round covered full-stack development fundamentals i…

Technical Screen0
ASMLCustomer Success Engineer
Reported Apr 2026

ASML Customer Success Engineer interview with an early end and a separate video assessment

The interview got off to a rough start and threw me off right away. The meeting felt awkward and rushed, and I didn't think the interviewer had strong practical familiarity with the job details we were discussing. The conversation barely moved beyond basic prompts, and it ended earlier than planned. I didn't feel I had a fair chance to engage. I had expected a deeper evaluation, but the interview…

Other0
CanonicalSoftware Engineer
Reported Apr 2026

Canonical Software Engineer technical rounds on Linux and open source

I interviewed for the Software Engineer role and went through a two-track technical process in the middle of a longer interview sequence. One track focused on architecture and engineering depth. The other covered Linux, open-source topics, and platform fundamentals. In the software architecture and engineering round, I was asked about architecture qualities, engineering methodologies, and how eng…

Technical Screen0
Epic SystemsSoftware Engineer
Reported Apr 2026

Epic Software Engineer interview: assessment funnel with math, logic, and coding

I started with a basic phone interview about my resume and why I was interested in the role and company. After that, I completed an assessment with several parts: a personality section, math and logic sections, and coding. Once I finished those, I had a longer final interview that combined a case study with behavioral questions. The final conversations felt fairly normal. They focused mostly on f…

Other0
ExperianSoftware Engineer
Reported Apr 2026

Experian Software Engineer interview: timed Q&A with 60 seconds to prepare

My first step was a quick interview that felt almost like a timed question-and-answer session. There were 4 to 5 questions, and I was at a "no person" stage, so it didn't feel like a traditional conversation. I had about 60 seconds to plan each answer and roughly two minutes to deliver it. The pacing stood out. The questions didn't leave much room to meander, so I had to organize my thoughts quic…

0
CanonicalSoftware Engineer
Reported Apr 2026

Canonical Software Engineer interview with a long written stage

I interviewed for a Software Engineer role, and the overall experience felt extremely punishing. It started with an unusually long, essay-style written stage, followed by aptitude and other tests, and ended with a slow or non-specific rejection. For the written interview, or long questionnaire, I answered extensive essay-style questions about my background. They often asked for school-related det…

Online Assessment0
BairesDevSoftware Engineer
Reported Apr 2026

BairesDev Software Engineer interview with weeks of silence

I went through a structured process for the Software Engineer role: an initial contact, a short screening call, a technical test on their platform, and interviews with technical interviewers and a team lead. The process itself felt fairly standard. After I completed everything, though, communication basically went silent. The uncertainty was the hardest part. I waited weeks without an update, eve…

Online Assessment0
ZscalerSoftware Engineer
Reported Apr 2026

Zscaler Software Engineer interview: DSA, OOPs, DBMS, and C++

My process was compact. I had one technical interview followed by a project round. The technical discussion included an hour of general discussion and then two DSA questions. We also covered basic OOPs, database management system topics, and C++ fundamentals. The overall level felt easy, and the structure didn't overwhelm me with too many moving parts. I still didn't receive an offer. My lingerin…

Technical Screen0
Lucid MotorsSoftware Engineer
Reported Apr 2026

Lucid Motors Software Engineer interview on motion planning and controls

The interviews focused heavily on motion planning and controls from the beginning. The hiring process felt organized, and the technical questions were reasonable, but I was expected to think as if I were actually designing the systems. I had to cover system design along with coding related to motion planning and control. I wasn’t only asked to name components. I had to explain how I would structu…

Other0
HubSpotBackend Engineer
Reported Apr 2026

HubSpot Backend Engineer: CodeSignal, systems design, and project deep dive

I went through a fairly classic HubSpot SWE process that started with an online assessment. Mine was a CodeSignal-style test. I also saw that there was an option to skip the OA if I had a recent score from another company. Either way, the early technical assessment was the first filter. After that, I had a short recruiter chat and then a longer technical sequence. The technical portion was split…

OfferOnline Assessment0
ServiceTitanSoftware Engineer
Reported Apr 2026

ServiceTitan Software Engineer interview with async/await and system design

My process started with a recruiter screen and then moved into three technical rounds. In the first two, I spent long sessions pair programming. I implemented a custom data structure from an interface, then worked on parallel processing with async/await. The difficulty felt medium or easier, and the interviewers were fair and clear, so I could collaborate and ask questions as I went. The third ro…

RejectedHR Screen0
DrwQuantitative Analyst
Reported Apr 2026

Drw Quantitative Analyst math test and options theory interviews

After a recruiter call, the process moved into a math and probability test. It was difficult enough that it didn't feel like a formality. Then came an HR screen followed by several interviews across different teams, with questions focused heavily on probability and option intuition. Early in the process, I was told that option theory was something they taught internally and wouldn't necessarily b…

Other0
DuolingoSoftware Engineer
Reported Apr 2026

Duolingo Software Engineer tree traversal and graph coding assessment

After a conversation with a recruiter, I did a technical screening focused on a coding problem that felt very "standard" for interviews, something like a tree traversal. There was also a short follow-up about how I would improve the algorithm's efficiency. The interviewer kept the conversation moving. Although the core question wasn't unfamiliar, the optimization questions made me slow down and t…

HR Screen0
HubSpotSoftware Engineer
Reported Apr 2026

HubSpot Software Engineer interview with two systems design rounds

I went through a loop in which an online assessment led into human interviews, and the technical work focused heavily on system design. After the initial coding assessment, I had multiple rounds, including two separate systems design interviews and a coding interview. I spent most of the process working through architecture questions. One systems design discussion centered on a streaming platform…

Online Assessment0
TwitchSoftware Engineer
Reported Apr 2026

Twitch Software Engineer interview with a CodeSignal design and debugging assessment

I applied to Twitch for a Software Engineer role, completed an assessment focused on design and debugging tasks, and then didn't move forward. The OA was a CodeSignal-style assessment with a system-design-and-coding prompt split into two parts. First, I had to implement classes and functions. Then I had to debug a helper class. I didn't hear back after the assessment. My takeaway was that the "de…

Online Assessment0
AKUNA CAPITALQuantitative Analyst
Reported Apr 2026

AKUNA CAPITAL Quantitative Analyst interview with options lectures and probability questions

Before any live interviews, I went through a mini-lecture series covering trading and options basics. There were three lectures, each paired with an online quiz that I had to complete before moving on. The process felt selective because only the top performers on those quizzes were chosen for the interview round, although they never explained exactly how the "top" threshold was determined. I then…

Online Assessment0
GrammarlyAccount Executive
Reported Apr 2026

Account Executive interview at Grammarly: Competitive offer and fair negotiation

From the beginning, the process felt smooth and fair. Follow-ups were scheduled quickly, everyone showed up on time, and the recruiter kept me updated with clear instructions and timely feedback at each stage. That tone continued in my conversations with the team. Even though the process took time, it never felt messy or stressful. I went through a straightforward set of rounds focused on clarity…

Offer0
SamsaraSoftware Engineer
Reported Apr 2026

Samsara Software Engineer, HTML parsing and simple system design

After several recruiter conversations, the process moved through technical discussions, a system design exercise, and a cultural fit check. The recruiting team kept everything organized, and the interviews felt efficient and coherent. One early step was described as a quick verification call with the recruiter. The system design exercise was supposed to be simple rather than elaborate. I also got…

OfferTechnical Screen0
Trexquant InvestmentQuantitative Analyst
Reported Apr 2026

Trexquant Investment Quantitative Analyst, medium LeetCode-style technical screen

About a week after the recruiter call, I had a technical screen. We went through my resume, then I solved a medium LeetCode-style coding problem. It felt like a straightforward test of whether I could turn my background into clean, working code. I eventually reached the next step, which sounded like it was leading toward a superday. I hadn't completed the onsite portion yet, so the process stoppe…

Technical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP