3 ms·
Day to day, how much code do you think principle and staff engineers write? Senior architects and team leads? The problem is I don't think we, as an engineering
by fragmede 3y ago
Day to day, how much code do you think principle and staff engineers write? Senior architects and team leads? The problem is I don't think we, as an engineering discipline and career path, are willing to recognize that the job of being a coder stops being about writing code! Yes there are deadbeats who don't contribute (some of them can code just fine), as there are in every industry, but until you've been in a project that failed because there was no senior architect, someone getting paid a comfortable salary to be the "senior architect" and not write code sounds like a waste of the company's money to the intern.
At the start of a SWE career, I don't think things broken. Study up some leetcode and write code on a whiteboard to prove that you, as a candidate, are smart and motivated enough to play the game. It's after that, that things get out of sync and you get absolutely amazing people who have written world changing software who can't pass your stupid puzzle of a whiteboard interview. And then what do you do? This person failed your test but you want to hire them. Here's the part where we fail, where we are too stuck on following the rules.
They failed the test so you can't make an offer? No. Move heaven and Earth to bend the rules, and make them the offer anyway. Don't hide behind corporate handbooks and the HR or the legal department.
Obviously this power can be abused, but I don't take it as a given that it must be, given a hiring panel.
Google could have made an offer to Homebrew's Max Howell but chose not to, which speaks volumes.
- aleph_minus_one 3y ago> Google could have made an offer to Homebrew's Max Howell but chose not to, which speaks volumes. Programming is divided into a multitude of various cultures with their own (often incompatible) rules. Not without reason, you tend to talk of a "Java shop", "C# shop", "Python shop", ... So, when looking for a good programmer, you either look for a beginner who is still "malleable" into your desired culture, or has the same right pedigree as your company. In this sense, I a priori have no doubt that Max Howell is a decent programmer, but I do believe that he comes from and is attached to a very different programming culture than Google's; thus he would likely not be a good fit.
- lmm 3y ago> Yes there are deadbeats who don't contribute (some of them can code just fine), as there are in every industry, but until you've been in a project that failed because there was no senior architect, someone getting paid a comfortable salary to be the "senior architect" and not write code sounds like a waste of the company's money to the intern. Oh, if only the worst was not contributing. I've been at a company full of brilliant programmers that was just driven into the ground by the senior architect, who wasn't necessary. Hiring someone who can't Fizzbuzz for that position (and giving him the authority to overrule the development leads) was absolutely the single decision that sank that company.