READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 68 of 153
Interview experiences · Hotstar
Hotstar Software Engineer interview experience: AI system design
After recruiter coordination, I had two rounds that felt hard. The first tested AI fluency in a system-design problem where AI use was allowed. I had to decide how the proposed system would connect to an existing system and its data inputs, rather than receiving that integration design up front. The second round also focused on design, but it did not fit a familiar pattern. It asked for a difficu…
Interview experiences · Hudson
HRT Data Scientist Interview Experience — An OA and a Mean-versus-Median Estimation Interview
I recently finished HRT's OA and first Zoom interview. Sharing the questions here—hope this helps people interviewing later! OA I received the coding OA invitation a few days ago and finished it today. There were three questions: Fancy Number A fancy number is a number that contains only 0 and 1 when written in base 4. Given n, return the count of fancy numbers smaller than n. This probably needs…
Interview experiences · HubSpot
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…
Interview experiences · HubSpot
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…
Interview experiences · HubSpot
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…
Interview experiences · HubSpot
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.…
Interview experiences · HubSpot
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…
Interview experiences · HubSpot
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…
Interview experiences · HubSpot
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…
Interview experiences · HubSpot
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…
Interview experiences · Hudson River Trading
Hudson Intern Software Engineer Interview Experience — A LeetCode-Easy Tree Path Question With No C++ Trivia
Fresh C++ SWE (Intern) first-round interview report Last week I had my first round for the C++ SWE (intern) position, a 1-hour Zoom coding interview. We spent a few minutes at the start briefly chatting about background, then moved into the problem. The question: given a binary tree where each node has an integer value, and a target, determine whether there's a path from root to leaf where the su…
Interview experiences · Hudson River Trading
Hudson River Trading Intern Algorithm Developer Interview Experience — Rejected After the Morning Onsite Rounds
I went to the onsite around October or November last year — sharing my experience getting rejected. I'm a US undergrad. I went through one coding OA and two math online interviews before getting to the onsite. The math rounds covered some probability and combinatorics questions — you need a solid grasp of the Central Limit Theorem and basic probability. The onsite has four rounds: programming, da…
Interview experiences · Hudson River Trading
Hudson River Trading New Grad Software Engineer Interview Experience — Perfect OA, Then a Rejection After One 30-Minute Coding Round
OA 70 minutes, 4 problems. The first two were super easy. The third one: given an m*n array, you define a diamond by its center point and radius, compute the sum of all the numbers inside the diamond, and return the largest sum among all valid diamonds. The fourth one was street lamps: given a set of lamps, each lamp has a center c and a radius r, so the segment [c-r, c+r] is lit by that lamp. Fi…
Interview experiences · Hudson River Trading
Hudson River Trading Site Reliability Engineer Interview Experience — Rejected After Answering Every Question
Role: Site Reliability Engineer I had found a really useful interview report on the forum before mine, and the overlap with what I actually got asked was pretty high. This is also my own area of work, so going into the interview I felt like I had a 100% chance of passing, but I still failed. I'm not really sure why. Let me write up roughly what was asked — honestly you can just ask AI what kinds…
Interview experiences · Hudson River Trading
Hudson River Trading Software Engineer interview
After a recruiter screen, I entered a long technical process centered on a take-home. The lack of feedback was difficult. I spent hours trying to meet the expected behavior without useful checkpoints. The RTL and verification assignment was ambiguous. I adapted my scoreboard to match the buggy RTL behavior, even though I thought a model should stay more abstract and respond only to the specified…
Interview experiences · Hudson River Trading
Hudson River Trading Software Engineer Interview Experience — an OA with almost no test cases given
Just finished the SWE OA, same setup as the reports people have posted in past years. Overall it wasn't that hard — compared to some other trading companies it wasn't especially hard, but the OA email did say you need to write your own test cases, and that turned out to be true. They give very, very few test cases, and there are a lot of edge cases you have to figure out and test yourself. On one…
Interview experiences · Hudson River Trading
Hudson River Trading Software Engineer interview on OS and C++
The process was low-level from the start. After an initial online assessment or coding step, I entered live rounds that demanded deep knowledge rather than surface familiarity. I was asked how things work under the hood, down to memory and kernel operation, with an emphasis on the kind of understanding that gives a developer full control. One screen focused on OS topics at an implementation level…
Interview experiences · Hudson River Trading
Hudson Software Engineer Interview Experience — A Watcher-and-Players Puzzle in the Technical Screen
This is the problem the interviewer described to me verbally during the technical screen, done in a coderpad environment. They also gave an example along with it. There is a game with multiple players. The road starts at position 0 and ends at position L. Each player has a starting position, and players can only move to the right, one unit per second. There is a watcher, starting at position W, i…
Interview experiences · Hudson
Hudson Software Engineer Interview Experience — An OA on Budgeted Item Purchases
Input: prices[]: An array of length n, where prices[i] is the price of item i. queries[]: A two-dimensional array whose elements are [start_i, budget_i]. Each query means that only items with indices greater than or equal to start_i may be purchased, with a total budget of budget_i. Rules: Each item may be purchased at most once. The order or positions of the items do not matter; they do not have…
Interview experiences · Hudson River Trading
Hudson Software Engineer Interview Experience — Two Verbal Technical Screens, No Test Cases
Both rounds were the interviewer dictating the problem out loud, so I had to take notes — miss one parameter and you're in trouble. Round 1: a one-dimensional array, N players walking to the right. A watcher starts at an initial position and watches the players. A player being watched can't move. The watcher switches direction according to a given list of timestamps. Given a termination time T, f…
Interview experiences · Hyland
Hyland Customer Success Engineer Interview Experience: Three rounds and an unclear decision
I completed three interview rounds, and the format stayed fairly consistent throughout. Each technical round lasted somewhere between around 30 minutes and nearly two hours. After all three, it looked as though the process would continue with a larger shortlist. What happened next threw me off. They selected a group of interns, then abruptly changed course and chose a smaller subset, specifically…
Interview experiences · IBM
IBM Consultant interview with a one-attempt recorded assessment and live storytelling rounds
After I applied, the process began with an online recorded assessment. It felt fast and high stakes because I had only one attempt for each answer. The short timed set covered behavioral and consulting-style questions, including working with others, pressure, and close deadlines. In the recording format, I had a brief moment to think and then a couple of minutes to answer. My camera had to stay o…
Interview experiences · IBM
IBM Intern Data Scientist Interview Experience — Lead Scoring Case Twice, Offer in Two Weeks
After I submitted my application, the OA went out automatically — one Python question and one SQL question, nothing too hard. First round (mainly asked about my resume, a deep dive into the ML project on my resume, and a case): What's your experience of building a statistical model and machine learning model? What kinds of variables/features did you use? Did the client only care about the results…
Interview experiences · IBM
IBM Intern Data Scientist Interview Experience — Marketing Lead-Scoring Case, Offer in Two Weeks
After I submitted my application, I automatically got sent an OA — one Python question and one SQL question, not too hard. First round (mainly asked about my resume, a deep dive into the ML project on my resume, and a case): What's your experience building a statistical model and a machine learning model? What kinds of variables/features did you use? Did the client only care about the results, or…