What questions to expect during a junior javascript developer interview? [closed]What questions to expect during a interview to renew a contract?Phone interview with CTO of company for junior web developer position. What to expect?Questions to ask during an interview?Why is it so hard to find a junior developer role?How to prepare for a conversation with someone much higher up?

Circuit breaker door shocked me. Static?

Up arrow under a sequence

Native Japanese vocabulary, pure Wago/Yamato Kotoba

How does the Intrepid class purge baryon particles?

How to make vehicular combat viable in a Post Apocalyptic world?

Function defined everywhere but continuous nowhere

Best way to get my money back from a friend having family problems

What do the dots and lines underneath these chords mean?

What is the name for a placename that contains what the thing is in a different language?

Help resolve territory acquisition design difference of opinion in MMO RTS

ethnic-related questions by immigration officer

How can you coordinate an attack against a monster that cannot be gazed upon?

Can an employer be forced to allow an employee to bring a gun to work (Washington State)?

How can I manage my team to maintain a reasonable productivity when my employer doesn't treat employees well?

How Would Civilisations on Different Planes of a Cube Planet Interact?

What is the most life you can have at the end of your first turn with only three cards?

How would an aircraft fly PIKES ONE departure procedure of Denver Airport?

Why is the fact that Ukraine President Zelenskiy publicly admitted that Trump didn't pressure him whatsoever being ignored?

Is 2FA via mobile phone still a good idea when phones are the most exposed device?

Is it okay to have an email address called "SS"?

Python: get overridden functions of subclass

What is the physical explanation for energy transport in simple electrical circuits?

Please help me to read schematic

How do you organize/plan your discovery session so that it does not conflict with the work of the current sprint?



What questions to expect during a junior javascript developer interview? [closed]


What questions to expect during a interview to renew a contract?Phone interview with CTO of company for junior web developer position. What to expect?Questions to ask during an interview?Why is it so hard to find a junior developer role?How to prepare for a conversation with someone much higher up?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









4

















I was invited in for a chat at a digital studio next week and I'm just going over some example questions etc.



The company seems really amazing. They make good looking products (Apps and the like) for small start-ups, nothing corporate or boring, just some cool people making cool things.



So I'm wondering what sort of questions I should expect? I will be preparing for the usual questions but any tips or guides would greatly help.










share|improve this question


















closed as primarily opinion-based by gnat, HorusKol, mag, Draken, Mister Positive Oct 15 at 11:14


Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.














  • 1





    Which country are you in? Interviewing techniques differ greatly between countries, the UK is more behavioural based whereas the US places a lot of emphasis on technical proficiency.

    – Jay Gould
    Oct 15 at 8:14











  • Try rephrasing your question and state a certain goal you'd like to achieve. 'What sort of question should I expect' & 'any tips or guides would greatly help' is very broad and primarily opinion-based..

    – iLuvLogix
    Oct 15 at 12:16

















4

















I was invited in for a chat at a digital studio next week and I'm just going over some example questions etc.



The company seems really amazing. They make good looking products (Apps and the like) for small start-ups, nothing corporate or boring, just some cool people making cool things.



So I'm wondering what sort of questions I should expect? I will be preparing for the usual questions but any tips or guides would greatly help.










share|improve this question


















closed as primarily opinion-based by gnat, HorusKol, mag, Draken, Mister Positive Oct 15 at 11:14


Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.














  • 1





    Which country are you in? Interviewing techniques differ greatly between countries, the UK is more behavioural based whereas the US places a lot of emphasis on technical proficiency.

    – Jay Gould
    Oct 15 at 8:14











  • Try rephrasing your question and state a certain goal you'd like to achieve. 'What sort of question should I expect' & 'any tips or guides would greatly help' is very broad and primarily opinion-based..

    – iLuvLogix
    Oct 15 at 12:16













4












4








4


3






I was invited in for a chat at a digital studio next week and I'm just going over some example questions etc.



The company seems really amazing. They make good looking products (Apps and the like) for small start-ups, nothing corporate or boring, just some cool people making cool things.



So I'm wondering what sort of questions I should expect? I will be preparing for the usual questions but any tips or guides would greatly help.










share|improve this question

















I was invited in for a chat at a digital studio next week and I'm just going over some example questions etc.



The company seems really amazing. They make good looking products (Apps and the like) for small start-ups, nothing corporate or boring, just some cool people making cool things.



So I'm wondering what sort of questions I should expect? I will be preparing for the usual questions but any tips or guides would greatly help.







interviewing job-search developer junior






share|improve this question
















share|improve this question













share|improve this question




share|improve this question








edited Oct 14 at 18:55









DarkCygnus

51.1k24 gold badges117 silver badges213 bronze badges




51.1k24 gold badges117 silver badges213 bronze badges










asked Oct 14 at 18:52









NooginyNooginy

272 bronze badges




272 bronze badges





closed as primarily opinion-based by gnat, HorusKol, mag, Draken, Mister Positive Oct 15 at 11:14


Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.











closed as primarily opinion-based by gnat, HorusKol, mag, Draken, Mister Positive Oct 15 at 11:14


Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.









closed as primarily opinion-based by gnat, HorusKol, mag, Draken, Mister Positive Oct 15 at 11:14


Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.









  • 1





    Which country are you in? Interviewing techniques differ greatly between countries, the UK is more behavioural based whereas the US places a lot of emphasis on technical proficiency.

    – Jay Gould
    Oct 15 at 8:14











  • Try rephrasing your question and state a certain goal you'd like to achieve. 'What sort of question should I expect' & 'any tips or guides would greatly help' is very broad and primarily opinion-based..

    – iLuvLogix
    Oct 15 at 12:16












  • 1





    Which country are you in? Interviewing techniques differ greatly between countries, the UK is more behavioural based whereas the US places a lot of emphasis on technical proficiency.

    – Jay Gould
    Oct 15 at 8:14











  • Try rephrasing your question and state a certain goal you'd like to achieve. 'What sort of question should I expect' & 'any tips or guides would greatly help' is very broad and primarily opinion-based..

    – iLuvLogix
    Oct 15 at 12:16







1




1





Which country are you in? Interviewing techniques differ greatly between countries, the UK is more behavioural based whereas the US places a lot of emphasis on technical proficiency.

– Jay Gould
Oct 15 at 8:14





Which country are you in? Interviewing techniques differ greatly between countries, the UK is more behavioural based whereas the US places a lot of emphasis on technical proficiency.

– Jay Gould
Oct 15 at 8:14













Try rephrasing your question and state a certain goal you'd like to achieve. 'What sort of question should I expect' & 'any tips or guides would greatly help' is very broad and primarily opinion-based..

– iLuvLogix
Oct 15 at 12:16





Try rephrasing your question and state a certain goal you'd like to achieve. 'What sort of question should I expect' & 'any tips or guides would greatly help' is very broad and primarily opinion-based..

– iLuvLogix
Oct 15 at 12:16










3 Answers
3






active

oldest

votes


















5


















You should expect to write code. Preferably, work on personal projects consistently in the weeks leading up to your interview. This will train your brain to be in JavaScript mode so you don't fumble JavaScript's syntax while trying to implement an algorithm they've asked you to write.



Search the web for "JavaScript exercises" or "JavaScript interview exercises" to find small exercises you can try to implement yourself. There's a good chance you will not practice the exact exercise they give you, but this will still get you thinking about how to approach a random problem.



I'm sure you already know this, but make sure you know the basics, such as the difference between let/var and the different ways to define a function. They also may ask you something along the lines of "what have you learned recently?", "what personal projects have you worked on?", and "are there any new features in JavaScript that excite you?" Try to have answers ready.



Best of luck!






share|improve this answer


























  • This is also true when you have worked with several languages over the years. Doing prep work by doing some simple development using the language is helpful in refreshing your memory of the syntax and idiosyncrasies of a given language.

    – Juha Untinen
    Oct 15 at 13:08











  • I agree, showing deep understanding by explaining different scopes of variables is just as important as being able to write simple code on the fly. My last company would always ask about the difference between "let" and "var", and it was a dealbreaker if someone would not know.

    – Pudora
    Oct 15 at 13:39


















4


















I wanted to put this as a comment but i don't have enough rep.
Anyway here is a questionnaire for job interviews with basic/common questions of javascript.
Although the focus is for front end, the questionnaire has many of the basics like these questions:




Basic JS Knowlegment



  • Explain event delegation.

  • Explain how this works in JavaScript.

  • What language constructions do you use for iterating over object properties and array items?

  • Can you describe the main difference between the Array.forEach() loop and Array.map() methods and why you would pick one versus the
    other?

  • Explain the difference between: function Person(), var person = Person(), and var person = new Person()?

  • Can you explain what Function.call and Function.apply do? What's the notable difference between the two?

  • Explain the differences on the usage of foo between function foo() and var foo = function()

  • What's the difference between an "attribute" and a "property"?

  • What is the difference between == and ===?

  • What are the differences between variables created using let, var or const?

Intermediate questions



  • Explain how prototypal inheritance works.

  • What's the difference between a variable that is: null, undefined or undeclared?

  • How would you go about checking for any of these states?

  • What is a closure, and how/why would you use one?

  • What's a typical use case for anonymous functions?

  • What's the difference between host objects and native objects?

  • Explain Function.prototype.bind.

  • Explain "hoisting".

  • Describe event bubbling.

  • Describe event capturing.

  • Why is it called a Ternary operator, what does the word "Ternary" indicate?

  • Explain the difference between synchronous and asynchronous functions.






share|improve this answer



































    3


















    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


    • 1.7 etc.


    In the second part I focus my questions on JS, starting with simple quesions:



    • 2.1 What is JavaScript?

    • 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.6 What is 'this' keyword in JavaScript?

    • 2.7 Which symbol is used for comments in Javascript?

    • 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..






    share|improve this answer



































      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      5


















      You should expect to write code. Preferably, work on personal projects consistently in the weeks leading up to your interview. This will train your brain to be in JavaScript mode so you don't fumble JavaScript's syntax while trying to implement an algorithm they've asked you to write.



      Search the web for "JavaScript exercises" or "JavaScript interview exercises" to find small exercises you can try to implement yourself. There's a good chance you will not practice the exact exercise they give you, but this will still get you thinking about how to approach a random problem.



      I'm sure you already know this, but make sure you know the basics, such as the difference between let/var and the different ways to define a function. They also may ask you something along the lines of "what have you learned recently?", "what personal projects have you worked on?", and "are there any new features in JavaScript that excite you?" Try to have answers ready.



      Best of luck!






      share|improve this answer


























      • This is also true when you have worked with several languages over the years. Doing prep work by doing some simple development using the language is helpful in refreshing your memory of the syntax and idiosyncrasies of a given language.

        – Juha Untinen
        Oct 15 at 13:08











      • I agree, showing deep understanding by explaining different scopes of variables is just as important as being able to write simple code on the fly. My last company would always ask about the difference between "let" and "var", and it was a dealbreaker if someone would not know.

        – Pudora
        Oct 15 at 13:39















      5


















      You should expect to write code. Preferably, work on personal projects consistently in the weeks leading up to your interview. This will train your brain to be in JavaScript mode so you don't fumble JavaScript's syntax while trying to implement an algorithm they've asked you to write.



      Search the web for "JavaScript exercises" or "JavaScript interview exercises" to find small exercises you can try to implement yourself. There's a good chance you will not practice the exact exercise they give you, but this will still get you thinking about how to approach a random problem.



      I'm sure you already know this, but make sure you know the basics, such as the difference between let/var and the different ways to define a function. They also may ask you something along the lines of "what have you learned recently?", "what personal projects have you worked on?", and "are there any new features in JavaScript that excite you?" Try to have answers ready.



      Best of luck!






      share|improve this answer


























      • This is also true when you have worked with several languages over the years. Doing prep work by doing some simple development using the language is helpful in refreshing your memory of the syntax and idiosyncrasies of a given language.

        – Juha Untinen
        Oct 15 at 13:08











      • I agree, showing deep understanding by explaining different scopes of variables is just as important as being able to write simple code on the fly. My last company would always ask about the difference between "let" and "var", and it was a dealbreaker if someone would not know.

        – Pudora
        Oct 15 at 13:39













      5














      5










      5









      You should expect to write code. Preferably, work on personal projects consistently in the weeks leading up to your interview. This will train your brain to be in JavaScript mode so you don't fumble JavaScript's syntax while trying to implement an algorithm they've asked you to write.



      Search the web for "JavaScript exercises" or "JavaScript interview exercises" to find small exercises you can try to implement yourself. There's a good chance you will not practice the exact exercise they give you, but this will still get you thinking about how to approach a random problem.



      I'm sure you already know this, but make sure you know the basics, such as the difference between let/var and the different ways to define a function. They also may ask you something along the lines of "what have you learned recently?", "what personal projects have you worked on?", and "are there any new features in JavaScript that excite you?" Try to have answers ready.



      Best of luck!






      share|improve this answer














      You should expect to write code. Preferably, work on personal projects consistently in the weeks leading up to your interview. This will train your brain to be in JavaScript mode so you don't fumble JavaScript's syntax while trying to implement an algorithm they've asked you to write.



      Search the web for "JavaScript exercises" or "JavaScript interview exercises" to find small exercises you can try to implement yourself. There's a good chance you will not practice the exact exercise they give you, but this will still get you thinking about how to approach a random problem.



      I'm sure you already know this, but make sure you know the basics, such as the difference between let/var and the different ways to define a function. They also may ask you something along the lines of "what have you learned recently?", "what personal projects have you worked on?", and "are there any new features in JavaScript that excite you?" Try to have answers ready.



      Best of luck!







      share|improve this answer













      share|improve this answer




      share|improve this answer










      answered Oct 14 at 19:33









      JaredJared

      2801 gold badge2 silver badges4 bronze badges




      2801 gold badge2 silver badges4 bronze badges















      • This is also true when you have worked with several languages over the years. Doing prep work by doing some simple development using the language is helpful in refreshing your memory of the syntax and idiosyncrasies of a given language.

        – Juha Untinen
        Oct 15 at 13:08











      • I agree, showing deep understanding by explaining different scopes of variables is just as important as being able to write simple code on the fly. My last company would always ask about the difference between "let" and "var", and it was a dealbreaker if someone would not know.

        – Pudora
        Oct 15 at 13:39

















      • This is also true when you have worked with several languages over the years. Doing prep work by doing some simple development using the language is helpful in refreshing your memory of the syntax and idiosyncrasies of a given language.

        – Juha Untinen
        Oct 15 at 13:08











      • I agree, showing deep understanding by explaining different scopes of variables is just as important as being able to write simple code on the fly. My last company would always ask about the difference between "let" and "var", and it was a dealbreaker if someone would not know.

        – Pudora
        Oct 15 at 13:39
















      This is also true when you have worked with several languages over the years. Doing prep work by doing some simple development using the language is helpful in refreshing your memory of the syntax and idiosyncrasies of a given language.

      – Juha Untinen
      Oct 15 at 13:08





      This is also true when you have worked with several languages over the years. Doing prep work by doing some simple development using the language is helpful in refreshing your memory of the syntax and idiosyncrasies of a given language.

      – Juha Untinen
      Oct 15 at 13:08













      I agree, showing deep understanding by explaining different scopes of variables is just as important as being able to write simple code on the fly. My last company would always ask about the difference between "let" and "var", and it was a dealbreaker if someone would not know.

      – Pudora
      Oct 15 at 13:39





      I agree, showing deep understanding by explaining different scopes of variables is just as important as being able to write simple code on the fly. My last company would always ask about the difference between "let" and "var", and it was a dealbreaker if someone would not know.

      – Pudora
      Oct 15 at 13:39













      4


















      I wanted to put this as a comment but i don't have enough rep.
      Anyway here is a questionnaire for job interviews with basic/common questions of javascript.
      Although the focus is for front end, the questionnaire has many of the basics like these questions:




      Basic JS Knowlegment



      • Explain event delegation.

      • Explain how this works in JavaScript.

      • What language constructions do you use for iterating over object properties and array items?

      • Can you describe the main difference between the Array.forEach() loop and Array.map() methods and why you would pick one versus the
        other?

      • Explain the difference between: function Person(), var person = Person(), and var person = new Person()?

      • Can you explain what Function.call and Function.apply do? What's the notable difference between the two?

      • Explain the differences on the usage of foo between function foo() and var foo = function()

      • What's the difference between an "attribute" and a "property"?

      • What is the difference between == and ===?

      • What are the differences between variables created using let, var or const?

      Intermediate questions



      • Explain how prototypal inheritance works.

      • What's the difference between a variable that is: null, undefined or undeclared?

      • How would you go about checking for any of these states?

      • What is a closure, and how/why would you use one?

      • What's a typical use case for anonymous functions?

      • What's the difference between host objects and native objects?

      • Explain Function.prototype.bind.

      • Explain "hoisting".

      • Describe event bubbling.

      • Describe event capturing.

      • Why is it called a Ternary operator, what does the word "Ternary" indicate?

      • Explain the difference between synchronous and asynchronous functions.






      share|improve this answer
































        4


















        I wanted to put this as a comment but i don't have enough rep.
        Anyway here is a questionnaire for job interviews with basic/common questions of javascript.
        Although the focus is for front end, the questionnaire has many of the basics like these questions:




        Basic JS Knowlegment



        • Explain event delegation.

        • Explain how this works in JavaScript.

        • What language constructions do you use for iterating over object properties and array items?

        • Can you describe the main difference between the Array.forEach() loop and Array.map() methods and why you would pick one versus the
          other?

        • Explain the difference between: function Person(), var person = Person(), and var person = new Person()?

        • Can you explain what Function.call and Function.apply do? What's the notable difference between the two?

        • Explain the differences on the usage of foo between function foo() and var foo = function()

        • What's the difference between an "attribute" and a "property"?

        • What is the difference between == and ===?

        • What are the differences between variables created using let, var or const?

        Intermediate questions



        • Explain how prototypal inheritance works.

        • What's the difference between a variable that is: null, undefined or undeclared?

        • How would you go about checking for any of these states?

        • What is a closure, and how/why would you use one?

        • What's a typical use case for anonymous functions?

        • What's the difference between host objects and native objects?

        • Explain Function.prototype.bind.

        • Explain "hoisting".

        • Describe event bubbling.

        • Describe event capturing.

        • Why is it called a Ternary operator, what does the word "Ternary" indicate?

        • Explain the difference between synchronous and asynchronous functions.






        share|improve this answer






























          4














          4










          4









          I wanted to put this as a comment but i don't have enough rep.
          Anyway here is a questionnaire for job interviews with basic/common questions of javascript.
          Although the focus is for front end, the questionnaire has many of the basics like these questions:




          Basic JS Knowlegment



          • Explain event delegation.

          • Explain how this works in JavaScript.

          • What language constructions do you use for iterating over object properties and array items?

          • Can you describe the main difference between the Array.forEach() loop and Array.map() methods and why you would pick one versus the
            other?

          • Explain the difference between: function Person(), var person = Person(), and var person = new Person()?

          • Can you explain what Function.call and Function.apply do? What's the notable difference between the two?

          • Explain the differences on the usage of foo between function foo() and var foo = function()

          • What's the difference between an "attribute" and a "property"?

          • What is the difference between == and ===?

          • What are the differences between variables created using let, var or const?

          Intermediate questions



          • Explain how prototypal inheritance works.

          • What's the difference between a variable that is: null, undefined or undeclared?

          • How would you go about checking for any of these states?

          • What is a closure, and how/why would you use one?

          • What's a typical use case for anonymous functions?

          • What's the difference between host objects and native objects?

          • Explain Function.prototype.bind.

          • Explain "hoisting".

          • Describe event bubbling.

          • Describe event capturing.

          • Why is it called a Ternary operator, what does the word "Ternary" indicate?

          • Explain the difference between synchronous and asynchronous functions.






          share|improve this answer
















          I wanted to put this as a comment but i don't have enough rep.
          Anyway here is a questionnaire for job interviews with basic/common questions of javascript.
          Although the focus is for front end, the questionnaire has many of the basics like these questions:




          Basic JS Knowlegment



          • Explain event delegation.

          • Explain how this works in JavaScript.

          • What language constructions do you use for iterating over object properties and array items?

          • Can you describe the main difference between the Array.forEach() loop and Array.map() methods and why you would pick one versus the
            other?

          • Explain the difference between: function Person(), var person = Person(), and var person = new Person()?

          • Can you explain what Function.call and Function.apply do? What's the notable difference between the two?

          • Explain the differences on the usage of foo between function foo() and var foo = function()

          • What's the difference between an "attribute" and a "property"?

          • What is the difference between == and ===?

          • What are the differences between variables created using let, var or const?

          Intermediate questions



          • Explain how prototypal inheritance works.

          • What's the difference between a variable that is: null, undefined or undeclared?

          • How would you go about checking for any of these states?

          • What is a closure, and how/why would you use one?

          • What's a typical use case for anonymous functions?

          • What's the difference between host objects and native objects?

          • Explain Function.prototype.bind.

          • Explain "hoisting".

          • Describe event bubbling.

          • Describe event capturing.

          • Why is it called a Ternary operator, what does the word "Ternary" indicate?

          • Explain the difference between synchronous and asynchronous functions.







          share|improve this answer















          share|improve this answer




          share|improve this answer








          edited Oct 15 at 14:55

























          answered Oct 14 at 21:17









          B.J. A.A.B.J. A.A.

          801 gold badge4 silver badges11 bronze badges




          801 gold badge4 silver badges11 bronze badges
























              3


















              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


              • 1.7 etc.


              In the second part I focus my questions on JS, starting with simple quesions:



              • 2.1 What is JavaScript?

              • 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.6 What is 'this' keyword in JavaScript?

              • 2.7 Which symbol is used for comments in Javascript?

              • 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..






              share|improve this answer
































                3


















                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


                • 1.7 etc.


                In the second part I focus my questions on JS, starting with simple quesions:



                • 2.1 What is JavaScript?

                • 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.6 What is 'this' keyword in JavaScript?

                • 2.7 Which symbol is used for comments in Javascript?

                • 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..






                share|improve this answer






























                  3














                  3










                  3









                  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


                  • 1.7 etc.


                  In the second part I focus my questions on JS, starting with simple quesions:



                  • 2.1 What is JavaScript?

                  • 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.6 What is 'this' keyword in JavaScript?

                  • 2.7 Which symbol is used for comments in Javascript?

                  • 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..






                  share|improve this answer
















                  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


                  • 1.7 etc.


                  In the second part I focus my questions on JS, starting with simple quesions:



                  • 2.1 What is JavaScript?

                  • 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.6 What is 'this' keyword in JavaScript?

                  • 2.7 Which symbol is used for comments in Javascript?

                  • 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..







                  share|improve this answer















                  share|improve this answer




                  share|improve this answer








                  edited Oct 15 at 10:56

























                  answered Oct 15 at 8:25









                  iLuvLogixiLuvLogix

                  2,0751 gold badge7 silver badges26 bronze badges




                  2,0751 gold badge7 silver badges26 bronze badges
















                      Popular posts from this blog

                      Canceling a color specificationRandomly assigning color to Graphics3D objects?Default color for Filling in Mathematica 9Coloring specific elements of sets with a prime modified order in an array plotHow to pick a color differing significantly from the colors already in a given color list?Detection of the text colorColor numbers based on their valueCan color schemes for use with ColorData include opacity specification?My dynamic color schemes

                      Invision Community Contents History See also References External links Navigation menuProprietaryinvisioncommunity.comIPS Community ForumsIPS Community Forumsthis blog entry"License Changes, IP.Board 3.4, and the Future""Interview -- Matt Mecham of Ibforums""CEO Invision Power Board, Matt Mecham Is a Liar, Thief!"IPB License Explanation 1.3, 1.3.1, 2.0, and 2.1ArchivedSecurity Fixes, Updates And Enhancements For IPB 1.3.1Archived"New Demo Accounts - Invision Power Services"the original"New Default Skin"the original"Invision Power Board 3.0.0 and Applications Released"the original"Archived copy"the original"Perpetual licenses being done away with""Release Notes - Invision Power Services""Introducing: IPS Community Suite 4!"Invision Community Release Notes

                      199年 目錄 大件事 到箇年出世嗰人 到箇年死嗰人 節慶、風俗習慣 導覽選單