I'm retired from the software biz but I think the technical interview probably should depend on the level of node expertise you are looking for. Your article seems suited for architectural level candidates or full stack engineers (why Node, what are the advantages? etc.)
These days, high-traffic sites require different tiers of knowledge. Your release engineers are going to need a different skill set than your transactional and middle-tier folks, for example. They'll need to know how to enforce library maintenance patterns, for example, and be true masters at managing external libraries and APIs.
They should be able to bundle and scaffold stuff with their eyes closed. If you ask them about left-pad, they should laugh and be able to tell you a good story. I should add, too, that I wouldn't even necessarily require node expertise for a release engineering position if the candidate has proven to be a release wizard in, say, Java. Given a node stack, they'll figure it out. Of course, if they claim node expertise, that's where you hit them with release-related node questions.
Anyway, that is a different skill set than the middle-tier people, or transactional folks, or what have you, who need to be masters at callbacks and should be good enough to avoid callback hell, which can be partly mitigated with the use of self-documenting function and variable names (instead of comments).
Deeply nested callbacks are usually a problem. So an emphasis on your statement, "Or the main nest can be split into multiple simple nests for easier management." That kind of thing can be enforced on pull requests, so if I was whiteboarding someone I wouldn't waste time asking for an example if they simply affirm the strategy.
Your front-end folks will have even different sets of questions, I'd think. Honestly, I'd mostly look for vanilla JS experts here - I wouldn't get too caught up in technical Node questions unless they claim expertise, which is easy enough to verify. They're busy keeping up on angular, react, backbone, CSS, and a jillion other things that don't really need to be evaluated if their core JavaScript skills can be confirmed.
Just some thoughts your article provoked. I hope it doesn't sound like I'm arguing against your post! I'm just adding to it a bit really, I hope. :-)
