I'd worry about an interviewer who focussed on this kind of thing rather than having a proper conversation about projects past and present, issues they've got and my opinions (in general) around them. I'd want them to find out if I would fit and likely learn what they and their clients need rather than whether I'm the current version of a Javascript language reference.
They should use my project experience to determine whether or not I'm used to using different tools to solve business relevant problems and whether I'd sit and pickle or actually go out and figure out exactly how to solve some awkward requirement.
If they're focussed on whether I know syntactic detail of a specific language, then they are a very junior interviewer and don't actually understand what their team needs.
If your questions are the kind that a few hours of google can answer, then you are thinking, conceptually, at the wrong end of the scale to get anything worthwhile done.
Unless you really really do want someone who just swallowed a javascript book?
Thanks for your valuable comment , richard .
While i totally agree with you but i have been asked these kind of questions many a times while i sat for an entry level dev position .
Ah I remember my first entry level too. I guess, being fair, context is everything.
Still, I'd hope a beginner would try to have projects already they can chat about as I'd still be biased against pop quizzes and strongly focussed on whether they would work with us, albeit as a newbie.
Absolutely having some good projects takes you a long way .
I remember mine first as well and since i had some projects built i was able to take the interviewer about how i went about creating them and in one of the projects we even discussed what could have improved if i would to optimise it right now ,
So i guess yeah having some projects is quite nice to have , it. shows that you really can do some work on your own and can learn
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'd worry about an interviewer who focussed on this kind of thing rather than having a proper conversation about projects past and present, issues they've got and my opinions (in general) around them. I'd want them to find out if I would fit and likely learn what they and their clients need rather than whether I'm the current version of a Javascript language reference.
They should use my project experience to determine whether or not I'm used to using different tools to solve business relevant problems and whether I'd sit and pickle or actually go out and figure out exactly how to solve some awkward requirement.
If they're focussed on whether I know syntactic detail of a specific language, then they are a very junior interviewer and don't actually understand what their team needs.
If your questions are the kind that a few hours of google can answer, then you are thinking, conceptually, at the wrong end of the scale to get anything worthwhile done.
Unless you really really do want someone who just swallowed a javascript book?
Thanks for your valuable comment , richard .
While i totally agree with you but i have been asked these kind of questions many a times while i sat for an entry level dev position .
Ah I remember my first entry level too. I guess, being fair, context is everything.
Still, I'd hope a beginner would try to have projects already they can chat about as I'd still be biased against pop quizzes and strongly focussed on whether they would work with us, albeit as a newbie.
Absolutely having some good projects takes you a long way .
I remember mine first as well and since i had some projects built i was able to take the interviewer about how i went about creating them and in one of the projects we even discussed what could have improved if i would to optimise it right now ,
So i guess yeah having some projects is quite nice to have , it. shows that you really can do some work on your own and can learn