Reflections After Four Backend Entry-Level Interviews

Since November I've sent out 20 applications and done 4 interviews. The result is 2 offers and 2 rejections. I figured writing up even a short summary might help someone, so here it is.

1. Technical questions are shallower than you'd expect. JPA N+1, transaction propagation, and indexes were pretty much all of it. The follow-up questions, though, are the scary part. They keep digging into why you did it that way.

2. You need to explain your project in under 3 minutes. At first I rambled for over 10 minutes and the interviewer's face went stiff. From my second interview on, I stuck to a Problem - Attempt - Result - What I'd Improve structure and kept it to exactly 3 minutes.

3. Don't memorize CS — explain it. If you recite textbook sentences word for word when asked "What's the difference between a process and a thread?", you get no follow-up question. Tying it to your own experience worked much better.

4. When they ask if you have any questions at the end, "No, I don't" is a real no-go. If you ask what the team's biggest challenge is right now, the conversation comes alive.

Hang in there, everyone who's preparing right now. I've got two more interviews left, so I need to do well on those too.

by 지나가던행인482

9 answers

Agreed, especially #2. In my first interview, I went on about a project for over 10 minutes and the atmosphere cooled off—I was literally breaking into a cold sweat lol

by 뉴비탈출37 · ▲0