I had an interview a while back that I really liked:
A pair programming session on a home assignment (it was a Java banking app) with 2–3 bugs and missing features. This allows the interviewer to see the candidate’s problem-solving skills and how quickly they can find, fix, and add features.
A take-home assignment with a static JSON file containing products, where the developer is asked to build both a front end and a back end around it. This lets you assess their systems thinking — do they overcomplicate things, chase the latest tech, or make wise, pragmatic decisions? During the interview, you can also expand the scope of the assignment, e.g., What if this needs to be production-ready? What would you add?
Anything else usually ends up being a waste of time for both the interviewer and the developer.
I had an interview a while back that I really liked:
Anything else usually ends up being a waste of time for both the interviewer and the developer.I’ve done over 100 of these in the last 10 years.
It really depends if you are talking front end/back end/mobile etc.
But the best I've ever seen was to review an actual PR (from the company doing the interviewing) and discuss what is good and bad about it.
Not sure, but it should reflect what you are paying for those five hours.