Echo JS 0.11.0

The question about port 80 is *not* a trick question. There are ways to listen on port 80 without superuser rights on *nix systems. Whether your code should be listening on port 80 in the first place is a different question. In any case I wouldn't expect a candidate (who is likely nervous and not thinking straight) to catch that low ports are special and infer you're asking about running apps in production.

I'd also say that the use of NPM shrinkwrap is not universally accepted as a best practice for actual deployment. Running "npm install" in production deployment is contentious for all the same reasons relying on GitHub is. Plus, even with shrinkwrap there are some situations in which the installs will be slightly different. A common alternative is just committing `node_modules` as well -- while this is definitely not a best practice for libraries, it avoids a lot of problems with deployment, as long as your development and production environments are sufficiently similar.

Also, the term "stub" isn't unambiguous. I would rephrase the question as "What are stubs, spies or mocks?" (the exact differences between them being less important than familiarity with the general idea behind their use).

I wouldn't have known what the term "test pyramid" is supposed to mean despite being familiar with the concept -- the exact differences between integration and acceptance tests and unit and integration tests tend to be contentious issues (the term "unit" is difficult to define) and not everything can be meaningfully tested in isolation.

Other than that, I mostly agree with the questions. It's probably more important to consider these as conversation starters to get a feeling for the candidate's general aptitude and opinions rather than a checklist to base a hiring decision on -- but these checklists tend to be worthless in real life anyway.

Nice article.

But questions are too simple, might be ok for a junior dev. Expected to see at least for mid+

Also I would split them as node and js related (just because there are much more to ask about nodejs)

I don't consider myself as an experienced nodejs ninja, but could have answered all of them.

Sure, but I think experienced developers should be able to give much more nuanced answers and show deeper understanding on the subjects.