5 ms·
> Ultimately I ended up with a bunch of highly paid employees who don’t know how to do anything but to “build and lead amazing teams.” I've worked at a lot of
by Aurornis 3y ago
> Ultimately I ended up with a bunch of highly paid employees who don’t know how to do anything but to “build and lead amazing teams.”
I've worked at a lot of startups. The worst of them were led by people who list things like "organization design" and "build and lead amazing teams" on their LinkedIn.
At the most dysfunctional company, the ex-FAANG CTO would take key job descriptions and add the requirement that they must have FAANG experience. This created a glass ceiling where the early employees, non of whom had FAANG backgrounds, were unable to be promoted. Instead, we got a lot of ex-FAANG VPs and Directors who didn't know how to function at a startup. They were told to lead teams of people who knew the business inside and out (because they built it!) yet they could barely function outside of a big company themselves. Every meeting would be a competition of stories about "At Microsoft we did this..." or "At Facebook we did that..." because playing the FAANG card was the only thing the CTO liked to hear.
The only non-FAANG person who thrived at that company was the single worst leader I've ever reported to. He is a LinkedIn influencer with his own newsletter where he talks about, among other things, his expertise in "Organizational Design". Yet the organization he designed was completely dysfunctional because he ignored how the business worked and instead hired arbitrary numbers of people according to some book he read. Half of the people at that company were 90% idle, while the other half were working 80 hour weeks because the "organizational design" person had strictly assigned responsibilities to arbitrary teams in a way that didn't account for how the business actually worked.
The next line from this post is exactly how he responded to every problem:
> Imagine you hire someone to scale an area and their solution is to divide that area into 5 sub areas and hire someone for each of them to figure it out, etc. that’s their solution.
He was never accountable for anything because he always had someone under him to blame.
- ethbr0 3y agoI interviewed a guy the other day. CS degree. "I have a proven track record of building and leading amazing engineering teams." "Okay. What's the difference between a character and a string?" *crickets* We all have our specialities, but jesus ¢@&#ing christ: if you're interviewing for an engineering role, of any sort, you should be able to answer basic questions.
- yieldcrv 3y agoThe bytes it takes up and how it can be cast? What answer would you be looking for
- F-W-M 3y ago"Strings are sequences of characters" or sth. like that.
- yieldcrv 3y agooh ok, I tend to overthink irrelevant questions in interviews
- ineedasername 3y agoThere’s nothing irrelevant about measuring someone’s technical understanding of the very basics at the same time that you gauge their ability to have a conversation about the domain.
- ethbr0 3y agoIt's a grab bag, tell-me-something-interesting icebreaker question. I'm looking for some evidence of the fact that you can differentiate the two in some meaningful way. Not intended to be a gotcha question! Just a quick test of basic CS knowledge to get the candidate comfortable.
- CapricornNoble 3y agoThis makes for frustrating reading, coming from an industry where "Organizational Design" can have extremely serious consequences: the military. A brief case study: Russia's invasion of Ukraine. The argument has been made (and I agree) that much of their early failures stem from not understanding/implementing Unified Command. They didn't have a Joint Task Force Commander who was responsible for the entire Area of Operations. They didn't have an Air Component Commander subordinate to the JTF to ensure all air operations achieved synergy with, and were in support of, the ground scheme of maneuver. Most field-grade officers who have planned and/or executed a major multi-service or multi-national training exercise are familiar with Command Relationship org charts and understand WHY they are important (if that stuff isn't clear, responsibilities get fuzzy when edge cases arise, and then in the resulting confusion/friction....people die). It's also just as important to understand how much of that "big DoD" cruft you can peel away when you are doing small, localized training with a developing nation with....austere practices, shall we say. So I could see adding "Organizational Design" to my LinkedIn....unknowingly putting myself in the same bucket as "hot-air no-nothing ex-FAANG managers". And then no one cares what digital signal processing stuff I could do for them as an IC... :(