READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 79 of 153
Interview experiences · Latent Health
Latent Health Senior+ Software Engineer Interview Experience — A 45-Minute System Design Screen on Prior Authorization Workflows
Role: Software Engineer (interviewer said they're targeting senior level) Round: System design phone screen Duration: 45 minutes (~5 min intros, ~35 min design, ~5 min candidate Q&A) Format: Screen share + Excalidraw (bring your own whiteboard tool — have a link ready) Background (given by the interviewer, ~4 minutes) Latent Health's first product is in the prior authorization (PA) space. The int…
Interview experiences · Lazard
Lazard Business Analyst Interview Experience: two short alignment conversations
I started with a short recruiter chat, about half an hour, about my background and why I was interested in the firm. The recruiter also asked whether I intended to relocate. It felt like a quick alignment conversation rather than a deep technical screen. About a week later, I had another half-hour discussion with a portfolio manager. We again covered my background and motivation, then moved into…
Interview experiences · Lead Bank
Lead Bank Software Engineer Interview Experience — Two Coding Rounds Plus a Hotel Reservation System Design
The first coding round was similar to what people describe online — it's the one where you treat it as a stock ticker + date + price log. The interviewer guides you step by step, so you can pretty naturally arrive at the solution. Here's roughly what my code looked like: System design: the classic hotel reservation system design that shows up online a lot. Though there was a twist — the interview…
Interview experiences · League
League Software Engineer Interview Experience — Rejected Right Before the System Design Round
League is a leading HealthTech company headquartered in Toronto. A friend referred me, and I quickly got a screen scheduled with HR. After that came a take-home assessment, no language restriction (they use Go internally). It wasn't a LeetCode-style algorithm question — instead you had to build a server, including various APIs, implementing some operations on a matrix (reverse, add, etc.). The as…
Interview experiences · Legora
Legora Software Engineer Interview Experience — A System Design Round with Almost No Coding
This one was basically the same as another writeup I'd already seen about this company's process. Round 1 was a project deep dive. Round 2 was system design + coding, though the coding part was so small it felt kind of pointless. I originally thought the coding portion would take 45 minutes, but this second round actually leaned much more toward system design. They gave me a chat app setup, asked…
Interview experiences · Lennar
Lennar Consultant interview: repeated delays and Caliper result
The recruiter call felt cold and combative, and it was hard not to take that personally. A later interview with a sales manager felt rigid too. I was told an assistant would arrange another sales-manager meeting, but after my thank-you email and follow-up, I was told there was limited space in my region. When I reapplied in another city, the same recruiter scheduled me with the same interviewer.…
Interview experiences · Lenovo
Lenovo Account Executive Interview: Recruiter call and two-person team interview
After I applied, I had an easygoing recruiter conversation that moved quickly, with clear next steps. It helped me understand the broader company and role while they assessed whether the fit worked from both sides. Later, I had an online interview with two team members. The discussion centered on my match for the position, but the feedback was not specific. It threw me off that they seemed not to…
Interview experiences · Leonardo
Leonardo Software Engineer Interview Experience: calm discussions of background and credentials
The process started with a friendly, relatively light conversation with the team in Italy about my experience, technical background, and degree. The tone was welcoming and relaxed, with no major surprises. It felt more like an effort to understand my fit than a test full of gotchas. The interviews then became more structured. I spoke with HR and senior technical stakeholders. The sequence was cle…
Interview experiences · LG Soft India
LG Soft India Software Engineer interview: aptitude, C/C++, DSA, and OOP
After a recruiter-style step, I went through a structured process that began with aptitude and then moved into coding that day or shortly after. The first stage was an easy MCQ aptitude round. The online assessment mixed MCQs and problem-solving, with a strong C/C++ focus. The questions were straightforward but not trivial, and the constrained format made language choice matter. I then had two in…
Interview experiences · Liftoff
Liftoff Machine Learning Engineer Interview Experience — Onsite With a Dice Probability Question and a KV Store
Sigh, I felt like I did okay, but it still ended in tragedy. Thanks to the forum for the help, even though most of these questions were already in the earlier posts. The other rounds were pretty much the same as what is already posted. I did not see details on the statistics and probability questions, or on the KV store question, so let me add them. One question: you roll a 6-sided die 1000 times…
Interview experiences · LinkedIn
LinkedIn Account Executive interview: fast recruiter-to-mock-call loop
The recruiter conversation was quick and friendly, and the process moved fast. Within minutes of applying, I received an email to schedule the first screening call. I spoke with three people in total: a recruiter, a hiring manager, and a panel-style mock call. The hiring team was great throughout. I answered their questions and felt they were listening. By the end of the last round, I had receive…
Interview experiences · LinkedIn
LinkedIn Data Scientist Interview Experience — A Technical Screen Packed with Stats Questions
No guarantee the answers here are correct, just for reference! LinkedIn Stats One bank has 5 tellers and a single line, another bank has 5 tellers with 5 separate lines — which one would you queue at? Simple statistical explanation: the "Long Plank Effect" (the opposite of the Weakest Link Effect). In a single queue, your waiting time is determined by the fastest available teller. In multiple que…
Interview experiences · LinkedIn
LinkedIn Data Scientist Interview Experience — Five Onsite Rounds from Course Data to Experimentation
My LinkedIn onsite had five rounds in total: Data presentation I was given two tables. One showed the current number of LinkedIn Learning courses in each category, and the other showed the number of courses and participants over time. I had to analyze them myself, then make slides and present. SQL + Python For SQL, I was given two experiment tables. One was a cohort table with users, their experi…
Interview experiences · LinkedIn
LinkedIn Data Scientist Interview Experience — Product Sense, SQL, and a Pandas Group-By Slip
Interviewers: the main interviewer and a shadow interviewer, both very friendly. Question 1: Product Sense — how would you analyze a drop in traffic from the Home Page to the Profile Page? (20 mins) My approach: Start with a qualitative check: open LinkedIn's homepage myself to see if there's an obvious change or bug. For example, there was a recent user report that searching for someone's name s…
Interview experiences · LinkedIn
LinkedIn Data Scientist Interview Experience — Statistics and Case-Study Questions from the Screening Round
I can't guarantee these answers are 100% correct — take them as reference only! LinkedIn Stats One bank has 5 tellers and a single line; another bank has 5 tellers but 5 separate lines. Which one would you stand in? Simple statistical explanation: the "long plank effect" (the opposite of the weakest-link effect). In a single queue, your waiting time is determined by the fastest available teller.…
Interview experiences · LinkedIn
LinkedIn Machine Learning Engineer Interview Experience — An Ambiguous Recommender Training Task
This was a very strange interview experience. It was the interviewer's first time interviewing, and she asked me to handwrite a binary-classification machine learning loader and trainer. The data was not a real dataset, so I could not write code that would actually run. She asked for pseudocode but did not explain what level of detail she wanted. She also did not clarify what the model was suppos…
Interview experiences · LinkedIn
LinkedIn Machine Learning Engineer Interview Experience — Onsite Undone by a Key-Value Store System Design Question
LinkedIn, AI track. I passed the technical screen before the layoffs, and it didn't get scheduled for onsite until this week. The hiring manager round is scheduled for before National Day — nothing much to say about that yet. After preparing for so long I was actually pretty confident, but today one of the system design rounds completely wrecked me. I'm not fully willing to accept that, but I'm s…
Interview experiences · LinkedIn
LinkedIn Machine Learning Engineer Interview Experience — Weird Phone Screen with BQs, Array Sum Coding and InMail System Design
Sharing a pretty weird LinkedIn phone screen. A recruiter reached out in early September and set up a 20-minute call. We briefly talked about my background, the target role and salary, and then the phone screen got scheduled. Phone screen: 1 hour. It started with about 5 minutes of intro. I got interrupted before I even finished my self-introduction. Overall it felt like the interviewer wasn't ve…
Interview experiences · LinkedIn
LinkedIn Senior Machine Learning Engineer Interview Experience — Debugging Logistic Regression, Then Job Click Prediction Design
The first part was 30 minutes of debugging a logistic regression implementation. I spent too much time on the sigmoid derivative at the start, so I didn't finish the last step, computing the gradients. Then came 20 minutes of ML design: Predict whether a member will click on a displayed job using member features, job content, and interaction history. I had to define everything myself: what data i…
Interview experiences · LinkedIn
LinkedIn Senior+ Data Engineer Interview Experience — Aced the Coding Round, Rejected the Next Day
Unfortunately I got laid off by my old company a few weeks ago. Through a good friend's referral, I got an interview for a LinkedIn Staff Data Engineer - Information Security role. The interviewer was really friendly — the whole thing was very warm and supportive. The interview was an hour total. We started with some small talk, then he asked two questions: Tell me about a project you worked on,…
Interview experiences · LinkedIn
LinkedIn Senior+ Software Engineer Interview Experience — Five-Round Onsite, Timezone Curveball in System Design
LinkedIn onsite interview experience, giving back to the community here. Some background first: I'm an SDE3 with 5 years of experience. I'd been grinding coding problems for a while, but my system design prep was just so-so. The whole onsite was five rounds, one hour each: Round 1 was a project deep dive. I talked through two projects, and the interviewer kept the conversation pretty natural, dig…
Interview experiences · LinkedIn
LinkedIn Software Engineer Interview Experience — A Five-Round IC2 Loop With an AI/Coding Round
Elimination Round Maximum Depth of Binary Tree Zigzag Level Order Traversal Round 1 – DSA Max Points on a Line / Max Collinear Points Minimum Length Substring Round 2 – AI + Coding LRU Cache with Counters Given different workloads, predict and calculate the cache's hit/miss ratio. This round required combining coding with reasoning about AI/system behavior. Round 3 – Hiring Manager Behavioral int…
Interview experiences · LinkedIn
LinkedIn Software Engineer Interview Experience — Five Rounds, No Hard Problems, All About Depth
Five rounds, with my approach and follow-ups for each. I've been lurking on this forum for years, and this interview process benefited a lot from it, so I'm writing up a full account to give back. As usual, I'll use homophone code names for the problems in the original, but I'll just describe them directly here. Overall impressions first. LinkedIn's interview pace is fairly restrained — not like…
Interview experiences · LinkedIn
LinkedIn Software Engineer Interview Experience — Interviewer Couldn't Follow My One-Pass DFS Trick
Two questions. The first was to merge an n-ary tree by key -- only nodes that share the same key get merged. It's solvable with DFS. Make sure to ask about the corner cases up front, like whether the root keys are even the same. The second question was similar in spirit. The interviewer completely did not understand this problem. I wrote out the following conversion formula, which lets you solve…