- Portfolio screening by recruitment personnel - Take home code assignment - Technical interview with EM, tech lead, and SE, which focuses on technical skill, design patterns, and best practices - Culture interview with Head of Engineer, CTO

My experience with Elmo during the interview process was a bit of a rollercoaster. The first stage with two leaders felt all over the place—random questions about tech stuff, behavioral scenarios, and my background thrown together without much structure. Then came the second round, which was just confusing and uncomfortable. They had me doing this pseudo code thing in React where I had to write out five tasks in a row without being able to run my code. The interviewers seemed like they didn't quite get React themselves—they kept questioning why I wrote things a certain way and wanted me to change stuff that I knew was right. Turns out, my original solutions were spot on, and theirs were way off base. So, when they gave me feedback saying I didn't understand React, I was pretty floored. It wasn't that I didn't get React; it's just they didn't get how React should actually work. The feedback was pretty arrogant and delivered in a bad manner. The whole process felt rushed and didn't really give me a fair shot to show what I know in a professional way. Not exactly the kind of company vibe I'd want to be a part of.