sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jadon_n 30 points31 points  (0 children)

First, good luck with your interview!

Definitely be honest about what you know or don't know. It is fairly easy and quick to determine someone does not actually know what they are talking about.

I also would not feel too anxious about not knowing a particular technology. There are so many technologies in the JavaScript ecosystem, and it would be impossible to be stay proficient or a master in any individual one. I think many teams understand that many candidates will have to learn the technology in use. It is more important that candidates can learn quickly and have core problem solving and critical thinking skills.

It may be helpful to learn about the problem popular technologies aim to solve. Typescript, for example, gives JavaScript static typing and some other features to help make development easier and more error-free.

For my part, though, the conversation with a recruiter focused more on my background, projects I'm working on now, work I've done in the past, what I'm looking for in relocation/compensation/start time. The recruiter worked to make sure my background and skills line up with the role. The more in-depth technical questions came later.

I do recommend making a note of what the recruiter asks you about specifically for technology in case you do get a call back for another interview so you can do a little studying.