READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 59 of 153
Interview experiences · Duolingo
Duolingo Intern Software Engineer Interview Experience — Karat Resource-Transition Probabilities
3 Short DSA analysis questions from the same thread Here is the question I got for the coding part.
Interview experiences · Duolingo
Duolingo Product Manager interview: take-home app feature assignment
The process began with a take-home assignment, and I didn't speak with anyone before submitting my work. I had only a few days to devise or reimagine a Duolingo app feature and create a slide deck. It took a lot of effort to get the deck to a presentable level. After I submitted it, the live rounds still felt as if the main goal was to collect ideas from candidates. The most jarring part wasn't t…
Interview experiences · Duolingo
Duolingo Product Manager interview: Take-home feature proposal and forty-five-minute product rounds
I started with an online application and then went through a recruiter step before meeting anyone live. After that, I completed a take-home product assignment. I had to choose a feature to add or improve in Duolingo and turn it into a short slide deck covering the problem, solution, success metrics, and MVP. It took a while, but the instructions were clear enough that I understood what they wante…
Interview experiences · Duolingo
Duolingo Product Manager: take-home feature design task and delayed rejection
I went through an internship-style process where the first real step was a take-home design task focused on a Duolingo feature. It took a significant amount of time. It felt like something they expected me to work on from start to finish and turn into a polished presentation. After I finished, the follow-up dragged on. The process went silent for a while, and I didn't receive a rejection until mo…
Interview experiences · Duolingo
Duolingo Software Engineer interview with a one-hour technical round
Once I reached that stage, the process had a strong final-round feel. It followed a kind of superday structure, starting with an online assessment on a Zoom call and ending with a behavioral round that included a couple of STAR-style questions about my experience. The decisions felt quick and decisive. As I progressed, the rounds looked like a shortlist process for engineers and finalists. There…
Interview experiences · Duolingo
Duolingo Software Engineer interview with CodeSignal and pair coding
The earliest stages were fairly smooth and lightweight compared with what I expected. I started with an online CodeSignal assessment, then had a short behavioral screen focused mainly on how I worked and handled team situations. In another run through the process, the coding assessment was also relatively manageable. It covered a subset of questions, including basic graph traversal and string or…
Interview experiences · Duolingo
Duolingo Software Engineer interview with disputed coding feedback
The recruiter communication set a strange tone from the beginning. When I was eventually rejected, the message said that my code was nonfunctional even though it had passed the tests. That mismatch bothered me because the feedback felt more dismissive than a simple statement that I wasn't a match. The overall atmosphere, from the recruiter to the interviewers, was unpleasant. It felt as though pe…
Interview experiences · Duolingo
Duolingo Software Engineer interview with multiple phone screens before the onsite
The process took much longer than I expected and didn't feel organized. I went through a standard recruiter screen, followed by several additional phone screens, before finally reaching an onsite. The recruiter and each later step made it seem as if things were moving forward, but the overall experience felt tedious and drawn out. By the time I reached the onsite, I was tired of the pacing and re…
Interview experiences · Duolingo
Duolingo Software Engineer practical tasks, pair programming, and onsite
The recruiter stage felt unusually clear and human. After a short screening, I was given a set of tasks related to the work itself, and I had to submit both my answers and explanations for the choices I made. They wanted to understand the reasoning behind the work, not only whether something worked. From there, the process used practical formats that resembled engineering work. I had a team-membe…
Interview experiences · Duolingo
Duolingo Software Engineer tree traversal and graph coding assessment
After a conversation with a recruiter, I did a technical screening focused on a coding problem that felt very "standard" for interviews, something like a tree traversal. There was also a short follow-up about how I would improve the algorithm's efficiency. The interviewer kept the conversation moving. Although the core question wasn't unfamiliar, the optimization questions made me slow down and t…
Interview experiences · DXC Technology
DXC Technology Software Engineer interview: .NET, APIs and frontend fundamentals
After introductions, we discussed my previous projects and work experience. The technical conversation went deeply into the Microsoft stack: .NET, C#, ASP.NET Core and SQL. We also covered REST APIs and frontend work in JavaScript and Angular. There were questions about object-oriented programming, dependency injection and debugging scenarios too. The interviewer was professional and gave me time…
Interview experiences · DXC Technology
DXC Technology Software Engineer interview: operations-focused discussion
I first spoke with HR about my background, skills, and reasons for considering a change. Then I met the team lead for a technical conversation on building software and operational concerns, including application and infrastructure monitoring and incident management. We discussed the technologies I had used and how my prior work translated to their delivery needs. I returned to HR to cover organiz…
Interview experiences · E2open
E2open Software Engineer interview on Java and meeting-room design
After speaking with the recruiter, I had two focused technical rounds. The first was an online technical discussion on Java fundamentals, including OOP, multithreading, and DSA-style problem-solving. Later I had a face-to-face system design round. The scenario was a meeting-room booking system, and we discussed how its database could scale. The progression from core concepts to system-level reaso…
Interview experiences · Ease
Ease Software Engineer Interview Experience — A "Debugging" Round That Was Really a Key-Value Store Without a Dictionary
Implement a key value store without a dictionary or set. I was told that this round was going to be a debugging session. The interviewer gave the question above. Mistakes that I made: I did not start with a class definition. The interviewer pointed it out, so I eventually started with a class definition. The interviewer kept asking me about cache collision. I raised an exception for the cache col…
Interview experiences · eBay
eBay Applied Scientist Interview Experience — Six Rounds, Then the Role Went On Hold and Was Cancelled
After six rounds of interviews they told me straight up that the position was on hold, and a month later they let me know the position had been cancelled. I suspect the interviewers had known about this for a long time, which is why the interviews were so all over the place and never lined up with anything. The questions I spent ages preparing were basically wasted effort. I'm sharing the questio…
Interview experiences · eBay
eBay Senior Software Engineer Interview Experience — Rejected After a Forced-JS Coding Screen
The recruiter only mentioned that the interview would cover algorithms and data structures, with no mention of a language requirement at all. Then right at the start of the interview, the interviewer told me I could only use JavaScript or TypeScript. I said I was more comfortable in Python, but I was still made to use JS/TS. This was the first time I've ever been forced into a specific language l…
Interview experiences · eBay
eBay Software Engineer Interview Experience — AI-Coding Phone Screen, Rejected After Onsite Coding Round
In June, an HR person reached out about an MTS role, and we talked through some behavioral questions and my project experience. Phone screen: AI coding — basically they give you some code and have you spot design pattern issues (like something not being extensible), or point out a bad data type. On CodeSignal, the AI is really strong and basically does the work for you. You just need to talk thro…
Interview experiences · eBay
eBay Software Engineer Interview Experience — An Onsite With No LeetCode
This was the most unusual interview I have had so far. There was not a single LeetCode question in the onsite. First round I wrote a shopping cart. There was not much algorithm work, and it felt as though the round was testing how I communicated with the interviewer. Second round I was asked basic questions about data structures and complexity, including very basic topics such as lists, hashes, a…
Interview experiences · eBay
eBay Software Engineer Interview Experience — Five Onsite Rounds and a CS102 Refresher
The onsite actually required 5 rounds... my vision went black for a second when I heard that, but since they'd already given me the opportunity, I figured I'd just go ahead and interview. The five rounds included: ML implementation: chatted about my background with the hiring manager, then did a case on how to handle cache update conflicts on the server. Design: yes, you read that right, another…
Interview experiences · eBay
eBay Software Engineer Interview Experience — Three Onsite Rounds With Two System Designs
Round 1 Given an array heights, where each element represents the height of a vertical line. Choose two lines to act as the walls of a container. Return the maximum amount of water the container can hold (max area). Given an array of integers temps representing daily temperatures, write a function to calculate, for each day, how many days you'd have to wait until a warmer temperature. The functio…
Interview experiences · Eightfold.Ai
Eightfold.Ai Software Engineer interview: AI coding and take-home
I came through campus recruiting, starting with a CGPA eligibility check and resume shortlisting. That led to a 60-minute coding interview with an AI. There were two questions, so I had to keep an eye on both the approach and correctness while the clock ran. Clearing that screen put me in consideration for a take-home assignment, although the hiring process was still underway when I last heard. T…
Interview experiences · Electronic Arts (Ea)
Electronic Arts (Ea) Software Engineer interview: mismatched technical expectations
After a recruiter call, I had five interviews: recruiter contact, a hiring manager, and three final-round interviews. I depended on the recruiter for preparation guidance, but the details were too vague to tell me what to study. The system-design round was framed first as technical architecture and then as mostly frontend React, but React barely mattered. Instead I faced OOP, performance optimiza…
Interview experiences · Elevenlabs
ElevenLabs Software Engineer Interview Experience — Three-Question OA With a Surprise 2-Minute AI Follow-up
Fresh out of the oven. 3 questions, increasing in difficulty I guess, with time limits of 25 minutes, 30 minutes and 45 minutes respectively. Question 1: Next Number The next_number function should return the smallest integer which is superior to n and whose digits are all different from all of n's digits. For example, next_number(654321) return 700000. If no such integer exists, then the functio…
Interview experiences · EliseAI
EliseAI Data Scientist Interview Experience — Tic-Tac-Toe Coding Round and a Lease Renewal Take-home
I applied online and a recruiter reached out. The first round was a 30-minute chat with a team member. The second round was coding, a tic-tac-toe variant. I'd suggest looking at all three of these: 348 - Design Tic-Tac-Toe 794 - Valid Tic-Tac-Toe State 1275 - Find Winner on a Tic Tac Toe Game The third round was a take-home: you get 24 hours to do it, and then there is a 30-minute presentation. T…