It was really interesting and one of my favorite interview process. You have an initial phone screen to find out if going fwd is mutually beneficial. You are given a take-home project that tests you on proper abstraction, a little bit of algorithms,
I had a recruiter screen, which was short and easy. Following this, I had a technical screen. The technical screen interviewer was nice, but I felt they asked a pretty difficult question for an initial phone screen. Anything goes for onsite, but a
Waste of time. An introductory recruiter call, which was normal, was followed by a one-hour tech screen. It involved a LeetCode hard recursion question that I answered correctly, but I was still rejected. I didn't need hints, but the interviewer kep
It was really interesting and one of my favorite interview process. You have an initial phone screen to find out if going fwd is mutually beneficial. You are given a take-home project that tests you on proper abstraction, a little bit of algorithms,
I had a recruiter screen, which was short and easy. Following this, I had a technical screen. The technical screen interviewer was nice, but I felt they asked a pretty difficult question for an initial phone screen. Anything goes for onsite, but a
Waste of time. An introductory recruiter call, which was normal, was followed by a one-hour tech screen. It involved a LeetCode hard recursion question that I answered correctly, but I was still rejected. I didn't need hints, but the interviewer kep