What I Learned from Interviewing at 8 Companies for Entry-Level Backend Roles
From the second half of last year to this spring, I interviewed at 8 companies for entry-level backend positions. One final offer, six rejections, and one still in progress. I'm writing this up in case there are others preparing like me.
First, technical questions often came up shallower than expected. But if you can't handle the follow-up questions that chain off those shallow questions, it shows immediately. In particular, it was tough when I couldn't answer "Why did you design it that way?" with stories from my own project.
Here's what I took away:
- CS ultimately is the material for explaining your own code. If you just memorize, you fall apart at the second or third follow-up question.
- For coding tests, solving 2 problems perfectly was better than half-solving 4. In fact, there was a place I got into that way.
- Even just skimming the company's tech blog for an hour makes your motivation for applying much more natural.
- Companies that give rejection notices quickly are actually more appreciated. If you hold on and wait, your mental state goes first.
I think the real fight is not the interview itself but how you endure the gaps in between. Good luck, everyone, and if you have any questions, ask in the comments.
5 answers
Agreed—2 coding test problems fully solved vs. 4 problems half-solved, I really relate to this. I’ve been rejected from a place where I thought I got everything right, and passed a place with half-finished answers, so I don’t know what the right answer is lol