That’s a pain, but not uncommon. I’ve heard of big, good companies that do this in some cases. Could be one person was unsure about your performance, or they’re

That’s a pain, but not uncommon. I’ve heard of big, good companies that do this in some cases. Could be one person was unsure about your performance, or they’re deciding between two levels for you, or even that the person that did your coding interview got fired and didn’t leave notes. I really wouldn’t overindex on it. Others are saying it’s a bad sign about their internal procedures and culture which, sure yeah it’s not an ideal way to run an interview process. But that might just mean that the HM did it in a previous job and it worked out well, or the recruiting head thinks it’s a good idea, and everything else is fine about the company. For the sake of an hour of your time and some extra interview practice- just do the interview. If you want, use this thread to guide your questions after you get an offer and figure out whether there are other signs of internal dysfunction. But turning down a job you want because of this one blip in the interview process would strike me as petulant.