The process started with an AI-based HR screening round, which was straightforward.
After that, HR informed me that the next round would be a machine coding interview scheduled after 2 days. However, just one day before, I received another call asking if I could attend the interview within the next 2 hours. Since I was interested in the opportunity, I agreed and joined on short notice.
Machine Coding Round
This round felt unusual because the machine coding interview was conducted only by HR, with no technical interviewer present. HR explained the problem statement, which was to build a small JavaScript-based game (similar to ping pong). I completed almost the entire task during the session, with only one minor part left, which I clearly communicated. I was then asked to push the code to GitHub and share the repository link, and HR said I would be updated.
What felt strange was that for a machine coding round, there was no technical person to evaluate the solution in real time, which made the process feel unclear.
Interview Setup
The virtual setup was also unusually strict. On Microsoft Teams, I had to:
Keep my laptop camera on
Share my screen
Place my mobile phone around 3 feet away with its camera on, so HR could monitor both me and my laptop
The interview only started once HR was satisfied with the setup. For a remote coding round, this felt excessive and uncomfortable.
Post-Interview Experience
The most disappointing part was after the interview. Despite completing the round and sharing the GitHub repository as asked, HR never came back with any update. I followed up multiple times, but there was no reply, no feedback, and no proper closure.
Overall Experience
The main issues were:
A machine coding round without any technical interviewer
An overly strict and uncomfortable monitoring setup
No professional communication after the interview
Overall, the process felt poorly managed and not respectful of the candidate’s time.
