HCL logo

HCL Java Developer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 34 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
64.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at HCL.

Showing 3 of 34
HCL logo
HCL

Java Developer

Engineering · a year ago

Entry Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Technical Coding

I applied via naukri and got a call from HR. I mentioned my internship experience. The first round was coding and I passed. They called me for a second round on another day. Upon arrival, they changed the requirement completely, looking for candidates with industrial experience. They also called me after the first round and gave me a call letter. It's disappointing that they didn't mention the need for experience earlier. I feel like I wasted my money, time, and energy. Worst management. Some people also received calls saying it was a walk-in. HCL HR might assume everyone has free time. Worst company.

Confirmed questions2 questions
  • Questions were asked regarding Java and SQL.
  • What are the basic requirements needed for a Java developer role, specifically for backend development?
HCL logo
HCL

Senior Java Developer

Engineering · more than a year ago

Senior Average Neutral experience Decline offer 3 rounds
Interview process
Technical screen Phone screen Recruiter call
Interview formats
Technical Behavioral

The interview process was good and ran smoothly. It started with a 1-hour first round covering basic Java 8, Spring Boot, and AWS. Following that was a second round, about 30 minutes long, focusing more on project management and the technology stacks I've used. Finally, there was an HR round where they seemed keen on reducing the offered salary, making compensation a significant point of discussion.

Confirmed questions5 questions
  • Can you explain Java Stream API?
  • What are Functional Interfaces in Java?
  • Could you write some SQL queries?
HCL logo
HCL

Java Developer

Engineering

Entry Average Positive experience Accept offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Technical Behavioral

I went through 2 interview rounds. The first was technical, focusing on core Java, multithreading, Spring, and Hibernate. They asked about the difference between HashMap and HashSet, thread pools, SQL statements, Spring MVC, and web services like SOAP and REST. The second round was with the manager, where we discussed my past projects and some behavioral questions. The overall interview felt easy.

Confirmed questions8 questions
  • Can you tell me about your previous projects and experience?
  • What's the difference between a hash map and a hash set?
  • Explain what a thread pool is.

HCL Java Developer Interview Questions

Quoted word for word from HCL interview reports.

When comparing strings initialized as String s1 = "XY"; and String s2 = new String("XY");, what's the difference in their initialization?

Read reports

What is the outcome if a thread's priority is set to zero?

Read reports

Now, if we set s2 = s2;, what would be the outcome of s1 == s2?

Read reports

Write a program to rearrange the numbers in the array [1,2,3,6,-1,10,5,-10,88] into [-1, 1, 2,3,5,6,-10, 10,88].

Read reports

What is the distinction between a 'tag' and the 'trunk' in SVN?

Read report

How would you invoke a REST web service from a plain Java class without using Spring or JAX-RS?

Read report

Beyond the limitation of not being able to extend other classes, what are the benefits of implementing Runnable compared to extending Thread?

Read report

What is the advantage of using jQuery when plain JavaScript can achieve the same functionality?

Read report

How would you write a program to reverse a string without utilizing any built-in methods?

Read report

Formats, difficulty and experience

Across all 34 HCL interview reports.

Interview formats

Technical 50%
Behavioral 24.4%
Coding 23.1%
Group 1.3%
System Design 1.3%

Interview difficulty

Easy 29.4%
Average 55.9%
Difficult 14.7%

Candidate experience

Neutral 11.8%
Positive 64.7%
Negative 23.5%