3 ms·
The role the article describes is usually called a VP of Engineering. The distinction between them is that VP Eng is an operational role - you're responsible f
by nostrademons 7y ago
The role the article describes is usually called a VP of Engineering. The distinction between them is that VP Eng is an operational role - you're responsible for managing a team of developers; instituting the appropriate process to keep productivity high and bug count low; dealing with technical debt; identifying portions of the codebase that won't scale and replacing them with solutions that will; and all of the nitty-gritty organizational tasks needed to ensure that the engineering organization doesn't grind to a halt.
The CTO role is a visionary one. You're responsible for looking outside the organization at new technological developments and deciding how they may impact the organization's strategy; identifying new technical areas that warrant some exploratory investment; prototyping new systems, sometimes with the help of a small team of engineers who enjoy that stuff; and advocating for innovation within the organization.
Think of the role of Larry & Sergey (technically Presidents of Product/Technology, respectively) vs. Urs Hoelzle (VP Eng) at early Google. Larry & Sergey were responsible for making sure that things like GMail, Google Maps, 20% time, Chrome, etc. got funded and Keyhole, Android, Blogger, Writely, etc. got bought. Urs instituted the engineering culture, made sure the right engineers got into the right roles and were able to be productive, technical debt got paid down (slowly), new systems were written as necessary to scale, etc.
The CTO role, properly defined, is the perfect place to kick a technical founder upstairs and yet still retain their expertise in innovation. The problem is that many CEOs conflate the two roles, assign VP responsibilities to a CTO with a personality type more suited for the CTO role, never hire a real VP, and then wonder why the organization devolves into chaos. If you're doing it right the bulk of the engineering organization should report up through the VP of Engineering and the CTO should have only a small number of special-projects reports.
- oarabbus_ 7y agoWhat is the difference between a President of Product, and a VP of Product? Obviously a President is "higher" than a Vice President, but most companies have a VP Eng/Product, but not a President of Eng/Prod
- kesor 7y agoUsually, companies have just one President, with all the others being Vice Presidents of the various aspects required for the company.
- nostrademons 7y ago"President of Product" is somewhat idiosyncratic to Google - I don't know any other company with that particular title. The etymology, I think, is specific to some quirks in corporate law, which still has some anachronisms from the 1600s. When you form a new organization, there are 3 positions that are assumed to exist: President (overall leader), Treasurer (responsible for keeping the books & finances), and Secretary (responsible for writing down meeting minutes). These are enshrined in corporate law, so when you form a new corporation, the bylaws need to specify holders for these offices (it's common for the founder to hold all 3, or to split them up among founders). The idea of a corporation in the 1600s didn't really envision today's massive multinational tech companies, so the actual org structure departs fairly significantly from these "official" offices. There's a rough correspondence that's developed though: President = CEO, and Treasurer = CFO, and Secretary = whoever's keeping the minutes. Sometimes you'll see this in official titles, as "President and CEO of X". Sometimes - particularly when you have a visionary CEO who needs a strong operational COO - the President title will be assigned to the COO. This is Gwynne Shotwell's title at SpaceX, and is a strong indication that actual operational leadership of the organization rests with the COO. A "Vice President", by analogy, is someone who helps out the President with the details of their duties. In the U.S. government there's only one Vice President, but many corporations have dozens. Google's tripartite leadership, with Eric as President & CEO, Larry as President of Product, and Sergey as President of Technology, was a way of showing that all 3 of them were in charge, and actual leadership rested with the triumvirate. If Larry had been VP of Product (a title actually held by Jonathan Rosenberg), it would've put him subservient to Eric, which is not how Google's leadership was actually structured. The reason most companies don't do this is that it's usually a really bad idea: having multiple bosses typically results in the destruction of the organization. Google could get away with it because they were so far ahead of the competitors and so profitable that having Larry & Sergey running around sponsoring crazy innovative products did not seriously impede the running of its normal business. It also speaks extremely well to the working relationship among the triumvirate, and Eric's humility in leadership.
- arbuge 7y agoI think this is the correct approach. The full-stack hacker building the MVP is the lead technical guy in the first stage of the company when formal titles have yet to be defined. That person should probably become CTO in the next stage, unless he/she is just plain lacking/disinterested on the vision front and wants to remain involved in the minute details of the product (which is not uncommon in my experience). When they become CTO, a VP Eng should be hired to take the MVP to the next level in terms of process, security, and scalability. Assuming they remain an individual contributor (the "not uncommon" scenario I refer to above)... well that means the organization might have two vacancies going forward to fill instead of one.
- harryh 7y agoThe default result for a startup founding engineer who gets "kicked upstairs" into a CTO role is for them to end up with no real responsibilities and end up leaving the company in ~12 months. Happens all the time. Using Google as an example for how things should work is generally a poor idea due to the huge outlier nature of the company.