READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 51 of 153
Interview experiences · Confluent
Confluent Software Engineer interview with system design and DSA rounds
My process had three segments. First, I completed a qualifying technical round. Then came the heavier middle section: three rounds combining system design with DSA, with the DSA portion mostly resembling LeetCode medium difficulty. The final segment was a behavioral round with a senior manager. The process felt difficult because the middle block required sustained technical thinking across severa…
Interview experiences · Confluent
Confluent Software Engineer interview with two technical rounds and harder follow-ups
My interview had a small set of core stages: recruiter coordination, two technical interviews, and a manager round. The problems were medium overall, with some harder follow-ups that required me to stay sharp after I thought I’d settled into the first question. I had a generally positive impression of the process. The recruiters were responsive and supportive, and it took only a few weeks from my…
Interview experiences · Confluent
Confluent Solutions Engineer interview: cloud and data management focus
My biggest issue started before the technical work. The role requirements felt misrepresented. I spent time with the recruiter and hiring manager discussing my background in detail, and they explicitly told me that specialized knowledge of their products or data streaming wasn't required. When the one-hour technical interview came, the focus didn't match what I had been led to expect. The convers…
Interview experiences · Accenture España
Consultant interview at Accenture España
Scheduling became frustrating almost immediately. I was arranged through WhatsApp, then left waiting by the assigned recruiter without notice. I later learned that I had effectively been dropped because I could not join an unplanned surprise call. It happened in other forms too: I was invited to an interview where nobody appeared, and follow-up email brought no clear explanation. In one case an A…
Interview experiences · Flight Centre Travel Group
Consultant interview at Flight Centre Travel Group: interview experience
The process was light-touch and felt more like a quick check than a large recruitment campaign. After applying, I had a short recruiter phone call about whether I had the confidence and energy they wanted. The questions stayed high level. I then joined a Zoom call with a few role-related questions about whether I could do the job day to day. There were not many hurdles, and the tone was calming r…
Interview experiences · Infosys (Finacle)
Consultant interview at Infosys Finacle: fast technical and HR process
I went through a structured process with screening, virtual technical interviews, and then in-person managerial and HR rounds. The second-round scheduling took some time, but once the process started it moved with momentum. I discussed previous work and projects, including async/await, microservices, and challenges from my prior role. The later conversations focused on experience and teamwork. I…
Interview experiences · McKinsey &
Consultant interview at McKinsey &: interview experience
Overall, I had a positive experience, although one part bothered me: I had to take an online numerical test. I understood it as a screening tool, but in 2026 it felt somewhat outdated. Apart from that, the process went well and I kept a good impression through the stages. I received an offer in the end, despite the friction of that numerical assessment. My reflection is simple. I could see the va…
Interview experiences · McKinsey &
Consultant interview at McKinsey &: six-month case process
My process lasted about six months, beginning with LinkedIn outreach and ending in rejection. The sequence was a game assessment, two interviews with engagement managers, and a final round of three partner interviews. I reached the end feeling confident, but was eliminated in the first interview of that final group after a simple math error. My result differed from the expected one, which led me…
Interview experiences · Migso-Pcubed
Consultant interview at Migso-Pcubed: interview experience
The process opened with a presentation I prepared in advance from a slide deck they asked me to bring. While I presented, we discussed it and they asked questions, so it stayed interactive rather than becoming a monologue. After the deck, they introduced the company and we continued with Q&A. The session ended with feedback from each person and information about whether I would be invited to the…
Interview experiences · CoreWeave
CoreWeave Software Engineer interview: concurrency screen and timed CoderPad task
I moved quickly once a recruiter contacted me. We scheduled a phone call for the next day, and the conversation felt efficient. We discussed why I wanted to join, what I considered my biggest mistake in my current role, my compensation expectations, and other fit questions. After that, I had a technical screen with a senior engineer focused on concurrency and multithreading. It was the kind of co…
Interview experiences · CoreWeave
CoreWeave Software Engineer interview with a 60-minute CoderPad task
I had one main evaluation that stood out because it was so concrete. It was a 60-minute CoderPad session in Python, where I had to build a CLI tool for field technicians to reboot remote servers through an API. The setup included a locally running backend and a specific POST endpoint, and the work was divided into several parts during the session. What made it intense wasn’t the unfamiliar enviro…
Interview experiences · CoreWeave
CoreWeave Software Engineer interview with a Python CLI task
My earliest round was a recruiter screen that went well, followed by a coding assessment that felt practical rather than like the usual LeetCode-style exercise. The question was timed, but the framing was closer to real-world work. The recruiters and interviewers also seemed knowledgeable and genuinely approachable. As I moved further through the process, I ran into a different kind of hurdle: a…
Interview experiences · Coupang
Coupang Software Engineer Interview Experience — A Group Anagrams Twist and a Write-vs-Read Tradeoff Question
Team: Marketplace Growth, the US team (people in the group said the whole org is about 100 people — 50–60 in Korea, 30–40 in China, and only this one team in the US, around 10 people; the org head is based in the US). Process: one phone screen (57 min) → onsite, same team. Phone screen structure: ~35 min coding → ~13 min project Q&A → ~10 min reverse questions. Coding (HackerRank) Question: a var…
Interview experiences · Coupang
Coupang Software Engineer Interview Experience — Live-Coded LeetCode 934, Debugged a Stack Overflow Myself
Problem LeetCode 934, Shortest Bridge When I answered, I first laid out all his examples in a structured way below, then started with the function just returning 0. Running it gave n zeros, and I told him this was the first iteration. The next step was to finish the function so it returns the correct result. While working through it, I ran into a case where the recursion wasn't controlled properl…
Interview experiences · Coursera
Coursera Software Engineer Interview Experience — Failed a Multi-Round Instant-Runoff Voting Question
The question was roughly this: given a set of ballots, where each ballot is a candidate preference ranking, like [A, B, C, D] or [B, A, C, D], representing a voter's priority order over the candidates. Part one was actually pretty direct — just look at the first candidate on each ballot and count who appears most often. If there's a tie, pick the smallest one in lexicographic order. This part was…
Interview experiences · Credit Genie
Credit Genie Software Engineer Interview Experience — FastAPI CRUD Pairing, Rejected Over a Communication Slip
When I was preparing, I couldn't find this question on the forum — it's a startup, so that's understandable. Here's the overall process: Hiring Manager Interview Technical Pairing, Python AI/ML Technical Pairing Systems Architecture & Design (AI/ML) Motivation + Mission Alignment Executive Interview I got cut after the first round, which combined the Technical Pairing and the Hiring Manager Inter…
Interview experiences · Cresta
Cresta Software Engineer Interview Experience — A Feature-Flag Evaluation Engine, Then Rejected After a ‘Great Chat’
I used Claude to help organize this write-up. The interviewer kept saying he really enjoyed our conversation, and then rejected me anyway. Problem background: you're given three JSON files and asked to implement a feature-flag evaluation engine that maps every user to a final boolean value (on/off) for every flag. Input files: flags.json — definitions for 7 flags user.json — 10,000 users expected…
Interview experiences · Cresta
Cresta Software Engineer Interview Experience — AI-Assisted Coding Round: Build a Flight-Booking Chat Agent in Python
You get an api.md doc plus an agent_starter.py file, and you have to use AI assistance to implement an AI Agent that searches for and books flights. The format is a chat dialog. Note: the language has to be Python, and you need to set up the whole project in your own IDE, so make sure you can actually run Python locally first. They'll also give you OPENAI_API_KEY, OPENAI_BASE_URL, and FLIGHT_API_…
Interview experiences · Cresta
Cresta Software Engineer Interview Experience — Phone Screen Building a Least-Load Job Dispatcher
Write a Job Dispatcher-Executor system. You are tasked with implementing a simple job dispatcher that distributes incoming jobs to a pool of executors (i.e., workers). Each job is represented as an integer (its ID), and executors are dynamically added and removed during runtime. You must define two classes: Executor – Represents a worker that can accept jobs. LoadBalancer – Maintains a list of ex…
Interview experiences · Cresta
Cresta Software Engineer Interview Experience — System Design Round: Build an Eval Platform for AI Agents
System design round They have you design an eval system to evaluate the results of an Agent using different models, e.g. tool usage, response speed, plus testing different system prompts, that kind of thing. The original question is below: > Design a system for evaluating AI agents. Users of the system are going to be teams developing AI agents, e.g. agents which automatically analyze contact cen…
Interview experiences · Crowdstrike
Crowdstrike Account Executive: fast-tracked interviews and a final panel
My process started with a straightforward recruiter conversation, followed by a small number of follow-ups rather than a long gauntlet. I had been in contact with the hiring side early on, and after a conversation they sent me an application link and connected me with the recruiting team. The conversations stayed professional and focused heavily on my cybersecurity sales background and how it fit…
Interview experiences · Crowdstrike
Crowdstrike Account Executive interview with sales management meetings
I started with a quick recruiter call and moved through the next steps quickly. The process felt straightforward, with short, focused conversations instead of anything especially technical. I was asked behavioral questions and general cybersecurity questions, with the discussion returning to my motivation, what I wanted from the role, and how my experience matched the business’s needs. One import…
Interview experiences · Crowdstrike
Crowdstrike Account Executive panel postponed without a reschedule
I went into the process expecting a typical sales interview cadence. After a screening and a second interview that felt straightforward, I moved to a panel with less than a day to prepare for a long session. Several delays kept pushing back my plans. During the panel presentation, there was also an unexpected language-related change request, which threw me off in the middle of the presentation. T…
Interview experiences · Crowdstrike
CrowdStrike Senior Software Engineer Interview Experience — A String-Templating Coding Round, Then a Rejection
Sharing a fresh rejection story. I don't have a cybersecurity background. I applied for a senior SWE, cloud role. The position requires being based in the US Eastern time zone, since it involves working with the team in Europe. First was an HR screen, with some basic questions — whether I knew Go, what the most complex project I'd worked on was, that kind of thing. At the time I thought I had no…