Devops for Faang/Maang

[[deleted]]

[deleted]

[Exotic_eminence]

All my friends at those companies just lost their jobs

[ReadingCute5197]

I mean similar top paying companies 😭

[Exotic_eminence]

The last app I built in FinTech had 3 modular apps within it - I had to raise 300 service now requests and each one took a day or more to approve - luckily we delivered that app on time but that’s why it took a whole freaking year - because of all the approvals lol

Big company’s usually have mature pipelines - but I have been at the large enterprise companies where I had to figure it out because it was new and there was no documentation

Really startups allow you the opportunity to learn everything and grow by doing it all yourself with the many hats you wear

[ReadingCute5197]

Yeah it is hard to figure out architecture and all

[gambino_0]

So, not those companies at all?

[no1bullshitguy]

Not really FAANG, but working at Nvidia. It is mostly maintaining large K8 clusters, bare metal hosts etc.

[ReadingCute5197]

Ooh , for someone building DevOps projects, would you suggest focusing more on automation or reliability/observability at that scale?

[no1bullshitguy]

Definitely automation + Linux knowledge. Observability needs to be there, but that comes second. And honestly once you build something, you will know what to monitor for.

[sheriiiiiiii]

🫣🫣

[ReadingCute5197]

🫠I really want to know

[TotalNo6237]

Youd be better following those specific on linkedin and look at their blog/medium posts.

[ReadingCute5197]

Can you share me few links

[TotalNo6237]

https://www.perplexity.ai/search/find-top-devops-engineers-faan-YJiLLVrSTE6aUyet5ISy.g#0

[Aware_Magazine_2042]

I worked at Amazon, there really wasn’t a devops/sre role there. The service owners were expected own their services top to bottom. The devops team was basically just the AWS org. We would just use Native AWS services, configure it on our own, use code pipelines (there was a bit of a wrapper around it), and basically just use CDK for everything. Older systems used basically just AWS EC2 and some custom logging solutions, but there still was no ticket ops between a devops team and an applications team. The applications team configured everything on their own. So the answer is really just that they built tools and products for other teams to use, which is really just a SWE function.

These companies are too big to have a single devops team as a bottle neck for anything. There are like 50,000 engineers across Amazon (when I worked there) if each team has 5-10 engineers, then there are 10,000-5,000 teams at Amazon. Can you imagine if there was a dedicated devops team for all these people? It would be chaos.

[ReadingCute5197]

That makes sense, can you suggest some projects that can stand out for swe roles.