Angular vs Vanilla JavaScript - Job Interview Coding Project

Angular vs Vanilla JavaScript - Job Interview Coding Project

As a developer, I am always looking for opportunities to learn and grow. Recently, I applied for a job that required knowledge of vanilla JavaScript and React, and was given a coding challenge to test my skills in these areas. While React was an option, I chose to complete the challenge using vanilla JavaScript.

After completing the challenge, I had a video conversation with Juan. During our conversation, I showed him what I did to complete the coding challenge. We discussed some of the differences between vanilla JavaScript and Angular.

Our conversation was not just about the coding challenge, but also about the broader differences between vanilla JavaScript and Angular. We discussed the approaches to data handling and DOM manipulation in both technologies, and how Angular provides a more efficient way of developing web applications.

It was interesting to see how our backgrounds in development allowed us to share knowledge and learn from each other.

Toward the end of our conversation, we explored ChatGPT in the field of web development. We tested the accuracy of the answers provided by ChatGPT for questions related to web development and programming.


Did I get a job offer from that company?

Despite fulfilling every requirement of the coding challenge, and going above and beyond by meticulously matching the colors of the provided image using Photoshop's eyedropper tool, I was not offered the job.

The lack of transparency and constructive feedback during the process was frustrating. It was only after I specifically asked that I was informed of the reasons for not being selected:

  • the number of my commits (they insisted that it could have been done with fewer commits - no shit, yeah it could be done with one commit really, everything could be done with one commit)

  • the language of my commits (it wasn't official enough for them apparently, but they are not even paying me for that work)

  • a section of my code that was copied for me to see. (yeah as if I do not know what my code looks like)

No constructive feedback was provided to help me improve for future opportunities. I believe that if someone makes a point, they should be able to support it with examples and offer suggestions for improvement. Without constructive criticism, feedback can be hollow and not beneficial.

Nevertheless, I am grateful for the experience, and it has taught me to be mindful of companies that do not value transparency and constructive feedback.

Leaving all the corporate bullshit aside - my conversation with Juan was a valuable learning experience that allowed me to share knowledge of vanilla JavaScript and capture insights from our experience in Angular development. Our discussion on the differences between the two technologies, as well as the exploration of ChatGPT, provided us with a deeper understanding of the potential of these technologies in the field of web development.