Interview Experiences

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

Share yours, earn XP

5 stories

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

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
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
HubSpotSoftware Engineer
Reported Mar 2026

HubSpot Software Engineer interview: banking-system assessment and system design rounds

My process started with a coding assessment under tight constraints. The time pressure felt real, and the tasks were divided into multiple levels. Each level opened only after I completed the previous one. I didn't get through all the levels. The prompt involved designing a banking system, so it went beyond standard LeetCode mechanics. In another attempt, the CodeSignal online assessment was also…

RejectedOnline Assessment0
HubSpotSoftware Engineer
Reported Feb 2026

HubSpot Software Engineer interview with a panel-style mock scenario

My process started with a recruiter screen about motivation and fit. I then had a hiring manager round focused more on competencies, including how I'd handled different situations and explained my thinking, than on technical trivia. The next step was a panel-style mock scenario. The pattern stayed consistent: recruiter first, then deeper competency questions, followed by a panel scenario. It wasn…

0
HubSpotSoftware EngineerSenior+
Reported Jan 2026

Backend Track Loop Plus a Late JavaScript Round

Backstory / context My application was for a senior software engineer position at HubSpot, and my background is full-stack. The bulk of my work history is shipping production systems with JavaScript, TypeScript, React, Node.js and various cloud services. Early in the process the company asks whether you lean toward a frontend or a backend interview track. I told them backend, and that answer set…

OfferOnsite0

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