EQ Technologic Interview Experience

In this particular blog, I am going to share my interview Experience with EQ Technologic. It was in mid — June when I received a mail from the recruiter for the Software Developer Role, University Graduate (2022).

Day 1: Online Assessment

I received a mail regarding the aptitude and coding round. The exam is divided into 2 sections.

Section 1: Aptitude

Consists of 14 questions of Logical Reasoning. The total duration of this section was 14 minutes and I was able to attempt 11–12 questions. The level of Question varies from Easy to Medium.

Section 2: Coding

Consist of 2 questions of Data structure & Algorithms. The total duration of this section was 60 minutes. The level of Question varies from Cakewalk to Simple, took me 15 mins to code both the questions.

Day 2:

Round 1: TPS-1 (Technical Phone Screen-1)

The interview was taken by one of the software developer of EQ Technologic. The interview started with a normal introduction about myself later, he asked me to share my screen and share my resume.

He questioned about the college projects, explanation of two projects with demonstration, and codebase took around 30 min.

Project 1:- Chatistics (website)

Project 2:- Attendance-Tracker (website)

I explained the projects with the following points:-

1. Project Introduction
2. Modules descripsation
3. Advantages and main functionality
4. Tools, technologies and Platform used
5. Personal contribution to the project.
6. Challenges in the project.
7. Numer of people in the project.
8. Duration of Project
9. Improvements in the future for the present system.
10. Drawbacks.

After that, the interviewer questioned me on OOPs, DSA and syntax. For the oops I had to explain the concepts with real-world examples. In the last, I was asked to design a portal for creating a web application. I had no prior idea about system design. The interviewer helped me a lot by continuously motivating me and giving me hints.

The interview duration for this round was about 1.5 hours.

Mistakes

• Hadn’t studied System Design and System Architecture.

Round 2: (Technical Phone Screen-2)

The interview was taken by one of the software developer lead of EQ Technologic. The interview started with a basic introduction just like the last round. The interviewer asked me about time complexity, space complexity, Array manipulation, Linked List operation, trees, graph and algorithms.

The level of question is from Easy-Medium to Hard. the interviewer is more interested in how well you are explaining your approach rather than the code of that particular algorithm.

In the next part of the interview, the interviewer asked me about the OOPs concept. The interviewer started with the basic questions after sometimes he gave me some situational problem in OOPs which are tricky and required some time to think and solve, interviewer sometimes also asked to write syntax/code for some problems. The level of question is from Easy to Medium-Hard.

The last part of the interview was about database and SQL. The first few questions were about basic definition like primary key, foreign key and normalisation stuff. After sometimes, the interviewer asked me some situational questions and based on my approach, I have to write down the SQL query. The level of question is from Medium to Hard.

The last question was based on string manipulation using a pointer. It took me around 10 minutes to write the code.

In the last, I asked some questions like how is your life at EQ Technologic? and some basic question about the nature of work. The interview duration for this round is about 1 hour and 45 minutes.

Mistakes

• Nervousness: I got nervous when the interviewer asked me that are you sure about your statement? the interviewer wanted to check how confident I was in a particular response.
• Think and Response: In some questions, I directly gave my answer and they were not that accurate. I should have taken some time to think of my approach and then must have given an accurate answer.
• Understanding Problem: In some questions, I wasn’t clear what was asked in the question. I should have asked the interviewer to explain the question again.
• Be Honest: In some questions, I didn’t know the answer but still attempted the question. I should have directly said that I don’t know about this topic. (In some cases, the interviewer might give you some hints for that question, only answer those question in which you are confident)

Day 3:

Round 3: (Behavioral + Technical Phone Screen-3)

This was the last round of the interview. This was an HR + coding round. It mainly consisted of common HR questions like introduction, hobbies, and questions about my lifestyle.

Tips:

• Be Honest
• Be Confident
• Be Positive

In the last part, I had to solve a question in under 45 minutes. I was told to write the code on a notepad and was warned not to use IDE. It took me around 35 minutes to find the logic and edge cases for the problem. The level of the question was medium-hard.

The interview duration for this round is about 1 hour and 20 minutes.

Preparation strategy

• Mock Interviews: Do as many mock interviews as you can. It will help you manage time well and increase your confidence level. Some sites where you can practice mock interviews are — Gainlo, InterviewBit or Pramp.
• Coding Aptitude: You should identify your strong and weak areas and then work hard on your weak areas. If you just want to practice questions, you can try BinarySearch (a personal favourite), Leetcode or InterviewBit.

• Aptitude: Start doing aptitude for at least 1 hour daily. If you just want to practice questions, indiabix.

Advises

• Don’t cram a concept: Cramming something will help you solve only a particular question but if you understand the concept, you can solve plenty of questions.
• Participate in Contests: It will help you improve your problem-solving skills, speed and accuracy. CodeForces and Leetcode contests are recommended.
• Think out loud: The interviewer needs to know your thought process throughout the interview. So make sure you speak or write everything you think.
• Practice on Google Doc: In interviews, you won’t be allowed to use your favourite IDE. So practice coding on a Google Doc and try to explain your thought process by writing it down.
• Maintain a good LinkedIn profile: A good LinkedIn profile attracts recruiters which may help you get an interview. Otherwise, you’ll have to find referrals before applying.
• Have confidence in yourselves: Always have faith in yourself and give your best during those 1 hours.

All the best everyone! ❤

Let’s connect on LinkedIn.