Context: For 3+ year experience.
I have to talk interviews of candidates for the position of frontend and React.js positions, every time I use to do is prepare question before hand by looking at candidates resume or If not prepared then ask from my experience.
I have a question to all the developers/interviewers that what they ask when taking interviews for React.js, JavaScript or for frontend engineers.[No DS/Algo rounds].
Do you guys have any cheat sheet and can share that will be very helpful.
I recently have given interviews myself and some companies ask to code in react while sharing screen (like: make a tic tac toe game) which I found really interesting and doable within 45min - 1hr.
Please do share your thoughts.
Thanks.
Top comments (7)
I'd prefer specific questions asked from the experience point of view than make people code for about 1hour (which is usually more).
Not just React questions but also JS ones, as React is just a lib, so you can notice if someone just learnt "react" or they understand how JS works (top to bottom).
A good JS dev that understands the principles over which React is built-in will be able to use React proficiently in few days/weeks.
A dev who only learnt React with online courses will probably struggle when facing challenges over those forementioned courses by lack of "vanilla" JS experience (or TS if it's what you use at the company/project).
So simple questions like:
And so on. You can order those questions as you like and present it as quick test to take an overview into the knowledge of the applicants.
Sometimes I found people that doesn't know the names of some concepts but they also have the concepts clear, in which situation be prepared with some hints. At the end you want to know if they're able to work proficiently and not just evaluating their theoretical knowledge and the keywords they memorized.
Hope it helps!
Very helpful. Thanks @joelbonetr
HTTP is a fundamental subject that I want to really comprehend. Actually the whole TCP/IP suite is my ultimate goal when it comes to Networking. But for now, my priority is the HTTP layer.
As for Javascript, yeah... I don't want to leave holes in some topics such as closure, strict mode, promises, async-await, etc, that I need to relearn them as well as other topics I haven't covered. Because I am interested in Node.js, I feel need for learning operating system conceptually, especially concepts like process and thread, to better understand how Node.js works as a single-thread JS run-time environment.
That's nice!
I would recommend you to add UDP into the list in contrast with TCP (a good way to learn UDP may be through websockets, see socket.io as example).
Also worker threads topic may be of your interest.
A note on your last sentence,
Node JS is coded in C, and it runs in multiple threads and cores (Node itself).
While the execution of JS is single-threaded at its base, we still can run some operations in parallel which is the main point on multi-threading. We do not create threads that share the same 'context', though.
When Node encounters blocking operations (reading from a DB for example), it delegates them to a separate pool of threads. This is managed by a C library known as libuv.
See the link about Worker Threads for more details 🙂
Thanks for the reply
I will take time to learn worker, not only in Node.js, but also in browser as covered in developer.mozilla.org/en-US/docs/W...
Actually for backend, I am also interested in Golang which provides goroutines and channels for handling concurrency. Also Java which I suspend my learning until I have time again.
i personally use my 22-part series - dev.to/frontendengineer/react-inte... which has HTML, CSS, JS and ReactJS questions. Many find this useful on their interview journey
ask your devs for a real problem they faced, and ask what would be his approach to the same problem. Don't expect him to resolve it, since is not familiarized with the project.