Phone screen round - 45 min technical, 30 min behavioral. Technical was broken up into 15 min data modeling, 15 min python, 15 min SQL. Contrary to some advice I've seen, my interviewer didn't want me to talk through my approach or think out loud while coding -- just wanted me to jump straight into coding. Was also able to run the code and make sure it works before moving on to next problem.

In the emails back and forth prior to my on-site interview, I usually only got a response from recruiting when I would follow up with them again (after a first response). My recruiter didn't show up to my phone call with them. Once I got to the on-site, my interview block was supposed to be 10:15-2:15 with a short lunch somewhere in the middle. On the morning of, the schedule got changed, so that it was a short coffee break early in the block, so I ended up not being able to get lunch (since they walk you out after the interview) until I got to the airport. This wouldn't have been a problem had I known about it ahead of time, but having it change on the day wasn't good. The best part though was that the hiring manager just straight up didn't show up for his interview with me and didn't (apparently) communicate anything to the recruiting team about it. I texted the recruiter about the absence, and didn't hear from them either. They really didn't have their act together. All of the tech phone screen and tech on-site interviews felt rushed. Maybe that was by design to put the candidate under time pressure, but especially with the data modeling question, the time crunch forced the design to be overly simplistic, make a lot of assumptions, and ignore a lot of really obvious use cases that the solution wouldn't work for. I felt like it does a disservice to people who are actually thoughtful about what they build and want to build things that last.