I applied through a recruiter. The process took 3 weeks.

It probably just depends on what kind of an interview process you're comfortable with. There's no one size fits all, and if you're the person that has spent the last year memorizing and perfecting leetcode problems so you can breeze through the interview and make more money than your parents, you'll probably be disappointed. Yes, there is a tech screen, then a long (90 min) discussion with a hiring manager to just make sure that you have the background and core experience that will make you successful. If you can just buckle in and get that over with, you'll move on to the core interview process -- which I was thankful for, because I'm not a leetcode memorization person.

I actually enjoy having conversations around the entire development process, and instead of being thrown in to a room of 4-6 people asking random questions to try and see just how much you can recall about the fastest array sorting algorithm, the conversations are all simply around developing a very simple CRUD service. You have the opportunity to spend an hour or so throwing together a simple solution on your own, and then having a 60 min conversation with other engineers to talk about what you built, why you used certain designs, and what you would do differently given a few new constraints that you may or may not have thought about.

Then there's an architectural discussion -- do you understand cloud architecture? load balancing? caching? network latency? Can you defend an opinion on when you'd use caching for data, when not to, and what the trad-offs are if you feel that it's necessary? You'll probably do fine. Then there's a discussion with the product team, which -- I thought was great. It gives you the opportunity to hear a real world problem that needs solved, and talk through how you'd approach it. It gives you the opportunity to ask that team questions about their philosophies for product management.. do they understand technical debt, and are they accepting of dev time in sprints to manage it, or averse to it and only want to deliver new features?

Spend some time truly trying to understand their process and focus.. this is huge from an engineers perspective, and they give you the opportunity to go as deep as you want to make sure that you're going to work cohesively with the product team. There aren't too many companies that I've interviewed with that include this as an engineering interview round. For me, the entire process was very straight forward and transparent. The technical recruiter was there every step of the way, making sure you knew what was up next, and what the general expectations were.

I am not allowed to disclose this per NDA.