Interview Experiences

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

Share yours, earn XP

8 stories

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

HubSpotSolutions Engineer
Reported May 2026

HubSpot Solutions Engineer: CodeSignal round followed by a long wait

After an initial screening, I moved into a CodeSignal round, and the process felt quick. The recruitment team was responsive, and it didn't take long to get from the first screen to the CodeSignal stage. The experience felt smooth overall, but I never reached a later stage and eventually received a rejection. On my second attempt, the recruiter asked general questions along with questions about m…

RejectedHR Screen0
HubSpotAccount Executive
Reported May 2026

HubSpot Account Executive: mock cold call and manager role plays

I interviewed for the HubSpot Account Executive role. The process was generally straightforward and well explained, with a consistent focus on sales execution over roughly three to four weeks. The recruiter screen was a short call about my background and motivation, along with high-level questions about KPIs, daily work, perks, compensation, and the interview flow. The mock cold call or role play…

HR Screen0
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
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
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
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

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