Live data from Hacker News

On Becoming a VP of Engineering

honeycomb.io

181–190 of 400 posts

Re: On Becoming a VP of Engineering

#181

In my experience ICs make product, managers make people, directors make process and VPs make policy. Everyone over that is an approval step in budget requests.

I like this framing a lot, but it seems to conspicuously miss who makes "strategy"? Assuming policy != strategy

Unless you're making a subtle joke that, nobody makes strategy... Which if so, then kudos for a nice joke

Re: On Becoming a VP of Engineering

#182
post #15

I found this part amusing: "Charity [company founder] has a more intuitive, spontaneous style, often shines brightest in a crisis, is allergic to checklists". It looks like an almost inadvertent admission. In other words, the founder doesn't have the qualifications or characteristics that the underlings assume they need to be in a leadership position. I automatically become CEO, CTO, etc., by starting my own company,…

> They choose themselves for leadership, and then they choose their friends as the first employees.

Could probably change that to "choose people they trust as first employees"

Re: On Becoming a VP of Engineering

#183
post #172

Earlier quoted context omitted.

> Just like with founders: the market is the ultimate arbiter. > The part that's ridiculous is to claim that the founders of successful companies haven't earned their position. "The market is the ultimate arbiter" is the exact opposite of the idea that you need the perfect résumé and experience to get and do the job. That's what you seem to be misinterpreting about my comments. A retroactive assessment of someone's t…

> There's no reason to believe that this is true, other than the meritocratic article of faith that the most money and power always go to the people who work the "hardest", whatever that means. And the observations of ~everyone who has done both. I've done both and starting a company is way harder.

[deleted]

Re: On Becoming a VP of Engineering

#184
post #155
post #137

Earlier quoted context omitted.

> The actual people who succeed by not running the company in the ground are the engineers This typically just isn't close to true. If you are in a tech based business, having competent engineering is table stakes, but that's not enough by itself.

If the CEO walks the company can very reasonably find another stiff in a suit that can run the show. Maybe at a slightly slower or more conservative pace but life moves on. If 80% of the engineering team walks your company catches fire and burns to the ground. The greatest case study we've seen is Twitter. Everything above contributor level is some varying degree of spreadsheet monkeying. Anyone with 20 years of runn…

I've much rather bet on a company with a great CEO and mediocre developers than one with a mediocre CEO and great developers. If you're building the wrong product it doesn't matter if Carmack or Linus is writing the code the company will fail. And judging from the code and technical competence I've seen, it's isn't uncommon for a company to succeed with mediocre devs

> You can teach most engineers to sell, lead, and plan.

Have you run a large company? I've run a small one so was forced to learn all of these skills, and let me tell you, it was hard, I found it much harder than learning how to code.

Re: On Becoming a VP of Engineering

#185
post #155

Earlier quoted context omitted.

If the CEO walks the company can very reasonably find another stiff in a suit that can run the show. Maybe at a slightly slower or more conservative pace but life moves on. If 80% of the engineering team walks your company catches fire and burns to the ground. The greatest case study we've seen is Twitter. Everything above contributor level is some varying degree of spreadsheet monkeying. Anyone with 20 years of runn…

I'm an engineer in a sales team, and my experience has shown that most engineers are terrible at selling... Not necessarily because they can't be taught to, but because they don't *want* to. Also if marketing isn't bringing in prospects, sales isn't closing deals, the UI isn't designed right, the documentation sucks, HR hires idiots ... I guarantee you the company will fail, even if it has the best engineering team.…

> tech company engineering has to be good

As much as I want this to be true, I don't know that a requirement. I think a quick test is asking yourself "Is the engineering good at every successful tech company I've worked at?" and given a sufficiently long career I don't think the answer to this is "yes".

Re: On Becoming a VP of Engineering

#186

Earlier quoted context omitted.

> What I’ve noticed is that the code quality from those backend devs is quite awful Without knowing which metrics you use to measure the code quality, my hunch says you are focusing on the wrong thing. I am a frontend engineer turned tech lead. I think we developers choose our focuses based on our personal inclinations and what we value, and usually what I would notice is people who choose frontend work have differen…

There's a few things that stood out to me from that codebase: 1. No unit tests. Integration tests broken weekly when external data source would change. 2. Hand rolled ORM resulting in inconsistent separation of concerns. Some controllers would use the ORM classes directly. Some would add layers of indirection. Some would make database calls directly in the indirection layers. 3. Database data model would "compress" d…

Does not seem like typical mistakes backend developers would make. Perhaps it is rather, that they moved on into leadership, since they found that to be their more effective roles, rather than their output as backend developers? Kind of like admitting, that perhaps it was not meant for them? With these kinds of practices, I could imagine that.

Re: On Becoming a VP of Engineering

#187
post #172

Earlier quoted context omitted.

> Just like with founders: the market is the ultimate arbiter. > The part that's ridiculous is to claim that the founders of successful companies haven't earned their position. "The market is the ultimate arbiter" is the exact opposite of the idea that you need the perfect résumé and experience to get and do the job. That's what you seem to be misinterpreting about my comments. A retroactive assessment of someone's t…

> There's no reason to believe that this is true, other than the meritocratic article of faith that the most money and power always go to the people who work the "hardest", whatever that means. And the observations of ~everyone who has done both. I've done both and starting a company is way harder.

Again, I've started a company, contrary to your previous assumption, and I know other people who have started companies. You don't speak for everyone or even most people.

If climbing the corporate hierarchy is so much easier, then how high up the ladder did you get exactly?

Re: On Becoming a VP of Engineering

#188
There is very little public discussion on the topic, because these roles are lucked into, at best (outside of founders, as people mentioned here already).

Here are the Engineering VPs I have personally met / worked with. These are for billion-dollar-revenue companies (Banking and Health Care specifically)

1. 20-something year old Developer (not senior) who followed a non-technical CTO to a new company and got the VP title before.

2. Architect of a small start up that got bought - right time, right place.

3. Scrum master who was a friend of someone at the company who has no technical background.

Re: On Becoming a VP of Engineering

#189
post #187

Earlier quoted context omitted.

> There's no reason to believe that this is true, other than the meritocratic article of faith that the most money and power always go to the people who work the "hardest", whatever that means. And the observations of ~everyone who has done both. I've done both and starting a company is way harder.

Again, I've started a company, contrary to your previous assumption, and I know other people who have started companies. You don't speak for everyone or even most people. If climbing the corporate hierarchy is so much easier, then how high up the ladder did you get exactly?

I never said you hadn't started a company. I explicitly asked if you had—the opposite of assuming. Nothing in my comment assumed you hadn't.

Since you're unwilling to argue in good faith, we can resolve this.

Re: On Becoming a VP of Engineering

#190
post #15

I found this part amusing: "Charity [company founder] has a more intuitive, spontaneous style, often shines brightest in a crisis, is allergic to checklists". It looks like an almost inadvertent admission. In other words, the founder doesn't have the qualifications or characteristics that the underlings assume they need to be in a leadership position. I automatically become CEO, CTO, etc., by starting my own company,…

I guess that's kind of true. However, once a company involves funding and builds a board of directors full of industry leaders, those same leaders are now on the hook to provide company value in the same way as any other company. In fact, companies have a legal responsibility to not drive it into the ground, or they face potential lawsuits from its investors. Investors do not need to be VCs, and could just be the founders themselves.

However, I do agree with you on another point. At the companies I've worked at, it's the people in the middle of the hierarchy who have impressed me the most. The have incredible hyper fast minds with intimidating levels of reasoning skills. I've always found them to be the true heroes of companies in my mind. They aren't usually there at the beginning and either were hired for their skills, or quickly rose up from the bottom and earned their place.

Post reply on HN