HR interview questions
Common HCL HR questions, sample answer frames, and STAR tips.
HCL Interview Experiences
How HCL fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
HCL placement process includes: 1. Online Assessment (90 minutes) - Aptitude, Technical, and Coding sections, 2. Technical Interview (45 minutes) - Programming problems, technical concepts, project discussion, 3. HR Interview (30 minutes) - General discussion, compensation, role expectations. Total duration: Approximately 2-3 weeks from application to offer.
Eligibility (from student reports): 6.0+ CGPA in 10th, 12th, and graduation.
Fresher package ballpark (from student reports): ₹4-4.5 LPA. Confirm on your offer letter.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 90-120 min | Aptitude + coding |
| Technical Interview | 30-45 min | OOPs, SQL, DSA basics, projects |
| HR Interview | 20-30 min | Relocation, shifts, motivation |
Real interview experiences
Section titled “Real interview experiences”Experience 1: Graduate Engineer Trainee, on-campus (2024)
Section titled “Experience 1: Graduate Engineer Trainee, on-campus (2024)”Source: GeeksforGeeks write-up - five stages
Aptitude test (about 2 hours)
- Numerical reasoning and logical problem-solving across several sections.
Group discussion (15 min)
- Topic: should cell phones be allowed in school? The group never reached a conclusion and the candidate still advanced - reaching consensus is not the bar.
Technical interview
- Self-introduction, then projects, including one that was not on the resume.
- Language basics off the resume: what the hashtag symbol is used for in Python, what pip is.
- A general discussion on cloud technologies in the market.
HR round 1
- Background and family, plus an opinion question on women’s empowerment.
HR round 2
- Document verification: school and graduation marksheets, resume check, hobbies and interests.
Result: Rejected. An active backlog in semester 6 disqualified the candidate despite positive feedback in every round.
What to take from it: HCL’s academic gate is enforced late, at document verification. Clear backlogs before the drive and carry several hard copies of every marksheet.
Experience 2: Graduate Engineer Trainee, on-campus full-time
Section titled “Experience 2: Graduate Engineer Trainee, on-campus full-time”Source: GeeksforGeeks write-up
Online assessment (75 questions, 90 min)
- Coding exercises plus technical MCQs across DBMS, OOPs, computer networks, software testing and OS.
- Logical, verbal, quantitative, and analytical / critical reasoning sections.
HR screening
- Document verification against a 70% academic criterion, held before the technical interview.
Technical interview
- Resume-driven JavaScript and React: string interpolation, rest vs spread, arrow functions, the Virtual DOM, hoisting, IIFEs, promises and callbacks.
- Then fundamentals: the pillars of OOPs and database normalisation.
HR interview
- A situational conflict-resolution question, willingness to relocate anywhere in India, and a personal achievement.
Result: A document-verification request arrived three days after the final round.
Takeaway: HCL interviews the stack listed on your resume. If you put React on it, expect Virtual DOM and hoisting; if you keep it plain, expect OOPs, DBMS and OS drawn straight from the assessment syllabus.
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Palindrome / reverse a linked list. Usually expects two pointers
- Character frequency in a string. Usually expects hashmap
- SQL: max salary per department. Usually expects GROUP BY / joins
- Discussion on OOPs and SQL, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why this company?
- Night shifts / relocation
- Bond (if mentioned in the college placement email)
- Where you see yourself in a few years
Practical tips for HCL
Section titled “Practical tips for HCL”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain OOPs in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of HCL panels. Do not skip fundamentals.
- HR answers should be concrete. One story with a result beats five slogans.
- If you do not know something, say so and outline how you would find out.
HR interview
Section titled “HR interview”After technical rounds, HCL usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.