READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 77 of 153
Interview experiences · Juspay
Juspay Software Engineer hackathon coding and systems threshold process
After a recruiter step, I went through a long sequence that felt closer to events than ordinary interviews. An early hackathon-style track included a live coding problem. A developer explained the prompt and stayed engaged while I worked, and the judging focused on how I wrote code and handled the engineering work as it unfolded. Later discussions covered DBMS, computer networks, operating system…
Interview experiences · Juspay
Juspay Software Engineer interview: uneven interviewer engagement and server-optimization design
The experience changed dramatically depending on the interviewer. One round felt barely engaged: there were only a few puzzles and questions, and the tone felt less like a serious evaluation than a confrontational attempt to provoke. Another round was much better. The interviewer was genuinely good, the session ran about forty-five minutes, and it combined DSA with a basic system-design problem a…
Interview experiences · Kantar
Kantar Research Analyst interview: assessment, recorded interview, and case presentation
I began with an online assessment of logic and critical thinking. After that, an email moved me to a recorded interview, where I answered questions about why I wanted to work for the company and similar prompts. I then met the hiring managers. The format combined a case study with a presentation, followed by a separate conversation about my thinking and fit for the role. It felt like a staged, st…
Interview experiences · Kantar
Kantar Research Analyst interview: case work and long gaps in communication
After a recruiter contacted me, a longer panel interview was scheduled. Everything seemed arranged, but I received no follow-up. I had to check the hiring portal myself to try to work out what was happening. The recruiter seemed to disappear, and even after a long wait I got no reply. In another similar process, I completed early screening, received a case study to present and did the interview.…
Interview experiences · Karat
Karat Software Engineer Interview Experience — Password Validator and a Three-Table Join Over Bad Audio
Weird screen, hard to categorize, but I hope this gets seen anyway... Classic low-quality Amazon-customer-service-tier microphone. I've worked with people like this for years and I still only understood about 50% of what the interviewer said. Fortunately they noticed too, so I politely asked them to speak a bit slower, and it got a lot better after that. Right at the start they said I didn't need…
Interview experiences · Karat
Karat Software Engineer interview: one-hour live coding and system design session
The process started with a short, multiple-choice qualifying test. I could choose topics such as backend, general coding logic, or algorithms and data structures. After I passed, I was invited almost immediately to schedule the actual interview. The main technical interview was a live online video session that lasted about an hour. It combined discussion and analysis questions with a system desig…
Interview experiences · Karat
Karat Software Engineer interview with a moderate algorithm question
The interview started with a casual introduction from the interviewer, which made the conversation feel less cold. I then talked through my background, including my achievements, previous experiences, and how I’d handled challenges on earlier projects. It felt like that discussion was meant to provide context before the technical portion. Afterward, I worked through a moderate algorithm question.…
Interview experiences · Karat
Karat Software Engineer interview with a rigid one-hour technical screen
My first contact involved scheduling and then a technical screen. The format felt time-boxed and rigid. I had a hard one-hour window, and the interaction style made it difficult to build momentum. We started with a quick setup where I was asked to explain my background in about a minute. The rest of the session became a quiz with multiple abstract scenarios, and I had to come up with solutions. A…
Interview experiences · Karat
Karat Software Engineer interview with learning materials before rejection
I was surprised by how much Karat tried to include "learning" before making a final decision. What they called onboarding felt like an extension of the interview process. I studied their learning materials for a while and completed a couple of practice interviews, then still got rejected after about a week. The part that threw me off was that it didn't feel like optional preparation. It felt like…
Interview experiences · Karat
Karat Software Engineer interview with live DS&A and platform feedback
After I received the initial email with the process details, I was invited to a technical interview. It felt straightforward. I joined a live video call and worked through a live data structures and algorithms test. Once the time was up, I received feedback on my performance. Overall, it was a good, well-run experience. I also liked that the setup felt modern and smooth, so I could focus on the w…
Interview experiences · Karat
Karat Software Engineer interview with three English and three coding questions
My Karat process began with a structured sequence of questions that felt a little relentless. After the initial stages, I answered three English questions and then moved straight into three coding problems. The first coding prompt asked whether a solution met the requirements. I was then asked more focused computer science questions about time and space complexity. The other coding problems were…
Interview experiences · Karat
Karat Software Engineer interview: written Splunk exam and video problem
I started with a written exam sent by email. It focused directly on Splunk-related engineering topics. I completed it and thought I had passed, so I moved on to a video round where I solved a problem during the call. Even after that, I couldn't move forward, and the rejection left me more puzzled than informed. What bothered me most was the uncertainty about the role. I didn't know which position…
Interview experiences · Karat
Karat Software Engineer: LeetCode-style coding under time pressure
My interview started with a classic skills screen: brief introductions and basic computer science questions, followed by the main coding portion in a live editor. The opening focused on fundamentals such as time and space complexity, and I remember the questions moving from easier concepts into harder problems. Once the coding round began, I worked through LeetCode-style questions. The first was…
Interview experiences · Kiewit Corporation
Kiewit Corporation Software Engineer Interview Experience: Engineering decisions and quality checks
The process was well managed from the start. A recruiter kept me updated while I discussed my background, previous work, means and methods, outcomes, and how I approach my work. The focus was practical engineering thinking rather than deep coding, with system design, technical due diligence, and QC or QA themes. The process moved faster than I expected. Shortly after the interview, they contacted…
Interview experiences · Kiewit Corporation
Kiewit Corporation Software Engineer Interview Experience: Fit and relocation
I began with a quick recruiter pre-screen that took under 15 minutes. It covered my past experience, what I wanted next, behavioral and situational questions, and logistics such as relocation. They said an in-person meeting could depend on where I lived, but my next step stayed virtual. The virtual interview was relaxed and light on technical depth. I explained my resume, how my work connected to…
Interview experiences · Kiewit Corporation
Kiewit Corporation Software Engineer recruiter, superintendent, and double in-person interview
This process was more intense and segmented than easier conversational screens I had experienced elsewhere. It began with a recruiter call, then a Zoom conversation with a local higher-up superintendent. From there, I had a double in-person interview with a project manager and a project sponsor, who was a senior, high-impact person. The people were wonderful, and the process was organized and pro…
Interview experiences · Kikoff
Kikoff Software Engineer Interview Experience — A Two-Part Log Parsing and Query Screen Question
Log Parsing, split into two parts. Problem Overview Part 1 You need to build a tool that parses and queries a set of server logs. The input is a list of log lines as strings (List[str]), which get parsed for use by the rest of the tool. Part 1: Parse and Filter Implement a function that reads logs coming from different services and parses them into structured objects. Things to watch out for: The…
Interview experiences · Kimley-Horn
Kimley-Horn Software Engineer Interview Experience: MEP heat transfer and fluids discussion
After a recruiter screen, the process felt almost effortless. Soon afterward, I had a relaxed technical-style block that lasted about 1 to 2 hours and involved several interviewers. Most of the conversation was about my background, how my past experience connected to the role, and the technical skills I had actually used. For the MEP track, the discussion focused heavily on heat transfer and flui…
Interview experiences · KLA
KLA Software Engineer interview: smooth process without feedback
The process felt unusually smooth from the start. After an initial step, they contacted me again to interview for the same role, and the flow stayed organized. During the interviews, I felt I answered every question and had not missed anything fundamental. The frustrating part came after the final interview, when I received no feedback, follow-up notes, or explanation of what happened next. Even…
Interview experiences · Klaviyo
Klaviyo Account Executive: Mock Discovery Call and In-Person Panel
My process began with a recruiter screen and then moved to a hiring manager interview. Most of the questions focused on my experience, along with situational prompts such as walking through a time I handled a specific situation. The recruiter and hiring manager conversations had a similar structure, although the recruiter also explained what to expect and how success would be measured. The next s…
Interview experiences · Klaviyo
Klaviyo Account Executive: repeated reschedules, missing Zoom details, and unanswered follow-ups
What stood out in my experience wasn't the interview questions. It was the communication and follow-through. I started with an initial recruiter interaction and then moved into later conversations, but the process felt inconsistent across several stages. There were short-notice reschedules, people who didn't show up, and rounds that started late without much explanation. The logistics also broke…
Interview experiences · Klaviyo
Klaviyo Data Scientist interview after a referral and team reassignment
I applied online with a referral, and a recruiter contacted me shortly afterward. The timing felt a little unusual because I’d just interviewed with another team, and it seemed that the result of that process influenced what happened next. My impression was that they’d decided internally that I might be a better fit for a different team, even though nobody from the first team had the authority to…
Interview experiences · Klaviyo
Klaviyo Full Stack Engineer interview with API design and system improvement rounds
My first contact was a quick recruiter screen. After that, I received the CodeSignal link for the online assessment. Once I completed it, the process moved into a longer onsite structure covering past work, technical thinking, and collaboration. The onsite included several technical and behavioral interviews. In one round, I went deep into past work and system design decisions, explaining the arc…
Interview experiences · Klaviyo
Klaviyo Software Engineer interview: CodeSignal assessment and production-focused final round
My interview process started with a recruiter call and then moved to a CodeSignal assessment. I found the assessment manageable as long as I had practiced the kinds of tasks used in these formats. It focused more on realistic coding than strict LeetCode patterns. The recruiter screen was straightforward. The final interview moved away from pure DSA questions and focused on the day-to-day work of…