Startup versus Big Tech: The Good, the Bad, and the Ugly

Published on Last Updated on Estimated Reading Time: 5 min

I’ve spent about two decades bouncing between startups, Big Tech, and everything in between. Recently, someone early in their engineering career asked me which path they should take.

My answer was the same as it is for most engineering questions: it depends but this is what I would do.

Both environments have completely different dynamics. They reward different styles and need different skills to be successful.

Here’s my honest take on the good, the bad, and the "ugly" of both.

And if you just want to know what I’d personally do, you can scroll to the end. But I'd urge you to actually figure out what works for you.

The stage of business determines what game you are playing in the first place: what the job will be like, who will be successful in it, and the mix of risk and reward you are accepting. So start there.

Dan Hock

Startups: The Good

Ready or Not: You learn fast

There is no - I don't know how to do that.

Startups are amazing places to learn a lot of different things quickly. Because the company is small, there usually aren't specialized teams to hand things off to.

You jump in where needed, even when you don't have a clue what you're doing.

At First AML, I touched everything: backend systems, developer tooling, processes, just whatever needed to be done. That kind of environment broadens your expertise incredibly fast.

Visible Impact

Startups are flat. You can influence the direction of the product, push back on decisions, and see the result of your work in the hands of real users quickly.

You know everyone.

Startups are tight-knit in a way that larger organisations can't replicate. It’s easier to feel a personal connection when you aren't just Employee #10,402.

Startups: The Bad

Learning is Self Directed

The flip side of "you learn fast" is that there's often nobody to learn from. When you're stuck, you're mostly stuck alone. No senior engineer who's solved this exact problem before, no internal documentation, no established way of doing things. No mentors. You can pick up bad habits without realizing it.

Compensation is… aspirational

Startup Equity is Monopoly Money

Base salaries are lower. Bonuses are rare. Stock options sound exciting until you realise that you need an IPO to see any of it.

Most exercise windows are short enough that leaving early means walking away from everything that you are "promised". You have no control over dilution or what kind of exit the company pursues.

Startups: The Ugly

Money Problems

Several startups I worked at had payroll problems. Salaries were delayed for months on end.

Holidays were cancelled because of a deadline that had to be met or the company would fold. It wasn't pretty.

Most of them fail

This is not a hot take. Startups fail. The earlier they are in the lifecycle, the higher the risk. You can do everything right and still find yourself out of a job because the runway ran out.

You might have little to show when the company folds.

Big Tech: The good

Career rocket fuel

Having a big name on your CV opens doors before a recruiter even looks at your skills. Your skills and expertise is assumed.

You learn a different kind of discipline

Big Tech teaches a different kind of engineering: depth, rigor, and long‑term thinking.

At Atlassian, the scale alone was an education. Established practices, specialized teams, engineers who’d solved hard problems before.

I learnt how to build systems that survive millions of users and thousands of edge cases. You learn how to plan and how to operate inside a complex ecosystem where different teams have their own roadmaps and commitments.

The money

Money is not the limiting factor.

Big Tech pays pays extremely well. Base salaries are high, bonuses are common, and equity is actually worth something. Perks feel unreal.

If financial independence or having shiny things is a goal, this environment makes it a lot easier.

Big Tech: The Bad

A small cog in a big machine

It can be genuinely hard to see how your work connects to anything that matters. You can ship something used by millions and still feel that you didn't move the needle.

Everything takes longer

A straightforward change can take days. Stakeholder approvals, code reviews, teams in different time zones who own different parts of the system all contribute. You will spend a non-trivial amount of your career waiting.

Growth can plateau

Progress isn’t always tied to ability.

You can be the best engineer on your team and still find that the path forward is unclear.

Big Tech: The Ugly

Performance reviews create strange incentive

Doing work that results in a great performance review is not always the same as doing work that best helps the company.

Individual impact is what gets measured, which makes it genuinely difficult to do work that benefits the broader organisation without also making sure it's visible enough to count for you personally.

Doing great work that benefits the company but doesn't "look" like a big individual win can actually hurt your career.

In the most pathological companies, work is created primarily so that someone more senior can demonstrate impact and get promoted, not because it's the right thing to build.

Switching Directions

The pay cut might be hard, but the loss of structure is harder.

The common path is startup to Big Tech, not the other way around. Big Tech teaches you how to build at scale with lots of support. Startups need scrappiness, breadth, and comfort with chaos. Big tech skills don’t always transfer cleanly.

What would I do?

If I were early in my career and had both options, I would take Big Tech.

You can always leave for a startup later. You can't go back and add the name to your CV.

While it wasn't exactly "Big Tech", this is why I joined Perot Systems after graduating. It signaled to future employers that I had the skills to be hired by a recognizable company. It was a stamp of approval.

A year later, I left to follow my passion - making games. I took a massive pay cut and joined a games company. Not a startup in the purest sense, but it had all the same problems: a tiny engineering team and constant payroll issues.

I could take that risk because I had Perot Systems on my CV. It provided me with a safety net and derisked that decision for me.

So which should you choose?

If you're early in your career and havent worked for a recognizable company yet, take the opportunity when it comes. It makes every future job hunt easier.

But don't stay so long that you forget how to hustle. They are called golden handcuffs for a reason. I know people who stayed so long they now struggle to move anywhere else except for maybe another big company.

Once you have some experience, optimize for learning over compensation.

The environments where you're slightly out of your depth are usually the ones that move your career forward fastest.

I grew more and learnt more things at First AML than anywhere else.

Conclusion

The sweet spot is somewhere between understanding the discipline of a large organisation and still being able to build something from scratch.

Where are you in your journey, and which way are you leaning right now? Do you prefer the stability of a big company or the excitement of wearing ten different hats at a startup? Or are you just there for the free snacks?