Enquero Interview Questions
& Process

The interview journey was really smooth from start to finish. Any questions I had were answered super quickly. Even though I was transitioning from a Software Development Engineer role with no prior Data Engineering experience, the process was manageable. There were three rounds in total: two technical interviews and one HR/salary discussion. The first technical round focused on core SQL and Python skills, with straightforward questions like three coding problems (involving recursion and hash maps), one SQL query, and basic Python concepts to gauge my understanding. The second technical round dug deeper into my foundational knowledge and experience, posing situation-based questions about everything on my resume, including Docker, Python, Flask, and Rest API. The final round was essentially a salary negotiation. Once T1 and T2 were cleared, the offer was pretty much guaranteed. It was a fantastic experience, and I felt comfortable throughout. They really emphasized overall capability rather than just a specific tech stack.

Had to go through my CV thoroughly, be sure to know your projects well. The process had three stages: first, a group discussion, which I passed. Then, a technical interview, which I also passed. Finally, an executive round with the regional head, but I didn't get selected. They really drill down on your CV and projects, and also asked about the job description, specifically what and why this role.

The whole process took place in a single day. It started with an online test that covered computer fundamentals and programming output questions. Next, there was a group discussion (GD) on the topic 'Effect of COVID in job search and recruitment'. This was followed by a face-to-face technical interview, which was like a rapid fire round; questions were mostly one-word or one-sentence answers. Then, a managerial round investigated my approach to problem-solving. I was given a problem like 'there are n inputs and need to return the sum of all the inputs, but the user will just give input without mentioning the number of inputs'. The interviewer wanted to see multiple approaches and was open to any ideas. Finally, the co-founder had a casual chat, like friends talking over tea, to understand my personality. Questions included my future plans, why I chose an M. Tech degree, and my reasons for selecting Computer Science. Results came out the next day, and I was selected.

A recruiter contacted me about an urgent opening, wanting to expedite the interview process. I agreed and scheduled it for the next day. During the interview, the interviewer was eating snacks, which I found unprofessional. They also came across as very knowledgeable. I answered all their questions and was upfront about areas where I lacked direct experience. The interviewer seemed interested and inquired about my hourly rate and visa status. I was then given a problem that the team had apparently struggled with for weeks, and asked to consider it for two days. I came up with a simple solution and resolved it within a few hours. Despite this, I never heard back. Upon reaching out, I was informed I wasn't selected.