Talked with a catty sounding guy on the phone who didn't really seem very interested in me or my background. No technical questions. Initial salary offering was less than what I was making. Got a rejection letter not too much later. I wouldn't bother with these guys.

- Interview consisted of three steps: technical, behavioral (with technical topics), and a technical/behavioral back-to-back interview. - Lots of other comments about recruiter T. I do not agree with them, but can see why they were perceived as "uninterested" or "catty." I think T has to go through a ton of content, screening, and candidates, but I did not feel a lack of professionalism. Just be ready to talk about your capability to do the work as a backend developer (for me this was a backend interview). - It's a straightforward process, pretty efficient, and everyone was friendly and professional. - The only thing I really take issue with is the difference in difficulty between the first and second technical. The difficulty of the second interview was orders of magnitude more difficult than the first. Out of several dozen technicals I've had in the 12 years I've been doing them, I think this was my worst performance. You will need to do at least several hours of review / prep if you are a middle-of-the-road developer or perform poorly under strong pressure, even if you work with Django every day. I did not have the luxury of prep material and can't guarantee that the interview format doesn't change, but hopefully you can learn from my failures (see question section below). I mark this interview as difficult, HOWEVER, this is not going to be the case if you are a gifted developer or work a ton with non-trivial queries in Django every day. I don't know why I felt that this was more difficult than my two FAANG/MANGA interviews several years ago, but I attribute it to the fact I had no way to prep for this and I did for those.