The first step was the recruiter screen, which included a fast 15 min coding problem. Then came coding rounds with engineers. The problems I received involved using dicts, recursion, arrays. For some reason I was given a lot of React problems. Maybe they saw I used to do a lot of UI and meant to make it easy, but I had been only practicing LC and system design since I'm interviewing with OpenAI. From Q&A it sounded like they did >= 80% frontend so it could be that interview panel.

I had a 45-minute interview scheduled with the recruiter. The first part of the conversation was mostly about my background, experience, and the role I was applying for. The recruiter asked about my previous projects, technical skills, and how my experience aligned with the position. Just when I thought we were wrapping up, they threw in a coding question at the end—definitely a curveball! It wasn’t something I was expecting in a recruiter screen, so it caught me a bit off guard. The problem itself wasn’t too complex but required some quick thinking.