Choosing the right place to work can change your entire career as a developer.

Choosing the right place to work can change your entire career as a developer.

Below, I share the story of the person who hired me at Splunk.

PJ was the one who hired me at Splunk and one of the best managers I've had in Silicon Valley.

From the very beginning, he understood something that many developers ignore:

salary matters, but it’s not optimized just by looking at current compensation.

He chose complex projects,

uncommon stacks,

and real scalability problems.

Not because they paid more that year,

but because they paid better in the long run.

For years, he worked on critical infrastructure,

systems that very few people knew how to handle

and that forced you to develop judgment, not just write code.

Those kinds of decisions do two things:

• They make you much more valuable in the market
• They allow you to negotiate your salary better later

PJ didn’t become valuable because of a title,

but because he was hard to replace.

Later, he ended up at Brex, where he had started in 2018.

Brex was sold for 5.5B.

Is this a case among a million?

Yes.

But the lesson isn’t about copying the outcome,

it’s about understanding the pattern.

Choosing the right place to work isn’t just about:

• how much they pay you today
• what stack you’re using now
• or what company you can put on your resume

It’s about thinking of:

• how much you’ll be worth in 3–5 years
• what types of roles you’ll be able to negotiate
• and which companies will want to hire you later

Many developers focus only on immediate salary

and unknowingly close future doors.

I do talk a lot about salary, yes.

But always from this idea:

A high salary is a consequence of good career decisions, not the other way around.