Getting ready for Coding Assignment Interviews

tkssharma - Feb 23 '23 - - Dev Community

Hi Folks,

In this Blogs i am going to talk about two different things about interviews

  • My experience when i was applying for position and failed !
  • My personal experience of interviewing many JS developers later
  • How actually you can crack JS Interviews

My overall IT experience is now more than 12 Years and i don't have exact count about how many developers i have hired in My Team working as Lead Developer.

Interview where i failed

First of all my experience when i was applying for position in javascript Stack during 2004, back in that time angular js was popular framework and i was getting lot of angularjs questions which i answered correctly now it was time of some coding exercise for some Product based Organization

  • question was to remove duplicates from an array in all different possible ways.
  • My answer was not according to what interviewer was looking for, i used long approach where it can be done by just doing filter with findIndex or building a simple Map (here i failed even after answering all angularjs questions)

So the moral of the story is be good at basic coding fundamentals

When i was taking interviews

It’s my opinion when I took a lot of javascript interviews in the last couple of years. Looking for javascript developers and Hiring a good javascript Developers is really a challenging task

The perception which people are having these days

  • My name is person X and since last 1 year i am working on react so I can apply for javascript Jobs, Learning framework is easy but learning bit and pieces of javascript is different
    working on Angular/React/Vue is not enough to get Javascript level Jobs

  • We just learn some framework and start saying that I am good at javascript and framework, according to me this will not be a correct statement.
    We should focus more on Learning Core of javascript which is missing among a lot of developers, they just jump in the direct framework and start saying, javascript experts
    Important of all that we should never Hire developers for a particular Javascript framework but we should Hire Good JS developers

  • The lifecycle of React, React state and props how it works and Redux pattern — Attendee is able to answer the answers of these questions as they are simple but related to basic react JS work

  • When questions come for how to do we shallow/deep copy or how to create Copy of object — this becomes tricky and some developers will not be able to answer this, they may talk about Object.assign and all but the final clean and clear answer you will not get

  • I always advise developers to look into MDN documentation for learning JS in depth, we write react or angular but everything is javascript only

During the interview, developers were not able to identify the difference between map and forEach methods on Array prototype, That was surprising as this was not expected from any JS developers This is something which we do daily in Javascript until unless we stuck with framework

Learn framework as they make development easy but also take care of Vanilla Javascript, javascript is functional programming and has more to learn

how should you learn and practise

There are different ways of learning and these days learning content is available everywhere you need to look for quality content and build experience on that tool or technology.

Coming to coding questions, You might be good at solving problems at framework level but when it comes to write vanilla javascript we stuck sometimes

So here i am going to help in practising these coding questions and doing simple live examples how to approach and solve a particular problem in javascript or any other javascript framework like (angular, react, vue js)
we can talk many platform for that like hackerrank, leetcode or any other.

https://www.youtube.com/watch?v=W33gtWKD10w&list=PLT5Jhb7lgSBOsHPeMm4YZkojofRxN3TBs

Happy Coding

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .