What I Learned from Interviewing at 8 Companies as a Junior Developer

I started preparing in the second half of last year and only recently managed to get an offer from one company. I was rejected by 7 out of 8 and got the last one, so looking back, I can see the things that were a real waste of time, and I’m writing them down.

1. Wasting 6 months on coding tests alone

I could solve problems, but I couldn’t explain my projects. I learned too late that coding tests are just the minimum bar for passing the resume screen, not the acceptance criteria.

2. Listing only features in your portfolio

I wrote things like “implemented sign-up, login, and a bulletin board,” and the interviewers’ reactions were pretty lukewarm. They kept asking “Why did you use this technology for this feature?” but I hadn’t prepared an answer.

3. Memorizing answers to technical questions

Memorized answers fall apart as soon as one follow-up question comes. It was much better to admit I didn’t know something and explain how I’d look it up.

4. Not looking into the company when applying

I only properly read what the company did after I got accepted. There were even places I was glad I got rejected from.

In conclusion, I think it’s right to split your time about half and half between coding tests and project explanations. I’m writing this in case someone else burns 6 months like I did.