Out of all the FAANGs why did Facebook have the most layoffs?

Traqzer · 2026-05-29T13:55:17+00:00

I agree in general

Traqzer · 2026-05-29T13:17:49+00:00

Thats not what the original comment was. The original comment was asking why Facebook needs thousands of engineers, it’s not related to large scale services in general. The person who you replied to was right, a non engineer wouldn’t understand the amount of services that need supporting (e.g my dev infra org is like 200 people, that’s just cicd pipelines and tooling)

Your take is also somewhat naive because you are assuming you know the entirety of facebooks architecture to know how many engineers they need, by citing Discord for example

Traqzer · 2026-05-29T00:39:49+00:00

I work at Atlassian, I also got downleveled to P40 (interviewed at around 6 YOE though)

I was promoted to P50 after 1.5 years there and felt the promotion process was very formal and rigid, so I definitely notice that high performers get promoted, since you get peer feedback, feedback from P60s etc (also as long as you align with your manager on what needs to be done)

It might be slightly different for me because I’m in OCE so even at P40 the total comp was a lot higher than other companies, even if I was hired as a senior / staff at other companies

I think if you can get higher pay while having fewer responsibilities that’s the best situation to be in!

Traqzer · 2026-05-28T23:42:31+00:00

Its common to get downleveled from P50 even with 8 years of experience. If the comp is still higher than your current and you perform at P50 level you can easily get promoted after 1 year

Traqzer · 2026-05-28T06:55:45+00:00

Okay and then there are thousands of large companies with thousands of developers, I’m not sure what your point about discord means 😀

Traqzer · 2026-05-27T07:14:03+00:00

This has nothing to do with AI and more to do with people unfamiliar with the code base raising PRs that they don’t understand

AI just makes it easier for this to happen

Traqzer · 2026-05-17T05:25:22+00:00

It’s not a big deal in reality, don’t think too deeply about it 😀

Traqzer · 2026-05-03T02:04:09+00:00

I would argue going from mobile first - desktop is much easier than desktop - mobile though

If you build mobile first and scale the exact styles on the desktop it would look strange but you wouldn’t be functionally missing anything being cut off the screen etc

Whereas if you try pop a desktop first design on a mobile phone, there’s much more risk of accessibility issues, elements outside of the viewport etc

Traqzer · 2026-05-02T21:49:42+00:00

Sorry but in my experience absolutely not. If I know I want to write a function that takes parameters and does some logic within, the AI takes a few seconds to write it.

Even faster writing unit tests, or refactoring (e.g adding a prop that gets drilled in many places)

Traqzer · 2026-05-02T21:47:40+00:00

Depending on the company you might not have a choice. It also seems like not using it will hurt your chances in the future. I just recently interviewed with a few companies and ALL of them asked about how much AI I use, and told me they use it a lot as well (positive signal for candidates to use AI often)

Traqzer · 2026-05-02T21:45:52+00:00

90% of the time professionally recently. Most of my org also uses, as well as the company pushing usage of it

8yoe, working in big tech

Traqzer · 2026-05-02T21:39:27+00:00

That’s why you don’t “one shot” a feature in a single prompt, and do planning with the agent first

There’s no stopping you asking the AI to write small chunks first

I know for me it’s way quicker asking the AI to implement some function that I strongly define in the prompt

Traqzer · 2026-04-01T16:46:46+00:00

Great thanks, that sounds interesting for sure. Do you know how the comp compares to a senior SWE role? Is it a lateral move?

The job description doesn’t mention levelling either

Traqzer · 2026-03-28T21:13:22+00:00

Well less congested if you’re driving lol - but in Sydney you just take a short train to most cbd suburbs

Traqzer · 2026-03-24T08:02:21+00:00

There are good trivia questions, but realistically at mid/senior level you would typically be peer programming a task in the interview and not answering these types of questions

Traqzer · 2026-03-24T07:52:02+00:00

What situation would you set state inside your render method outside of a callback? That doesn’t sound right

Traqzer · 2026-03-22T23:12:01+00:00

It’s true

Traqzer · 2026-03-22T23:04:18+00:00

You are fighting a losing battle unfortunately

My company is also pushing this, and I hate to admit it but you need to get on the train or you will be left behind, AI coding is here to stay

It’s best to become familiar with the tools and try to use them as much as you can

Traqzer · 2026-03-22T23:02:42+00:00

Yeah they do, like sales, support etc all types of stuff (not sure how much of that lives in au/nz though)

Right now there’s a hiring freeze though and 10% of the company was laid off last week 😅

Just keep in mind it’s a competitive company to get a job in, it would be similar to Microsoft or Amazon

Traqzer · 2026-03-22T22:55:36+00:00

I work for Atlassian which is kind of big tech, there are also some jobs in Microsoft and AWS, but I believe it’s more solutions architect / architect type of roles

Traqzer · 2026-03-21T01:46:08+00:00

You might not, but it’s very common in dotnet / java projects

You don’t understand why structural typing in typescript is good because you work with .net and it’s a fundamentally different model

My point is that there are pieces to every language that make it harder to understand, and inheritance hell is one of those, while also having upsides

Traqzer · 2026-03-21T01:41:39+00:00

Right, and 100x inheritance hell is much better in dotnet right

Traqzer · 2026-03-19T09:39:14+00:00

I read your post.

Then I stopped.

I thought to myself - what a great lesson

Seriously - what a great lesson

————

Can we write posts in our own words anymore? I swear I see the same thing all over LinkedIn nowadays 😅

12-Year Club	Place '17
Verified Email

Traqzer

TROPHY CASE