Software Developer (Intern + FTE)
Interview Date
February 11, 2024 (Published date, experience likely around 7th semester prior to this)
Result
Offered "INTERN + FTE" position
Difficulty
—
Rounds
3 rounds
Drive Type
On-Campus/Internship/Full-Time
Topics asked
Detailed experience
College: Not Specified (On-campus placements)
Interview Date: February 11, 2024 (Published date, experience likely around 7th semester prior to this)
Interview Type: On-Campus/Internship/Full-Time
Result: Offered "INTERN + FTE" position
Difficulty: Not Specified
Rounds: 3 rounds
Topics Asked: Coding Questions (Time complexity, Space complexity), Projects (web development, ML-based), OSI layer and protocols, Behavioral (Why software over ECE core, why HPE, overview of projects).
The candidate was offered an "INTERN + FTE" position at HPE after on-campus placements. The interview process followed a standard format with three rounds.
Round 1: Technical Round (1 hour long)
The interview began with introductions from the two panelists, followed by the candidate's self-introduction. After the introduction, the candidate was asked to solve a few coding questions. For each problem, they were also asked to state the Time complexity and Space complexity.
Round 2: Managerial + Technical Round (30 minutes)
This round involved project discussion and fundamental concepts. The candidate had three projects (one on web development and one ML-based) and explained them one by one, which took most of the time. The interviewer then asked about the OSI layer and requested an explanation of the protocols involved in each layer. Finally, a behavioral question was posed: "why I wanted to go for software but not for the ECE core domain since I was from ECE."
Round 3: HR Round (10 minutes)
This was the final round. The HR round is crucial as not everyone who reaches it gets selected. The interviewer first asked for an introduction, then "What do you know about the company?" Secondly, an overview of projects was requested. Lastly, the question "Why HPE?" was asked.
Overall advice from the candidate: be solid on data structures (especially arrays to linked lists), fundamentals, and know your projects thoroughly.