Tech Interview Processes

Are you me?! I have almost the exact same story and feel the same way. One thing that particularly annoys me is how interviews at a lot of places have devolved into 4 interviews and around the 3rd you talk to some smug engineer that expects you to have memorized pedantic things about programming languages. I’ve worked in senior level positions for years doing very high quality work but I still google a lot of stuff and it just makes no sense to me why they do this instead of evaluating applied

Big tech companies get so many applications that they struggle to find interviewers. Hence, it's pretty common to get random engineers from random teams to interview random candidates. This is a burden for most engineers that need to focus on their work instead of interviewing people several times a week. Do you think these engineers care about getting to know you or asking fair questions? For many of them, having a script is much easier.

Nowadays I am on the other part of the fence, I am the interviewer. We are not a FAANG, so we just use a SANE interview process. Single interview, we ask the candidate about his CV and what his expectations are, what are his competences and we ask him to show us some code he has written. That's all. The process is fast and extremely effective. You can discriminate week candidates in minutes.

Per this person's experience (which seems sadly far from atypical), you might as well be:https://www.benjamistan.tech/2022/06/26/wasting-time-in-tech...

Not everywhere. Most places I've interviewed for had a recruiter and an actual team member; after the recruiter ticks their checkboxes for "moves Mt.Fuji" and "can tell a RB tree from a hole in the ground", someone who actually works with the code takes over with domain-specific questions. (Yes, I'm aware this wouldn't scale for an organization that hires by the thousands)

I worked at a company where we split the interview up. 5 interviews (including HR screen). The 3 tech screens were just that - tech screens. You didn't go over the work history or work in a team. It was three 45 minute sessions with a developer where you were given leetcode questions to complete in the 45 minutes. Nothing else.I was asked to do one for another team and during the meeting where we discussed if the prospective hire would get hired I got in trouble because I didn't cop

1) People lie. I found out one person had someone listening in and chatting the answers to them.2) The interviews get progressively more technical. We do a non-technical first round (some people don’t show up on time, aren’t great communicators, etc.), then have a technical interview about high level concepts followed by a technical test.3) Efficiency. We can learn more from a 1hr coding challenge than a 1hr verbal interview. And it requires less involvement from the team.

Most tech companies now do around 4-5 interviews. It has been like that for at least 7-8 years (probably more) but I just found out that not all companies are like that. After being subjected to these demeaning Leetcoding interviews I went through a refreshingly pleasant experience. It was an interview with just one person. They gave me a technical open-ended problem and two weeks time. After two weeks I had to do a presentation to them how I would solve that problem. Not much more was required.

You're the minority, from what I've read from others and experienced firsthand.Typically the technical interviews at companies (in the US at least) consist of HackerRank (either something generic a la leetcode or something made in-house at the company) followed by a live coding test and trivia (SOLID principles, Gang of Four design patterns, OOP fundamentals, sometimes things specific to the languages the company is using). This is for senior level positions. I find most companies p

While I have never interviewed with Google, my experience with other companies is that.1. With senior or experienced developer, it is usually pleasant and respectful and they are open to a diverging answer if it is justified.2. Some of these companies either have an inexperienced person in a senior position or delegate it to an inexperienced developer to do the initial filtering.3. Inexperienced people are extremely painful to interview with, they have "accomplished" something