Went through whole process. Clarified role was remote since first phone call with recruiter. After on-sites they said "crushed interviews but we don't want to do remote, want to move to SF?". Said no, they said they'd get back to me, never heard from again.
Overall seemed inconsiderate and childish.
Interview questions [1]
Question 1
Debug round then virtual on-sites with coding round, behavioral round, architecture round.
I applied online. The process took 2 weeks. I interviewed at Metronome (CA) in Feb 2025
Interview
1. Recruiter Call
2. Manager Call
3. Live Debugging in your personal environment
4. Onsite ((coding, sys design, behavioral, head of engineering meeting)
I didn't make it past the debugging round although I fixed a bug, identified another and communicated my thought process well. I'm not sure what the bar is. Identifying a bug in unfamiliar code in a limited timeframe is a little difficult.
Interview questions [1]
Question 1
Debug some convoluted file. I was encouraged to only rely on print statements.
I applied through an employee referral. The process took 4 weeks. I interviewed at Metronome (CA) in Apr 2024
Interview
4 Steps Process. Speak to recruiter, then the hiring manager, a take home assignment, present that to the HM, and then may be one or two more rounds.
The take home assignment round and readout is where it got tricky. There is no specific evaluation metric and only the HM knew what he was looking for during the readout.
The recruiter is nice enough to keep you updated about the process in a timely manner, but rejection emails are understandably kept very generic i.e., no specific reason for rejection is given.
My recommendation is to be a bit more familiar with ERP systems if you are applying for this role. There is a severe knowledge gap with how ERP systems work. Their product itself is intuitive and very easy.