READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 11 of 153
Interview experiences · ADP
ADP Software Engineer interview: project depth, Java ecosystem questions, and a final HR check
The interview process felt organized and quick, beginning with a large pool. Roughly fifty students were shortlisted, then the process moved through three stages. In the first technical round, I leaned heavily on my resume because the discussion focused on projects, including architecture choices and implementation details. Near the end, the interviewer moved to core DSA, especially searching and…
Interview experiences · ADP
ADP Software Engineer SQL and project interview experience
My process followed an online assessment, two technical rounds, and HR. The assessment filtered for coding and basic problem-solving. The interviews then focused more on concepts I would use day to day. SQL was a major part of the first technical round, including joins and outer joins. I also discussed OOP topics such as method overriding and overloading. The interviewer asked about a problem fro…
Interview experiences · Advanced Micro Devices
Advanced Micro Devices Software Engineer interview: technical panels and C++ STL
The first conversation was a quick discussion with the hiring manager about my day-to-day experience and previous work. From there, I moved into technical panels with several interviewers evaluating me at once. They asked about both problem solving and technical depth, and seemed interested in how I reasoned through a question. The panels included medium LeetCode-style problems and more logic-hea…
Interview experiences · Adyen
Adyen Account Executive interview: missing customer context
Recruiting contacted me several times over about two months. Once I finally replied, the process followed a normal path: recruiter first, then a hiring-manager round that felt as though it went well. The third round surprised me because nobody had told me it would be a set of hypothetical, multilayered customer questions. I could speak at length about my own customers and had strong stories, but…
Interview experiences · Adyen
Adyen Software Engineer Interview Experience — 100% on the OA, Rejected After the Technical Round
There isn't much Adyen interview experience on the forum, so let me contribute mine. I'd never heard of Adyen and didn't even know they hire in the US — they have an office in Chicago and require onsite for a few days. Interview process: HR -> HackerRank OA -> Technical -> System Design -> Leadership -> Board The OA had two questions: the first was LRU, the second was similar to combination sum,…
Interview experiences · Adyen
Adyen Software Engineer interview: unclear final communication
My interviews lasted a while, and the technical work was not the part that stayed with me most. I began with recruiter screening, then went through several rounds with technical discussion followed by leadership or manager-style conversations. At one point I was told I would be brought to the Amsterdam office for a leadership interview. That final round felt inconsistent with what I had shown ear…
Interview experiences · AECOM
AECOM Software Engineer interview: cooling systems and confidential project boundaries
My three-round process began with a talent screening call and then a deeper technical conversation with technical hiring managers. That discussion covered complex hyperscaler facility design, including dual-path hydraulic loops, strict thermal-margin calculations when switching between air and liquid cooling in mixed-density data halls, and rapid economizer or free-cooling switchovers during extr…
Interview experiences · AECOM
AECOM Software Engineer interview: supportive conversations and decision timelines
The process was structured without being high stress. I started with a recruiter or HR touchpoint, then spoke with technical or hiring managers about what I had done and what they expected from someone joining the team. The rounds focused on experience rather than obscure problems. Some interviews felt especially supportive. In one, the engineers responded quickly and made it clear I could ask qu…
Interview experiences · Affirm
Affirm Senior Data Analyst Interview Experience — A Downlevel After Passing the Take-home
In July, a kind younger alum referred me for Full Stack Analyst II. In early August, HR contacted me to say that role was gone and asked whether I'd consider another Senior Analyst role. After that, it was one step each week: HR call -> hiring manager interview -> take-home. The HM case: Analyze what could have caused the delinquency rate to jump in the past quarter. The take-home: What product a…
Interview experiences · Affirm
Affirm Software Engineer Interview Experience — A Log-Matching Question That Fed Into a Trust Score
Affirm phone screen — should be for an SDE2 role. The interviewer started with casual mutual introductions for about 10-15 minutes (didn't feel like it needed to take that long, but she kept talking and I didn't want to interrupt). The question was about two days of logs — find users who show up in both days and have loan type >= 2. The second part was to calculate a trust score. I finished writi…
Interview experiences · Affirm
Affirm Software Engineer Interview Experience — Failed the Easy Card Game Problem in the Technical Screen
I had reviewed nothing but hard problems and never reviewed this easy kind of one, and of course that's what I got. Ha. The problem: 52 playing cards, shuffle first, and each person takes a pile. Each round you compare whose top card is bigger. The side with the bigger card seems to take the other side's card too and put it aside together with their own (I forgot the exact rules, but I think that…
Interview experiences · Affirm
Affirm Software Engineer Interview Experience — Fraud Detection Coding and a Payment System Design Round
Four rounds total: one hour of coding + half an hour of behavioral questions + one hour of system design + half an hour of behavioral questions. The two behavioral rounds were just the standard questions. Coding round (the prompt was long, but not hard): Part 1: Live Fraud Detector (Debug Existing Function) Description One of Affirm's competitive edges is our ability to do credit underwriting and…
Interview experiences · Affirm
Affirm Software Engineer Interview Experience: payments design and poor recruiter communication
After an initial recruiter call, I entered a fintech-focused process. The roughly 30-minute screen covered my background, interest in fintech and BNPL, compensation, and location. A deeper hiring-manager conversation followed, covering past projects, technical decisions, and fit for the specific team. The coding portion was a 60-minute HackerRank session. Next came about an hour of system design…
Interview experiences · Affirm
Affirm Software Engineer interview: finance-style coding and a timed technical screen
My online assessment felt like a finance-specific LeetCode problem. Afterward, I had a 30-minute recruiter screen about the role and logistics, including compensation, the actual work and cultural fit. It wasn't a particularly deep conversation, but it gave me an idea of what they wanted. Next came a technical screen where I shared my screen for a timed coding problem. I only saw the prompt when…
Interview experiences · Agilent Technologies
Agilent Technologies Software Engineer interview: five-round onsite
After a recruiter call, I went through a longer sequence of evaluation rounds. About a week later I had a technical screen, followed by a five-round onsite. The onsite combined coding, system design, behavioral questions, and a domain-focused segment. It was intense and lasted several hours with multiple interviewers. I also saw that some roles in the process required a slide presentation about a…
Interview experiences · Agoda
Agoda Senior+ Data Engineer Interview Experience — Reschedule Red Flag, Then Five Questions in Under 20 Minutes
I applied cold just to see what would happen, and got an OA the very next day (I think it was one SQL question and one Java question, don't quite remember). The phone interview was originally scheduled for last week evening to match their daytime hours, but when it came time, the interviewer's HackerRank was broken and wouldn't open. It got rescheduled last-minute to this week, which felt like a…
Interview experiences · Agoda
Agoda Software Engineer interview: a moderate online assessment
My first major step was an online assessment with multiple-choice and DSA questions. It felt moderate rather than brutal, and I solved most of what I saw, so it came across as reasonably straightforward. I finished feeling that it was a solid fundamentals test instead of an obscure trick. I did not receive an offer, but it still seemed like a fair, well-scoped online screen. My performance mostly…
Interview experiences · Agoda
Agoda Software Engineer interview with screen-shared JavaScript coding
After speaking with a recruiter, I moved to a hands-on technical stage where I shared my screen. The exercise resembled a common LeetCode format and was not tied to one programming language. I used JavaScript even though the role leaned more toward Java. The developer running the session was approachable and supportive, so it felt more collaborative than competitive. I left with a positive impres…
Interview experiences · Ai2
Ai2 Senior Software Engineer Interview Experience — A Streaming Step-Hierarchy Design Problem
The question gives a set of StepProgressEvents, where each event contains: The same step_id can receive multiple updates — for example first running, then later done — and events can also arrive out of order. Each step can have child steps, and in the end you need to maintain and output the current latest step hierarchy, for example: Also, after the initial batch of events is processed, the syste…
Interview experiences · Aim Intelligent Machine
Aim Intelligent Machine Senior+ Software Engineer Interview Experience — A Merge Intervals Question and a Curveball Follow-up
This is a startup building autonomous excavators. I felt like I wasn't really a match for it, but a recruiter reached out, and since the job market is rough right now, I figured I'd use it as practice. The role is senior, and they have an office in Bellevue. I first got a hardware guy who spent a while asking why I was considering their company and stuff like that. I told him there wasn't really…
Interview experiences · Air Liquide Home Healthcare
Air Liquide Home Healthcare Software Engineer electronics experience online interview
My first step was an online interview that felt comfortable and smooth. The interviewer asked about my technical knowledge and my experience in electronics. It was not confrontational or excessively technical. It felt like a conversation about how I thought and what I had done. The interviewer also helped me understand the role and how my background could translate into contributions at the compa…
Interview experiences · Airbnb
Airbnb Data Engineer Interview Experience — Four-Round Onsite, Then a Recruiter Who Ghosted Me
Not many interview reports out there, so let me add mine — hope it helps. My recruiter was unreliable and ghosted me right after the interview. One round of OA. The VO (onsite) was four rounds of analytics interviews. OA: The SQL was pretty easy. The Python question gave a list/dict of city housing prices, and I had to find the median price for each city. VO: SQL: Find the top N, then figure out…
Interview experiences · Airbnb
Airbnb Data Scientist Interview Experience — HM Screen Where the Role Didn't Match the JD
The HM started off by introducing what the team does, saying this team works on analytics-related stuff. He also mentioned there are two other data-related teams besides this one: the data science team and the modeling team. According to the HM, when the analytics team has work that needs research or a deep dive, it gets handed off to the data science team. I'm not totally clear on how Airbnb div…
Interview experiences · Airbnb
Airbnb Senior Machine Learning Engineer Interview Experience — Four ML System Design Rounds, Rejected on Calibration
Four rounds, overall leaning heavily into ML system / ranking / marketplace scenarios. Not especially rote-memorization heavy, but they really value business sense and decision making. Two weeks later I got a curt rejection. Round 1: ML Experience / Behavioral + Technical This round mainly revolved around past projects, with a lot of focus on tradeoffs and decision making. I talked about a projec…