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

BoeingFrontend Engineer
Reported Mar 2026

Boeing Frontend Engineer interview, Korean and English technical sessions

My interview was split into two technical segments with different interviewers. First, I had a 30-minute technical interview in Korean with three engineers. Then I had another 30-minute technical session in English with two hiring managers. The overall atmosphere felt comfortable, and the technical questions were mostly based on what I'd put on my resume. Because the questions were tied closely t…

OfferTechnical Screen0
Clipboard HealthSoftware Engineer
Reported Mar 2026

Clipboard Health Software Engineer interview with two API scripts

I interviewed for a Software Engineer role with an overall average difficulty. I spent a short burst writing scripts and then waited. For the assignment, I wrote two API scripts after being brought into a process that referenced "top workers/workplaces" data. I submitted them and waited. Afterward, I had a follow-up interview where they reviewed what I produced. I didn't receive an offer, and I'm…

In progressTake-home Project0
CanonicalSoftware Engineer
Reported Mar 2026

Canonical Software Engineer online assessments with unclear follow-up

I interviewed for the Software Engineer role through a process that was quick to schedule but ultimately unclear. It involved questionnaires and online tests, followed by either an early decline, no follow-up, or a rejection with little explanation. I filled out a form-like application and completed a detailed written interview about my background and problem-solving. I also took an aptitude-styl…

RejectedOnline Assessment0
Clipboard HealthSoftware Engineer
Reported Mar 2026

Clipboard Health Software Engineer interview: assessment-first process with documentation review

I interviewed for a Software Engineer role through an assessment-first process that moved quickly into interviews. The first step was a coding and logic assessment. If the results looked promising, I was scheduled for later interviews. In one interview, we discussed what I had done in the take-home assignment and how I had approached the problem. I then completed another documentation-style asses…

Take-home Project0
GarminSoftware Engineer
Reported Mar 2026

Garmin Software Engineer interview: career-fair concepts and electronics checks

I interviewed in formats that felt less like a traditional software interview and more like career-fair conversations or quick technical assessments. Some sessions were brief but focused heavily on concepts. At the career fair, I had a general conversation about my resume followed by technical concept questions. The interviewer asked whether I knew specific ideas. After that initial discussion, I…

Onsite0
Clipboard HealthSoftware Engineer
Reported Mar 2026

Clipboard Health Software Engineer interview with PR and TDD work

I interviewed for a Software Engineer role through a difficult, multi-step technical process. It included pull request work and written technical thinking before I was turned down. I submitted code through a pull request and then had a follow-up interview that referred to a technical design document. I completed a TDD-style write-up for a feature and then went through another PR or related assign…

Take-home Project0
NavanAccount Executive
Reported Mar 2026

Navan Account Executive interview with informal-first structure and vibe fit

My first step was a recruiter screening call that became one of the most discouraging conversations I'd had. The interviewer's delivery felt oddly automated, as if my answers weren't being heard. I'd finish a response, and they would immediately move to the next question without any reaction or follow-up. The whole thing felt pointless. The same problem showed up differently as I moved into what…

HR Screen0
HubSpotSoftware Engineer
Reported Mar 2026

HubSpot Software Engineer interview: final rounds canceled within three hours

My experience started normally. I completed an OA built around an HTTP GET style prompt, then was scheduled for a behavioral step and final rounds. While I was waiting, I even spoke with someone internally because I was trying to understand what was happening. The final-round day still feels unreal. They scheduled me for the end-stage interviews and then canceled them less than three hours later.…

RejectedOnline Assessment0
GrammarlySoftware Engineer
Reported Mar 2026

Grammarly Software Engineer interview: backend coding and team match

I started with a recruiter screen, then moved into CS fundamentals and a backend coding interview. I also presented my projects before going through team-match conversations. The process felt well organized and clearly communicated. My recruiter kept me grounded by proactively sharing detailed information about each stage. The technical interviews were challenging but fair. I could tell they care…

OfferHR Screen0
HubSpotSolutions Engineer
Reported Mar 2026

HubSpot Solutions Engineer interview: recruiter screens and delayed follow-up

I barely got started. I sent in my CV and had a first interview scheduled, but the call itself was extremely brief and felt oddly disconnected from what I expected. It ended quickly, and I got the impression that their compensation expectations were far below market. The fit just didn't seem to take hold. In another recruiter screening, I was told I'd move forward after the call, but the follow-u…

RejectedHR Screen0
WhatnotFull Stack Engineer
Reported Mar 2026

Whatnot Full Stack Engineer: recruiter call ended before technical depth

My first step was a quick recruiter call focused almost entirely on my projects. I tried to give a one-sentence summary of each team and company so I could cover my experience efficiently, but the interviewer stopped me earlier than I expected and focused on one project in more detail. The conversation ended shortly afterward, and I was declined. What bothered me was that it never went into much…

Rejected0
Trexquant InvestmentQuantitative Analyst
Reported Mar 2026

Trexquant Investment Quantitative Analyst interview: one-month process ending with a CEO round

I first spoke with a recruiter about my background and general fit. That was followed by an online technical interview with a quant researcher focused on my analytical and quantitative skills. After that, I attended an onsite superday with several back-to-back interviews with different team members. The final stage was an interview with the CEO. The process took around a month. The recurring topi…

HR Screen0
DocusignAccount Executive
Reported Mar 2026

Docusign Account Executive interview with multiple presentations

I went through an Account Executive hiring process that felt average to difficult. It dragged on for months, with several rounds, shifting timelines, and a lot of work for the candidate. The early recruiter conversations seemed promising. I then had additional interviews with hiring managers, followed by separate presentations that I had to prepare and deliver. Those presentations took substantia…

RejectedHR Screen0
WhatnotSoftware Engineer
Reported Mar 2026

Whatnot Software Engineer interview with HireVue and Karat

My process started with a HireVue-style interview, followed by a Karat technical interview. The technical portion moved from easy to harder LeetCode questions, and the increase in difficulty was noticeable. After the Karat round, I had a short recruiter screening. If I passed that, I would move on to another technical interview with engineers. That phase was described as including more problem-so…

Other0
Rocket LabSoftware Engineer
Reported Mar 2026

Software Engineer interview at Rocket Lab: Large take-home assignment followed by long silences

The process started with a recruiter reaching out, and scheduling moved quickly. I had a short phone conversation, then met with a senior software engineer and received a take-home test. I completed it promptly over the weekend and sent it back as requested. After that, everything stalled. There was no review of the submission and no clear rejection. I kept following up, but I never received a di…

No responseTake-home Project0
DrwQuantitative Analyst
Reported Mar 2026

Drw Quantitative Analyst interview focused on competitor strategy

What started as an unusually strategic conversation quickly felt unlike a normal hiring process. My initial discussion was with the head of the business, and the focus wasn't on my background or skills. Instead, I was questioned about what the firm's competitors were doing, where they were making money, and what ideas they might be using. The tone made it seem as though the goal was to learn abou…

Other0
GrammarlySoftware Engineer
Reported Mar 2026

Grammarly Software Engineer four-question coding assessment

My interview process started before I spoke with any engineers. I submitted an application and completed coding assessments with four questions, followed by an HR phone screen. After that, the process focused heavily on live, timed problem solving. I had two live coding rounds. One used LeetCode-style questions, and the other involved solving an actual problem from beginning to end. After the cod…

OfferOnline Assessment0
WhatnotSoftware Engineer
Reported Mar 2026

Whatnot Software Engineer interview with a one-hour LeetCode-style round

I had a one-hour LeetCode-style round with an engineer. The interviewer was present but very quiet while I worked, so there wasn't much back-and-forth or verbal guidance. The session felt more isolated than I expected, and I ended up not moving forward. The unusual silence is what I remember most. It put more pressure on me to drive the problem-solving process on my own. Location: United States.…

Rejected0
WhatnotSoftware Engineer
Reported Mar 2026

Whatnot Software Engineer interview: four rounds and a collaborative process

My interview loop had four rounds. It started with a technical screen focused on core software engineering skills, followed by coding, system design, and product sense rounds. The product sense round felt different from the others because it was more of a discussion than a typical question-and-answer session. The interviewers were kind and supportive throughout, and the overall tone felt collabor…

Technical Screen0
KlaviyoAccount Executive
Reported Mar 2026

Klaviyo Account Executive: repeated reschedules, missing Zoom details, and unanswered follow-ups

What stood out in my experience wasn't the interview questions. It was the communication and follow-through. I started with an initial recruiter interaction and then moved into later conversations, but the process felt inconsistent across several stages. There were short-notice reschedules, people who didn't show up, and rounds that started late without much explanation. The logistics also broke…

No responseOther0

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