[mvpu]

The same way Charlie Rose interviews his guests: read their resume, and poke into their background with curiosity and respect. Dig into their past life to your heart's content, but make them feel good about it.

In this case, I would poke them on a) relevant problems they worked on and how they went about solving them (dig as deep as you can), b) how they approach problem solving and coding in general (what excites them), c) how they made career decisions to date (what drives them), and why they're interested in the role you're hiring for (what's motivating them).

I wouldn't waste time with algorithm questions. A thoughtful and motivated developer will figure out and deliver much more than a algorithm guru.