[AndrewKemendo]

There is no right answer to this. Every company is different, so there is no right way to do software interviews.

Enterprise SaaS, Consumer Social and ML API companies will all have different working environments. Add on to that options of remote vs on-prem, CI/CD vs TDD, customer integration requirements, staff numbers, perks etc... and you have completely different needs for workers and teams.

A team earns their hires, and people will naturally gravitate to environments that suit their work styles.

[tchaffee]

> there is no right way to do software interviews.

In the context you presented this in, I agree with you. However, interviewing is a skill that must be learned or you are going to make loads of beginner mistakes. In that sense there are many right things you should be doing in an interview and whatever your company style is, you're going to want to use at least some of those best practices in your interviews if you want to find the best candidates in the shortest time.

[AndrewKemendo]

Isn't this true for anything though? More experience = better (on average).

In theory there is an optima between a new hires ideal workplace and the hiring company's style of work. As with most things it's about knowing yourself and identifying in others if there is a match.

[tchaffee]

Sure it's true for anything. Which is why it's surprising when 95% of the engineering interviews you go on the interviewer doesn't have even a remote clue about interviewing best practices. Which is also why you get so many whiteboard coding interviews. "That's what happened to me once in an interview, so I'll just do the same thing".

It's the very reason I mentioned it. Too many people haven't figured out the very obvious fix: get some training in how to interview!