You’ve missed some other formats that are already used in production. Domain-specific pair programming exists for both web and mobile engineering interviews. There’s also “read this code and debug it” which is an underrated format.
I’m not even sure the Leetcode style needs to be abolished, so much as it can be tweaked to remove some of the additional pressures of the format (time limits, stress from monitoring, overuse of memorization)
> What if you're looking for someone who's good at development but have not used a specific tech stack?
Then you have an interview specific to that use case of candidate. It doesn’t invalidate the format used in interviewing other types of candidates.
I’m not even sure the Leetcode style needs to be abolished, so much as it can be tweaked to remove some of the additional pressures of the format (time limits, stress from monitoring, overuse of memorization)
> What if you're looking for someone who's good at development but have not used a specific tech stack?
Then you have an interview specific to that use case of candidate. It doesn’t invalidate the format used in interviewing other types of candidates.