Re:How to Get Hired: From a Developer and Manager Point of View
by majormajor on Saturday March 03, 2018 @01:10PM
(#16510608)
I believe that insisting on seeing code is a trap. Code is notoriously tricky to evaluate without actually running it for a while, anyway - look at all the bugs that make it through code reviews - so it works well for "ok they're not completely full of shit" but rarely a lot beyond that.
If there's truly interesting and clever architectural stuff going on, that can be explained in words in an interview (in person or not). That puts some burden back on people skills, but... if you're creating clever solutions you can't explain to other technical people, I'm going to be worried about your ability to work on a team anyway.
If I'm hiring someone with more than 5 years of experience I'm hoping they can tell me some interesting war stories or have some interesting design ideas when asked about a potential business problem.
If there's truly interesting and clever architectural stuff going on, that can be explained in words in an interview (in person or not). That puts some burden back on people skills, but... if you're creating clever solutions you can't explain to other technical people, I'm going to be worried about your ability to work on a team anyway.
If I'm hiring someone with more than 5 years of experience I'm hoping they can tell me some interesting war stories or have some interesting design ideas when asked about a potential business problem.