How I failed my first junior developer interview — and what I learned (PART 2)
My very first developer interview experience ended in failure. I wasn’t prepared at all and didn’t understand the technology enough, but I learned a lot. I’ll share my experiences from a month-long journey in this two-part article series. Part 1 can be found here in case you missed it:
So the previous article ended with me beginning to work on a real digital product with a real developer team for three company trial days. A week prior, an HR representative had called me and asked me what technology I prefer to work with. I had a decent understanding of Java at the time, as well as a little knowledge of JavaScript and React; however, I knew I wanted to work as a full-stack developer with React frontend anyways, so I chose JavaScript.
By the way, my friend who told me about the job earlier said that the company didn’t really need Java developers because the main technologies were JavaScript frontend frameworks and Node.js backend, so that was another plus for the JavaScript team.
I had a feeling I’d made it at that point. “They will eventually hire me because of my convincing performance in the first two rounds, so I didn’t have to be smart or hardworking.” — I thought.
