#1 on that list is enthusiasm for the company. Really...? So, you gotta be a good bullsh!tter? I can see this for small startups, because passion will take you

#1 on that list is enthusiasm for the company. Really...? So, you gotta be a good bullsh!tter? I can see this for small startups, because passion will take you to places. But for large companies, their software products are so diverse. I work for a manufacturing company and my application space has nothing to do with manufacturing. Every space has their challenges and pitfalls. As long as you have good tech, good people, and aren't doing anything unethical, I'll want to work for you. Also, I've thought about the interviewing problem a bit. I don't do the interview for my team...but if I have the opportunity to interview and was given free range, I think I would create a small application using our tech stack. Put some bugs in there, put some bad practices, and let the interviewee fix it. Talk about the tech stack, how to scale it, design trade offs, etc. IMHO reading code and maintaining code is more important than knowing bfs and dfs by heart.