READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 78 of 153
Interview experiences · Klaviyo
Klaviyo Software Engineer interview, CodeSignal unlock sequence
I applied, and the recruiter reached out quickly by email and through the candidate portal. The recruiter call was easy and straightforward, and they accommodated my timeline so I could move directly to an assessment through CodeSignal. The assessment worked like an online unlock sequence. Getting a full score on one problem allowed me to move to the next. I didn’t pass overall, but I was told th…
Interview experiences · Klaviyo
Klaviyo Software Engineer Interview Experience — No-Camera OA, Passed 3 of 4 on a Banking System Design Problem
No need to turn the camera on. Out of four questions, all subtasks passed on three of them. I was just using it as practice — I didn't use AI, wrote all three questions myself. Level 1 and 2 were fairly simple. Design Banking System Level 3: Schedule Payments transfer(timestamp, source_account_id, target_account_id, amount) -> str|None At timestamp, deduct amount from source_account_id and freeze…
Interview experiences · KnowBe4
KnowBe4 Customer Success Engineer interview experience: absent follow-up
Scheduling began normally, but the first live HR conversation felt wrong. The interviewer seemed disengaged with my answers, and I felt I was not being taken seriously. Without an explanation, it seemed as if they might already have someone else in mind, though that was only my impression. The communication problems continued. I was told I would hear about feedback or next steps, but I did not, a…
Interview experiences · Koch
Koch Financial Analyst Interview Experience: values, behavioral examples, and English
The process began with a recruiter touchpoint, followed soon by a technical screen that surprised me because it did not focus much on hard technical questions. Most of it was behavioral. It felt as though the interviewers were looking for something very specific, although I could not tell exactly what they were targeting. Later conversations included many questions about company values. The conve…
Interview experiences · Koch Minerals & Trading
Koch Minerals & Trading Financial Analyst Interview Experience: fit and communication over technical depth
The rounds felt designed to test fit and how I expressed myself more than raw technical knowledge. The office was very professional, and the interviewers were respectful and welcoming. Still, the questions made me feel they were looking for something specific in the kind of analyst I would be. Behavioral prompts were a large part of the process. I described situations I had handled in ways that a…
Interview experiences · Kohl's
Kohl's Account Executive interview: two practical conversations and pay expectations
The first recruiter-style call was light and practical. We discussed my availability, why I wanted to work at Kohl's, and my strengths and weaknesses. The recruiter also described some of the day-to-day work. It was low-stress. A short time later, I had another quick remote conversation. It covered standard questions and basic fit, with nothing especially technical or difficult. What mattered mos…
Interview experiences · Konrad Group
Konrad Group UX/UI Designer Interview Experience: Portfolio and design challenge
I began with a short, easygoing HR or recruiter chat. We discussed why I was interested in design and the company, my salary expectations, and what I did outside work. It was friendly and conversational rather than an interrogation; it felt as though they wanted to understand me. Next, I presented my portfolio in person and answered behavioral questions as I walked through it. That was followed b…
Interview experiences · Kotak
Kotak Software Engineer interview: Two Sum, food delivery design, and trade-offs
I started with a BarRaiser-style first round that mixed DSA, low-level design, and distributed systems. It lasted about 1.5 hours and leaned hard on fundamentals, with little time spent on my resume. For DSA, I got classic array problems such as Two Sum and a buy/sell-stocks style question. For low-level design, I designed a food-delivery system like Swiggy or Zomato, discussing classes, relation…
Interview experiences · KPMG
KPMG Consultant HR screen through partner culture conversation
My process was structured from the start. I began with an HR screen, then had consecutive interviews that ended with a partner. The path was clear: an early fit check, manager- and director-level conversations, then a final conversation about culture fit with the partner. The earlier discussions mixed behavioral questions with role-relevant topics. As I reached the later stages, the focus narrowe…
Interview experiences · KPMG
KPMG Consultant interview: consulting cases and stakeholder reasoning
The process followed a familiar consulting pattern: recruiter or HR first, then several interviews over a few weeks that mixed fit and business thinking. The interviewers were friendly, but they followed up on my answers rather than letting me stay at a high level. Later scenarios asked me to frame an approach to integration, separation, and M&A situations. I discussed how I would organize the wo…
Interview experiences · Kpmg India
Kpmg India Consultant interview: business scenarios and fit
The recruiter scheduled the HR step through Zoom or email and kept the conversation relaxed, focusing on my background and fit. I then had behavioral and scenario conversations, including business situations around integration, separation, and M&A. Interviewers followed up on my answers and asked me to explain my reasoning rather than stay broad. The next phase was an assessment followed by an in…
Interview experiences · KPMG Philippines
KPMG Philippines Consultant interview: structured business cases
I started with back-to-back behavioral and scenario sessions. The scenario round was a business case about how I would approach an engagement, including integration, separation, and M&A considerations. It tested structure and reasoning more than memorized material. The next stage again paired behavioral work with technical-style thinking in a service-line setting. The technical piece was not codi…
Interview experiences · KPMG Philippines
KPMG Philippines Solutions Consultant interview: recruiter screen and manager discussions
I began with a friendly recruiter phone screen. We discussed my work experience and salary, and the recruiter said I should hear back within about two weeks. It felt straightforward and positive, like a check that I met the basics before moving on. Afterward, I had an HR screen and hiring-manager-style interviews. The interviewers were approachable, explained how the process would work, and took…
Interview experiences · Kpmg Us
Kpmg Us Consultant interview: consulting fit and cases
After I applied, the process moved from recruiter and HR conversations to manager-led interviews. It felt professional and structured: people introduced themselves, then probed after my answers. The rounds were about fit and communication rather than pure coding. I had back-to-back behavioral and scenario sessions. The case topics included integration, separation, and M&A, and I discussed my resp…
Interview experiences · Kyndryl
Kyndryl Software Engineer interview: English assessment, group discussion and networking
After an initial recruiter-style step, I took an online English assessment. It had a fluency check, then vocabulary and spelling questions, all under a time limit with many questions. It stressed speed and accuracy, and I had to be careful with unknown answers because wrong answers carried negative marking. Soon after, I joined a group discussion on a current technology topic. Everyone needed a c…
Interview experiences · Kyndryl
Kyndryl Software Engineer interview: networking fundamentals
The opening screening was smooth and casual. They asked about my education and willingness to relocate, and the tone was comfortable rather than interrogative. The later interview was more direct, but the interviewer was polite and gave me space to answer without feeling rushed. Most questions covered computer-networking basics. It was not a heavy-coding exercise; they wanted to see whether I und…
Interview experiences · L3Harris
L3Harris Software Engineer Interview Experience: HR and manager conversations
I started with an HR phone screen about my resume, past projects, and why I wanted the role. Next came a Zoom-style conversation with managers on the team. It was mostly behavioral, though a few lightly technical questions came up through how I described my experience and how I work. It was a typical multi-round process focused on my background and how I would operate in the role. Location: Camde…
Interview experiences · L3Harris
L3Harris Software Engineer Interview Experience: smooth referral to STAR behavioral Teams interview
After I applied, I had a recruiter phone call and the next step was set up immediately. There was no separate pass-or-fail update. At the end of the call, I was told a Teams interview with the hiring manager would be scheduled, and I chose a time. Because I had a referral, the recruiter interaction felt smooth. The hiring-manager interview on Teams was straightforward. I discussed my experience a…
Interview experiences · L3Harris
L3Harris Software Engineer Interview Experience: Take-home after three rounds
I went through three rounds, starting with a hiring-manager conversation and then another engineer. The last stage was a team interview where I was grilled for about an hour. I also had a take-home assignment, which was the hardest part of the process. The difficulty rose as I progressed. By the team round, it felt more intense and less like a conversation. I thought I did reasonably well in the…
Interview experiences · La Fosse
La Fosse Consultant interview: prolonged culture-fit process
This was the opposite of the smooth, well-communicated process I expected. I went through what felt like too many culture-fit discussions, then received last-minute requests to scramble together business plans. The handling of references and the wider feeling that my time was not respected threw me off. At times, it felt as if information I had given was being used as intelligence rather than for…
Interview experiences · Lam Research
Lam Research Software Engineer interview: code analysis, project presentation and a director round
After a recruiter screen, I had a technical discussion where I analyzed sample code. It felt like a direct way to assess how I read an implementation and reasoned about it. About a week into the process, I went through a structured three-round loop. The hiring-manager screen covered my technical background and some behavioral questions. The onsite technical stage included a presentation about my…
Interview experiences · Lambda
Lambda Software Engineer Interview Experience — Recruiter Screen Grills You on K8s, Bare Metal, and Fleet Management
Basically it's the company introduction, but they also do an initial screen within it — they ask you about some terms and questions, then write down your explanations for the hiring manager. They'll tell you they're using a Google Meet transcript for this; if you don't want that, the recruiter just listens to you and matches keywords instead. Some of what they asked about: Experience in Infra as…
Interview experiences · L&T Technology Services
L&T Technology Services Software Engineer interview: networking and core theory
After the recruiter screen, I had two back-to-back technical interviews. They focused on my C, Linux, networking, and WiFi background, and I had to explain both concepts and the resume work behind them. One round also covered circuits, signals, communication, basic programming logic, and my projects. The manager round was more conversational. I discussed past work from my resume and answered scen…
Interview experiences · LangChain
LangChain Senior+ Software Engineer Interview Experience — Take-Home Optimization Then Three Onsite Rounds in One Day
First I talked with the recruiter, then they gave me a take-home with one week to finish. The take-home was optimizing a benchmark testing setup — there's a POST endpoint and a GET endpoint, using S3 as the database. The version they hand you originally reads the whole JSON out every time and uses string find to look for the offset. The overall speed of the POST was about 20+ seconds, and the goa…