Honeywell Tech Lead interview questions

Honeywell is doing alpha testing for its interview process in Bangalore. Luckily I also subscribed to their test version on one of the weekend. Here goes my comments on the entire process: 1 Online test: There will be an online Multi choice + Programming(coding) test which I guess needs to be completed to appear for the next round. The test was having around 22 questions. Questions were included from both C and C++. Most of them were based on pointers, time complexity of various data structures and lastly few C++ programs and queries which were not part of my skill set. Recruiter told me that I have cleared the test after 3 days of completing it. 2. Hackathon: This is the main part of the their entire recruitment testing. On a scheduled day aspirants were assembled first in a room inside honeywell campus. The crowd contained aspirants from all the different technologies for various openings. After showing a 2 minute video clip on Honeywell recruiter described the process: i.. Their will be a problem statement given which according to them will be specific to either automation, embedded or mobile application and related technology fields. For me it was falling under embedded domain. ii. 2 Teams were created among the aspirants consisting of 5-6 member each. As this was a recruitment process test, recruiters were not really worried about how and on what basis the teams should be created. As per their best judgment, people sitting on the left side will be one team and people on the other will be second. iii. Around 2-3 hours time was given to attack the problem. Hardware and few laptops were also provided but laptop chargers were fewer than the number of laptops. As this was only a test process, hardware provided ( in our case it was raspberry board) was not really verified beforehand to be working properly and can be used for the project. They were not working readily and recruiters told to start on whatever is available. iv. According to the recruiters there will be constant evaluation happening between the time given for the project but I didn't find any of them were really interested in the evaluation. v. In the afternoon around 3:30pm recruiters told us to stop the work and be ready for the presentation. vi As it was a test process, recruiters told us to join the presentation given by the test automation aspirants. We were also free to ask question after the presentation given by the automation aspirants. Since it was not really a hiring process, none of them were really interested in what the aspirants from our domain had really worked. vii After 1-2 hours of the automation presentation, recruiters were kind of tired with the day's process so they were not really interested in our presentaion. One of them just asked what we have done. As they were running out of time it took around 5 minutes for him to evaluate the entire team of 6 people and provided the results to his superiors. viii After that it was end of the process for us and we were asked to leave and told to be contacted later for further process.

The interview was a new process that was being tried to find suitable candidates. The first round was an online test of 30 questions, with 2 of them for writing code while the rest of them were for objective answers of various topics. This was followed by one day onsite hackathon kind of event where they asked candidates to form groups and implement/create an application for a given problem. This was followed by two discussion rounds, one each with a senior manager and HR lead.