Interviewing as a developer nowadays is at the same time pretty exciting — technology is playing a crucial and exciting role in our cultures and societies — and harrowing — tech companies are engaged in what I’ve often heard described as a “talent arms race.” As a result, there are quite a few posts, talks, books, &c. about how to crack/solve/pass the coding interview. This post isn’t about the whiteboard or problem-solving end of things, where the company is evaluating you, but rather about the part where you get to evaluate the company.