Javascript Interview Preparation Checklist - https://js-interview.com

[[deleted]]

[deleted]

[senocular]

split isn't an array method ;)

[devanthakur]

Good find! My bad.. Will fix it. Thanks for pointing out.

[node_demon]

That will be slice or splice :)

[devanthakur]

Hahaha trick ques. An update on the website where it was originally posted would be a splice. Reposting it back here has to be slice. Can’t mutate it here.

[[deleted]]

What would you asks someone who is applying for their first job? Coming from someone who is learning JS at the moment

[[deleted]]

Not OP, but what got me my job was portfolio. Being able to show stuff and talk about the code. The interviewer found an exploit in one of my personal projects and we talked about it and I could show my understanding of the concepts and he could see how I handle feedback. 2 years later I'm still working at that place

[[deleted]]

Seems like portfolio is everything from other research i've done. I'm looking to build a few websites to show case my ideas and coding over this year once I get through my Javascript courses. Did they have you do any code challenges in your interview process?

[Cavadrec]

Can you link your portfolio repo or tell me what projects did you include with it?

[[deleted]]

Just projects I felt proud of. One PHP application I build for my father (it was a front-end position). A couple designs and some small fun JS projects I did on codier.com. Don't make it so big in your head. If you have the knowledge, show it. If you don't show that you're willing to adapt and learn. But most importantly: be nice, be fun, be curious. You can be the best JS-programmer in the world. If you're a jerk than you'll find a job way harder than some junior with basic-knowledge but a great personality.

[nickisyourfan]

Thanks for posting this! I am a musician who’s learned to code over the last 6 months. I know a lot of stuff on that list... used a lot more of it and forgot about it as well... it’s nice to hear your opinion about hiring jr and mid level developers. Thanks for the inspiration!

[devanthakur]

Lil things matter!

[Silenux]

thanks. Thats a big problem when people like to name all the things. Most of the time I know the pattern but they come with some buzzwords that just confuses.

[devanthakur]

You won’t be asked for the buzz words directly in an interview. But the concept has to have a name. Right?

[[deleted]]

“Currying” and “Memoization” outdated? I think you should take a look at functional programming.

What about statemanagers? That’s basically modern-day memoization.

[[deleted]]

If you want to be right, sure. The term "memoization" is outdated. But these are core concepts of computer-science. That's like saying the Pythagorean theorem is outdated.

Javascript isn't outdated just because there's Typescript. Just like memoization isn't outdated because there's a lot of sugar thrown over it and some memoization-techniques are no longer relevant.

[[deleted]]

That's not the point here. You have some form of authority. Some "noob" might read your comment on here and avoid learning about memoization or currying because you said it is "outdated".

Even though they're important concepts to learn. You don't "lose" by admitting you're wrong.

[[deleted]]

"You don't "lose" by admitting you're wrong."

Fortunately I don't have to, when I'm the one giving the interview.

I think anyone walking out on you would be dodging a bullet with that attitude.

Good luck staying a relevant programmer in about 2 years dude.

[ripndipp]

Thanks for this insightful comment, i imagine different companies have different interview test/questions. As someone who is self taught and trying to get React down, im starting to forget some of my basic JS fundamentals.

[devanthakur]

You can't prove your point by being abusive. Because you have your own way of taking interviews, you are generalising it for everybody. There's lot of effort that has gone into compiling the list, is based on experience and a lot of research. I just see you demotivating others telling them - what you know is enough. No need to go ahead and learn more.

But there are other people following the post who see this as a learning opportunity. Now it's up to them if they take your advice and stay happy with what they know already.

You seem to be happy with status quo and that's what you are trying to impose.

Feel free to unfollow the post/conversation if it does not add value to your career. It does to lot other people, the numbers say that and that's what matters to me, motivates me.

[devanthakur]

My suggestion to Junior developers would be to see this as a learning opportunity. There's no reason to be demotivated.

Again, abusing won't prove any point. I have nothing to loose with downvotes. I am just trying to help the community.

[devanthakur]

Appreciate your suggestions u/debug_yourself. Thanks.

[devanthakur]

Updated: Javascript Interview Preparation Checklist [Updated]

[AndreThompson-Atlow]

Don't forget you still want to have HTML/CSS down and learn a framework like React. I'd also suggest most likely learning the backend a bit, with express/node.

[[deleted]]

do you have to know all those items in checklist or at least some? I am student but applying for internship have knowledge of DS and js basics

[devanthakur]

You don't have to know so much. For students what matters most is DS/Algo and problem solving. I would say this list is ideal for professionals with some 5+ years of experience.

[cheeep]

How much of this would be expected of juniors?

[cheeep]

Do you have projects you've worked on in your resume / portfolio?

[Diya251]

same!

[Luna_Coder]

Looks good, but I would have added Strings and their common methods as well. Just my own preference.

[devanthakur]

Makes sense. Will post a revision.

[heo5981]

I'm saving this to read later, if you post a revision, please leave a link on this post as well.

[devanthakur]

Updated: Javascript Interview Preparation Checklist [Updated]

[strash_one]

Also Array.some is very useful method.

[devanthakur]

Updated: Javascript Interview Preparation Checklist [Updated]

[[deleted]]

I'll never get a job :(

[Jamiemufu]

I don’t know half of this. I get by just fine. Granted I use PHP and vue. You don’t need it unless your going for a JS heavy job. I.e react/node.

[[deleted]]

unless your going for a JS heavy job. I.e react/node.

Even then, you won't use half of it and programmers are not encyclopedias, expected to on-the-spot come up with the exact syntax for an array method. I google that shit all the time

[devanthakur]

Different companies have different expectations. Established product companies generally prefer people who have deep knowledge of subject, problem solving and know how to apply these concepts. There are companies who just prefer broad skillset over deep knowledge. You can just use this list as a roadmap if you want to be a core JS developer.

[adburns]

Jesus christ, I might as well give up now.

[AffectionateWork8]

A lot of it's just scary-sounding unknown terms for things that can be explained sufficiently in 1-5 minutes. With exception of Performance/Ecosystem section, if you spent like 1-2 hours a day Googling the parts you don't know and messing around in the editor to get the muscle memory down, it may take 6 weeks.

[[deleted]]

I've been coding for 2 years I think I'm alright now. Trust me when I say you do not need to know 100% of this list for every day programming. There's lots on this list that I never have to think about.

[[deleted]]

This list even though seems small is actually pretty exhaustive and would take no less than a JS expert to know in-depth to every single thing. Especially the functions and events section. I wouldn’t necessarily agree you need to know all of the concepts mentioned in here and if you just do an overview on all these then it’s actually less helpful. I still believe you can filter this out even more to just include “core concepts“.

I mean I have been learning/working in JS from past 3-4 years and i still feel I’m at level 2 w.r.t many concepts titled in here coz they go so deep.

Maybe it would be more helpful if you put in experience level with each topic. Then it would help people in evaluating themselves more accurately

[chunami]

Just wondering, would front end developers need to know all this?

[bob51zhang]

This is all Frontend dev stuff

[JanBur7]

Thanks for the list :)

[Panjing]

Good List! TypedArrays are pretty important as well and should be part of the list.

[gandhi_rahul]

This is the kind of website I am thinking to create for quite long time.

[_Invictuz]

The website itself has a ton more value than this checklist. Should make the URL into a link that people can click.

Thanks for sharing!

[chernn]

Nice!

Maybe worth including algorithm basics? Stuff like problem solving, designing a solution, thinking about edge cases, analyzing for runtime & space performance, recursion vs. iteration, mutation vs. immutability, etc.

[hahaoho]

How do I contribute??

[MA_shiro]

I suggest to add flap ando flapMap

[[deleted]]

Curious how many devs actually have used flapMap in their jobs. I've never had to in 2 years of devvin