Loading Question...
Platform : HackerEarth Eligibility: CE and CSE (For the 2025 passout batch, EXTC was also eligible, so for 2027, anything could happen.) There was a 7.5+ CGPA criteria to apply. (Just telling in case you don’t know — the college considers CGPA of only 5 semesters till the 6th sem result is out. In our case, from August 8th, they began considering the 6th semester CGPA as well) There were 21 technical MCQs and 50 mins were given, but 15–20 mins were more than enough to complete everything. Since there was a lot of time, I noted down a few points and some less-known theory questions:
Last updated Oct 29, 2026
As I mentioned, don’t be afraid after reading "Machine Coding Round." It’s just a problem statement, and you need to provide a solution. BrowserStack has been using the same problem statement for the last 3-4 years. The problem involves implementing Socket.IO for real-time updates, so make sure you’re comfortable with it. We were called to BrowserStack’s office in Goregaon for the machine coding round and interview. HR called every selected candidate 2 days before the interview to invite us to their Goregaon office. On the call, she mentioned there would be 2 rounds: machine coding and then an interview. She also said the machine coding problem statement requires knowledge of Socket.IO and suggested practicing for the machine coding round. Candidates were divided into batches, with 5 candidates per batch and one mentor per batch. On the same day, there were candidates from other colleges too. I think there were about 12 batches in total. I was in Batch 1 with 5 candidates, all from our college. The other 2 candidates from our college were in Batch 2 with 3 candidates from a different college. Instructions Provided to Us: What to bring: ● Personal laptop ● Hard copy of resume ● Government-issued photo ID Ensure the following setup on your laptop before the interview: ● Compiler/interpreter of your preferred programming language ● IDE/code editor of your choice ● Root/admin access to the system ● Latest version of Chrome, Firefox, Safari, or Edge We were allowed to use our personal laptops, and Google and GPT were permitted.
The interviewer was the Director of Engineering. He kicked things off by introducing himself and then asked about my CET, SSC, and HSC scores, and why I chose SPIT. After that, he asked me to give a quick introduction about myself. Then, he asked about my internship experience, specifically what I did during it and what kind of work I handled. I shared details about my role, the tasks I contributed to, and the impact I made, like leading development or solving specific challenges. Once I was done, he explained the interview flow: first, we’d dive into my projects, and then he’d test my problem-solving skills. He started with, “Tell me about a project where you faced a lot of difficulties and challenges.” So, I began explaining one of my projects, and while I was talking, he jumped in with questions. He asked about specific situations where I hit technical roadblocks, how I resolved them, and how I tackled things overall. Then came the “why” questions: ● Why did I pick Next.js over React.js for my project? (I used Next.js, so I explained my reasoning—stuff like server-side rendering and better SEO.) ● Why SQL over NoSQL? Then, in SQL, why PostgreSQL over MySQL? What was the reason behind these choices? ● What if I had used a NoSQL database for the same project? How would it have impacted things? After the “why” questions, he dug deeper into scaling and deployment: ● How would I scale up my existing project? ● What factors did I consider when deploying my project? ● How was I monitoring things post-deployment, and why did I choose Vercel for deployment? ● Since I used NeonDB (PostgreSQL), what features did NeonDB provide that helped throughout my project? After the project discussion, we moved to a DSA question: Daily Temperatures. It’s a classic Monotonic Stack problem. He asked me to write proper code on paper and do a dry run with the example he gave. I walked through the solution, explaining the stack logic and how it tracks indices to compute the result.
Tips: I’m not listing everything you already know—just focusing on some less commonly discussed topics : ● OOPS: Study on GeeksforGeeks (GFG) Best Resource for OOPS. ● Puzzles: Practice GFG’s Top 100 Puzzles. ● Must-Study Topics: