I've held a couple of interviews with prospective employees supposed to work with js, ng, node & pgsql and therefore put a little questionnaire together to rate the candidates.
The first part doesn't even consist of any programming but rather general IT-questions to see if they have even the most basic understandings of computers and networks:
1.1 Describe the purpose and the functionality of a proxy-server & reverse proxy-server
1.2 Name & describe the layers of the OSI-model
1.3 What the difference between a router and a switch
1.4 Name a couple of firewalls you are familiar with
1.5 Describe the functionality of a compiler and an interpretor
1.6 Describe the programming paradigms of object-oriented and function-oriented programming languages
In the second part I focus my questions on JS, starting with simple quesions:
- 2.2 What is NodeJS?
- 2.3 Name and explain the different data-types.
- 2.4 What is a function-scope?
- 2.5 What are global variables?
- 2.8 Whats the difference between == and === ?
- 2.9 etc..
In the third part I focus on Angular specific questions such as:
- 3.1 Explain what 'declarations', 'providers', and 'imports' do.
- 3.2 Explain AOT compilation
- 3.3 What is a subscription?
- 3.4 What is an observable?
- 3.5 Explain the steps of the ng-lifecycle.
- 3.6 etc..
And in the fourth part I let them write a couple of semi-difficult SQL queries to see if they are familiar with db-operations.
Additionally, an interviewer could also ask you about past work experiences and projects you have worked on until now.
In the last part I tend to ask personal questions related to work-ethics, teamwork-capabilities and interpersonal skills.
So you see that such a questionnaire could just not only exist of pure js-related questions but could also contain a broad variety of questions related to front to backend and full-stack-development - depending on the needs of the company interviewing you.
Alltogether, including the candidates behaviour, rethorical skills, creativity, body-language and knowledge-base, I get a somehow clear picture if he's in the 'hire' or in the 'no-hire' fraction of the candidate-pool.
p.s.: It's always useful to familiarize yourself with a variety of sdk's and ide's and to get your hands dirty by developing some small projects beforehand. And obviously try to present yourself from the best side and show interest in the company as well by asking them a couple questions. Good luck and may your secret sauce be with you!
Joel Spolsky's "The Guerrilla Guide to Interviewing" is also inspiring and worth a read for both - interviewers and interviewees..