Live data from Hacker News

Flexport CEO resigns a year after joining logistics company

geekwire.com

31–40 of 160 posts

Re: Flexport CEO resigns a year after joining logistics company

#32

Good for them. Dave Clark is a stain on humanity. Horrible horrible human.

I'm curious, what's the story behind him?

I heard him talk at a conference once and thought his insights were somewhat benign for someone in his position, but he didn't strike me as evil. Just uninteresting, I guess.

Re: Flexport CEO resigns a year after joining logistics company

#33
I'm sure there's some juicy details behind the curtains, but people are too professional to air it publicly. Here's some fun but baseless theories:

1) Typical big-company guy fails to adapt to startup life. A year ago, Flexport's tech team was 400 people. That's minuscule compared to what Dave's used to at Amazon. He came in, insisted on a bunch of unnecessary hiring, bloated the tech team with deadwood, internal kingdoms and politics, and a "move slow and don't break anything" mentality. Founder got fed up and showed him the door, though presumably they were gracious enough to let him hit his 1-year cliff

2) Almost-CEO-of-Amazon tries to build the next Amazon. Makes a bunch of wildly risky investments into random moonshots, because he doesn't want to settle for a single-digit-billion company. Founder is initially taken in by bigshot's vision. But after 1 year of minimal progress and changing market conditions, founder tells CEO to get back to basics and focus on freight logistics. CEO decides that's not sexy enough for him. Waits for his 1-year cliff, then resigns

Exited to hear more wild theories from others.

Re: Flexport CEO resigns a year after joining logistics company

#35

"resigns" Even in the letter he shared himself he said the founder didn't see eye to eye with him, he 100% got fired. This is also the typical process at Amazon when directors and about are fired, they all "choose to leave to refocus on family".

At this level and in this industry there is really no difference unless you’re basically retiring

Re: Flexport CEO resigns a year after joining logistics company

#36
post #33

I'm sure there's some juicy details behind the curtains, but people are too professional to air it publicly. Here's some fun but baseless theories: 1) Typical big-company guy fails to adapt to startup life. A year ago, Flexport's tech team was 400 people. That's minuscule compared to what Dave's used to at Amazon. He came in, insisted on a bunch of unnecessary hiring, bloated the tech team with deadwood, internal kin…

[deleted]

Re: Flexport CEO resigns a year after joining logistics company

#37

Earlier quoted context omitted.

This is the scariest part of the whole article “during a presentation they said took months to prepare.” This sounds like what I would expect in the federal government or IBM. Not a fast growing startup changing the world. I hope Ryan can change this part of the culture or they are dead.

Lines up with the sentiment about Flexport being a tech retirement home

Pretty provincial attitude probably propagated by some overpaid MAANG bro who doesn't realize that there's an entire industry of tech folks out there who aren't making $300K/yr TC. So if you are making that . . . a little humility is in order.

Re: Flexport CEO resigns a year after joining logistics company

#38
The thing to keep in mind is that they have competitors still eating their lunch while running 40+ year-old COBOL backends which have their IS departments tearing their hair out regularly.

It's as if the efficacy of a business isn't completely positively correlated with the coolness of its tech stack. I work for one of their competitors, and I'd kill for their tech stack. But ultimately their business revolves around a bunch of professional logisticians and customs brokers being able to execute reliably and effectively, and all tech can do is enable this. I wonder if they realize this.

Re: Flexport CEO resigns a year after joining logistics company

#39
post #29

hopefully by now companies realize parachuting in ex-AMZN employees is a recipe for disappointment, esp in terms of cost relative to work output

Depends on the intent. I don't know Flexport's situation, so I can't say this is what happened. But, it's pretty common to parachute in outsiders to do the terrible things you want to do (layoffs, big policy changes, etc) that you know will have an adverse effect on morale. Then, once it's done, you boot the outsiders and commiserate with the masses..."yeah, sorry, clearly that was a bad idea".

Re: Flexport CEO resigns a year after joining logistics company

#40
Sounds a bit like the very common story, "We hired this STAR EMPLOYEE from BIGCORP to do BIG things and it was a DISASTER! Help!"

I have often thought about this throughout my career, both being in the reporting chain of said star, and once being that star. The fundamental thing is that a persons performance in a role is much less under their own control than even they often expect. So why is that? Especially in management roles?

People have a reputation that permeates the organization they lead. It will have plusses and minuses, fans and haters, but generally there is a tremendous amount of context about how they lead and how to interpret their actions. There is also a tremendous amount of history about their choices and how they have dealt with both good and bad outcomes from their choices.

Additionally, people who have been in an organization a "long time" (years) and especially if they have "grown up" through that organization, have a really solid network of other folks they can turn to who both know what they can do, and understand what they are asking.

When you change jobs there is a "honeymoon" period where what you do, or don't do, can always be ascribed to "they are new here." It is imperative that new leaders use this period to "course correct" to get to a point where they can effectively lead the new organization they are leading. This is the most important thing they need to do in their first 100 days. Even if you are dropped into a complete dumpster fire, understanding how to "wield" your organization is critical if you want to actually address the fires. On at least one occasion I watched a VP Eng parachute into an org and flame out horribly (even though they had the chops to get the job done) because they focused on "getting things back on track" before "getting to know the organization."

If you work for someone who is new and "previously experienced" (which is to say they got their experience somewhere else). Helping them learn the ins and outs of the organization will benefit both you and them. You because you won't be subjected to obviously stupid decisions which are only obvious if you know how the organization works, and the "new guy" (assuming they aren't a sociopath) will appreciate your efforts and look favorably on your future inputs.

Post reply on HN