3 ms·
It's important to remember that it's also YOU interviewing THEM. The coding interview is an opportunity to get to know the company culture in a very feet-on-th
by kstenerud 5y ago
It's important to remember that it's also YOU interviewing THEM.
The coding interview is an opportunity to get to know the company culture in a very feet-on-the-ground fashion. How the interviewer behaves and how they expect you to do things reflects upon them as managers, mentors, and in general people you'll be working with for potentially a long time.
- If they're forcing you to go against your natural flow, that's a red flag.
- If they're preventing you from building or explaining things as you'd normally do on the job, that's a red flag.
- If they don't allow you to consult the resources you'd normally do, that's a red flag.
- If they prevent you from testing your work and assumptions as you'd normally do, that's a red flag.
- If they're only looking for work and no conversation (all questions to you and none to them), that's a red flag.
I've had times during an interview where I've had to pause everything and explain that this is how I work, and how I would work if I were hired. Usually the interviewer will stop, reassess, apologize and we move on no harm no foul. I've also had occasion to stop the interview and say that we're not going to be a good fit, sorry and goodbye.
It's on YOU, the interviewee, to make sure that you're not getting bullied or coerced (either accidentally or deliberately). This is not a one-way street. If you don't push back, at best you get hired into an abusive or incompetent environment, and at worst they reject you after toying with you, wasting even more of your time and sapping your morale. Yeah, it's a bad time when one hires a bad employee, but it's MUCH MUCH worse to get hired into a bad company! You're taking a bigger risk than they are, so make sure you interview them well!
Breaking off an interview is not a bad thing; you're assessing THEM as much as they are assessing you, and eliminating the deadwood early is in your best interests, because YOUR time and resources are precious too.
Remember: THEY can fail phone screens, too.
- drclau 5y ago> It's important to remember that it's also YOU interviewing THEM. I agree with what you said in the rest of the comment, but I'd like to go one step further with the idea of "YOU interviewing THEM". Let's add some symmetry! Let's make the interview double the usual time, and half of it I get to ask the other side to solve LC problems that I pick at random, or design systems I made up the day before, or behavioural questions about their past experiences. According to companies, that is the only way to assess if a person is good enough for the job, so I'd like to use the same method to find out if I want to work there.
- zcw100 5y agoI've always thought it would be fun do say, "Ok, this sounds like a fun game. It's only fair that if you get to ask me a question I get to ask you one." I'd be willing to bet 90% of the interviewers would crumble on the first question. I've noticed that most of the interviewers not only select their questions ahead of time but also have to do research so they are sure they know the answers too.
- notreallyserio 5y agoI hate interviewing but the very few opportunities I've had to have a technical discussion back-and-forth Q&A with a candidate have been helpful. A lot of candidates don't even ask about the day-to-day expectations or stack, and I think that's unfortunate for them.