5 ms·
Both engineers and managers at big tech companies can get by working 2 hours a day. And remote vs on-site doesn't affect that. This has been true since well bef
by paxys 5y ago
Both engineers and managers at big tech companies can get by working 2 hours a day. And remote vs on-site doesn't affect that. This has been true since well before WFH.
As for the location-based pay part, I bet none of the people who were furious about getting "adjusted" after moving out of the Bay Area ever complained about their colleagues in Bangalore working the same amount as them and making 1/5 as much.
- vgel 5y ago> As for the location-based pay part, I bet none of the people who were furious about getting "adjusted" after moving out of the Bay Area ever complained about their colleagues in Bangalore working the same amount as them and making 1/5 as much. That's not just either, even if people didn't complain about it. Sometimes it takes a bad thing happening to someone for them to realize injustice that existed before. I would hope anyone against location-based paycuts within the US is also now against international location-based paycuts.
- paxys 5y agoIf someone is truly in favor of comp reform and thinks that everyone at the company should get paid based on their value rather than where they are located, are they going to be okay with accepting a salary adjustment that is ~50% of the way between Silicon Valley and India wages?
- vgel 5y agoI don't believe this scenario (a reduction in wages) is likely. Here's my reasoning. If a company was paying SV wages to someone, that must be because their labor is worth > that amount to the company. Salaries within SV, not hitting a profitability cap, exist on a supply / demand curve. Companies are rational actors, so they have no reason to be paying their SV employees any more than is necessary. The current pay dynamic for all companies (that I know of) is location-based pay. Either they only hire in one location (so are trivially location-based), or they pay US employees more than overseas employees. Maybe they, like Google, are moving to a more granular within-US system. Now, for the leveling. What mechanism would force a company to pay non-SV / non-US employees the same as SV employees? Possibly a law, maybe a union at a specific company, or simply social pressure from employees of the company. So the facts are: 1) the company can afford SV salaries, 2) that company pays less than SV salaries for workers outside SV, and 3) we assume a leveling event that changes that. Now a company has (roughly) two actions when this happens: bring SV employees down, or everyone else up. In the first scenario: you're an SV employee. You're being paid market rate for SV, and the company announces they're bringing your salary down. You'd quit, right? Other companies aren't doing this, and since your salary was market rate, you can simply hop over to another company in SV that's paying your old, higher salary. There's a coordination problem for the companies here: if they all made this change at once, nobody would move and the SV salary would reduce (at least in the short term). But that would be illegal (see the Apple/Google recruiter ban lawsuits). So instead, they would quickly attrite all their programmer talent to companies who haven't made this move, until they are solely employing non-SV programmers who are happy with whatever the below-SV-market-rate salary is. Which may be fine! Many companies locate outside SV and pay less in comp as a result. But the most successful American tech companies locate in SV (or similar CoL areas, like Seattle), so they must see something to hiring those programmers, even if they're more expensive. In the second scenario: the company brings up the salaries of non-SV employees. This has no effect on you as an SV employee, except perhaps making it easier to get a job in the area, since companies have less incentive to outsource. Now here's a major caveat: companies often outsource easier work to lower-CoL areas, but I think this is a broken / honestly somewhat offensive practice. I think it's OK to pay, say, someone who's main skillset is banging out internal apps using low-code tools less than a senior full-stack engineer with deep performance / kernel tuning experience. People able to do the former are more common than the latter! But companies, falsely and offensively, assume the former = non-US, the latter = SV, and then assign their pay in that way. But why shouldn't someone in SV trying to break into programming be able to earn $40k doing the internal apps? And, conversely, why should a high-skilled engineer in, say, India be forced to move to the US to earn wages at American companies that are equal to their skill? (sans timezone issues, etc., if that's important for the role, which is a separate discussion). If Google can pay an L4 280k in SV, they can afford to pay an L4 in Minnesota, or India, or anywhere the same amount. They wouldn't pay an L4 that much in SV if they weren't worth that much (and, realistically, they're worth much more). Conversely, if Google wants to hire a contractor for cheap, that's fine! That job just shouldn't be tied to location either. Why shouldn't someone in the US be able to take that job, if they want it?
- blablabla123 5y agoAt my first fulltime job my boss and a colleague constantly made jokes that I work too much. Really depends on the company but if it's a corporate it's kind of normal and you might not get any upside unless you work significantly more than on the contract
- iratewizard 5y agoThe people from Bangalore only got the job because they are willing to work for that wage and be a cost cutting center. You think executives offshore to the 3rd world because that's where the quality is?
- brutus1213 5y agoI get a bit annoyed hearing about the 2 hour a day folks. They are probably forcing their peers or managers to take on more work than is their fair share. I'm in management now .. as an engineer, I most certainly used to work over 8 hours a day (probably 12 hours, counting all the time I spent studying to keep up). Now, in management, the hours have actually gone up .. I now have to worry about things my team is doing 24/7, have to deal with a ton of human, infra and organizational issues, being open to meetings at any hour of the day, in addition to staying technical (my direct code contributions have gone down but my engagement with codebase and overall non-code issues has skyrocketed). I am in a large company and do AI research (so work and what I enjoy are the same, and doing cutting edge research is pretty much as hard as it gets). Point is .. when people boast how little work they do, it makes me wonder who is the poor slob who gets to do extra. We are software professionals, and professionals need to act by a certain creed and abide by an unspoken ethic. Maybe this is my immigrant roots showing .. as I grew up, my folks always taught me to make sure I'm worth the salt I'm paid. I certainly have had periods where I was in a funk (especially early on in my career) but when a job just didn't gel, I left and tried to find something more engaging. I certainly don't feel I can coast for a few months. Who the heck are these companies that are so relaxed. Pls don't say FANG (or MANG or whatever). People I know at the senior level work really hard too (from my peers). It could be certain areas of a large company, and it could be for some short period where people can get away with coasting. I don't think this is really sustainable with how competitive today's software landscape is.
- i_love_music 5y agoI will say it. FANG/MANG is as easy as it gets. These companies hire people so their competitors don't, not that the people hired are expected to generate tons and tons of value. It is easy to put these companies on a pedestal, but the more you look into it the more you learn that these companies are HUGE and that finding a team that only requires you to work 2 hours a day is pretty normal. This at least has been my experience and the experience of many friends as senior+ in FANGMA
- paxys 5y agoIf you are constantly working 24/7 despite not getting adequately compensated for it, that's on you. Why blame your colleagues and not upper management?