READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 151 of 153
Interview experiences · Xccelerated
Xccelerated Software Engineer interview on Java, Kafka, and DSA
The process was pleasantly straightforward and not overly stressful. I completed roughly three to four rounds, with a positive overall tone and average difficulty. It never felt as if they were trying to trip me up. The discussions drew on software fundamentals: arrays, data structures, DSA, and my previous experience. We also covered Java and high-level Kafka design. I completed a medium-level c…
Interview experiences · Xebia
Xebia Software Engineer interview on DSA, Java, and Kafka
The process was straightforward and not especially stressful. I had about three to four rounds, with early conversations on my background, fit, and core engineering fundamentals. Technical rounds covered arrays, algorithms and DSA, including a medium-level live coding problem. There was also a Java discussion and a higher-level Kafka conversation about system design and data flow. I gave a quick…
Interview experiences · Xero
Xero Product Manager interview: recruiter, manager, and team fit conversations
I began with a recruiter conversation that felt like a general culture-fit screen. Shortly afterward, I met the hiring manager, where the focus shifted to whether I fit the Product Manager role itself. I then spoke with a broader group from the team. That final stage also centered on fit, both whether I could do the work and whether I would work well with the team. The process felt structured and…
Interview experiences · Xero
Xero Software Engineer interview: live coding and a role closed after later rounds
After an HR screen, most of the process involved hands-on work and live interviews. I solved a typical algorithms question in a live HackerRank round, then laid out a high-level system design and explained my decisions. A hiring-manager discussion covered behavior and team fit, particularly how I handled conflict and resolved problems. At times, I felt they were testing my collaboration as closel…
Interview experiences · Xometry
Xometry Senior+ Machine Learning Engineer Interview Experience — A Deploy-Under-200ms Deep Dive
Company: Xometry (March) Round: Round 1 Position: Lead ML Questions/format: 1) Walk through your background and your projects in detail 2) The DS team handed you a model — if you had to deploy it, the requirement is that a single inference call has to come in under 200ms 1) Key points for talking about project background Project goal: the business problem you're solving, and the evaluation metric…
Interview experiences · XPeng
XPeng Data Engineer Interview Experience — Recruiter Went Silent, LRU Cache Blank-Out
I've always dreamed of working at a self-driving company! These days, anyone who can still put their heart into working in autonomous driving really has passion for it. But unfortunately I didn't manage to make the most of my interview opportunity with XPeng :( I don't think their recruiter was very professional. I emailed the recruiter to ask if there was an interview prep guide, and after the P…
Interview experiences · Xylem
Xylem Software Engineer interview: fundamentals under pressure
The interview was hard and highly conceptual. I had to think deeply instead of reciting facts, and vague answers were not enough. They wanted precise answers grounded in fundamentals. I do not remember a long, step-by-step sequence of stages. What I do remember is that the difficulty stayed consistent: conceptual depth mattered more than quick problem-solving tricks. I did not receive an offer. L…
Interview experiences · Yahoo
Yahoo Senior+ Machine Learning Engineer Interview Experience — Great Technical Screen, Then the Role Got Paused
Yahoo News interview (April), Round 1. Question 1: Talk about your background and one of your projects in detail — they dug deep into one particular project. Key points for the answer (aim for a total of 3–6 minutes) and my own suggestions: Quick background (20–30s): one sentence on the role, your responsibilities on the team, and list 1–2 projects. Deep-dive framework (3–4 minutes, using STAR):…
Interview experiences · Yardi Systems
Yardi Systems Engineering Manager interview: six-week behavioral process
After the initial phone-interview outreach, I moved through a compact sequence over about six weeks: a recruiter phone call and two follow-up interviews with different team leads. Right after the first call, I received an online assessment on critical thinking and basic arithmetic, separate from the conversations. The questions were mostly behavioral. The first call focused on why Yardi and a wal…
Interview experiences · YASH Technologies
YASH Technologies Consultant interview: SAP MM process flow
The interview was calm, and the main thing I remember was one significant technical question about business processes and the SAP MM module. The interviewer wanted me to explain the business process first, then connect that understanding to the relevant T-codes. It was a focused conversation rather than a broad grilling. The structure of the question made me feel that they were checking whether I…
Interview experiences · YASH Technologies
YASH Technologies Software Engineer interview: SAP, ABAP and database fundamentals
The interview was difficult and closely tied to SAP work, with ABAP as the main skill. Most questions covered database concepts and SQL, and I needed to explain how those fundamentals connected with the domain. SQL came up repeatedly, along with RICEF questions. It felt much more specific than a general software interview. I was able to handle the questions, so in that sense the conversation went…
Interview experiences · Yelp
Yelp Data Scientist Interview Experience — SQL, Python, and Experimentation
Overall, there were three parts: SQL, Python, and experimentation. SQL: the main focus They provide several table schemas. The first question starts with basic aggregation. You just need to use count(distinct ...) flexibly together with sensible filtering, so the key is to understand the table schemas carefully first. You can ask more questions. The second question generally tests a simple metric…
Interview experiences · YipitData
YipitData Account Executive interview: a 15-minute screen and a sales presentation
After a recruiter screen of about 15 minutes, I moved to a hiring-manager conversation and continued round by round. The process was organized, but about a week between each step made it stretch longer than I expected. The first real round was with the hiring manager. The second was a separate sales presentation, followed by a director conversation. The structure seemed intended to check fit and…
Interview experiences · Yochana
Yochana Software Engineer Interview Experience: JavaScript, React, Node.js, and REST
After an HR screen, I had two technical rounds and then a managerial discussion. The process was smooth, with average difficulty. Nothing blindsided me, but it still called for solid problem-solving. During the technical rounds, I discussed project experience and answered questions about JavaScript, React, Node.js, REST API concepts, and database fundamentals. The interviewers focused on how I ap…
Interview experiences · Yochana
Yochana Software Engineer Interview Experience: resume fundamentals and easy coding
The discussion began with my projects, experience, and the technologies listed on my resume. It then moved through basic programming and OOP, including an explicit OOPS question, along with SQL. There was a coding component, but it stayed easy and tested whether I could implement fundamentals. The same technical discussion included straightforward DSA prompts aimed at basic problem solving rather…
Interview experiences · Yochana
Yochana Software Engineer interview: late Teams interviewer and tense tone
My interview call was on Teams, and the tone felt off from the start. The interviewer joined late and then asked questions in an abrupt, almost machine-like way. I felt they were more interested in showing their own knowledge than evaluating how I solved the problem. When I could not answer one question immediately, the impatience was obvious. The interaction became colder, with an arrogant respo…
Interview experiences · Zalando
Zalando Software Engineer Interview Experience: Mismatch on level and pay
The process soured quickly. I went through complex rounds and was rejected for a mid-level role. To me, the expectations did not match what had been communicated: they seemed to want more experience while offering less pay. The interviewer interactions felt rude and unfriendly, which made it hard to stay motivated. I left upset, with the sense that the company was not acting in good faith about f…
Interview experiences · Zalando
Zalando Software Engineer interview: technical depth, system design, and manager debrief
After a recruiter screen, I had an HR call about my experience, salary expectations, and a detailed explanation of the process and interviewers. I then had several technical rounds in a structured but flexible sequence: general technical depth, system design, and behavioral or managerial evaluation. Each technical round lasted about an hour. The questions tied closely to work I had described, inc…
Interview experiences · Zemoso Technologies
Zemoso Technologies Software Engineer interview: backend-heavy technical rounds
I went through two technical rounds and an HR discussion, and things moved quickly. In one experience, an offer letter was already arriving in about ten days. The interviews were practical, covering backend work along with some frontend work. About seventy percent of the technical questions were backend-focused. I discussed Node.js middleware, REST APIs, JWT authentication, and asynchronous progr…
Interview experiences · Zensar
Zensar Software Engineer interview: an unexpected technical evaluation during HR
The first round was a fairly straightforward technical discussion of fundamentals and object-oriented programming. Afterward, I expected a general HR conversation. Instead, that discussion became a full technical evaluation with little warning. I wasn't ready for the sudden change. The interviewer seemed impatient and unprofessional, asking questions rapidly without making much effort to understa…
Interview experiences · Zensar Technologies
Zensar Technologies Software Engineer interview: campus assessment, interview, and HR
The process began on campus and had two parts: an online assessment, followed by an interview and an HR round. It felt straightforward to moderately challenging. Nothing was especially punishing, but it was not completely trivial either. The interview followed the assessment, and the HR conversation was the final step. My impression was that the process was structured and kept moving. I did not f…
Interview experiences · Zest AI
Zest AI Data Scientist Interview Experience — Eight Rounds, Then Ghosted by a Vanishing HR
Let me share the funniest interview experience I've had recently. I saw the posting online and applied on a whim. The recruiter emailed me to reach out. From start to finish there were 8 rounds total. Yes, 8, for a company this small. First was the hiring manager round: resume and machine learning concepts. Then a technical screen. The first question showed a graph where training, testing, and va…
Interview experiences · ZF Group
ZF Group Software Engineer Interview Experience: An easy Teams round followed by deeper resume questions
My process had two structured rounds. The first was a Teams interview that felt relatively easy and stayed close to C programming fundamentals and Autosar concepts. I remember answering everything correctly, which helped me relax into the conversation. The second round went deeper into the skills on my resume. The questions were no longer surface-level; they asked about the reasoning behind what…
Interview experiences · ZF Group
ZF Group Software Engineer Interview Experience: Mapping prior work to the role
Before anything formal happened, the process focused on my fit for the role. I had to write down what I had done previously and explain how it mapped to the job description, including how I solved problems in my field and why that experience would matter going forward. The interview kept returning to how my past work connected to the position. I described how I approached problems, managed time t…