I feel very anxious when developers interviewing me asks
1. is nodejs single threaded or multithreaded ?
2. How does node handle requests
3. How do u manage concurrency
4. What is event emitter and callback.

Dude i have given you my resume, without knowing these things i could never do that ?

I feel the discussion must be based on concepts and general problem solving rather than focusing on one technology. Tech can always be learnt.

One of two things is happening here.

1) they don't see the type of experience you think you have. You should update your resume or provide a small portfolio of products you have worked on and what your role was in them.

2) they are inexperienced and are reading these questions from some blog on "how to find the best node dev"

In my experience a CV isn't really trustworthy. Never assume anything when interviewing someone.

I was once asked the version number of a language I used in the past.
I replied that I didn’t remember and anyway it was not important as everything changes too fast.

He said it was important.

So I asked what version were they using then

He replied that he had to ask the lead programmer

🖕

@Crost yes, you can ask better questions. A organization that understands it needs adopt to newer technologies should never reply on one technology when the industry is moving forward and that too ask basic questions in that. It should be based on concepts.

@vvinu9876: If you have millions of lines in Fortran, what you need is someone who can do Fortran. Doesn't matter how fast the industry moves.

Same for any other "tech" that is well-established in a company. Can't just dump it all because hippest framework of the week has arrived...

@vvinu9876: Also, it is impossible to not rely on any "tech" - as the manifestation of the solution to the problem has to be written in _something_ and probably needs to use _some_ framework/API/libs. As it gets written, the comitment to the used "tech" is factually done.

Surely you can always rewrite or upgrade - but that isn't free. And it might be impossible depending on the size of the existing code base and resources of the company. Legacy is the norm - not the exception.