Embedded C Developer 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 60.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Embedded C Developer roles take an average of 1 day to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at HCLTech overall takes an average of 17 days.
Common stages of the interview process at HCLTech as a Embedded C Developer according to 1 Glassdoor interviews include:
Skills test: 50%
IQ intelligence test: 50%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at HCLTech (New Delhi) in Jan 2019
Interview
2 levels of interview telephonic discussion and a video interview .first round was only on basics of c and second round dwell in to device drivers ,kernel programming ,linux internals
I applied online. I interviewed at HCLTech (Chennai) in Jan 2019
Interview
Process tooks 1 day, first round would be the online exam and second round would be the technical, if we are prepared well for interview then it will be easy
Interview questions [1]
Question 1
pointers concepts like dangling pointer, linked list etc
I applied through a recruiter. The process took 1 day. I interviewed at HCLTech (Bengaluru) in Mar 2018
Interview
Two technical rounds and one HR round. Interview process was too worst they took a lot time to complete first round nearly 1PM for only half members for remaining people they complete by 5PM. After that they take second round interview.
Interview questions [1]
Question 1
They asked about pointers,
storage classes,
diff between char array and char string,
which compiler u r using,
memory segments, malloc, calloc,
bit manipulations,
which controller u used, what processor used in that controller , which architecture it is,
watchdog timer, what is volatile,
type cast, how to cast int to char,
void pointer and why we use it
what is stack why we use that
rs232,rs485
functionpointers, array of function pointers
which debugger u used
linked list