Your fellow reader Samuel asked a pointed question and I thought my answer could help you too.
Samuel asked how much I make and I answered – 213k + equity – then the bombshell:
I must say that seeing your skills and your experience, I would have expected way more. Are the Netflix senior engineers who reached 600k$ TC last year really better than you are?
Better at solving Netflix-sized problems? Yes. They have hands-on practice and I have an abstract understanding of the problem space. Experience wins.
Better in some vague notion of engineering goodness? Eh probably not. On average we're all about average.
The more interesting question is a layer deeper: Why aren't I working in BigTech? Why isn't everyone, if the money's so good and the coasting so sweet? Rest and vest is a real thing that happens.
The short answer – I don't think I'd like it.
BigTech is the quintessential job job. Every movie you've seen about the soul-crushing grind of corporate, that's BigTech. They like to pretend they're fun little startups, but they aren't.
Individual teams can be fun. Whole departments can be exciting rocketships. But the 50,000+ employee behemoth as a whole? Nah that's a corporate grind machine.
I have friends who work for and with these big companies. They always talk about the money, the awesome benefits, the wonderful perks, that cool coworker or two, ...
You know what none of them has ever said? "I love my job".
When talk gets to the job itself, they either shut up or complain a lot. Everything takes forever, the projects are dumb, the pressure is arbitrary, the stress is unnecessary, the impact is smol, and the meetings oh god the meetings.
A designer friend of mine recently spent an hour in a high level leadership meeting with 10 VP level people ... arguing over the exact shade of blue to use for a cartoon character's shirt. 🙄
Not my cup of tea.
As organizations grow, so does their overhead and bureaucracy. What works to coordinate 5 engineers in a room is different than what you need for 5,000 engineers across 3 continents.
I've heard from engineers at big companies that many of their deliverables are ... documents.
You have an idea and you write a proposal document. Then you have a few dozen meetings to collect feedback. Nobody reads or edits the document. Too busy. You re-explain everything you've written in this document to everyone.
You update the document with their feedback and your evolved understanding of the problem. After a few weeks you have an air-tight solution designed on paper.
Management takes a look and says "That's nice, but not a priority. We'll think about it in Q3 2027". Polite office speak for never.
I like to get shit done. Understand problems by creating solutions. By the time I'm done, I want the problem solved, not described.
Strategic Doing is a great book on this topic. Do things, don't just talk about them.
Tech compensation is funny. Yes there's engineers at Netflix and friends making 600k in "total comp", but that doesn't mean 600k hits their bank account.
Here's a screenshot from Levels.fyi for software engineers in San Francisco
Pretty representative based on what I've heard.
Look at the cash component – 164k, 218k, 219k. That's the number hitting your bank account. For a software engineer this component tops out around 250k no matter how good you are.
Now look at the equity component – 36k, 250k, 160k. That's the funny money tech uses to attract talent and tie your success to company success. Incentives aligned 💪
I call equity "funny money" because its value changes. Many companies give you a grant based on current stock price. You have to wait N years (that's how they keep you around) before you can sell.
When you sell, you hope it's worth more than when you got it. But it could be worth less.
I have a friend who used to sell his falling stock every month to pay rent. It was worth less long-term than his cash salary.
If you got a 400k Netflix grant in January 2021, it is now worth 218k. Ouch. But if you got the same grant in January 2017 and haven't sold, it is now worth 900k. 🤔
That's the gamble.
At pre-IPO startups it gets even funnier. You get equity based on latest valuation and you can't sell. It's all fake paper money in a spreadsheet that you can't use. Many companies even block sales on secondary markets lest you get rich sooner than the investors do.
As Nassim Taleb says – the best strategy is to cap your downside and maximize your upside.
If you're gonna pay me enough cash, then I want the biggest possible lottery ticket of equity I can find. That's early-ish stage startups.
Plus the work is more fun.
But as my experienced manager likes to warn: There are more ways for your equity to be worth nothing, than for you to get rich. Make sure you love the job now.
Continue reading about "If you're so good, why aren't you making 600k at BigTech?"
Semantically similar articles hand-picked by GPT-4
- Should you work at a startup
- What if engineers were paid like athletes
- Pay yourself first
- Are you the engineer who scoffs at high salary numbers?
- Why you should talk about engineering salaries
Get promoted, earn a bigger salary, work for top companies
Getting that senior title is easy. Just stick around. Being a true senior takes a new way of thinking. Do you have it?
Get a free chapter from the Senior Engineer Mindset book and a sample audiobook chapter, followed by a Senior Mindset 101 email course.
You'll get insights to apply at your work right away.
Senior Mindset Book
Get promoted, earn a bigger salary, work for top companiesLearn more
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️