FORESIGHT(2023): Summer Internship at Honeywell | Mihir Raj |
Introduction
Hey, I am Mihir Raj, a third-year undergraduate student from the Department of Mechanical Engineering pursuing a B.Tech course at IIT Kharagpur. I am from Ranchi, Jharkhand. I will be joining Honeywell as a software engineering intern from May‘23.
How did you get into Honeywell(SWE)? What was the selection procedure?
This role was open for all the pre-final students from all the departments. The screening test consisted of three coding questions with moderate difficulty levels. The test was conducted on the Hackerank platform.
Question 1: It was on Graph Traversal, where we were presented with an undirected graph with N nodes and M edges and had to calculate the Connected Sum of each component and finally come to the final answer.
Question 2: It was on Segment Tress, but O(n 2 ) approach passed all the test cases because of its weak nature. In this, we have given two arrays, one of which stores the indices of the items in the order they are placed in the queue, and the other stores the instantaneous position where the corresponding item is placed in the queue. It was mentioned that each time an item is inserted, all the following items are shifted toward the right by one position, and finally, we need need to find out the sequence of the item in the queue after all the items have been placed.
Question 3: It was based on a map and some operations of it; I do not remember it exactly :)
After the shortlisting based on CV and test, the next step involved a technical interview followed by an HR round. The technical round has some questions on sorting algorithms (as my project was a sorting visualizer), a couple of short coding questions followed by some basics on the OOPs concepts, and a brief discussion on all the projects I had mentioned in my CV and finally discussed all the technical expertise mentioned in my CV. The last round was the HR round, where standard HR questions like past experiences, what difference you can make if selected,
and how you are a team player. HR would be particularly interested in extracurricular activities, your ability to express yourself, and, most significantly, whether or not you share the company’s values. Going through the firm’s page and checking out the current working domain of the organization is highly recommended for the HR round, as HR would want you to have some understanding of the company to which you are applying. Examine the company’s values as
well.
How to prepare for them?
To prepare specifically for Honeywell, you should have an excellent grasp of Data Structures and Algorithms. There will be medium questions on the test, so clear all of the principles of conventional DSA, and concentrate more on Dynamic programming and graphs, as these topics are included in practically every company’s test. In terms of coding examinations, you should solve questions for at least two months to gain a firm grasp. You could practice questions on sites such as Leetcode, InterviewBit, and GFG because the questions will be pretty similar. I personally used the AlgoZenith platform and InterviewBit mostly to solve the question.
You should be familiar with the projects listed on your interview CV. Maintain your composure and avoid panicking throughout the interview. Never code in an interview as if you know everything about the problem; instead, try to interact with the interviewer, ask questions, and if you don’t have any, tell him what you’re doing to solve the problem and why you’re doing it; only then will the interviewer be interested in you; ask for hints if you’re stuck anywhere; the interviewer is there to help you; they just want to check your thought process. To prepare for the behavioral questions in the HR round, you should be familiar with the STAR (situation, task, action, and result) technique and look over the company’s Leadership principles.
What difficulties did you face while preparing for this Company/Profile? How did you overcome this problem?
The most challenging issue I encountered was thinking about the question with its optimal response in a certain period during the screening exam while under pressure to do better than others. To overcome this, you can give mock tests before the CDC test begins. Technical interviews are not the same as competitive programming. In interviews, you must gradually work
your way up to the most effective answer while being unaware of the limits. However, the limits determine the entire approach and mentality in a programming competition. Being a CP man might cause some issues during interviews. Occasionally not directly looking at the limitations
should be sufficient to circumvent this difficulty.
While studying for CDC, you may suffer rejections in coding exams, mainly due to CGPA on Day 1 or Day 2. During this time, you must be psychologically intense and trust in yourself.
According to you, who should ideally apply for this job?
Anyone interested in developing software, coding, or handling extensive data, in general, can apply for this role. Honeywell provides various tech stacks and projects for interns, including DevOps, Machine Learning, Web apps, MicroServices, Databases, and more. You might be able to work on these cutting-edge technologies. Anyone interested in these positions is
welcome to apply; Honeywell had no department or CG criteria at our time, and the work-life balance will become apparent after I begin my internship on the 22nd of May.
What are some of the major points you think would be valid to mention in your CV while targeting this profile? (any specific suggestions you would like to make?)
Write down all of your projects/internships and show them adequately in your CV, as this is a crucial component of any interview. The project can be self-directed or directed by a professor. Highlight all of your accomplishments in the Academic Achievements section. Enter your handle ratings from sites such as Codeforces and CodeChef. Mention your rank if you participated in Google Code Jam, Kickstart, or Facebook Hacker Cup. Put open source contributions, if any.
Finally, avoid getting caught up in the number games of Day 1, 2, and so on.
Any specific advice you want to give to the junta sitting for internships this year. During the interview, always think out loud. Never try to lie on your CV, and be prepared to answer inquiries regarding projects you stated on it. Follow your heart and only apply for roles in which you are interested. Only apply for some jobs that come your way in the first few days. It’s
preferable to receive an internship in a role you’re interested in on Day 2, 3, or even later than to settle for a Day 1 internship wholly unrelated to your field of interest. Determine which roles you want to pursue and prepare appropriately. Make in touch with others who are planning for the
same event. Discuss worries and doubts with them. Always read the editorials after you’ve solved an issue. It aids in the investigation of improved coding styles and other ways. Align your CVs with the positions you’ll be applying for and have them checked by 2–3 seniors. The coding
tests are hectic, so get proper rest during break time. Maintain your enthusiasm on the interview day, and keep going if your friends get internships on Day 1 or Day 2. Don’t worry too much about CDC internships. The CDC does not spell the end of the world. There are other
alternatives available, including off-campus or research internships outside of the CDC.
Best Wishes, and All the Best!!
