FAANG or Full stack devs from startups
There will always be exceptions but the demographics are no better than the general public: if there's 1% in the general population are suitable for startups, then only 1% of FAANG employees are suitable for startups.
I'd never assume anything just because they worked for a FAANG.
BTW I worked at HP and honestly most HP alums I know who were "lifers" would be no more suitable. Only if they were in certain roles and changed jobs fairly often would it be likely they'd be able to handle it.
Rather than looking at the company names, you probably want to look at the quality of the work your candidates did. Was there manager-level experience, did it involve dev ops, was there evidence of growth progression, etc. This sort of stuff matters more.
That's not to say that people who function well with a structured environment aren't useful. Structure is necessary as the business grows out of the start-up phase and bringing in the right ex-FAANG employees at that phase to can help build that.
You might not have the luxury to choose - how many FAANG employees are applying for your open positions and what are you offering them to make the move?
Design your interview process according to your needs. Don't test on knowledge, bur rather reasoning skill according to the type of product. For example, for backend services positions, we set up a debugging problem based on the real world example that we had to go through, and it has been a very valuable tool for screening candidates.
The only way to answer the question is to generalize. There will always be individual exceptions. The pros and cons below mainly apply to engineers who only have experience in one or the other. They are personal observations and definitely do not represent _all_ engineers:
FAANG engineers
+ comfortable with thinking about scale
+ used to being on call
+ less likely to overpromise and underdeliver (consequences are worse at a FAANG)
- less able to work without requirements (they've always worked with a PM)
- used to working with incredible internal tooling
- expect a lot of compensation!
Startup engineers
+ more comfortable with switching stack/technologies
+ happier to pitch in with ideas outside of their team
+ more likely to have been involved in interviewing, even at junior level
- less used to documenting everything
- more likely to resist "formalizing" processes as the startup grows
So, If you're cool with the people that make that happen, then, yeah. Recruit away.
[0] https://www.theguardian.com/technology/2014/oct/02/facebook-....
[1] https://theintercept.com/2022/04/04/amazon-union-living-wage...
[2] https://www.theguardian.com/technology/2021/sep/18/teenage-g...
[3] https://www.washingtonpost.com/lifestyle/2021/09/17/instagra...
[4] https://www.psychologytoday.com/us/blog/encountering-america...
[5] https://www.forbes.com/sites/kalevleetaru/2018/11/23/should-...
I on the other hand don’t mind risk and always valued an interesting, worthwhile job over security.
That seems like the wrong question.
Shouldn't you be worrying about who would be the best fit in your company? Or better yet, who will help you succeed NOW? (And then there's "who can you actually get?" The people you want have options.) In other words, relevant specifics, not generics.
I do a lot of work with early startups and if I'd invested in your company, we'd be meeting right now to figure out whether you're clueless (and what to do about it) or just wrote something that you didn't actually mean.
Found the individual, their attitude and work track record were better signals for fit than FAANG vs. startup dev.
This site might be useful for attracting the right candidates: https://topstartups.io/
The reality is that different human beings, different teams within a FAANG are WILDLY different.
You could take the majority of people that are on my team, and do amazing at a Startup.
You could not do that with the majority of teams we interface with.
It depends.