HP Interview Experience 2024
Interview Experience
I attended the HP interview two weeks ago through offline mode. They selected students for the interview by conducting a technical assessment a week prior. And I would lik...
Full Details
I attended the HP interview two weeks ago through offline mode. They selected students for the interview by conducting a technical assessment a week prior. And I would like to share my entire interview experience in detail. Technical assessment: The Assessment consisted of three sections:
MCQ , on numerical, verbal and logical reasoning. MCQs on technical subjects like OS, CN, and output-based questions, etc., 3 Programming questions that were of easy-medium difficulty (To be noted: Python was not offered as a programming option) Ninety-five members were selected for interviews, which were conducted in 3 sections. Technical Managerial HR And each round was an elimination round.
Technical Round: Firstly, when I entered, she asked me to introduce myself. She also inquired me why I wanted to join HP and why I Preferred to work in Bangalore when my native place is so beautiful. She asked questions based on my skills in C++, SQL and DBMS as well as some questions related to Machine Learning, Since I had completed a project in that area. Here are the questions I was asked: Write SQL query to get full name by joining their first and last name what are joins and explain all types of joins Return the element from array whose frequency is high Difference between stack and queue. Difference between array and linked list. About circular queue About priority queue What is Reinforcement Learning What is supervised and unsupervised Explain KNN and Kmeans ? Are they supervised or unsupervised? ( She asked about these models as I didn't include them in my project) What are the metrics used in my project and to explain them and their formulas what is confusion matrix? Explain True Positive, False Positive, True Negative and False Negative with example what is friend function and inline function Explain access specifiers What is denormalization what is data replication Managerial Round: After this round, I was called for Managerial round which I found quite easy and straightforward. The questions included: Explain views and their advantages. Provide a basic SQL query on views and discuss what would happen if we didn't use views. Explain the steps for data cleaning in your project. How would you remove duplicates in Excel and Python. Do you know about cloud computing? Would you be willing to work as an intern in that domain?
HR Round: Then, I was called for HR. Although, I don't remember every question, it didn't take much time to complete this round. How confident are you, and what is the reason for your confidence? Do you have any questions for me? Thirty students attended the HR round, and I was one of them. Although it has been more than two weeks since the interview, I haven't received results for our college yet. I am waiting with hope, as the HR round is also an elimination round. I hope this article will be helpful to you. Points to Note: Prepare thoroughly based on your resume and projects. If you do a project on Machine Learning, make sure to learn about all the important and basic models.
About This Question
This is a candidate experience report from a hp interview for a swe role (intern level) during the recruiter round reported in 2024.
It covers the following topics: Ml, Linked List, Heap, Matrix, Sql, Stack Queue, Queue, Arrays, Stack .
Difficulty rating: Easy
Topics
More Hp Interview Questions
About Hp Interview Reports
This question was reported by a candidate who interviewed at Hp. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Hp are the higher-signal extractions to take from this report.
For broader preparation context, the Hp interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Hp reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Hp Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Hp reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.