Earlier quoted context omitted.
Absolutely, he probably would not be the right hire to squeeze an extra 0.1% of performance out of Google search, but on any team which has to understand the needs of the legal industry (plenty of these at FAANG and non-FAANG companies) he could find himself in a senior role very quickly.
Isn't the 'senior role' aligned with what he said though? He'd have the industry insight to design product roadmaps and UX wire frames in a PM type role, but wouldn't touch the codebase because he's a lawyer who wrote some code a long time ago, not a lawyer who codes, and the non-lawyers his team can hire have much more experience in actual software engineering.
Why are so many successful founding CEOs software engineers?
301–310 of 365 posts
Re: Why are so many successful founding CEOs software engineers?
#302All of the people on this list are "software engineers" in the sense that they have some rudimentary education in the field. Almost none of them could get a job as a software engineer at their own company, if they had to, because they would be completely unqualified. And I'm not looking down my nose at anyone: I have an undergraduate degree in CS, but I got it 16 years ago and then went to law school, and there is no…
Yes, there are exceptions to the rule. Especially in fields whose core business isn't software.
But in general it helps for founders to be able to, you know, actually build the thing they are trying to sell. I think that's all there is to it.
Re: Why are so many successful founding CEOs software engineers?
#303All of the people on this list are "software engineers" in the sense that they have some rudimentary education in the field. Almost none of them could get a job as a software engineer at their own company, if they had to, because they would be completely unqualified. And I'm not looking down my nose at anyone: I have an undergraduate degree in CS, but I got it 16 years ago and then went to law school, and there is no…
A necessary precondition for showing that something new & innovative is worth doing is usually to do it. It's not a sufficient condition though: you also need the risk tolerance to work on things new & innovative that may not work; you need the deep understanding of your problem to understand what the solution looks like; you need the location & social connections to access capital and hire real software engineers to scale your solution; and you need the judgment to hire the right people to fill in your skillset gaps. That's why most software engineers aren't off founding billion dollar companies.
Note that this applies to other founder-led enterprises. Fred Koch was a hell of a chemist before Koch Industries became a huge conglomerate. Warren Buffett studied under one of the greatest value investors (Benjamin Graham) on Wall Street. Carnegie started as a telegrapher and railroad superintendent before becoming a steel magnate. You need that operational experience and domain knowledge before founding a world-changing company.
Re: Why are so many successful founding CEOs software engineers?
#304Earlier quoted context omitted.
What? You honestly think the Stanford PhDs who created Google couldn't get hired as basic SWEs? Seriously? I mean if true that says a lot more about the SWE interviews than it does about Stanford PhDs. I mean there are Yale JDs that fail the bar exam but no one would claim that the average Yale JD couldn't get hired as a Big Law associate or judicial clerk.
Google famously refused to hire Max Howell, the programmer who wrote Homebrew, which (based on Google's own statements) was used by 90% of Google's engineers at the time of his interview, because he couldn't invert a binary tree in the specific (but unstated) manner that the interviewer wanted. So it's definitely possible, indeed likely, that Serge and Larry wouldn't get hired at the Google of today. The "average Yal…
> Homebrew, which was used by 90% of Google's engineers at the time of his interview
This is definitely not true.
Re: Why are so many successful founding CEOs software engineers?
#305Earlier quoted context omitted.
Google famously refused to hire Max Howell, the programmer who wrote Homebrew, which (based on Google's own statements) was used by 90% of Google's engineers at the time of his interview, because he couldn't invert a binary tree in the specific (but unstated) manner that the interviewer wanted. So it's definitely possible, indeed likely, that Serge and Larry wouldn't get hired at the Google of today. The "average Yal…
I don't know about the rest of that, but > Homebrew, which was used by 90% of Google's engineers at the time of his interview This is definitely not true.
At any rate, the point is that a guy who used software used by a large portion of Google's engineering team because it was superior to the in-house solution could not get a job at Google because he failed to answer a programming question in the specific manner the interviewer wanted for a type of problem he would never actually encounter on the job. And in that vein, Sergie and Larry would similarly have difficulty getting hired at Google because other than their original algorithm, which Google has not used in over a decade, they have no modern or recent software experience and would likely fail all of the programming interviews.
Re: Why are so many successful founding CEOs software engineers?
#306All of the people on this list are "software engineers" in the sense that they have some rudimentary education in the field. Almost none of them could get a job as a software engineer at their own company, if they had to, because they would be completely unqualified. And I'm not looking down my nose at anyone: I have an undergraduate degree in CS, but I got it 16 years ago and then went to law school, and there is no…
Re: Why are so many successful founding CEOs software engineers?
#307All of the people on this list are "software engineers" in the sense that they have some rudimentary education in the field. Almost none of them could get a job as a software engineer at their own company, if they had to, because they would be completely unqualified. And I'm not looking down my nose at anyone: I have an undergraduate degree in CS, but I got it 16 years ago and then went to law school, and there is no…
Because there are many more software engineering jobs in the world than CEO jobs.
> Almost none of them could get a job as a software engineer at their own company, if they had to, because they would be completely unqualified.
Which probably reflects more that the hiring process is broken, than that these people couldn't contribute to a business writing code.
The real problem is that, in addition to writing code, they would also start identifying business opportunities and new ways to improve processes and increase revenues and cut costs, threatening the perceived job security of the people in management above them.
Re: Why are so many successful founding CEOs software engineers?
#308I'd say if you don't have that perspective and are CEO of a software driven company, I'd make sure that you have a very close group of constant SE advisers to help you out.
Re: Why are so many successful founding CEOs software engineers?
#309Earlier quoted context omitted.
> there is not a serious place on earth that would let me touch their codebase. It depends on what you mean by "serious". Software development is very much a free-for-all as far as backgrounds go. It attracts people from all disciplines. There are NO CREDENTIALS needed to be called a "software engineer", and it will remain this way for the foreseeable future. Every organization that develops software has its own rule…
> There are NO CREDENTIALS needed to be called a "software engineer" In the USA, maybe that's true. In Canada, for instance, there are legal requirements to being able to call yourself an Engineer. That's why "Software Developer" is used.
Professional Engineer is a protected title in Canada. Is that what you’re thinking of?
Re: Why are so many successful founding CEOs software engineers?
#310Earlier quoted context omitted.
> Zuckerberg could get a job at Facebook. He obviously wrote a lot of Facebook's early code. > Gates & Allen allegedly didn't do much actual coding themselves but they certainly understood it. What? Gates & Allen similarly wrote "a lot of early code". Gates also acted as a Chief Software Architect in his final days at Microsoft.
My understanding is that the last application code Gates was involved in was the TRS-80 Model 100 [1] circa 1982; I taught my kids assembly on the Model 100 and think it's great. [1] https://en.wikipedia.org/wiki/TRS-80_Model_100#ROM_firmware