READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 67 of 153
Interview experiences · HPE
Hewlett Packard Enterprise | HPE Software Engineer interview: placement-path networking
I entered through a university placement internship path, and the process felt quick and straightforward. After an initial recruiter-style step, I had a technical screen with a basic DSA question and networking fundamentals. I talked through data transfer at a high level, what VPNs do under the hood, and basics of application behavior. The process continued with practical foundations. An assessme…
Interview experiences · HPE
Hewlett Packard Enterprise | HPE Software Engineer interview: rounds then hold
A recruiter called to schedule an open position, and the Hewlett Packard Enterprise process expanded into around four virtual rounds plus an onsite at an office. Each stage emphasized deep technical work. The questions were mostly DSA coding, with operating systems and computer networking mixed in. Later interviews pushed further into technical depth and topics tied to the job description. After…
Interview experiences · Hex
Hex Software Engineer Interview Experience — Five Onsite Rounds and Feedback for Leaning Too Much on AI
I just got done with my onsite interview at Hex, so I wanted to contribute this data point. For the full stack track, I went through quite a few rounds: web dev, system design, product taste, behavioral, and a CTO round. The feedback I ended up getting was that the web dev round relied too much on AI... Personally, I think the line for this kind of AI-native interview format is actually pretty ha…
Interview experiences · Hexaware
Hexaware Software Engineer interview: crowded multi-round process
I found the Hexaware process extremely long and crowded. Around 300+ people arrived for interviews, and it felt built for a large batch rather than careful one-on-one assessment. There were about two or three technical rounds, roughly an hour each, plus a managerial round. The main challenge was patience. Without the ability to sit through delays and wait for my turn, the process itself would hav…
Interview experiences · Hexaware
Hexaware Software Engineer Interview Experience: an uncomfortable virtual interview
My first impression of the Hexaware virtual interview was not good at all. I joined the online interview with my screen shared, and I was thrown off when the interviewer did not turn on their own camera. That small thing quickly set the tone for the rest of the session. When I got stuck trying to understand a question, the interviewer showed little patience and would not really walk through it wh…
Interview experiences · Hexaware
Hexaware Software Engineer Interview Experience: client interview pending after background check
I started the process in July and it initially seemed promising. I cleared the assessment and technical rounds and was told a client interview would be scheduled. Instead, background verification began and I was asked for documents. Later I was told the position was on hold. The explanation was conflicting: no offer had been released because the client interview was still pending, which made me q…
Interview experiences · Hexaware
Hexaware Software Engineer Interview Experience: Four elimination rounds and time pressure in the OA
My Hexaware process had a clear elimination flow across four rounds: a group discussion, an online assessment, a technical plus HR interview, and a final general HR interview. The group discussion focused on communication. The online assessment combined aptitude, technical MCQs, debugging, short coding, and prompt-style tasks. It was under strict time pressure, which made it feel high-stakes. The…
Interview experiences · Hexaware
Hexaware Software Engineer Interview Experience: Four-round campus process with vibe coding
I attended an on-campus Hexaware placement process with four rounds. Before it began, the placement team gave a pre-placement talk and explained the sequence, which made it less intimidating. The first round was a group discussion on general topics. The next was an online assessment with aptitude, technical MCQs, coding-style questions, and vibe coding. Then came a combined technical and HR inter…
Interview experiences · Hexaware
Hexaware Software Engineer Interview Experience: Java, Python, SQL, and final HR rejection
My process had four rounds: a group discussion, an online technical assessment, a technical interview, and an HR interview. The technical interview drew on my Java and Python self-ratings and my resume projects. Exception handling and SQL joins also came up. The HR round was the last step, and I could not get past it. I did not expect that because I felt I had done well in the technical interview…
Interview experiences · Hexaware
Hexaware Software Engineer interview with group discussion and OOP
My Hexaware process began with a group discussion on general topics. It tested how I communicated and how confidently I could present ideas, but the topics were not designed to trick me. Then I took a technical assessment with MCQs, pseudocode, aptitude, bug finding, logical reasoning, pattern matching, puzzles, and coding questions. That step felt manageable. The technical interview covered OOP,…
Interview experiences · Hexaware
Hexaware Software Engineer interview with Java, DBMS, and campus placement
My interview started through campus placement, and the staff were friendly throughout the rounds. The first step was an online assessment with aptitude, logical reasoning, verbal ability, technical MCQs, and coding questions. The aptitude part felt medium, while coding was easy to medium. After clearing it, I had a technical interview on Java and OOP, DBMS and SQL, operating systems, and computer…
Interview experiences · Hexaware
Hexaware Software Engineer interview with timed aptitude and debugging OA
The Hexaware process had four elimination-style rounds: a group discussion, an online assessment, a technical and HR interview, and a final general HR interview. The group discussion focused on communication. The online assessment combined aptitude, technical MCQs, debugging, short coding, and prompt-style tasks under strict time pressure. The aptitude section included data interpretation questio…
Interview experiences · Hilti Group
Hilti Group Account Executive interview: group case study and sales roleplay
The interview lasted a whole day and felt intense and carefully structured. I started with a group case study. After reading the cases, I roleplayed persuading the interviewers to buy into my approach. It seemed designed to test whether I could turn my analysis into a convincing sales story. Next, I met area sales managers for more straightforward conversations about fit and how I'd work day to d…
Interview experiences · Hilti Group
Hilti Group Software Engineer interview: vague rejection feedback
My first conversation was directly with the hiring manager and felt scrutinizing from the start. The focus seemed to stay on critical points in my resume. The positive parts of my experience and what excited me got little time, so I felt I was defending myself instead of discussing technical background and motivation. Questions came quickly, with limited room to expand. I also asked about the rol…
Interview experiences · Home Depot
Home Depot Business Analyst Interview Experience — Manager Merged Two Rounds Into One
In late October I got an interview for an HD SBA role through a friend's referral, so let me share how it went (spoiler: I got rejected). Since I hadn't interviewed in a long time, but my friend's referral was really strong, the process moved super fast — a total of 10 days to get through 2 rounds of interviews (actually 3 rounds, since the hiring manager decided to merge round 2 and round 3). Ti…
Interview experiences · Home Depot
Home Depot Business Analyst Interview Experience — Two Rounds Merged Into One 70-Minute Call, Rejected on the Case
In late October 2025 I got an interview for the Home Depot SBA role through a friend's referral, and I'm here to share my rejection report. Since I hadn't interviewed in a long time, and my friend's strong referral really helped, the process moved really fast — 10 days total to get through 2 rounds of interviews (actually 3 rounds, since the hiring manager decided to merge round 2 and round 3). T…
Interview experiences · Honeywell Technologies
Honeywell Technologies Software Engineer interview experience
I started with an online assessment, then had a technical interview that covered coding, my projects, and core subjects. After the technical part, I went through a managerial and HR round that focused more on how I work with people: teamwork, communication, and my career goals. What made the process feel different was the balance. It did not feel like a purely technical elimination round. It felt…
Interview experiences · Honeywell Technologies
Honeywell Technologies Software Engineer Interview Experience: recruiter discussion of pay and benefits
The selection process felt organized and fairly smooth. The recruiter conversation made the role and its expectations clear, and the questions were straightforward and easy to follow. Compensation and benefits also came up as part of discussing what the position would offer. It felt more like aligning expectations than a stressful grilling. I didn't receive an offer, but it was still a decent and…
Interview experiences · Honeywell Technologies
Honeywell Technologies Software Engineer Interview Experience: System design and AI themes
The process focused on explaining concepts and showing how well I understood the work behind them. Rather than going straight into coding, it centered on the systems side of software engineering, and I spent a lot of time talking through system design ideas. There was also a noticeable focus on newer AI themes. I tried to connect what I knew to the current "latest trends" type of questions. The b…
Interview experiences · Honeywell Technologies
Honeywell Technologies Software Engineer interview: interruptions and laughter
The Honeywell Technologies process started with HR, with the recruiter calling candidates one by one. I then met two interviewers in the interview room. Their tone threw me off. They seemed mean, laughed while I answered, and repeatedly interrupted me before I could finish. The format itself was ordinary, but I experienced the interaction as disrespectful and unreceptive. I did not receive an off…
Interview experiences · Honeywell Technologies
Honeywell Technologies Software Engineer interview: role fit and communication
I was first contacted for an introductory conversation and then moved to a technical interview. The technical discussion centered on the role itself, what I would be doing, and how well I understood the requirements. They also asked about my English language skills and my studies. It felt more like a screen for fit and communication than a hard technical challenge. I did not receive an offer, but…
Interview experiences · Honeywell Technologies
Honeywell Technologies Software Engineer interview: STAR answers and resume discussion
The recruiter call was mostly basic behavioral questions. About a week later, I spoke technically with a group of engineers. The pace was quick, and they explicitly wanted structured answers, so I used STAR throughout. The technical questions were manageable and tied mainly to my resume and background rather than deep, tricky problems. I did not get an offer, but the process was more manageable t…
Interview experiences · Hot Topic
Hot Topic Account Executive interview experience: a quick store-manager conversation
After applying, I went through a quick, low-stakes process. A recruiter-style call came first. About a week later, I had a technical or sales-screen-style conversation that stayed casual and direct. We covered who I was, why I wanted the job, and how I would handle customer situations. The interview itself was simple and laid back. I spoke with a manager in the store about the usual retail topics…
Interview experiences · Hot Topic
Hot Topic Account Executive Interview Experience: pop culture and customer scenarios
The interview was closer to sales-associate fundamentals than anything technical, but they also wanted to see whether I fit the store's vibe. The early questions covered helping customers, handling the basic functions in the job preview, and responding to customers who were shy or difficult. They also asked about my pop-culture interests, including music and shows. What stood out was discussing p…