READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 61 of 153
Interview experiences · Ethos
Ethos Software Engineer Interview Experience — Online Assessment on Recoverable Elements from Range-Sum Queries
Recoverable Elements from Range-Sum Queries You are given an unknown integer array A of length N, with elements indexed from 1 to N. You will receive Q range-sum queries. Each query contains two integers L and R, and gives you the sum of all elements of A from index L to index R. Your task is to use the given query information to find all the elements A[i] whose exact value can be uniquely determ…
Interview experiences · Eurofins scientific
Eurofins scientific Software Engineer four interviews and unanswered follow-ups
The recruitment process began with urgency, and I committed a lot of time because the timeline was presented as critical. I completed four interviews. After the last one, I received no response: no positive feedback and no rejection. Over the next several weeks, I followed up repeatedly by email, phone, and voice message, about a week apart. Nothing was answered. I eventually contacted an enginee…
Interview experiences · Eurofins scientific
Eurofins scientific Software Engineer two-round interview experience
I had two scheduled rounds for the Software Engineer role. The process was short, friendly, and straightforward. The questions felt easy to medium and mostly covered Java, Spring Boot, and material from my resume. The interviewer was easy to speak with, so it never felt like an interrogation. Hiring later slowed because of a freeze, and I did not receive an offer letter. Technically, I felt the i…
Interview experiences · EvenUp
EvenUp New Grad Software Engineer Interview Experience — Blunt Recruiter Feedback, Then a Canditech OA
I applied 8 months ago, and now I've gone from being a new grad to being an old veteran before I finally got an interview. My first round was a phone call, and I answered pretty confused. The recruiter told me straight up that I answered very poorly, but I said I don't really care about WLB, blah blah, and he said that's exactly the signal they're looking for, so he moved me on to the OA. (Which…
Interview experiences · EvenUp
EvenUp Staff Data Scientist Interview Experience — OA With No IDE, Then a BQ-Only HM Round
The first stage was an OA that took about an hour. It had two parts. The first part was maybe a dozen or so multiple choice questions, covering a lot of ground quickly — there were data processing questions, questions about statistical distributions, and some basic hypothesis testing concepts. There was plenty of time, I think it was 25 minutes for under 15 questions? The second part was rough —…
Interview experiences · Exa
Exa Research Engineer Interview Experience — Two Phone Screens, One 40-Minute t-digest Derivation
Haven't seen anyone share about this company on the forum, so let me be the first to post. Research Engineer — two phone screens total. Round 1: Mostly a PyTorch contrastive loss debugging exercise. Basically just fixing some matmul shape mismatches. Once I got it working, there were no more issues. The interviewer was a young guy, really nice, and he even guided me toward the right direction. Ac…
Interview experiences · Exl
Exl Business Analyst interview: shifting final stages
The process began with a hiring-team interview that went well, followed by a VP round. I was told an AVP-style final interview would come next, and the technical and leadership discussions seemed positive. I expected the process to reach a decision. Instead, I was pulled into another client-related conversation after the interviews appeared finished. I was then rejected for a basic hands-on skill…
Interview experiences · EXL Service
EXL Service Business Analyst interview: long and disorganized rounds
After the initial HR contact, the process became a long sequence of interviews with gaps between them. There were so many stages that one day felt as though it would never end. I spoke with several people, including senior leadership, and repeatedly had to restate my background and the basics tied to the role. Coordination was the hardest part. I was asked to attend extra rounds that were not cle…
Interview experiences · EXL Service Philippines
EXL Service Philippines Business Analyst interview: extra client round
I expected a straightforward process, starting with a hiring-team interview that went well, then further rounds with a VP and what was described as an AVP final step. The earlier conversations covered the same basic hands-on skill that later became an issue, and I felt I had answered it well. After I thought the process was done, recruiting added a client interview. I was eventually rejected on t…
Interview experiences · Exoduspoint
Exoduspoint Software Engineer Interview Experience — Rejected Over a Bridge-Crossing Brainteaser
I felt pretty good about the first round, but I still got rejected. Thinking back on it, I think it's because I didn't give the optimal solution to a brainteaser. Investment companies like this one seem to care a lot about that. So I'm posting this for anyone who interviews here after me. The first round was with a department head. The interview was made up of a lot of small questions — a few sho…
Interview experiences · Expedia
Expedia Data Scientist III Interview Experience — Five-Round Onsite Panel, Then a Lowball Offer Fell Through
Switching jobs this year wasn't easy either — all told I went through something like 7 rounds of interviews, and in the end the money didn't work out and the offer fell through, which was a shame. This has some things in common with a post I made before. I noticed there aren't really any Expedia interview experience posts here related to Data Science, so a while back I interviewed for an Expedia…
Interview experiences · Expedia
Expedia Senior Software Engineer Interview Experience — HR Ghosted for a Month Before the Virtual Onsite
I interviewed for the global payments team. The phone screen was in mid-February, then HR just ghosted me. I emailed to ask about the result and only got a reply five days later. The virtual onsite ended up landing almost a month late. After the self-introduction in every round there was a small Expedia values behavioral question. Round 1 was coding with the interviewer — a LeetCode question. Aft…
Interview experiences · Experian
Experian Data Analyst interview: assessment-centre group task and learnability tests
My process began with assessments before I got deeply into the interviews. I completed an image-based behavioral check about how I work, followed by situational judgment questions that felt close to workplace decisions. There was also an assessment focused on learnability, where I had to solve a problem and use new information after it was introduced. When the interview stage started, I received…
Interview experiences · Experian
Experian Data Analyst interview: prerecorded video and basic online assessment
My interview experience started with a prerecorded video component. It was easy to step into and felt more like a low-pressure way to introduce myself than a live interrogation. There was also an online assessment focused on basic skills. For the video section, I had a short window to answer typical interview questions. I used that time to talk about my interests and fit. The process moved quickl…
Interview experiences · Experian
Experian Data Analyst interview with a data analysis walkthrough
My process started with HR-style questions and quickly shifted into scenarios related to the role. The interview lasted about 45 minutes, and I was asked a few technical questions tied to the work I would be doing rather than abstract trivia. A week after the initial interview, I completed an online assessment or assignment with the hiring team. Later, I had an in-person interview that lasted abo…
Interview experiences · Experian
Experian Full Stack Engineer interview with front-end and back-end live coding
My process was short and tightly structured. I had two interviews: one with the team manager and another technical conversation with team members. Both the technical and managerial portions centered on live coding. The technical round was split into two parts, with one focused on the front end and the other on the back end. It felt like they were testing how I think across the entire stack rather…
Interview experiences · Experian
Experian Software Engineer interview: timed Q&A with 60 seconds to prepare
My first step was a quick interview that felt almost like a timed question-and-answer session. There were 4 to 5 questions, and I was at a "no person" stage, so it didn't feel like a traditional conversation. I had about 60 seconds to plan each answer and roughly two minutes to deliver it. The pacing stood out. The questions didn't leave much room to meander, so I had to organize my thoughts quic…
Interview experiences · Experian
Experian Software Engineer interview with an assessment center and one-way interview
My early rounds felt more like an organized ladder than a long gauntlet. I started with a short screen-style interaction covering general skills and behavioral questions. The process had a structured feel, with time limits throughout. There were also assessment-style elements that tested how I think under constraints, including sequencing problems and scenarios framed as work-style questions. Whe…
Interview experiences · Experian
Experian Software Engineer, unclear team details and concurrency discussion
I went through a fairly standard multi-stage process, but the experience felt messy. It began with a recruiter phone call where the interviewer spoke extremely quickly and the connection kept breaking. It was difficult to ask questions or clarify anything. Next, I had an online interview with a manager. The interviewer was late, and the conversation didn’t feel grounded in what the team actually…
Interview experiences · EY
EY Technology Consultant Interview Experience — A 30-Minute HR Screen Driven by Follow-up Questions
I had a referral, and three days after the referral I received an HR phone-screen invitation. I scheduled the call for the next day. The HR interviewer was very experienced. They did not ask me to introduce myself and instead moved directly from small talk into questions about my previous experience. They asked follow-up questions based on our conversation, and we spoke for about 30 minutes. The…
Interview experiences · Facebook
Facebook Software Engineer interview: BFS matrix task and unfinished technical loop
After the recruiter step, I had a coding-centered technical round with two questions in about 45 minutes. One required a normal solution followed by an optimization follow-up, which made the round more demanding than I expected. In the next video-conference interview, the interviewer was very communicative and answered questions as they came up. The coding challenge used BFS: I was given a matrix…
Interview experiences · Facebook
Facebook Software Engineer interview: coding loop, system design, and offer
A recruiter phone screen led into a classic technical sequence. After the call, I did two back-to-back LeetCode medium coding interviews with engineers. The tone was collaborative and friendly, with emphasis on explaining my thinking, writing good code, and improving my solution in follow-ups rather than being caught out. Later, the onsite had a full-loop structure: two coding sessions with two L…
Interview experiences · Facebook
Facebook Software Engineer interview: recruiter screen, LeetCode loop, and no offer
After a recruiter contacted me on LinkedIn, I had a scheduled screen about my background and what I wanted from a new role. It was clearly a gate: if the alignment looked right, I would move forward. The technical sequence followed a familiar pattern, starting with a phone screen and then an onsite that mixed coding, behavioral questions, and system design. The coding questions were LeetCode-styl…
Interview experiences · Facebook
Facebook Software Engineer interview: two coding questions and onsite loop
After a recruiter call, I had a technical screen that began immediately with coding. I answered two LeetCode-style questions and had to communicate clearly as I worked. The questions were heavily Meta-tagged, so targeted preparation mattered more than generic DSA practice. The onsite loop added behavioral, two more coding questions, and system design. The recruiter was accommodating and the proce…