←back to thread

263 points mooreds | 1 comments | | HN request time: 0.22s | source
Show context
Cornbilly ◴[] No.45421796[source]
When I hire juniors, I try to give them problems that I know they likely won't be able to solve in the interview because I want to see how they think about things. The problem has become that a lot of kids coming out of college have done little more than memorize Leetcode problems and outsourced classwork to AI. I've also seen less and less passion for the career as the years go by (ie. less computer nerds).

Unless the company is doing something that requires almost no special domain knowledge, it's almost inevitable that it's going to take a good while for them to on-board. For us, it usually takes about year to get them to the point that they can contribute without some form of handholding. However, that also mostly holds true for seniors coming to us from other industries.

replies(28): >>45421860 #>>45421875 #>>45421907 #>>45421943 #>>45421994 #>>45422037 #>>45422071 #>>45422091 #>>45422103 #>>45422129 #>>45422144 #>>45422160 #>>45422277 #>>45422301 #>>45422324 #>>45422415 #>>45422442 #>>45422501 #>>45424757 #>>45427099 #>>45430210 #>>45431214 #>>45433919 #>>45434598 #>>45434938 #>>45435782 #>>45439610 #>>45447908 #
1. CharlieDigital ◴[] No.45433919[source]
When I hire juniors I give them problems that focus on fundamentals.

If a junior can code vanilla JS well, they can learn React, Vue, Svelte, etc. if they can't, they will never fully understand any of them. If they can write raw CSS, that can learn Tailwind and understand how and why. If thry can explain what's happening in the browser console, they can find the entry point for most bugs.

This is pretty much how I also test seniors. Focus on the fundamentals; if those are off, nothing else matters.