Hacker News Reader

Comment by amacasubstack | Hacker News Reader

My main trick has been to specialize in things that all companies like a lot (AWS, js, python), jumping gigs, and leveraging Remote Contracting networks [1].

To get to ~200k remote salaries is hard, but not impossible if you make clear what kind of business leverage you bring and what responsibilities you can take.

In addition, you might not actually need such a high Remote salary if you choose to live in cheaper towns. You don't need a $200k salary if you can make your $120k feel like $1M by living in the countryside.

[1] "How I got wealthy without working too hard": https://amaca.substack.com/p/how-i-got-wealthy-without-worki...

View on HN

Interesting point, would you say it makes more sense to focus on adopted technologies rather then interesting ones in thier growth phase?

Concrete: I learned React a while ago but find Svelte interesting and think it has potential. I am no SWE but interested.

I'm in that $250k range. When I'm looking for a new gig I would much rather have skills that 100 companies are hiring for than skills that 5 companies are hiring for.

That said, I do need something to differentiate myself from any other rando they might hire for less. That could hypothetically be a niche technology. I once met someone who specialized in making databases of 3D artifacts. He made a ton of money bouncing form one defense contractor to another creating their object databases for simulation purposes. That's the "niche knowledge" path.

In my case, that's soft skills. I'm a great communicator with a history of using those skills to land big project successes. In particular, I don't make the business people feel dumb when I explain technical things to them, and being a small business owner myself I have a better balance of understanding between business needs and technical needs compared to most devs.

Not OP but I have a thought here:

For engineers early in their career, I'd say you probably want to focus on tech that is adopted but not generally viewed as heading towards obsolescence (React or Java are in this category, for example).

Mid to late career it can be smart to latch onto tech in its growth phase if you believe in it. For example if you were early on the Kubernetes train and managed to build those skills well you're worth a lot of money right now. Actually making that kind of judgment call probably isn't smart when you're junior because you're unlikely to have the kind of experience and instincts to consistently pick winners.

Wow, I love the preamble there. So nice when successful people don't do the "I am a self-made man, I started out squeezing loose hydrogen and oxygen atoms to create my own water" routine.

Great article.

That article's thread: https://news.ycombinator.com/item?id=29267070

Reply on news.ycombinator.com