The purpose of a job interview is two fold :
- Employer figures out if he wants you
- You figure out if you want to work with them
Many people forget about that 2nd point, but it is equally important. Now, to figure out if you want to work with them, you can ask questions. But you can also learn a lot from the interview process itself and how its conducted. You just have to pay attention to what is (not) said.
How are they conducting the interview process?
Openness about the interview process often match openness within the company as well. If they don’t share anything about what’s coming up, even if you ask them, I’d safely assume that asking questions once you’re employed will end up with the same non-answers. If they are happy to share, that’s a good sign. If they explain it all without you having to ask anything, it shows that they care about you and you’ll likely get the same openness and explanation about the business once you’re in.
Another aspect is if they actually follow up when / as they told. If they don’t or go silent, that’s not a good sign. They’re basically telegraphing that they only care about you when they want something from you.
Now, there are a lot of material now about building good interview process, so I think this signal is become less relevant as time goes. A lot of bad businesses have a great interview process. That said, I’ve never heard of a good business having a really bad interview process. So it is still good to filter out some bad place to work.
What are their questions topic?
Questions you’ll be asked generally falls in 3 buckets:
- Technical : coding, system design, architecture, algorithms, etc.
- Soft skills : emotional intelligence, behavioral, situational, etc.
- Product oriented : user experience, product’s purpose, domain knowledge, etc.
Those are all good questions, no doubt. What you’ll see is that the amount of questions in each of those buckets will differ between businesses (and even teams). Some interview process will be light on soft skills and product questions, but you’ll spend more time on technical stuff. Elsewhere you might get a smaller amount of technical questions, but lots on product. Obviously, this also depends on the role you’re interviewing for.
What is good to do is, for similar roles in different businesses, compare how many questions (or importance of those questions) were in each bucket. That way, you’ll see what’s more important for them. Why you’d care about this? You can infer a lot from that information.
If technical is top most, you might expect : - An engineering 1st culture, where engineering qualities of the product are more important than a user driven product development. - Team members are likely great individual contributor, but the whole team might not work well together. - Can be a good place to learn technical skills from top engineers.
If soft skills are top most instead, you can expect : - A people first culture, where employee happiness and well being is the most important thing, expecting that product and company success result from that. - Teams working well together, less conflicts, less politics at work - Can be a good place to learn leadership skills
If product is top most, you might expect : - A user 1st culture, with a user / market driven product development, where engineering is put to service of the user. Expect more refactoring, more iterations, shipping faster, etc. - Team members likely care about the users, but might not work well together depending on how strong beliefs about what’s best for the user are held. - Can be a good place to learn about product development, product market fit, etc.
Of course, we aren’t in a binary world, so you’ll get a mix of those questions, and from that you can rate that work place. But those are guesses; will be wrong for some places. Still, making an educated guess when you’re about to make important decisions is a really good idea.
Originally published on Medium