In the world of web development, pure Javascript remains king. If you came into web development only using jQuery, stop it. Now.

Better yet, any framework or library for that matter. PURE JavaScript is KING!

Learning + PRACTICING the necessary foundations of JavaScript is critical in your frontend development career, especially if you want to pursue a career in this field.

I've gone through several dozens of interviews, each one having failed because I couldn't complete the code (and sucked at problem-solving, granted I didn't know how even to approach some of these problems).

But, a skill that most wouldn't outright tell you is this:

interviewing is test-taking

Do you remember your finals in college? Or a pop quiz that came out of nowhere that was worth 50% of your grade? Think of all that put together and add in the professor/instructor watching you do it all under 15 minutes.

I was horrible with test-taking. But that's the unfortunate reality.

Another option is to approach interviewing as if you're coding alongside a friend/co-worker. Doing this will lessen the interview anxieties that will hopefully lead to your success.

Learn and develop the skills as to what precisely the interviewer might be looking after.

For instance, if you're interviewing for a frontend position, learn all things, everything frontend. Learn how the web works, what "HTTP" requests are, how APIs work, DOM manipulation, etc.

And for the love of God, take your time with each of the questions given to you. You're not some kind of hacker trying to break a security wall before the F.B.I. breaks in your door. You're changing a box on a webpage.

Below, you'll find a complete (possible) solution to the problems I had to solve.

You don't need to read them.

In summary, I was unprepared to solve each of these seemingly simple Frontend JavaScript and HTML/CSS problems. I also had major test-taking anxiety that froze me up several times throughout each of the interviews.

Center this shit

This one job interview that I'm glad I didn't pass. The position was full remote and eventually laid off over half their staff a few months after I had interviewed.

Everything went well up until the last portion of the coding test where I had to work with JavaScript and implement basic DOM manipulation.

In shot, make sure you know how to do basic Vanilla JS DOM manipulation. I'm talking things like "documment.getElementById" or "document.getQuerySelector".

Let's Move These Damn Boxes

Goal: Move the first box to the right without moving the other two boxes.

The most difficult part about this question was, how do we get a single div tag to overlap and move over the other div nodes? It's easy to determine that now, just use translate-transform.

The answer could have been all done in CSS. Unfortunately, I didn't have the knowledge of translate - transform property. This was something I didn't bother to completely understand since I wanted to move on from it to learn other seemingly, more inportant CSS concepts.

I really, really wanted this job. I love the company that I was interviewing for.

Moral of the story, learn and understand EVERYTHING to be a master of your craft. This is a non-negotiable. In this case, know everything there is to know about your CSS. I work with CSS every day for my job, yet this concept was a bit unknown to me because I never took the time to stop and learn what exactly I was doing to make specific styles work - CSS isn't magic.

Stupid Stoplight

This was my first technical interview. For someone who has never been in one, I was overwhelmed with nervousness and excitement. Based on the job description, this is easy peasy!

For the most part, things seemed to be going well. I made decent styles and had a seemingly good grasp on the React coding concept.

Then came the ending

Your Dog Days Are Over

I hadn't interviewed for a few months prior ot this coding interview. Based on the job description, this seemed like yet another interview I could pass with flying colors.

Once again, overthinking mixed with sheer nervousness and interview anxiety got the best of me. I ended up never finishing the exercise despite how easy it was with all the past interview experience I had.

This was the closest I was to getting past the second round. His feedback was that he wanted to see a higher "score" on my coding test. At the very least, I guess I know that these interviewers are grading me with some kind of point system.

For The Love of God, Make This Responsive!

It's been 15 minutes, you haven't coded anything...It's not looking good.

These weren't his exact words, but it wasn't far from them. Hearing this wasn't as painful as it seemed. In fact, I was relieved that he was upfront with me about not wanting to move forward with me.

The main problem with this interview was that I was utterly nervous. When a seemingly simple question is thrown my way, I get nervous, especially since I haven't interviewed in a while. This was the first interview I had since revamping my interivew application.

Change The Freakin' Grid!

This was my last interview. Long story short I didn't pass. I couldn't think straight with the time I had left and everything that I thought I knew was thrown out the door. The interviewer made suggestions for me that I didn't understand and it left me feeling lost towards the end of the interview. Moral of the story once again, PREPARE your ass off and LISTEN to whatever cues are coming from your interviewer.