I've been through and used several different styles of interview and the one that stands out as being "the best" at predicting whether a person will fit on the team is just to bring them in and work with them for a day on your actual product
1) You don't do problems you've already solved that they have to come up with same answer to.
2) You don't do algorithm / problem testing that they're never going to use on the job.
3) You don't do whiteboarding except as you would in real life.
Engineering teams are people working collaboratively to solve complicated problems where nobody knows the "right" answer. Any interview that's going to tell you something is going to measure along those metrics, and not "can you invert this b-tree on a whiteboard."
1) You don't do problems you've already solved that they have to come up with same answer to.
2) You don't do algorithm / problem testing that they're never going to use on the job.
3) You don't do whiteboarding except as you would in real life.
Engineering teams are people working collaboratively to solve complicated problems where nobody knows the "right" answer. Any interview that's going to tell you something is going to measure along those metrics, and not "can you invert this b-tree on a whiteboard."