> This is also why you see so many "solve this random programming problem" type interviews - they hope (wrongly) that it's less fakeable and somehow gives you an idea of how they will do in the future.
Whether they can code or not isn’t indicative of whether they can get things done. The last time I had an open req last year, the coding part was ChatGPT simple. It was for a green field initiative. I needed to be able to throw any random thing that came up - a complex deliverable - and know they could run with it - talk to the stakeholders, disambiguate the problem space, notice XYProblems, come back with a design and a proposal and learn what they needed to learn with a little direction. I needed a real “senior developer”. Not someone that “codez real gud”.
I actually turned down a “smart” candidate who was laid off from the AWS EC2 service team I think dealing with Elastic Block Storage (EC2 encompasses more than just VMs).
I knew he could code. But he didn’t show me any indication that he could deal with the ambiguity on the level I needed or the soft skills.
Whether they can code or not isn’t indicative of whether they can get things done. The last time I had an open req last year, the coding part was ChatGPT simple. It was for a green field initiative. I needed to be able to throw any random thing that came up - a complex deliverable - and know they could run with it - talk to the stakeholders, disambiguate the problem space, notice XYProblems, come back with a design and a proposal and learn what they needed to learn with a little direction. I needed a real “senior developer”. Not someone that “codez real gud”.
I actually turned down a “smart” candidate who was laid off from the AWS EC2 service team I think dealing with Elastic Block Storage (EC2 encompasses more than just VMs).
I knew he could code. But he didn’t show me any indication that he could deal with the ambiguity on the level I needed or the soft skills.