Recently had a chance to interview at a pretty mature startup(moengage), a recruiter called me up, we set up a time and date for a machine coding round. I was pretty excited to be honest and looking forward to the interview. Fast forward to the day of reckoning , I join the interview with my intellij set up, my pen and paper to draw the ERD ready and my mind full of design patterns, only to be confronted with two DS & Algo questions(i legit gave up the moment i heard ds), the questions were interesting and the interviewer chill but it blindsided me by a whole lot and I couldn’t solve anything. It’s pretty weird that startups with so many resources at their disposal could be so out of sync internally.
Had the same experience with a startup.
Good thing about the interview?
Made me realise, dont assume anything based on interviews round name. Simply study all the concepts sd(lld+hld+machine), dsa, core subject no matter the interview round. I have legit studied these things for hr round as well😂
Am I dumb? Sure, but with so little opportunities at hand, I dont want to leave any stone unturned
Had a weird job interview experience a few days ago, for a pretty senior-ish PM position. This was the first round interview with the team after a basic recruiter round.
Hiring manager joins the call on his phone with camera off. Sure n...
I’m not a big fan of 6 rounds of Dynamic programming, but, should easy interviews be viewed as red flags? I recently landed an offer from a startup ( <50 employees ). They had only 1 tech round ( API development assignment ). Rest was ta...
During a recent interview at a Pune-based startup, I encountered a problem statement that involved a rather uncommon custom data structure.
The problem, summarized on one page with about 150 words, took me around 10 minutes to fully c...
