Sr Consultant applicants have rated the interview process at HCLTech with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 100% positive. This is according to Glassdoor user ratings.
Candidates applying for Sr Consultant roles take an average of 2 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at HCLTech overall takes an average of 15 days.
Common stages of the interview process at HCLTech as a Sr Consultant according to 1 Glassdoor interviews include:
Other: 50%
Phone interview: 50%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at HCLTech (Calgary, AB) in Jun 2026
Interview
Telephonic around
Video Conferencing Interview - Round 1
Video Conferencing Interview - Round 2
The round 2 never happened. HR called to confirm the dates but never responded back. They kind of ghosted me. I tried following up but no response.
2 tech round both are basic js and react base question.
que 1 - reverse the string(in-place) and make first char of every word capital.
Que 2 find the duplicate values in the array
Interview questions [1]
Question 1
Reverse the string(in-place) and make first char of every word capital.
I applied through a recruiter. I interviewed at HCLTech (Noida) in Apr 2022
Interview
Technical Round 1: Core Configuration & Platform Knowledge
This round evaluates your understanding of the Salesforce ecosystem and the "Consultant" mindset.
Technical Round 2: Architecture & Hands-on Coding
This round often involves more advanced architectural concepts and may include a coding component or a case study.
Managerial Round: Leadership & Project Governance
The final round with a hiring manager focuses on your ability to lead a team and manage client expectations.
Interview questions [1]
Question 1
A client needs to sync approximately 1 million records from an external ERP to Salesforce daily. However, they are frequently hitting Apex Governor Limits during this process. How would you redesign this integration to ensure it is robust and scalable?