READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 127 of 153
Interview experiences · Sprinklr
Sprinklr Software Engineer interview: running median and LRU
I started with an online coding assessment, then moved into interviews that leaned heavily on classic DSA and competitive-programming-style problems. In the first interview, I was asked about finding the median in a running stream and about an LRU cache. It felt practical, as though they were testing whether I understood the data structures underneath the ideas. That round also included a horses…
Interview experiences · Squarepoint
Squarepoint Data Scientist Interview Experience — First Round, Three Coding Questions with a Friendly DQA
The interviewer is a DQA who already works there. The conversation was relaxed overall, the interviewer was easygoing and happy to talk and give hints, and the whole thing felt more like chatting while solving problems. Climbing stairs: each step you can choose from xx ways of moving, and you need to count how many ways there are to reach step n. This maps to LeetCode 70, and DP is enough. There…
Interview experiences · Squarepoint
Squarepoint Data Scientist Interview Experience — Six-Question OA With Rotating Questions
Squarepoint's OA has 6 questions total. The first four are probability, statistics, and reading a piece of code to analyze its time complexity. The fourth question gives a scenario and asks which kind of bias in statistics the scenario describes. None of these are hard — you can finish them in 5-10 minutes or even faster. The last two questions are coding. The first one is easy: a store has n dif…
Interview experiences · Squarepoint
Squarepoint Desk Quant Analyst Interview Experience — A Screen Full of Probability Puzzles and Finance Basics
Let X and Y be independent Uniform(0,1) random variables. What is the probability that the product is greater than one-half? Imagine we have a deck with 52 cards and play a game: I draw one card randomly, then you draw one from the remaining 51 cards. The higher card wins. If the two cards have the same rank, we return them, shuffle, and repeat the draw until a winner is determined. Who has the h…
Interview experiences · Squarepoint
Squarepoint Intern Software Engineer Interview Experience — Two Onsite Rounds, Rejected After a Two-Week Wait
The first round was an OA — I already posted about that separately, so check it out if you get the chance. After the OA I did two rounds of VO. Three rounds in total. Round 1: This interview was with a junior software engineer. He asked a few simple resume questions first — nothing to worry about, the interviewer just wants to understand your background. After that he asked some technical questio…
Interview experiences · Squarepoint
Squarepoint Quantitative Researcher Interview Experience — Algorithms, Data Structures, Bash, and Dice
Short version: two algorithm questions, one data-structure question, one development-related question, and one statistics question. For an array of n positive integers arr[n] and an integer k, a subarray is good if it contains at least k distinct integers. Find the minimum length of a good subarray; otherwise return -1. Given a list containing an odd number of positive integers, you may remove ex…
Interview experiences · Squarepoint
Squarepoint Risk Technology Software Engineer Interview Experience — A Three-Month Process Ending in Rejection
I am an older programmer. After graduating in 2016, I spent my early career doing C++ backend development at internet companies. After the pandemic, I moved into quantitative development. My most recent job was developing trading infrastructure in the Singapore office of a small quantitative firm, and my former employer laid me off in March. From March through May, I interviewed intensively with…
Interview experiences · Squarepoint
Squarepoint Software Engineer Interview Experience — OA With Two Coding Questions and an All-or-Nothing Pass Bar
Just finished the Squarepoint OA, sharing the two coding questions. The first question was about maximizing store revenue. Given n items, each with quantity[i] representing the remaining stock, the price equals the quantity. There are m customers, each buying one item, and the goal is to maximize revenue. I solved it with a max heap — each time popping the largest, selling it, then pushing it bac…
Interview experiences · Squarespace
Squarespace Senior Data Scientist Interview Experience — A Take-Home on Predicting Seller Intent
Timeline & standard rounds The whole process ran from mid-November to mid-December, about a month. Round 1: Recruiter Screen (30 minutes) Standard behavioral questions and background introduction. Round 2: HM Screen (30 minutes) Talked with a Software Engineering Manager. Mainly dug into past project experience, cross-team collaboration experience, and assessed culture fit. Round 3: Technical int…
Interview experiences · Ss&C Technologies Holdings
Ss&C Technologies Holdings Financial Analyst interview: clipped technical screen
I did not feel much emotion during the process. It was very businesslike and clipped. They skipped the usual introduction and went straight into technical questions. When I asked questions back, the answers were extremely short, as though they were trying to keep each reply to a few words. Most of the interview was a barrage of technical checks, with perhaps one situational prompt mixed in. The p…
Interview experiences · Stackadapt
Stackadapt Account Executive interview: 10-day project and presentation
The process felt more rigorous than I expected from the outside. After a recruiter screen, I interviewed with a Director about a week later. The conversation focused heavily on scenarios, and I also got deeper industry knowledge questions than I was ready for. The pacing and format changed as the rounds went on. Next was a project and presentation round with a Director and a Manager. I had 10 day…
Interview experiences · Stackadapt
Stackadapt Account Executive interview: three rounds with clear feedback
The interview process felt unusually smooth and respectful to me. The recruiter communicated throughout, and the company’s values came through in how people treated me. I wasn’t ghosted, and the process was clear. I went through three rounds and spoke with five different people. Those conversations helped me learn about the role and how the team worked. Each one felt honest and grounded rather th…
Interview experiences · Stackadapt
Stackadapt Account Executive interview with shifting final rounds
My experience with the recruiter and recruiting manager was frustrating from the start because the logistics never felt stable. I was repeatedly told I'd be meeting one person, only for the meeting to change at the last minute. It became hard to keep track of who the actual hiring manager was, especially after I went through multiple rounds with people who all had the same title. I also received…
Interview experiences · Stackadapt
Stackadapt Software Engineer case study with unstable evaluation standards
My process started positively, but the final stage was deeply disappointing and left me uneasy about the evaluation standards. I was asked to complete what was presented as a case-study assignment for an enterprise agent solutions developer role. Although it was part of the interview, the work felt close to a real product and architecture project compressed into a short timeline. The most frustra…
Interview experiences · StackAdapt
StackAdapt Software Engineer Interview Experience — An OOP Recipe and Inventory Coding Question
This was more of an OOP-style question, and the problem itself wasn't hard. You're given two concepts. Recipe stores the dish name, how long it takes, and the ingredients it needs. Supply stores ingredients and their inventory counts. A dish can also appear as an ingredient — for example, one dish in Recipe can be used as an ingredient for another dish. Based on this, you implement a series of fu…
Interview experiences · StackAdapt
StackAdapt Software Engineer Interview Experience — Windowed Map Coding Question, Rude Interviewer
The question was to implement a Windowed Map — a KV store with a time window. Data arrives at irregular intervals, and only the data within the most recent window size / time window is kept; anything outside the window is expired and no longer visible to the user. You need to implement 3 methods (as efficiently as possible): Get(key): if the key exists and hasn't expired, return the value; otherw…
Interview experiences · Stackadapt
Stackadapt Software Engineer interview with four rounds and a three-hour session
My interview felt intense from the beginning. I went through four rounds back to back, including one session that lasted around three hours. The questions were difficult. The interviewers were kind, but the pace and scope made it hard to give a complete answer. One technical round was especially rough. I had to complete both a LeetCode-style medium problem and a system design prompt within the sa…
Interview experiences · Stackadapt
Stackadapt Software Engineer three technical rounds
After a recruiter reached out and invited me to schedule, the process quickly became a sequence of conversations that felt somewhat shuffled compared with what I had been told. I completed an HR screen, then manager and culture-style interviews, followed by three technical rounds. Each technical round combined live coding with a system design prompt. What caught me off guard was that the intervie…
Interview experiences · Starr Companies
Starr Companies Software Engineer interview experience
Within a few business days of applying, I was invited to interview through an AI-style HireVue recording. I logged in, read one prompt at a time, had a short preparation window, and recorded a camera response. The questions were mostly STAR-style behavioral questions, with two attempts per prompt. Using the second attempt submitted it automatically. Near the end, a coding challenge appeared in th…
Interview experiences · State Farm
State Farm Software Engineer interview experience
A few business days after applying, I received an interview invitation. The first step was asynchronous HireVue: I logged in, read each prompt, and recorded answers on camera. The behavioral questions were standard STAR-style questions, but near the end they added a coding task that had to be finished in the same recording window. The coding part was difficult largely because I could not ask clar…
Interview experiences · Stefanini Brasil
Stefanini Brasil Software Engineer interview: client architecture discussion
I began with an alignment conversation with HR, then interviewed with technical leadership. After that, I was introduced to a client. The role would be in a financial context, so the conversation stayed close to the kinds of decisions and architecture I had worked on before. The technical part was light but still required clear explanations. I was asked about choices I had made in an earlier hack…
Interview experiences · Stefanini Brasil
Stefanini Brasil Software Engineer interview: organic and conversational process
The interview unfolded in a fairly organic way. There were different moments, a few pauses, relaxed conversations, and varied questions along the way. I answered naturally and did not feel as though I was being interrogated. My impressions became clearer as the discussion moved forward. Overall, the process continued normally to the end, with balanced expectations. I left with the sense that the…
Interview experiences · Stellantis Financial Services Us
Stellantis Financial Services Us Software Engineer interview
I began with a short phone call about why Stellantis and why the role suited me. It was the usual walk-me-through-yourself and fit discussion. About a week later, I had a Teams interview. It was one behavioral session with a couple of targeted questions, followed mostly by a normal conversation. I used STAR to organize my examples, and the tone stayed easygoing and low-stress. There were no surpr…
Interview experiences · Stellantis
Stellantis Software Engineer interview
The recruiter first called to ask why I wanted Stellantis and why I thought I fit. Soon after, I had a Teams interview. It was mostly behavioral, and I used STAR to keep my answers organized, but the exchange did not feel like an interrogation. The 30-minute virtual interview was a small panel of engineers, with no HR present. They asked a few pointed questions and talked through examples from my…