READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 81 of 153
Interview experiences · LTM
LTM Software Engineer interview: logistics overshadowed evaluation
The process began with group discussion and aptitude, then moved into technical and HR stages. The early portions were fine, but the technical and HR handling turned sour. One interviewer was especially rude, and the timing was badly managed. I waited in line for a long time without proper coordination for entry. By the time I tried to participate, I was frustrated and could not settle into a smo…
Interview experiences · Lucid Motors
Lucid Motors Software Engineer 4 to 5 hour panel interview
The sequence was straightforward. I started with a screening, then had a hiring manager interview, followed by a panel interview. The panel lasted around 4 to 5 hours, so it was a long day. The questions during the panel felt fair and thought-provoking. The interviewers communicated directly, and the process was well organized. I got the impression that they were testing how I reasoned and how cl…
Interview experiences · Lucid Motors
Lucid Motors Software Engineer interview: 30-minute screen, CoderPad, and four-hour loop
The structure of the process stood out to me. It began with a 30-minute screening call, followed by a 45-minute technical interview that included a CoderPad coding challenge. The final stage was a long, intensive loop that lasted about four hours. It focused on technical depth, problem-solving, and overall fit, and it was the most concentrated part of the process. I remember finishing the loop fe…
Interview experiences · Lucid Motors
Lucid Motors Software Engineer interview: C++, sensors, and Nvidia SoCs
My first contact was a fit conversation with the hiring manager, and it quickly set the tone for the rest of the loop. After that, I had interviews with several people. The discussions focused mostly on my C++ experience and how I had worked with sensors and Nvidia SoCs. Coding questions were mixed in, so the process wasn’t purely based on experience. What made the experience difficult was how ab…
Interview experiences · Lucid Motors
Lucid Motors Software Engineer interview: functional safety concerns and a month-long recruiter delay
Early on, the process seemed to be moving, but the ending was abrupt and frustrating. I interviewed for a functional safety team and asked about the team. The response wasn't very clear, which made me uneasy. When I looked into it, I noticed that people didn't seem to stay in the role for long. That felt like a red flag, so I decided not to continue after the hiring manager conversation. Separate…
Interview experiences · Lucid Motors
Lucid Motors Software Engineer interview leading to an Engineer 2 offer
I went through a recruiter screening and then one-on-one interviews with people who would have been on my team. One interview was delayed because someone no-showed, and I had to reach out to get it rescheduled. The recruiter communication was where things soured. The process ended with an offer, but it was for an Engineer 2 position instead of the senior level I had interviewed for. The recruiter…
Interview experiences · Lucid Motors
Lucid Motors Software Engineer interview on motion planning and controls
The interviews focused heavily on motion planning and controls from the beginning. The hiring process felt organized, and the technical questions were reasonable, but I was expected to think as if I were actually designing the systems. I had to cover system design along with coding related to motion planning and control. I wasn’t only asked to name components. I had to explain how I would structu…
Interview experiences · Lucid Motors
Lucid Motors Software Engineer interview: PyTorch attention and C++ coding
My process started with an initial coding round in PyTorch. I had to implement multi-head attention from scratch, which was more hands-on than I expected. After that, I moved into a panel-style stage with two technical interviews and two C++ LeetCode-style medium coding rounds. The pace was brisk, and the difficulty felt fairly consistent across the coding and technical discussions. Overall, it f…
Interview experiences · Lucid Motors
Lucid Motors Software Engineer interview: three engineer technical rounds
I began with a recruiter phone screen about my background and what the role involved. Then I had three technical interviews with engineers back to back. The process was friendly and structured, with questions rooted in fundamentals. Most of the discussion was about mechanical engineering: problem solving, mechanical concepts, and my earlier projects. There was also a behavioral section about ordi…
Interview experiences · Lucid Motors
Lucid Motors Software Engineer interview with mechanics and vehicle body design questions
Recruiter outreach kicked things off quickly. I got a call to schedule the initial chat, and during that phone conversation, the recruiter explained what would happen next. They promised to follow up shortly after the interview, within about a day or two. The interview with the hiring manager felt fairly normal and even pleasant. We started with a resume review, then talked through my experience.…
Interview experiences · Luma
Luma Software Engineer Interview Experience — AI Product Engineering Loop With a Take-home Review, CTO Chat, and Build-Uber System Design
Luma is a small-to-mid-size company, currently around 200-300 people, split mainly into research and product. The process is fast and also a bit chaotic: recruiter, take-home, onsite, offer. If the recruiter doesn't get back to you about the next step, you can follow up yourself. TC is very high, they mainly want to be in the same range as OpenAI and Anthropic, but most of it is Series C paper mo…
Interview experiences · Lumen
Lumen Intern Data Analyst Interview Experience — Online Assessment Is All Behavioral Scenarios and a Recorded Presentation
The questions weren't hard. I applied for the analyst position — even though it lists requirements like SQL, it doesn't really seem like a technical role, so it's basically all testing behavior. As soon as you apply you get an OA. It also seems like this one can be a remote internship, which is a nice touch. The general question types were: given an article, then multiple choice questions on it;…
Interview experiences · Lutron
Lutron Software Engineer interview: duplicate-removal problem
After the recruiter step, I had a short two-part interview. The technical part lasted about an hour and asked me to remove duplicates from an array without using a HashSet. I could choose the language, which made it feel more like demonstrating my reasoning than being put under unnecessary pressure. The behavioral discussion took about half an hour. The interviewers were nice, and both sections l…
Interview experiences · Lutron
Lutron Software Engineer Interview Experience: Technical barrage and app design
The first round was intense, more a barrage of technical questions than a calm conversation. I had to reason out loud as I went, which kept it stressful even when I felt confident. The next stage shifted to personality and professionalism, and that felt easier because it involved less technical problem solving. A later scheduling-app design session asked me to build the frontend and backend end t…
Interview experiences · Luxoft India
Luxoft India Software Engineer interview: engineering stack and incident handling
After a recruiter introduction, I spoke with HR about my background, motivations, what I had done, and what I wanted to change. A little later, I had a technical discussion with the team lead that went deeper into software development, application and infrastructure monitoring, incident handling, and technologies from prior projects. The technical conversation was about day-to-day engineering kno…
Interview experiences · Luxoft
Luxoft Software Engineer interview: tense client-style call
The round felt tense and difficult immediately. The interviewer came across as abrasive and one-sided, spending time explaining their own points without really listening to what I said. I got through the client-style call, but it was hard to navigate. By the end, I did not feel the difficulty was simply about my performance. The communication style made the interaction harder than it needed to be…
Interview experiences · Lyft
Lyft Data Scientist Interview Experience — Surprised by the Low L4 Base Pay, Then a Four-Round Onsite
The HR video interview covered salary expectations (the L4 base salary was really low — I was shocked). After passing that round, I had a tech phone screen (pretty similar to what people share online — probability calculations, an open-ended supply-and-demand question). After that round they went straight to scheduling a 4-round onsite. HR was really nice and gave me a rough idea of what each rou…
Interview experiences · Lyft
Lyft Data Scientist interview: probability to causal modeling
I began with a recruiter screen of about 30 minutes. It was structured: they checked the basic boxes and explained what would happen next. The process then moved through a general data-science screen on probability, A/B testing, and business sense, followed by four deeper technical rounds. Those covered coding and algorithms, optimization, causal modeling, and business acumen tied back to product…
Interview experiences · Lyft
Lyft Intern Software Engineer Interview Experience — Three Rounds, Rejected for No Headcount After Three Months
The OA had two parts. The first was responding to a PM's comments inside a doc, and the second was coding — more like they hand you a stripped-down existing project and have you edit the code according to review comments, not your typical LeetCode problem. VO1: one hour of coding, something like LRU. I basically finished within 30 minutes. The interviewer was really nice, and there weren't many f…
Interview experiences · Lyft
Lyft Senior Software Engineer Interview Experience — Messenger Design and a Next-Day Pass
The target level was Senior. The process was bizarre, but I'll leave that aside. Overall, the interviews weren't difficult. Surprisingly, the hardest coding problem was in the phone screen. Phone-screen coding: LeetCode 76. VO 1: The behavioral round. They asked about my past projects, which project I was proudest of, how I had moved projects forward with colleagues over the past two years, and s…
Interview experiences · Lyft
Lyft Senior Software Engineer Interview Experience — Onsite Went Fine, Hiring Manager Call Was Discouraging
First, the technical screen. It was a sliding window LeetCode hard, but honestly not that hard — it was just 76, Minimum Window Substring. Next came the onsite, three rounds total. The first round was coding. The first 15 minutes were spent talking about past projects, then 60 minutes on the problem, and the last 15 minutes was free-form chat. The problem: given a set of jobs, each with a start t…
Interview experiences · Lyft
Lyft Software Engineer Interview Experience: A transactional recruiter screen
The recruiter screen set a rough tone immediately. I came in for a backend engineering role, but the conversation felt overly transactional, as though boxes were being checked instead of discussing the technical impact I had delivered. I shared concrete examples from past work, including architecture decisions, optimizations, and engineering scenarios. I expected the conversation to connect those…
Interview experiences · Lyft
Lyft Software Engineer Interview Experience — Onsite Loop with a Paginated Fetch Design and a Job Scheduler
Onsite. They gave me a long chunk of existing code and asked me to implement a function based on it. Essentially there's a fetch(page) function that returns the items on that page along with the next page's nextPage. We needed to implement fetch_n as a method on another class, so that we could pull n elements continuously. Each call continues extracting from wherever the last call left off, so th…
Interview experiences · Lyft
Lyft Software Engineer Interview Experience — Wiki Crawler Design and a Talent Pool Rejection
The phone screen was the typical one: they give you an API that can fetch pages, and you write a wrapper that calls this external API to implement fetching by word count. Onsite, showtime. The system design was wiki crawling: how do you crawl all of the wiki's content and store it, while keeping it updated within a certain time window, for example no more than five days stale. The coding was the…