Re:Hunger beats tenure: Advice for junior engineers
by toadi on Wednesday October 28, 2026 @02:42AM
(#50269961)
I used to have a stack of books with references notes on my desk. The internet came and I could search and even stack-overflow improved this. Doing a whiteboard riddle from rote knowledge is something I always fail. That particular solution I maybe used it once or twice in my 30 years as SWE. Why would I remember this. I do remember where I can find the solution for it.
Re:Hunger beats tenure: Advice for junior engineers
by blitzar on Wednesday October 28, 2026 @04:36AM
(#50270687)
The heart of the coding interview is to get signal on a candidates’ willingness to join the cult.
Re:Hunger beats tenure: Advice for junior engineers
by braj0 on Wednesday October 28, 2026 @09:16AM
(#50273057)
I dunno why you are getting downvoted for this. Enthusiasm to take orders is often valued far more then pure intellect. Have other people not made this observation or had this experience? Companies want good soldiers who follow orders not free-spirits.
Because of AI, what it means to “not have all of the inputs” has changed as anyone can cut and paste a Leetcode problem to a chatbot and solve it.
I think we are going to iterate a bit to figure out a better signal than the typical coding interview. For junior engineers, I think coding questions will move towards MBA style problems when someone is given more of an open ended question with a codebase and you see what the candidate does without context to reduce the problem.