Hacker News new | ask | show | jobs
by pro-duct 2631 days ago
The hard part of engineering isn't the ability to glue packages and microservices together. Those tasks are literally done by entry level, bottom of the totem pole engineers. You're saying that all bankers do is run models and spit out valuations, and all a chef does is put stuff in a pan.

I'm not speaking toward your argument of a bubble bursting, but engineering isn't going anywhere. And where else would an entry level engineer start than at the bottom, npm installing the package that solves their problem? It's using these concepts every day that builds good engineers who think of tomorrow's solutions, and can architect it both technically and socially. That is the line between software development and computer science.

Engineers paid under 120k that whine aren't doing anything beyond their immediate usefulness, i.e. 'just doing their jobs.' The engineers that get paid 300k are usually the ones running the show, and writing significantly less / no code.

2 comments

$300K to live on the west coast is really not that appealing to someone who is living in a major city, with the stereotypical house in the burbs in a good school system with 2.1 kids where on the higher end you can make $150K to $160K as an architect/team lead/principal. Especially if you are married with two incomes where you can easily put the lower income completely toward increasing net worth or cash flowing your kids college expenses.

Engineers getting paid $300K could easily be the stereotypical r/cscareerquestions “learn LeetCode and work for a FAANG” type graduating from college.

I think you are perhaps too focused on the immediate salary, and not thinking long-term.

Yeah, $300k in the Bay Area isn’t that much. But if you work for a Tier 1/2 company for a few years, it can have a drastic impact on your future employment prospects and salary levels. Furthermore, the street cred can open many doors that otherwise would remain closed to you.

I think my reply would have had more context in response to a sibling reply made by another poster:

Consider the scaling factor for salaries; My salary is on the high end in my area, but would be on the low end of a living wage in the Bay Area. My salary is in the neighborhood of 120k; I'm a senior-level engineer with almost a decade of experience...

So think about the trade offs. If you’re young and single, the tradeoff between a one bedroom in a major city anywhere not on the west coast and the west coast and the difference in the salary you can make is well worth it.

In most major cities a junior developer will make $60K and can probably find an apartment for $900/month in a decent part of town. If they work on the west coast and get $250K and find an apartment for $2400K/month, that’s a tradeoff worth making.

10-15 years into your career, you may already be married with kids. That $120K he’s making can easily buy a 3000 square foot house in the burbs, brand new build, great school system and close to work for $350K. This is from personal experience (not the salary, the price of the house). Now that tradeoff between $150K and $300K-$400K doesn’t look so appealing when you can’t live nearly the same lifestyle on the West Coast that you could live on much less money

If he’s like me, he’s probably built a local network where any door he wants to open locally is probably already open to him.

In my case, I’m 45, but because of $bad_life_decisions, I only started taking my software development career seriously a decade ago. But I do have a great local network, skills that match what the market demands and the house in the burbs with the wife, the white picket fence and 2.1 kids.

I don’t really need new doors opened to me. As soon as the youngest graduates and I’m willing to travel, I am already in the position of being a high earning “consultant”. Not bragging, I have been working over 20 years, I should be able to consult somebody

> Furthermore, the street cred can open many doors that otherwise would remain closed to you.

The assumption here is that technical screenings actually work. As many here have pointed out, technical interviews today are highly capricious and pretty have no correlation with actual technical qualifications. "Street cred" and even superb interview performance don't seem to matter anymore.

I’ve found that people who work for large companies are often not a fit for smaller companies. They may be good developers, but most of the time they come in with prebuilt infrastructure, processes, separate departments to handle the infrastructure parts etc.

Most small companies I’ve worked for, I’ve had to go back and forth between every layer of the stack - currently including the infrastructure set up. You just don’t get your hands dirty with multiple parts of the stack at a large company.

DING DING DING.

I've seen quite a few people only focus on the $300k aspect in HackerNews (and made negative remarks) without thinking about the trajectory.

Anyone who is making $135K+ in any city that is not on the west coast or NYC, is probably 10 years into their career and may already have a family. In that case, they probably don’t want to make the sacrifices needed to go from making enough to live an upper middle class lifestyle - ie the nice house in the burbs to downgrading to a small apartment.

In my case, I’m 45, why would I move to the west coast for $300K when I can just stay in $major_city and work for a consulting when my younger son graduates and can make $180K-200K+ and still have the same lifestyle?

And then go back to being just a developer anytime I wanted to and still live comfortably?

But you're assuming with 10-15 years of experience you're stuck at 250-300k.

People who advanced in their career at Bay Area can make 500k or more (IC, not management), solving challenges that did not exist in the first place too (that alone might potentially put you in top 1-5%?). There are more startup opportunities (whether IPO or just the technical challenges, that's up to you) with higher chances of success.

Different people have different goals.

I’m not denying that different people have different goals. But if you already are living a life free from worry, can work part of the year, doing what you enjoy, paid off house, what’s really the difference between 2 million and 15 million? (not saying I am there yet).

It’s not like I go to work everyday hating software development and hating what I have been doing since I was 12 years old. My wife works for the government and we have guaranteed access to health care whether she works or quits tomorrow.

I can have technical challenges and jump from opportunity to opportunity in two years once my youngest graduates.

Outside of the west coast/HN bubble, people retire comfortably all the time with a million in the bank, I paid off house, and social security.

Consider the scaling factor for salaries; My salary is on the high end in my area, but would be on the low end of a living wage in the Bay Area.

My salary is in the neighborhood of 120k; I'm a senior-level engineer with almost a decade of experience, involved in some of the high-level planning tasks you describe.