[causehealth101]

Interesting.

What I'm most curious about is the Hiring Manager's POV. Do they, in fact, even want FAANG engineers?

Money aside for a moment, do startups require too much of a transition in culture (small, fast & unpredictable) or skills (more generalist & unsiloed) for FAANG engineers to perform successfully?

[calebkaiser]

I used to work for a technical recruiting platform. I can say that anecdotally, most startups are happy to have a FAANG engineer in their pipeline. If an engineer has the talent level for FAANG, and they want what comes with a startup role, they will generally work out. There might be some cultural ramp up, but it's almost always navigable.

The most common issue I saw around FAANG engineers and startups was actually retention (which is more broadly an issue throughout engineering). Owning a substantial piece of a company is an exciting thought when you first join, but after a year and a half of making 60% of your old salary, in which the startup has had enough ups and downs to make you question whether this equity will ever actually be worth anything, moving on can be very attractive.

[giantg2]

I don't know about those points.

I remember a well publicized story that talked about a startup trying to poach a google engineer (they offered him $1M but he turned it down because Google was paying $3M). So I guess some startups want them depending on the skillset or reputation.

[quickthrower2]

Funny because you poach the Google engineer, and probably they are hamstrung because the startup doesn't have Google's infrastructure. E.g. you are stuck with Kubernetes, not whatever Google now uses. I could understand maybe Microsoft poaching for the long term brain dump value.

[giantg2]

I think they were headhunting him because he had a reputation for being excellent in a technology that wasn't specific to Google. He definitely wasn't just an average employee (Google was paying $3M/yr!).