{"id":45335500,"user":"sethops1","time":1758557528,"time_ago":"2 months ago","type":"comment","content":"

Does it matter? The point of the interview is not to produce an output.","comments":[{"id":45337300,"user":"shomp","time":1758564660,"time_ago":"2 months ago","type":"comment","content":"

If you don't solve the problem, do you get the job?","comments":[{"id":45337720,"user":"WalterBright","time":1758566624,"time_ago":"2 months ago","type":"comment","content":"

Depends on why you didn't solve it.","comments":[{"id":45344372,"user":"jondwillis","time":1758616621,"time_ago":"2 months ago","type":"comment","content":"

Never once has this happened","comments":[{"id":45347091,"user":"lsaferite","time":1758635703,"time_ago":"2 months ago","type":"comment","content":"

I've hired someone that didn't solve a specific technical problem.

If they are able to walk through what they are doing and it shows the capability to do the expected tasks, why would you exclude them for failing to 'solve' some specific task? We are generally hiring for overall capabilities, not the ability to solve one specific problem.

Generally my methodology for working through these kinds of things during hiring now days focuses more on the code review side of things. I started doing that 5+ years ago at this point. That's actually fortuitous given the fact that reviewing code in the age of AI Coding Assistants has become so much more important.

Anyway, a sample size of 1 here refutes the assertion that someone's never been hired even when failing to solve a technical interview problem. FWIW, they turned out to be an absolute beast of a developer when they joined the team.","comments":[],"comments_count":0,"level":3,"url":"item?id=45347091"}],"comments_count":1,"level":2,"url":"item?id=45344372"}],"comments_count":2,"level":1,"url":"item?id=45337720"}],"comments_count":3,"level":0,"url":"item?id=45337300"}],"comments_count":4,"url":"item?id=45335500"}

Comment by sethops1