READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 54 of 153
Interview experiences · Datavant
Datavant Software Engineer interview disrupted by rescheduling
The part that defined my experience wasn’t the interviews. It was the coordination. I was scheduled for an HR screen and then a technical screen, but rescheduling became a mess. It took about two weeks and several different coordinators to move the interview. On the day of the rescheduled interview, I arrived early, only for the interviewer not to show up. The recruiter and coordinator didn’t res…
Interview experiences · Datavant
Datavant Software Engineer interview with debugging and system design rounds
The process started when a recruiter reached out on LinkedIn. I sent over my CV, completed an HR screening call, and then moved into debugging. The technical work focused on debugging code and getting the tests to pass. I got most of them through, but I ran out of time while trying to fix one of the last issues. I was surprised to receive an invitation to the next round after that time squeeze. T…
Interview experiences · DatologyAI
DatologyAI Software Engineer Interview Experience — A Text Editor, Then a Mock Spark RDD Where I Blanked on Intersect
Writing down the questions from my DatologyAI interviews back in January at the start of the year. At the time I couldn't find anything about them online 😂 so I'm filling in the gap. Jan 6: The first round was with an interviewer who works on frontend. The question was to implement a text editor: Implement a TextEditor supporting: type_in(char): type a character at the cursor backspace(): delete…
Interview experiences · DatologyAI
DatologyAI Software Engineer Interview Experience — A Three-Part Text Editor
DatologyAI is a startup that raised a Series A two years ago and still has not raised a Series B. I went into the interview completely unprepared. The problem was a text editor, and only when I was writing this report did I realize that it seemed to be a question the company asks often. There were three parts. Part 1: Implement adding characters and deleting characters, and print all characters.…
Interview experiences · Dave
Dave Machine Learning Engineer Interview Experience — A Long Python OA and Live Data Exercise
After I spoke with the recruiter, I received a fairly long online assessment. It had multiple-choice questions about the language used for the role, which in this case was Python, along with syntax questions. It also had two longer CoderPad questions. The first involved data manipulation. The second was a very long debugging problem with multiple steps. Retakes were allowed, so I could contact th…
Interview experiences · Dayforce
Dayforce Software Engineer interview: SQL, JavaScript, and behavioral manager round
After recruiter outreach, I had a structured set of interviews. The first technical step used screen sharing: I discussed my background and answered questions about SQL and JavaScript. Soon afterward, I had a longer technical interview lasting about two hours in total, including a separate manager-focused section. I explained my experience concretely, while the manager asked behavioral questions…
Interview experiences · Decagon
Decagon AI Engineer Interview Experience — A Tic-Tac-Toe Sequence-Counting Problem in the Coding Round
I recently interviewed for Decagon's AI Engineer role, first round (the coding round), and got a question that doesn't have an exact match on LeetCode, so I wanted to share it. Problem Two players take turns placing marks on a 3x3 board, X goes first, then O, alternating. A game is the entire sequence of moves from an empty board to the end of the game. The game ends immediately as soon as one si…
Interview experiences · Decagon
Decagon Software Engineer Interview Experience — CSAT Tracker Question on the Phone Screen
I interviewed for 45 minutes and got one question. I'd solved it before, but I still wrote two bugs. Luckily I caught and fixed both while testing, and it passed in the end. Thanks to the interviewer for going easy on me. The question was the one that comes up most often for the phone screen: design a customer satisfaction (CSAT) tracking class. Scores are fixed in the range 1 to 5. __init__(self…
Interview experiences · Decagon
Decagon Software Engineer Interview Experience — Rejected After the Onsite Culture Screen
First was a hiring call with Decagon. Then a technical phone screen, which was a shopping cart problem with redo and undo. Next was a system design phone screen, where I had to design security for the Decagon chatbot. The onsite was a culture screen. They asked pretty generic questions like tell me about a project, tell me about a project that went wrong, and how do you use AI. I was rejected imm…
Interview experiences · Decagon
Decagon Software Engineer Interview Experience — Shopping Cart Versioning, Then Rejected on Tic-Tac-Toe
Round 1 was the shopping cart problem that other interview reports have also mentioned, but part 2 seemed a bit different. You're building a shopping cart for a cooking app. Users can add recipes to their cart. Each recipe has a list of ingredients (e.g., Chicken, Garlic). When the same ingredient appears across multiple recipes, the total count qualifies for bulk discounts. Part 1 was the same a…
Interview experiences · Deliveroo
Deliveroo Account Executive Interview Experience: discouraging communication
I expected a fairly normal process, but it felt discouraging almost immediately. During the recruiter call, there was a long monologue and very little meaningful interaction. When it ended, I felt the decision had already been made. I was doing account work in my current role, so being told I was not "pure" enough for the job landed badly, especially when there was no room for questions. The lack…
Interview experiences · Delivery Hero
Delivery Hero Software Engineer interview: backend-heavy technical rounds
The process began with an HR screen, moved through technical interviews, and ended with a hiring-manager discussion. I was not offered the role. The technical rounds were the hardest part. They covered Python fundamentals, backend development, system design, APIs, databases, concurrency, and general problem solving. The questions were practical and tied to engineering scenarios rather than stayin…
Interview experiences · Delivery Hero
Delivery Hero Software Engineer Interview Experience: Three quick and kind rounds
After the recruiter call, I went through three rounds: a technical interview, a hiring-manager round, and a bar raiser. The process moved quickly and matched what I expected going in. Everyone I spoke with was kind and understanding, which made the pace easier to handle. I did not get an offer, but the process did not feel hostile or chaotic. It was a straightforward, quick evaluation path. Locat…
Interview experiences · Dell Tech Laboratories
Dell Tech Laboratories Software Engineer interview: broad CS fundamentals
For the Software Engineering Student role, my process had three main stages and ended on July 27, 2026. It began with a HackerRank assessment on general software development, followed by an in-person interview at the Be'er Sheva office that went hard on core computer science fundamentals. That in-person round and the later advanced technical interview, held on July 12, both asked me to demonstrat…
Interview experiences · Dell Tech Laboratories
Dell Tech Laboratories Software Engineer interview
After an online assessment, I went through four rounds: two technical discussions, a managerial or technical discussion, and HR. Clearing each stage felt necessary to stay in the process. The technical interviews assessed my engineering approach and fit. The managerial or technical conversation added how I would think with broader ownership and cross-functional responsibilities. I received an off…
Interview experiences · Dell Tech Laboratories
Dell Tech Laboratories Software Engineer Interview Experience: 90-minute technical and project discussion
The process began with a phone screen with an HR representative. We covered my background and prior experience, why I wanted to apply, and general details about the role and company. About a week later, I had a technical interview with two interviewers. It lasted around 90 minutes and mixed technical problem solving with discussion of my previous projects. They wanted more than correct answers. I…
Interview experiences · Dell Tech Laboratories
Dell Tech Laboratories Software Engineer Interview Experience: A delayed schedule
The process felt streamlined overall. The HR contact was humble and responsive, including when I needed help scheduling around my availability. The frustrating part was the delay: I had to wait an entire day to complete the interview when it felt as though it could have happened sooner. Aside from that timing issue, the interaction did not seem especially complicated and the coordination was othe…
Interview experiences · Dell Tech Laboratories
Dell Tech Laboratories Software Engineer interview experience: home assignment and onsite
My hiring loop began with a home assignment, before I reached the onsite. After submitting it, I attended an onsite that lasted about 1.5 hours and included three questions. The first onsite interview was strongly LeetCode-oriented, with time-pressured problem-solving. The second stayed entirely technical, without personal or background questions. Across those two technical questions, the bar fel…
Interview experiences · Dell Tech Laboratories
Dell Tech Laboratories Software Engineer Interview Experience: Java, Kafka, and product architecture
A recruiter contacted me first, and the process was straightforward and responsive from the beginning. Soon after, I had two technical rounds and an HR round. I used Java, and the questions covered data-structures and algorithms prompts, strings, collections, and concurrency concepts. The second technical discussion looked at how systems work, not only syntax. I explained async architecture and t…
Interview experiences · Dell Tech Laboratories
Dell Tech Laboratories Software Engineer interview: reasoning over memorization
The Dell Tech Laboratories interview was positive and professional from the start. It focused on how I approached a problem, not only how quickly I could state an answer. I was asked to explain my reasoning and walk through my thought process step by step. The interviewer was friendly and encouraged discussion of different approaches. It felt less like a memorization test than a check on whether…
Interview experiences · Delta Air Lines
Delta Air Lines Software Engineer interview: dismissive manager led to withdrawal
The first conversation was uncomfortable from the start. The hiring manager felt condescending, told me to "slow down" while I explained my background, and when I asked for feedback, criticized only my attire as too casual even though he was dressed much more casually. Very little of the discussion concerned technical skills or performance. He pointed to internal communications for the formality…
Interview experiences · Deutsche Bank
Deutsche Bank Financial Analyst Interview Experience: defending valuation assumptions
After an opening conversation where I introduced myself, the interviews moved quickly into technical territory. I was asked direct questions about valuation and how to justify assumptions: EBITDA multiples, DCF setup and its assumptions, plus multi step accounting work. The difficulty came from going beyond memorized answers; I felt they wanted to see that I understood the concepts. The second st…
Interview experiences · Deutsche Bank
Deutsche Bank Software Engineer Interview Experience — Two LeetCode Easy Rounds, Then a BQ Round That Was Really a Technical Interview
This is from an interview I had two months ago. The first two technical rounds were each 1 hour, with 2 interviewers per round, and both interviewers asked questions. Each round had one question, both original LeetCode Easy problems — one was checking whether two trees are the same, the other was valid parentheses. Then you had to write test cases. Probably because I was using Java, the interview…
Interview experiences · Discord
Discord New Grad Software Engineer Interview Experience — Cut After One AI-Assisted Chat Server Round
I got a referral to Discord late last year and got rejected right away. This month, ironically, I got picked up through a mass application instead. When I talked to the recruiter he said the package looks pretty big, but the interview bar is high too. I'm honestly not that strong, and at the time I felt like I wasn't at that level, but I gritted my teeth and went anyway. In the end I only made it…