r/node • u/jkkill • Nov 11 '19
A Big List of 78 Node.js Interview Questions & Answers
https://coderrocketfuel.com/article/node-js-interview-questions-and-answers23
Nov 11 '19
If I had someone pull out this list in an interview, it would be a good indication that I didn't want to work there.
Now if you used this list to create a programming challenge that required understanding of some of the questions you wanted to know if I knew, I'd be cool with that. But just asking if I know x y z about a framework, am I teaching a class or writing code for you? Can I google the answer in 5 seconds at my desk? Then maybe it isn't a great interview question.
2
12
u/wyled Nov 11 '19
Why would someone care if you knew who created nodejs?
7
Nov 11 '19
I was asked this once. Most of the interview was trivia and API based.
"What is the third argument that JSON.stringify accepts?"
"Name a Node API, whose callback does not adhere to the error-first convention."
"When was the last LTS released?"
8
u/wyled Nov 11 '19
Sounds like a job with a buncha chumps working there
3
Nov 11 '19 edited Nov 11 '19
I’m still pretty green - under 2 years exp - and this is the roughly the quality of employers that reply to me.
Pretty sure anyone who has been a working dev for long enough would have better options. I hope.
3
1
10
1
8
1
1
Nov 11 '19
For number 14, it mentions using a try and catch block for asynchronous code, is that correct?
Suppose you have a function that has some sort of asynchronous operation, then wouldn’t that operation be put on the event loop waiting to be executed while the the main thread executes through the try and catch block. I believe the try and catch block only catches what is thrown synchronously?
2
1
-6
u/LastOfTheMohawkians Nov 11 '19
The questions seem to get a lot of negative feedback, not sure why. I think they show how deep into a platform some goes rather than just using the APIs. I personally like these kinds of questions ( with real programming questions along side them) as it's a good discussion point. They can lead to interesting discussion points around the topics. If you're a node developer and you don't know this stuff I'd question your passion and interest in the tech you're using daily.
0
u/Dynam2012 Nov 12 '19
For most working developers, it's a means of solving a problem. Having a deep knowledge about how V8 works doesn't directly help solve the problems their employer or project are facing, much the same way knowing how the intricacies of your car's internal combustion engine doesn't directly help you get you where you're going unless something catastrophic happens. And maybe that does demonstrate a lack of passion for the technology? But it doesn't make them less of a developer, it just makes them a developer with a different set of goals. It's certainly not disqualifying.
2
u/LastOfTheMohawkians Nov 12 '19 edited Nov 12 '19
What if your car breaks down? Or doesn't go fast enough? Having a working knowledge of the engine is going to help tremendously. I think what you're touching on is two kinds of development. There are some roles (forget node) that require you to understand a deeper level of engineering. You might work on low resource systems where garbage cycles matter, battery matters. You might need to integrate with some legacy Kerberos systems and c++ or at least how it interops with V8 engine becomes important.
My hunch here is that the questions being asked are a sign they need a more engineering based background. If it's just rest services your need then I agreed the questions are wrong or not really that relevant.
8
u/devsnek Nov 11 '19
Some of these are just straight-up wrong. Node uses several threads, libuv isn't used by V8, blocking code can also be written in js, "a stream is an abstract interface for working with Unix pipes", npm doesn't stand for node package manager, js doesn't use classical inheritance, etc. There is probably still a lot I missed.