Hunger beats tenure: Advice for junior engineers

ispq

While the approach makes sense, I have yet to see a quantifiable and normalised way to replace Leetcode interviews. It’s probably too soon to claim “death of the coding interview”.

kayashaolu2

The heart of the coding interview is to get signal on a candidates’ ability to solve a problem without all of the inputs given to them, see how they and explain their thought process as they do it. 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.

anilgulecha

In the new world, normalised interviews are going away, because business value is not normalized. This means that domain based interviewing and signals are going to make a comeback. It would make sense to build your career in a single domain, since your built up expertize will transfer to other companies within that domain. Far fewer switches will happen for seniors across domains.