Hacker News new | ask | show | jobs
by kevin_thibedeau 2102 days ago
The math is simple: Replace a senior salary with 2 H1Bs for (hopefully) 1.5x productivity. 2 weeks vacation, no family, and no health issues makes for the ideal servant.
3 comments

Incoming rant.

Plus the government is in on it. They're effectively handing a subsidy to coporations who can jump the hoops versus those who hire and then train locals.

The pitch goes like this: give the immigrant the promise of America if they just serve the masters for ~10 years (or forever if you're the wrong race of immigrant[1]), keep them subservient by continuously threatening deportation at the loss of employment (short window to rehire). Limit the max number of H1B years to ensure increasing dire circumstance. Don't give them representation (despite taxation) so they can't feedback on the system.

Now, an H1B doesn't have always have all the features of a millenial, such as they usually don't have student debt, but the student visa can fix that.

[1]: https://www.washingtonpost.com/immigration/the-employment-gr...

What could possibly go wrong?!?
Yeah this is it in my experience. It looks like they're optimizing for age, but they're really optimizing for cost and ageism is a side-effect.

I've seen this happen at almost every job I've had: Senior engineer with 10+ years experience works 40-50 hours a week and gets laid off. Senior engineer is opinionated about how things are implemented and can come across as "difficult." Two junior engineers are hired for about the same cost and are pushed to 60+ hours a week. They'll do literally anything you tell them to. Non-engineer management sees a win but then eventually gets mad about codebase issues like it's unrelated, and end up churning through juniors trying to fix it.

Another alternative is outsourcing of course, in which you can end up with a small team for the short-term cost of one senior engineer... and a lot of the same problems with the junior route.

It feels like one of those risk problems where people are happy about the short-term gain but fail to look far enough ahead to see the long-term issues.

Some anecdata to add to the case.

My first job out of school was as a startup founder (10% ownership) where our new CEO was a sales guy from a healthcare company. Great at raising money, but no deep technical knowledge. We were building a music search recommender using mfcc spectrograms and ML. He decided to fire all the engineers and hire out to cheap overseas hotspot. We weren't especially expensive, being young guys, but nevertheless you could get 3 for 1 overseas...

The company shut down a few months after the local engineers left.

I would argue that the entire corporate structure is designed like this. I've seen it in every industry I have worked in, it's a quarter by quarter slog to see some decrease in cost and increase in profit.

It's part of reason that I feel like everyone is looking for that fabled "exit" and building a sustainable business just doesn't really exist..

> Two junior engineers are hired for about the same cost and are pushed to 60+ hours a week. They'll do literally anything you tell them to. Non-engineer management sees a win but then eventually gets mad about codebase issues like it's unrelated

The “lord of flies” cultures these teams become can be astoundingly horrible and toxic. Imagine a lot inexperienced people trying to one up each other, no one providing any direction whatsoever. I happily left one such team not long ago!