An interview is a meeting where a company asks questions to know about you, your skills, and your knowledge before giving a job.
At most of the top tech companies algorithm and coding problems form the largest component of the interview process.
You should do your best to talk out loud throughout the problem and explain your thought process.
At the end of the interview, the interviewer will walkaway with a gut feel for how you did, A numeric score
might be assigned to your performance, but it's not actually a quantitative assessment.
Do your personality and values fit with the company and team? Did
you communicate well with your interviewer.
The weighting of these areas will vary based on the question, interviewer, role, team, and company. In a
standard algorithm question, it might be almost entirely the first three of those.
Top comments (1)
The article's point about how subjective interview evaluations can be is spot-on, which is why practicing how you explain your thought process is important. Just doing well on LeetCode isn't enough. I've been using PracHub along with other platforms, especially for follow-up questions in technical rounds. Their question bank matches real interview scenarios better than the scattered info on Glassdoor. It's frustrating that so much depends on 'gut feel', but matching your solutions to the interviewer's expectations is a big part of the challenge.