Layoffs here are always done in conjunction with the unions. People are moved to different jobs, helped with training etc...
Only in very critical jobs they'd walk you out immediately but then you still get the pay.
People literally would just disappear day to day. I've had several instances where I only found out a colleague had been fired because I tried to write them on Slack only to find that their account had been deactivated
Personally I felt constantly worried working in such an environment and I don't want to work for another US company again if I can help it
There are of course bad cases in the EU, but in my experience it's way less common than in the US
its much easier to find another job in US because of this though.
Most purely European companies don't do that. Actually, unfortunately, some of them do, because of American influence. But for sure they didn't use to.
Now, every job I apply for has 4-5 rounds, leetcode is more common, they do behavioural and system design rounds that you have to prepare for, etc. One job I applied to even asked me two behavioural questions via email before I even talked to someone. Something's truly off.
I personally have interviewed for 7 enterprise dev jobs and I have had 2 coding interviews and those were simple.
What EU regulations hamper isn't job creation, it's employee and customer exploitation. The distinction between "job creation" and "employee exploitation" is important.
What the former means in practice is that there is a massive contractor market in the UK and EU. So if companies need temporary staff, they'll hire a contractor. If they need permanent staff then they'll hire an employee. And contractors in the UK & EU are paid significantly more than their employee peers. In fact their pay is much more equivalent to US employees. So companies will make constant tradeoffs between more expensive labor for short-lived projects vs cheaper staff and knowledge retention but stricter employment laws. It's a fair trade most of the time.
So a more accurate way of comparing US vs EU businesses in terms of employees would be US employees vs EU contractors. Things then begin to look a lot more equivalent.
My job is purely transactional. I’ve worked for 10 companies in almost 30 years. I gave them labor and they gave me money. Whenever one side decided the arrangement wasn’t working, I moved on to another job.
I’m personally well acquainted with many people in tech, especially big tech. Many of them are doing little or nothing, certainly not justifying $300k+ salaries.
What you do has risk but is fundamentally more honest - your skills are around technology and output, not navigating corporate bureaucracy.
There is also COBRA that lets you stay on your employer’s plan. You have to pay the entire premium. I pay $600 a month now and my employer pays $1200 a month. That’s me + family.
If you would work non-contract here in Poland for an equivalent of ~$120k you would pay around $1k USD. If your wife is working she will also pay, of course this also covers all you kids.
So lets say both of you make around $120k here - so you would pay $2k monthly for "free" healthcare and its quality is atrocious. Even for serious stuff you many times need to wait 1-2 years for something, all hospitals are understaffed, the care quality is abysmal.
If you are ambitious and make good money the US is better. Europe in general is better for people that don't aim too high and want the state to enforce some minimum of QoL for them at the expense of the rest.
I don't think most folks graduate college and think, "You know what sounds amazing? Sitting at a desk doing nothing five days a week!"
I expect most of the time they have good reason to be "unproductive," and would respond positively to those reasons getting addressed, or you're not capturing their contributions accurately with whatever metrics you're using to find "slackers."
And people are doing things, I’m not saying they’re sitting making paper airplanes — just things with no value or that drain their value. I had a high school friend who was brilliant, but his career got nerfed when he stuck with a bad tech/business unit.
If you’re the world’s premier expert in some peculiar process that only exists in one place, that’s no mas. Companies have been rolling in dough for a long time and some have way more people than they used to. One big company I deal with went from an account team of 6 to almost 50.
Some of it boils down to ineffective management and lack of mentoring, for sure, and could be addressed in a better way. Some of it is people getting in way over their heads.
I worked at a company where utility companies sent us data files and we created, printed and mailed bills.
In 2008 during the financial crisis the next time I looked for a job (my third), I had two offers relatively quickly - one programming point of sales systems and the other that I accepted programming ruggedized Windows CE devices for field service workers.
Fast forward to 2020 at the height of COVID, I got my one and only BigTech job working at AWS (my 8th job).
Unlike the author of the submitted article, when I got Amazoned 3.5 years later, I shrugged, my $40K severance was deposited in my account and I reached out to my network and targeted outreach to some recruiters in my niche and had four interviews and 3 offers within 3 weeks. Why would I waste time getting emotional about a company knowing that the CEO is 6-7 positions up on the career ladder and I’m just a random number to most of the organization?
A year later in 2024 around 9:00 PM I had a “1-1” with my manager invite for the next morning. I already had my suspicions and told my wife that I am probably going to be laid off in the morning. She said let her know how it goes and we went to sleep.
I woke up the next morning, was notified about my layoff asked when I would get my severance and responded to a recruiter that reached out to me about a week prior.
I started the interview process and three weeks later I had a job making the same as I was making at AWS.
I don’t need to “justify” what I’m making. I have a skillset and experience that are in demand and companies are willing to pay me for it because by employing me they get a positive ROI.
And knowing how to “deal with ambiguity” and focus on how to add business value. If you look at the leveling guidelines of any tech company, anything above mid level is focused on “scope”, “impact” and “dealing with ambiguity”.
Knowing AWS really well is just a tool and it doesn’t hurt that I have a stint at AWS ProServe on my resume
Notice “codez real gud” is not a differentiator.
There is no hard skill you can learn that thousands of of others don’t know that will set you apart.
Well except for some vertical market stuff that will leave you pigeonholed.
Sources:
https://www.levels.fyi/blog/swe-level-framework.html
https://dropbox.tech/culture/sharing-our-engineering-career-...
People in IT who take the employment route rather than contracting, do so because they want job security. eg they might have families. And much as you might be happy with your arrangement, there are plenty in the UK and Europe who do prefer longer-term job security over a few extra £££ in their pocket.
Lots of people, when evaluating the risks of contracting vs employment, find the reward far outweighs the risk. It sounds like you'd be one of them if you were presented with the same choice. And that's a fine decision for you to come to. But that's not going to be the same conclusion for everyone.
Every employee in the US is “at will”.
But you’re right that IR35 really hasn’t helped situations either.
Some of my friends have commented that the last few years has been the worst time in their 20+ years as a contractor.
It forced highly specialised professionals into employment in all but name, just without the rights, security, or support. A square peg jammed into a round PAYE hole. And the long-term effect? Exactly what you'd expect: the best talent either left the UK, shifted to servicing overseas clients (where Chapter 10 doesn't apply), or left the field altogether. The real talent pool shrank, not because of market conditions, but because there was no longer a viable way to operate independently.
To make matters worse, the government compounded this by lowering the barriers to import cheaper labour from abroad ("Boriswave"), creating a race to the bottom on wages, with zero incentives for local upskilling or long-term investment in the domestic workforce.
So yes, the job market took a hit - but IR35 didn't just "not help" - it actively accelerated the decline by removing the last flexible, self-directed model for highly skilled work. The damage wasn't cyclical. It was engineered.
For example:
> People lost the ability to operate as businesses, to manage their tax affairs fairly, to invest in their own skills, and to retain profit.
I don’t know a single IT contractor that lost that ability. Maybe in other business sectors, but we are talking about IT here.
> What they got in return was, at best, a modest day-rate bump—hardly compensation for losing all autonomy, business deductions (like training, equipment, downtime), and legal protections.
This is also an exaggeration.
And you’re overlooking the point that IR35 only affects contractors working on BAU or who have worked with the same company for more than 2 years.
Firstly 2 years is a long time in contractor terms. And secondly, most occasions for hiring contractors was to work on new developments. So most of the IT contractors were still outside of IR35.
That’s not to mention that many companies would describe the work in ways that are favourable to working inside IR35 (not to the extent of tax fraud, but to the extent where any BAU responsibilities that were required weren’t the primary responsibility in the job specification.
Ironically places hardest hit by IR35 were government departments rather than businesses. Some of who ended up just adding ~40% to the contracted salary so the government still ended up covering the tax rather than the contractors.
And the very few contractors who were inside IR35 and didn’t get a bump in the contract fee would tell me they were still better off contracting rather than being employed (even taking loss of perks into account).
Now I’m not going to say that IR35 made things easier for contractors. Clearly it didn’t. But it wouldn’t have been catastrophic for the contract market had the employment bubble not also pop shortly afterwards.
You also seem to suggest that IR35 prevented contractors from claiming expenses back in tax, and that simply isn’t true either.
Edit: I will concede that it’s been 3 years since I was last given a budget and told “go hire, you decide who” so if there’s been any legal changes to IR35 since then I might have missed it.
> I don’t know a single IT contractor that lost that ability.
I do. In fact, I knew dozens of people who ran small, legitimate limited companies - offering high-quality services across IT disciplines - who were forced to shut down or stop trading as businesses once clients tightened their risk assessments. In the early days, yes, some niche contractors were spared because they were too hard to replace. But even that dried up as corporate legal teams standardised engagement models and de-risked by banning sourcing services from small business entirely.
> You also seem to suggest that IR35 prevented contractors from claiming expenses back in tax, and that simply isn’t true either.
This is misleading. If you’re inside IR35 or forced into an umbrella, you can only claim expenses on the same terms as an employee of the client. That means you can't offset training, equipment, home office, insurance, downtime, software etc. - because your business isn't recognised as a business anymore. And if you can't make profit, you have nothing to deduct from anyway.
> you’re overlooking the point that IR35 only affects contractors working on BAU or who have worked with the same company for more than 2 years.
This is based on a fundamental misunderstanding. There is no “2-year” IR35 rule. That might relate to travel expenses. IR35 assessments depend on control, substitution, and mutuality of obligation. Even short, project-based work can be deemed inside. And under Chapter 10, only clients carry the liability - so they default to "inside" for anything remotely borderline, including repeat work.
And that’s exactly the issue: having loyal clients and repeat business — something any serious business would strive for — is now penalised. The system structurally disincentivises hiring genuine small consultancies, because clients now carry legal and tax risk for treating you as "outside." So naturally, they avoid it.
And that quote about companies “describing work in ways favourable to IR35” to avoid falling foul of the rules - you realise you’ve just described a legal minefield that only small businesses are forced to navigate? If an individual or a small consultancy tries to deliver a long-term service or repeat work, they're suddenly in danger of being labelled "too BAU" and dragged into inside IR35 or worse, accused of misrepresentation.
Meanwhile, large consultancies are completely exempt. They can supply entire teams of workers to perform exactly the same repeat, embedded, long-term services - even effectively occupying roles inside the client’s organisation - and no one blinks, because the worker isn't the owner of the delivery company. IR35 doesn't apply.
So what you're pointing out as a "grey area" for independents is actually a core business model for Accenture, Capita, Deloitte, etc. - and it's legally protected. They can pump in as many BAU bodies as they like, make profit to their heart's content, and face none of the scrutiny aimed at smaller suppliers. It's a structural bias against worker-owned businesses and it's about making sure the same work flows through corporate channels, where the big business win - and independent economic actors are locked out.
> But it wouldn’t have been catastrophic for the contract market had the employment bubble not also pop shortly afterwards.
That reverses cause and effect. IR35 was the trigger. It removed the incentive to engage skilled local contractors as businesses. Clients - especially in the public sector - stopped hiring small operators entirely to avoid compliance risk. The result wasn’t just tighter budgets - it was the structural removal of independent contracting as a viable model.
And just as IR35 pushed domestic professionals out of the market, post-Brexit immigration reforms ("Boriswave") made it easier for companies to import overseas workers on lower salaries - with sponsorship pathways explicitly designed to undercut local rates. So the market didn't just shrink—it shifted, away from experienced, independent professionals toward cheaper, controllable labour with fewer rights and no negotiation leverage.
The combination was catastrophic. It collapsed the domestic contractor market from both ends—removing the supply of viable independent businesses, and removing the demand for them by creating cheaper alternatives. That wasn't an unfortunate consequence — it was a predictable outcome of policies designed to centralise control and reduce labour costs at all levels whilst maximising corporate profits.
> Contracting is still better than being employed.
That may be true for a small segment of high-end day-rate earners, but it ignores how many people used contracting as a sustainable, long-term way to build independent businesses. For them, IR35 removed the very basis of that independence-profit, autonomy, and client trust.
Thanks for taking the time to share that.
did you account for rsu value too or just basepay/hours . now that i am a perm employee a big share of my comp comes from rsu.
E.g. the entire I-9 thing and other IRS paperwork, who (if anyone) is responsible for various insurances (unemployment insurance, workers comp, liability insurance, etc), minimum wage and overtime for hourly employees, etc. Many things depend on this distinction.
I can't speak to differences from Europe as I am not familiar with that side of the Atlantic.
In my current position I'm hired for an expected 37 hours per week. This can be more if I'm asked to work overtime, but my weekly hours cannot exceed 45 hours per week on average in a 3 month window without additional compensation
Additionally I have six weeks of paid time off every year plus public holidays
If I calculate my hourly salary it's better than what I was paid by US companies
That's not to mention the security of having a legally mandated termination period of minimum 3 months (in which you're, in most cases, not expected to work)
> If I calculate my hourly salary it's better than what I was paid by US companies
prbly not.
It’s a bunch of copium thinking that American tech workers are working 60-80 hour weeks.
And I know it’s not the norm, but right now I have “unlimited PTO” and most people take at least 5 weeks a year.
If the average American tech worker is making 2x - 4x the average EU worker, they should be able to save more than enough to have a three month cushion.
And we are talking about Google. They have a very generous severance package. Even Amazon where I use to work gave me three months severance.
Though what would also help if you had an explanation for why we tend to hear these stories mostly from the US and not from other countries.
because internet is dominated by 'stories mostly from US'
The only time I've ever been expected to put in those kinds of long hours was in case of an emergency. Stuff like, a natural disaster hit the company's primary data center so they needed to be all hands on deck to get services restored. But it's definitely not common day to day, and even in case of emergencies the company generally gives you a little something (extra time off, a bonus, whatever) to compensate you for the long hard hours you had to work.
I don’t care what the “average” is. I plan on taking 30 days this year.
First link -16 days for unlimited PTO vs 14 days without
https://www.inc.com/suzanne-lucas/ive-been-an-hr-professiona...
Now if you look at where those numbers come from, this article quotes another article from WSJ (https://archive.is/MVRur) which is also titled "Why You Should Be Wary of the Unlimited Vacation Perk". Hmm...
And the WSJ article, in turn, takes its number from this report: https://www.empower.com/the-currency/work/pursuit-of-pto-res...
Now when you look at the survey, the problem with comparing those numbers is that they are averages for all workers. That is, 14 days without PTO is the average across all companies, not just those that had adopted UPTO. And the 16 days with UPTO is, of course, only for those companies. So the numbers don't actually tell you anything about the effect of "unlimited" PTO adoption in a given company. Those companies where 14 days is the norm are generally not the ones that decide to switch to UPTO because, well, there's no actual benefit in it for them. Companies that do adopt it, like many Big Tech firms in the past few years, are also the ones that had much more generous paid PTO to begin with - at Microsoft, for example, as a senior engineer, I had four weeks of PTO before the switch.
So, you need to look at comparisons before and after UPTO adoption for the same company to see the trend. Conveniently, that very article you linked to has some sources for that, e.g.: https://www.bbc.com/worklife/article/20220520-the-smoke-and-...
There are other negative aspects to it, too. For example, when you have guaranteed vacation PTO, it is wholly separate from other things like paid medical leave. But with UPTO, it's that much harder to argue for it to your manager if you have already taken medical leave that year.
I’m not going to look up the PTO for other BigTech companies. But the one I worked for (Amazon) had 15 days PTO and 5 personal days.
And most people who have defined PTO, also don’t take all of their allocated days off.
https://www.pewresearch.org/short-reads/2023/08/10/more-than...
That’s not evidence of defined vs unlimited PTO as a limiting factor of UPTO.
And because of laws in different states, companies with unlimited PTO also often have a separate bucket for sick time.
Does it? Sounds more like an opinion than a fact to me.
There is demand for tech workers, but the output of EU tech companies can't afford huge salaries. Lower margins.
sorry i forgot to add "typically" which apparently is a license to spout any BS .
The ability to hire and fire easily is critical if you want to build successful companies.
There’s a reason ambitious founders move from Europe to the US and why most billion dollar tech companies are American. Europe has made really bad policy decisions around this for decades and their economy reflects it. Europe is poor and to an extent I don’t think Europeans really understand.
Yes, and it's because of larger, more liquid capital markets make it much easier to obtain VC funding.
> Europe is poor and to an extent I don’t think Europeans really understand.
Europe is definitely not poor in terms of either wealth or income (particularly Western Europe, which is the appropriate comparator for the US).
Not really, people get hired all the time that can't do a fizzbuzz.
European companies have very little staff turnover, so new jobs are fewer. Another aspect is that salaries are very even across much of the industry, as it is often negotiated by unions and unless you are also switching roles (e.g. into management) salaries at different companies will be very similar. That is why working for the same company for a long time is much more common in Europe.
Can you specify what country you're drawing these facts from? Europe does not have standard employment law, and I definitely haven't experienced salaries being set by unions or being common across the industry.
There are also union negotiated rates for pay across much of the industry. Even if you switch employer your pay might remain exactly the same, unless you also get promoted and into a higher level or a different industry. "Flächentarifvertrag" it is called.
Obviously this drastically disincentivizes hoping employers.
OK, good to know. I definitely haven't experienced flat income after taxes post salary bump, even though I pay 52% marginal on my income (in Ireland).
> Obviously this drastically disincentivizes hoping employers.
I can totally see that. Is it really that common in tech jobs though? I'd have expected this to be much more common in larger, older companies (like the automotive industry).
What is a "tech job"? Wouldn't a job where you are designing the electrical/mechanical/software parts of a car be a "tech job"?
Of course this is much more common in older, well established industries. But that is where most of the "tech jobs" are. Germany, especially labor laws, are hostile to start-ups so it is natural that people get employed at these older companies with union negotiated salaries.
You can work for a US company in the UE. They have to follow the local rules like anybody else.
Most of my colleagues were shocked by the treatment. Moral took a dive after that.
That being said, if they want to get rid of employees, they always find a way. And the European market isn't as dynamic as the US one, so there are pros and cons. Personally, all things considered (risks of layoffs, PTO, cost of living) I'm happier in Europe but it really depends on individual situation.
One thing that I saw (but never experienced myself) happen with North American companies wanted to leave EU is just doing their usual things (thus not following local rules), and then people have to sue and wait many years to be compensated.
An employee decided to be laid off is equally written off immediately, it's just delegated to the regional/local HR to "manage the rest".
If you're not escorted off-premise, you get to enjoy some additional days/weeks of colleagues and managers telling you how surprised they were...
> where I only found out a colleague had been fired because I tried to write them on Slack only to find that their account had been deactivated
The colleague will just be one that's based in the US, but that doesn't make it much easier.
Lots of US tech companies like to pretend otherwise, but a complaint or two from the misclassified employee can create plenty of pain for the employer for lying to both the US and foreign governments about the genuine nature of the relationship. And these penalties generally go not to the employee but to the employer, since the noncompliance is generally around employer tax, payroll, and reporting obligations as well as laws which are meant to protect employee rights.
But for example, someone who is fired or laid off in a way that wouldn’t comply with local employment protections if the employment relationship were correctly classified might assert their misclassification claim so that they can also get compensation for their wrongful termination.
If that happens, then the company not only has to scramble to catch up on the overdue social contributions for the complaining employee and pay any applicable penalties, but also likely have to undergo an audit of their other workers in that country plus the same consequences for them.
There’s a reason why any US tech company that’s big enough to be a juicy financial target tends to do this correctly, and why companies like Deel, Remote.com, and their less tech-branded competitors (such as Velocity Global) are gaining popularity among people who want to do this correctly at smaller scales than those for which it makes sense to set up foreign subsidiaries.
When smaller companies take this particular shortcut, are risking severe financial consequences for the company if the authorities discover it, and in many cases this also comes with personal liability for some of the executives who are neglecting their legal duties.
If it was legal to work in the office of your only "client" 40 hours a week on a permanent basis, then any EU company could ignore the entire employment legislation of their real country by setting up a shell subsidiary in the US.
> If it was legal to work in the office of your only "client" 40 hours a week on a permanent basis, then any EU company could ignore the entire employment legislation of their real country by setting up a shell subsidiary in the US.
That wouldn't work because it would be an obvious sham designed mainly to avoid the EU company's responsibilities under employment law. Courts see through those shams very quickly.
Technical people -- including me -- like to try and reduce the law to a series of digital if/then/else tests, but reality is much more analogue. If you're one of a small number of highly-experienced remote contractors engaged by a US-based client with no local subsidiary, the authorities are likely to accept the arrangement, or at least not to spend significant amounts of time investigating it. If you're one of very many Uber-driver-like "contractors" working for a company that is obviously dodging its local employment law obligations, then they're much more likely to be interested.
In principle, an organization that is built on reciprocal loyalty is more productive than one that treats people as interchangeable cogs, because people are individually happier and go to greater lengths to achieve the shared goals, making them more productive. However, this arrangement can only be built on trust, and trust doesn't scale well past the Dunbar number. Thus, spirit of the rules is replaced by letter of the rules (which can be meaningfully enforced).
Thus, the larger the bureaucracy, the more soulless it is even in individual interactions between people within it, and the more it treats those people as interchangeable cogs that are there solely to serve the overall function of the organization. If the organization is a for-profit corporation, its overall function is profit, and thus megacorps always tend to optimize squeezing their employees.
Short-term this can be reversed somewhat if leadership is concentrated and opinionated. E.g. when the company grows out of a startup dominated by a single founder, and that founder has certain ethical standards or beliefs that they enforce on the org, overriding the natural tendency. This arrangement never lasts long-term, though - either the founder goes away and is replaced by generic management which has neither the desire nor the capacity to go against the current, or the founder becomes corrupt.
I watched a layoff take out half the security team during an incident. That was fun.
I feel like global acronym bankruptcy is overdue.
http://www.catb.org/jargon/html/T/TLA.html
...
The self-effacing phrase “TDM TLA” (Too Damn Many...) is often used to bemoan the plethora of TLAs in use. In 1989, a random of the journalistic persuasion asked hacker Paul Boutin “What do you think will be the biggest problem in computing in the 90s?” Paul's straight-faced response: “There are only 17,000 three-letter acronyms.” (To be exact, there are 26^3 = 17,576.) There is probably some karmic justice in the fact that Paul Boutin subsequently became a journalist.
It might be interesting to take a sample of TLAs used and look what words can be used in those spots. If the third position is 90% likely to be a noun, that could change the distribution... guessing not in a significant way itself but it could be interesting to see.
There's a scene where they put a folder in front of him with a brightly-coloured sailboat on the cover labelled "LOOKING AHEAD." It's exactly as grim as it sounds.
"I hope, considering your [pause to check personnel file] over nineteen years of service to the firm you will understand that these measures are in no way a reflection of the firm's feelings towards your performance or your character"
Europe is vastly diverse and your experience is not representative of all Europe.
As in after a termination there's a period during which you're still supposed to work and collect the salary.
Exceptions are B2B contracts (but they still often have one of those) and some piece work contracts.
Of course a particular bastard of a company can still immediately cut you off everything but the salary including the doors.
In the UK big corporations got a loophole where they can get employees without affording them any rights. It's called IR35 that Tory government amended to facilitate this, as Brexit benefit (the regulation would have been illegal otherwise if we were still in the EU).
It's totally legal to fire employee without any notice for any reason or even pay them below minimum wage.
Well, getting escorted out definitely doesn't happen here either at least.
It 100% does. It happened to me in Brno, Czechia, and this February I interviewed someone to whom the same thing happened and who was attempting to sue for unfair dismissal.
As someone from Europe, I’ve never experienced US salaries. Go figure.
I would prefer to have a higher salary and be "allowed" (thanks to my own money) to quit (even if I don't want to).
Such things definitely exist, but they are far less common than is often implied here on HN and elsewhere. I think this is largely because people who don't work long hours are much less likely to wax poetic about it, just because, well, it's not at all unusual or interesting.
92% of American had health insurance in 2023. Some people may have more than one insurance plans, thus the total number below is greater than 100%.
Of the subtypes of health insurance coverage, employment-based insurance was the most common, covering 53.7 percent of the population for some or all of the calendar year, followed by Medicaid (18.9 percent), Medicare (18.9 percent), direct-purchase coverage (10.2 percent), TRICARE (2.6 percent), and VA and CHAMPVA coverage (1.0 percent).
https://www.census.gov/library/publications/2024/demo/p60-28...
In the end someone who was working at Google in the Bay Area for 15-20 years can retire if they didn't have life style creep (which is different than cost of living). Not the case in Europe.
This has nothing to do with Europe. This is particular a tech thing
On paper, my employer pays me 72k per year. I net 36k of this after taxes and social insurances are paid.
Fun fact I learned the last time this topic came up, social security in the US pays more than German government pensions.
Basically, almost all places, particularly in the UK, have worse salary to cost of living ratios.
Those few months pay thing is the key difference. That is legally mandated.
If you get fired for fraud or for being incompetent, for example, it's often different.
Some states require payout for unused, earned vacation time.
State-managed unemployment pay is also a thing, assuming the employee wasn't fired for cause. I think some states require employers to pay into this via a payroll tax.
Yes, it may be different for full-time non-contract jobs, but once you're on a contract, nobody cares.
Here in the Netherlands contractors are also 'at will employed' as the Americans say.
But they pay you more so...
Yes, they get paid 1.5-2x, and that also prices in that it’s not always 100% utilization. Only once had a contractor oppose that, but that was in the context of (severe) underperformance.
With contractors, you have more freedom of choice when you write the contracts, but whatever contract you agree on, you still have to honor the contract as agreed.
Contractors don't have that kind of support pretty much anywhere (that's sort of the point), and it's just a standard contract dispute that lawyers argue about.
We are a law and order country.
You got yourself played
in any company, plans change. if that means going on a multi-year “managing out” of useless employees, idk why would i hire in EU.
> unions are just corporate blackmailing.
This is such an absurdly ignorant take that is hard to start educating you, it also depends a lot on what society you live in since your view on unions will be tainted by what you see in it.
In places like the Nordics, unions are one of the cornerstones of a free labour market, look up how Sweden has a freer labour market than the USA to learn something at least :)
If your point is to score virtue point, keep at it, but if you actually want to change anyone mind, avoid terms like "is hard to start educating you", it just makes you sound like a douche
I don't even think it's possible to change someone's mind who already think that way, since it's purely from a point of absolute ignorance and I'm not willing to put enough effort to cite literature that could give them good starting points to understand something they are very likely not even willing to start understanding. They have a lazy position, I reply lazily.
They have an ideological position, based on ignorance, and from a single statement it's pretty clear they aren't curious and willing to change their mind.
Hence why I cite to look into how unions work in the Nordics, at least that is a starting point if they want to learn more about labour movements. It takes someone being curious though.
In the end, it was absolutely honest: it is hard to start educating someone who holds that position a priori and based on pure ignorance, and if not ignorance it's maliciousness, there's not much of a spectrum in this case.
Why else do you go to work?
The fact that these things are seen as optional and unimportant explains a lot of what's happened to public discourse.
In your case, yes, you were absolutely a resource. This is exactly why companies of that size simply shouldn't exist - because they cannot not treat their employees as resources, with all the inhumanity this implies.
And again, work is a transaction. I’m perfectly fine with being treated as a resource when I was getting a quarter million a year and working remotely…
But, more importantly, a company that large is simply too much concentrated economic power (which then translates to political power). Even if it was all just robots, I'd still say no. Our political system is in shambles in large part because of these kinds of entities.
Our politics is in shambles because of religious nutcases, anti science, anti intellectuals, who are afraid of the country becoming majority-minority and straight out racism and bitterness.
Amazon has nothing to do with that.
Amazon didn’t have any significant lobbying 20 years ago and it definitely was the behemoth it is today. That being said, even today it isn’t as large as Walmart and was definitely not a large retailer back then.
It was seriously in doubt 20 years ago whether Amazon would ever survive and definitely wasn’t consistently profitable.
However, I would be very surprised if they weren't lobbying heavily to keep said exemption for as long as possible.
Your choice of verb tells a lot about what you think of your employees.
In many cases problematic employees can and are removed from EU companies.
Also, surely if they were excellent candidates then you'd be doing your absolute best to keep them around?
Well to be fair excellent candidates are excellent on paper. It sometimes happens (not often, but not once in a blue moon either) that the candidate turns out to be completely unsuitable for the job.
You don't sound like a big company ceo. If you have a good reason, even as a small company, and revenue / affordability is one, you can fire people.
You just need to be able to pay them for min. 3 month if thats your contract length and as a business owner you should know how to calculate.
just to hammer this point home: Every mandatory employee benefit has a huge cost, and adding enough of them kills your economy. It makes it more expensive to have an employee than X many jobs can justify. That X grows every year, and that's X people who cant do that job and get paid money for it.
Meanwhile, Big tech (pre-2022) went to pretty extreme lengths to keep tenured employees around because of all the knowledge they'd built up which made them valuable to the company.
But whatevs, you do you. I'd advise you to only hire contractors if you want people to stay less than a year.
And it's worth noting that you appear to be responding to people who are in German speaking countries, where 3 months notice is standard. Other parts of Europe are not like this, and in Ireland you can fire as per the US for the first 6 months/year, and only need to pay redundancy if they've been there 2+ years.
If it was, why would I be evaluating whether you're improving it or not? Surely a discussion only needs improvement if it has room for it, right?
> edit: you are another coper europoor.
Strong words from someone who recurringly goes into US vs. EU discussions just to post inflammatory garbage. [0] [1] [2]
[0] https://news.ycombinator.com/item?id=43417884
Yeah, no. Also European, and have been marched out without notice, cut off that day with no chance to say goodbye, etc.
1. Which countries are we talking about? Europe is not homogeneous
2. Which type of business? Are workers unionized?
I never felt good about that company ever again.
It was stark, the difference in process between the two countries. Leadership was openly complaining about how they couldn't close out shuttering the company because it was going to take six months to handle legal compliance in Germany.
This was during an all-hands, and one delightfully brave soul who knew it didn't matter much what he said since we were all exiting anyway commented in the public channel "Because of those laws, the American employees also get a six-month heads up instead of a locked door when they drive in in the morning, so today, we're all very grateful to Germany and our German peers."
>Only in very critical jobs they'd walk you out immediately but then you still get the pay.
Presumably you are also still employed, just not given any tasks. I do not think that here in Germany there is any way to immediately fire someone, just because he was working on something critical.
Many companies refuse to do layoffs entirely. Which often means that they have difficulties responding to changes in the environment or need to heavily rely on contractors.
That is something both sides have to agree on. So it can not be considered "firing".
>Freistellung
You are still employed, just have no tasks assigned to you. Completely different scenario for the employee, who now can look for a new job, while still being paid as if he were employed. Arguably it is even better than being let go, but having to continue working. Definitely anything but a "firing on the spot".
The problem is, before the layoffs, the employee may have felt they had an obligation to do right by the company. Once they're fired, it may no longer be the case. Some may very well become spiteful, act on their vengeance, & seek immediate retribution.
The risk posed by an employee going rouge is what most CEOs are playing for, especially as in GP's case, for a company as large as Google, where they need to plan for all possible failures and scenarios, some of which may or may not have happened before hand.
Maybe in US laid off employees can go rogue because they're treated like shit in the process?
Some employers may decide to give a few months of pay and benefits to laid off employees (although 6 months would be unusually large) but it is definitely not required and is not always done. Mass layoffs of 100+ people need to be announced 60 days ahead (but without naming who will be laid off) but there are no requirements for any kind of severance.
After college I worked for a large regional manufacturer. They laid off about 10% of their employees, I got nothing.
Severance pay is a white collar benefit.
He literally just told you it’s different in France?
> It is a genuinely terrible idea by the CEO though.
Maybe in your culture, but not all. In many cultures (people have shared numerous personal stories here), there are more humane ways to handle layoffs rather than treating former employees like a trespasser/thief/criminal one microsecond after the announcement.This is the culture where I am from. Nevertheless I absolutely believe that work relationships should be professional relationships, based on the employer paying for the employees time. Mutating that into "trust" will only create problems. The only thing I trust my employer with is him fulfilling his legal obligations towards me and I will fulfill my legal obligations towards him.
But one thing that could be better is transparency around severance, so you know in advance what it will be should you get laid off. (Six months may or may not be “generous” depending on tenure.)
When I was laid off we got what was “customary” in that country, but before the offer was on the table nobody was sure we’d get it. It’s so much nicer when this is a matter of law — I’m all for a ~ free labor market but severance requirements help to balance the risk so the employees can relax and do their best work.
* Was there any sour grapes in the Slack channel? Or was it a bummer or distraction for remaining employees?
* Did the Slack actually help the employees readjust and refocus on their new job search?
* Why not encourage people to say goodbyes and exchange contact info, and pay for a job search coaching service (with no reporting back to the company)?
It's very interesting how so many people in upper management seem to think that they can trust employees not to sabotage and cause billions of dollars in losses by paying them like 100k a year.
Only one of them would be seen as negligent.
If a current employee causes damage, that's one thing. But if a recently laid-off employee who retained full system access causes billions in losses, the CEO and board would face severe consequences legally and reputationally, since it would be perceived as an obvious security lapse.
That's no way to run an (overly litigious) society.
Employers generally assume liability for torts (civil liability arising from wrong-doings) vicariously. For example if an employee somehow puts rat poison into a customer's burger, the employer is automatically liable for that, because they are responsible for the employee's actions. (See eg. https://en.wikipedia.org/wiki/Vicarious_liability )
But if on the other hand a recently laid-off ex-employee sneaks back to the restaurant and then adds rat poison to the burgers, the liability of the employer isn't automatic (you can claim they should have done better with their security etc., but it is probably a defense to say they did all reasonable steps to secure the facilities).
So yeah, I call bullshit. More likely is that the C-suite just cargo-culted some "layoff best practices" and it just became a thing you did without questioning.
I'd be curious if every laid off Google employee experiences this hard cut off, or if it's determined case by case.
This situation is endemic in smaller companies with the tight budgets.
Cutting access and having security walk them out is more or less security theater. If an employee really wanted to cause damage the odds are they either already have or will still find a way. In this scenario having generous severance and treating them with respect is likely to better defuse the situation than kicking them out the door.
So no, this question doesn't apply equally to the opposite side. An employee does not take responsibility for what the company does. A lot of people wonder why CEOs are paid so much; part of that is simply to take responsibility.
Ironically, a lot of people complain about useless CEOs, but if you asked them to take that responsibility for the pay, they wouldn't take it (note that that responsibility includes things like sweet talking shareholders and giving public statements on short notice on things that could nuke millions of dollars in value and create very real legal liability).
This is a twisted way to look at the risk.
Disgruntled employees have more reason to wreak havoc. All the more reason they should be treated as humanely as possible in a difficult period that in most cases is inflicted by the company itself.
In our industry and many others, being a professional and maintaining good relations with your ex -colleagues, who form your professional network, is much more valuable than any emotional satisfaction from screwing them over, even without the risk of going to prison.
That must depend on the country. In Switzerland it's standard that employees don't work during the notice period when they're laid off.
Someone may find the question offensive because of that.
According to this video you can't keep preciously-lent ammunition from the military. But you can for sure buy your own.
As to why people don't use it or aren't scared, I guess they just aren't as wild...
Also, from my experience, there is not a clear trend whether companies in Switzerland want employees to keep working or if they just let them go during the notice period. I've seen many examples of both.
I believe the overall positive employer-employee relationship in Europe is much more of a product of legislature and cultural norms, than the threat of violence.
At the end of the day it's more about culture (i.e. people's expectations of what is normal) than any objective factors.
That is obviously decided by a court.
Ironically exactly this happens at VW, where getting fired is exceedingly difficult. Neither incompetence nor underperformance are enough.
Working is often treated as transactional but it is about so much more. Self-worth, professional reputation, bonds with coworkers, ownership and stewardship of solutions. Even the simple everyday routine that a workplace drives is important.
The process was that IT locked the laptop until the severance package was signed, then you got a code that let you reboot and reinstall MacOS.
Some of it they've tried to become more formal about in ways that actually make it worse - so for example, the timing of this (which the person complains about) is because (AFAIK) they now have one day a month where ~all role eliminations that are going to happen that month, happen. Or so i'm told this is the case.
Ostensibly so you don't have random role eliminations every day, which makes some sense, but then you have no way for people on the ground to do anything more compassionate (like move the timing a bit) because they can't get through the bureaucracy.
In the end - it's simple - if you disempower all the people from helping you make it compassionate, it will not be compassionate. The counter argument is usually that those folks don't know how to do it in legally safe/etc ways. But this to me is silly - if you don't trust them to know how to do it, either train them and trust them, or fire them if they simply can't be trusted overall.
Or rather you can’t benchmark the performance of anyone there against industry peers because they are protected by a two-sided market. Bazel, Kubernetes and other startup killing tools are developed there because with monopoly services they can hire 3x the number of developers at 3x the rate of other firms and shackle them with tools and processes that make them 1/3x as productive and survive. It’s even worse when it comes to evaluating top management, somebody like Marissa Meyer might be average at best but has such a powerful flywheel behind them that they might seem to succeed brilliantly even if they were trying to fail with all their might.
I have been ghosted so heavily from recruiters TWICE at Google when I was literally telling them "Hey I have offers from $x and $y and I need to decide in 2 weeks. Is there any chance I can get an offer from Google beforehand?" only to receive complete silence and had to go with a different offer. 1-2 months later, the recruiter gets back to me with an offer, I have to decline.
The most hilarious part about it: after I decline, I get interviewed by some team at G that tries to figure out why people declined. I guess they're expecting some teachable moment, some nuance and insight. My answer both times started with "lemme show you an email thread that is very one-sided..."
He called me to discuss my experience, one of which mentioned that I worked in an environment where my team managed "30,000+ servers". He took the opportunity to say something along the lines of "that's irrelevant, that's smaller than one datacenter in one of our regions".
I honestly have no idea why the recruiters from these places have such a superiority complex that they need to belittle people like that. It's not even the manager of the team you'd be working on, just some recruiter that probably doesn't have any of the skills/background the job they're recruiting for requires. Yet they need to make you feel small and worthless right out of the gate.
Is it just prepping you for how you'll be treated there? Trying to select for people that are okay with being belittled?
Anyhow a couple years later I got called by a recruiter from Amazon asking me if I'd be willing to relocate to work there.
FWIW I think it's because recruiters at most companies are effectively contractors and don't have access to all history of communications.
The barrier of entry to become a receruiter in general is very, very low.
Many, many years ago I sat next to HR in an open plan office while on a freelance gig.
They treated almost all candidates like subhumans, both when talking about the candidates within the team and when speaking on the phone to candidates.
They handled everyone from factory worker and janitorial roles, to specialists to director level. I very clearly got the impression that they only treated candidates well if those candidates could turn into people who had any power over them within the org.
I've carried that with me since and I often recognize it in HR staff I interact with now.
They became significantly more attentive when I got an internship offer from a competing big-tech company, but as much as my recruiter seemed to try, the process just seem to be deficient beyond their capacity to do anything about it. It had to go through many steps, and be reviewed by many people who seemingly had better things to do.
Eventually they reached to the right people to tell me my decision before my other deadline. I _was_ going to get an offer. They couldn't get me the actual offer letter, or tell me if I had guaranteed host-matching though. I happened to know Google can send intern offers that don't guarantee you'll be matched to a team, and if you're not, the internship just doesn't happen. In my book that's not only as good as no offer really, it's also just disrespectful. I knew people who had this type of offers and didn't get teams.
I took the other offer. "You will get an offer, the details are just taking a while" is not enough to decide on, and the whole process didn't particularly warm me up to Google. For comparison, and to give credit where credit is due, the other company was Meta (then FB). My recruiter was very response, understanding, and personable, which is especially appreciated as an college student— you're nervous, unexperienced and have a lot going on beyond interviewing. They sent me pictures of their dog to lighten the mood. I had told them I'd appreciate quickness, and by the time I was eating dinner after my on-site, I had the offer letter in my inbox.
It was incredibly inconsiderate, the only thing I could guess is that they're intentionally horrible to applicants in order to filter out the ones that won't tolerate it.
I had two friends within the span of 18 months have this experience where they've run the gauntlet of pre-screening, get invited out to Google offices. Run through two days of grueling interviews, all the while getting a lot of great positive feedback about their performance. They end the last day, go back to the hotel, thinking about leaving the following morning.
They get a call around dinner time. "Hey, we had two more directors that wanted to speak to you tomorrow, it would only be for a few hours, but they were really impressed with the feedback and wanted to have some more time with you. Can you stay for one more day?"
Both later found out this is a complete ruse to find out how bad you want to work at Google. This forces you to change your flight plans, pay for the change to your ticket, pay for another night at a hotel, etc. If you do, they line something up that's super casual. If you reject the offer and return home, they conclude you didn't want to work their bad enough to change all of your plans and remove you from the candidate pool.
Same thing, once you turn them down and maintain your plans of leaving the next morning, they just ghost you and you never hear back from them. The irony was one of the two was contacted a year later from a different department asking him if he would be interested in interviewing for another position there. He said he rolled his eyes and politely declined the offer. He said it was pretty unreal to treat him like garbage and then come back and see if he was interested in another role there. As if everything there is so disconnected or they thought this was just completely acceptable behavior.
Why would the candidate be on the hook for the flight change and extra night at a hotel?
When I interviewed with Google ~10 years ago, they booked and paid for my my flights (from China to the US), hotel and car hire. I didn't have to book, pay and then ask for reimbursement, let alone foot the bill myself.
The 'two days' sounds weird to me as well. In my experience (on both sides of the table) face to face interviews were scheduled to be on a single day.
Perhaps things have changed or your friends were interviewing for very specialist roles?
Actually, I can’t even think of a similar company nowadays.
Anyway, it wouldn’t surprise me if they had a really bad hiring pipeline as a result. Why work on the skill of hiring, if people will jump through flaming hoops to work for you.
As MS converts into IBM, and Google converts into MS, I guess they will have to figure that out.
Shocking how real this is.
But IBM was first, right?
> after I decline, I get interviewed by some team at G that tries to figure out why people declined
I am surprised that you accept. I would never waste my time. If these companies refuse to provide reasonable interview feedback, why would you provide it to them?If a startup is killed by Bazel, it probably wasn't the right tech choice for their scale, and it would be more accurate to say that the startup was killed by bad technical leadership.
So, this i'd take issue with. I agree on the overall attitude for sure.
But some of the data here is just very wrong.
Google can't hire 3x the number of developers at 3x the rate. It hasn't been able to in probably a decade. At least in established markets. It's true that in new markets it can come in and often hire very quickly, but so can lots of others. I say this all as someone who has:
1. Established multiple mid/large developer sites for Google a number of times over ~2 decades, so saw how it changed.
2. Watched my counterparts at other companies try to do it as well.
...
So i have a bunch of direct experience in knowing how fast it can hire and how many it can hire :)
It's also no longer willing to pay what it would take to get 3x developers 3x as fast but that's orthogonal to whether it could - i've watched it try and fail at getting 2x developers 2x as fast in many markets. It used to be able to, but now the only trick up its sleeve is money, sometimes freedom. That doesn't go as far as one would think.
As for 1/3rd productive due to tools and processes - most companies have near zero telemetry on their developer productivity, or very basic telemetry (build times, bug times, etc), while google has an amazing amount.
I don't even think most companies have enough telemetry to be able to quantify their productivity for real to even say it's 3x google's.
For example, most companies could not tell me how long it takes to get a feature from idea to production, what parts of the process take up what time, and how all that has changed over time and breaks down among their various developer populations. Let alone provide real insight into it.
(Feel free to pick your alternative measure, I would still bet most of the time the telemetry isn't captured)
Most seem to drive productivity based on very small parts of their chain (build times, etc) and the rest on sentiment.
That may actually be the right level of telemetry for them, depending on what they are trying to do, but it makes it very hard to say they are actually more productive or not.
There are many complaints you could make about Google, but the productivity of tools is not one of them. Sure, some people love them, some people hate them, like anything, but that is orthogonal. I've certainly seen the "i like x better" or "i am much more productive in x" complaints. But by any objective measure, the tools make Google's developers are wildly productive, and are one of the reasons they are able to overcome so much more process.
The process part i agree with, like any other large company, google is smothered in process these days.
I remember having the following discussion with a 5000 person org about their launch bits:
Them: We've done some data and tracking and discovered we think only the following kinds of properties of launches are actually really risky for us, so we want to make them blocking on the following launch bits.
Me: Great, does that mean the other launches aren't risky and you don't really care about the launch bits you have to approve for them?
Them: Yes
Me: Are you going to remove the launch bits from them so it stops slowing them down?
Them: No.
That’s the thing, they might be winning all the productivity battles there are (and I genuinely believe that they do, on top of great tools Google employs good-enough programmers to make use of those tools), but at the same time they’re losing the general war. Because, with rare exceptions, the last war Google the company won when it came to launching something of lasting value happened in the late 2000s, give or take a few years.
The botched Google+ launch broke them in that department, or maybe that was just a symptom of how badly-broken things already were inside the company. They’re still making lots and lots of money, though, so that’s still a good thing for them.
Or maybe it's a business problem that Google shares with Microsoft, Facebook and Apple.
Microsoft has struggled to find any new products that will really move the needle in terms of revenue but they support their old customers with enduring loyalty while making the occasional absurd-but-bold move like Windows 8 and sticking to businesses that seem to make no sense like XBOX.
Facebook is the captain of cringe, not cool, but at least they're investing big in VR as a platform. They subsidize great rigs for Beat Saber because Zuckerberg will never forgive himself if he gives up and somebody else succeeds. [1]
Apple will never find a product as big as the iPhone. To do so they've have to make an iCar or iHouse or skip Starship and go straight to O'Neill Colonies. At least they are indisputably the best at what they do and they can occasionally take a hopeless shot at someone else's turf (Vision Pro) feeling justified that the only rival platform has a trashcan for a logo.
Google has trained us all that anything new from Google has a shelf life less than day old bread. They go at new projects as if they a startup that didn't get into Y Combinator or like the kind of company that Marissa Mayer starts these days [2] -- they don't realize part of the special opportunity of being a huge company like that with an absurd valuation is you can do really big, audacious, and irrational things.
[1] I learned for myself how dangerous this attitude is but all I could do was max out my HELOC.
[2] see https://sunshine.com/ not to put it down, I might be involved in something like that if I wasn't doing what I am doing
People repeat this a lot, but it's obviously not true. Google Photos is recent, really good, and had more than a billion users really quickly. Waymo is like a decade away from eating the entire urban taxi market. Gemini is the best LLM for writing code right now. I guess you could call these "rare exceptions" but I don't think that's a useful way to describe them.
Hell, even YouTube improves every year by leaps and bounds from both a revenue/profit standpoint, AND from a creator support standpoint.
Google deserves to be heckled mercilessly for how easy engineers have it there and how eager it is to kill off products, but suggesting that it's a dying company coasting on ad money is just totally wrong.
It’s a decade old and that’s only if we don’t count what it was before it was spun into its own product, google’s more recent integrations spun as “releases” non withstanding.
YouTube INCREASING creator support? That’s news to me and every other YouTube creator. Creator support peaked around the time Photos released, nearly a decade ago and has only gotten worse since (although if we were to graph it, it would certainly have peaks and valleys).
If the point you're trying to make is that Google needs to bring every service they offer up to a billion users within five years of launching it, I don't know if there's much of a point to me trying to convince you
They said, if Photos is currently recent (aka 2025-2015 = 10 years = recent) then Search was recent when Photos came out (aka 2015-1998 = 12 years = recent).
Which given the overall timeframes, I'd say that's close enough to say 10 years ~= 12 years. And they said they'd actually count the non-Photos time of Photos as Photos, so add some to the 10 years.
Well I didn’t say anything like this or anything that implied anything close to this so I suppose you’d have to engage with what I actually said.
Photos existed and was available to the public before it was “released” in 2015. Even then, 10 years is certainly not recent for a company of Google’s age. I don’t think even IBM would consider a 10 year old product a recent release.
Google has had several previous photos apps! The actually useful one is the most recent.
> Even then, 10 years is certainly not recent for a company of Google’s age.
So you swear you aren't demanding proof that services released in the past five years are successes, but you're complaining that pretty much anything older is too old.
Dude, I am engaging with what you said. Almost no product is wildly successful in less than 10 years by Google's standards, because Google measures users in billions.
If you still wanna ignore Photos, then talk about Gemini, Cloud, and Waymo. The Pixel phones are also doing pretty well, considering how dominant Apple has been.
My point here is that you're ignoring numbers that would be INSANE for any startup because the product is from Google. It really seems to me like you're looking for reasons to discredit the company instead of the truth, which is that non-ad revenue is 25% of the total and growing.
That's pretty significant and in absolute terms makes Google a giant even without search.
My post was Thesis: Photos is not new
Supporting evidence: everything else.
I am not OP, I am not saying anything you’re responding to (and when I look at the OP you responded to they didn’t say what you’re responding to either).
I’m not ignoring any numbers they just don’t have anything to do with my post.
Additionally, Photos was a relaunched app that’s why I’m saying the 2015 is a little misleading, I am aware Google had other photo apps before Photos and I’m not talking about that.
I can say “your examples are bad” without espousing “Google doesn’t do anything”
> Supporting evidence: everything else.
I am getting my number from Wikipedia, because that's when the actual "good" version of Photos launched. I don't know what the status quo was before the relaunch, because the app wasn't useful to me before it got the ML features that caused it to blow up and become a wild success.
The point I am trying to make is that Photos, on its own, would be a multibillion dollar startup. In the context of billion-user apps, even being 10 years old is still pretty recent.
My complaint with your take is that if you exclude anything younger than that, OBVIOUSLY there will not be as many (or any) wild successes. It takes time for a product to become successful.
So? It's not a weird callout, it's an example where the whole arc is well known.
Marissa Mayer left Google like, 13 years ago...?
The BigTech firms have been doing this intentionally for a very long time. I started hearing about Microsoft doing the security-escorts-you-straight-out-the-door all the way back in 2012.
It's not that they are bad at this, it's that they think the trade-off works out in their favour. And it probably does - what's a few but-hurt former employees, versus one disgruntled former employee who had enough warning to snag critical data on their way out the door?
Though it's probably our fault, since we're all so trusting of our mega corp employers, and/or so optimistic about our chances of surviving layoffs, that no one is stashing the incriminating data ahead of time.
Are you sure about that? Microsoft's 2014 layoffs, which were large enough to be reported in the tech press, let employees keep network and building access until the actual layoff date.
I do recall stories of people getting escorted out, but this was from 00s.
I wonder what changed?
It feels like there was leadership turnover in the late 2010s where "conventional company" people assumed the reins of power and started managing it like one.
The founders are complicit too. People like to think "before Larry and Sergey stepped down…" but the founders still control the board (tacitly or explicitly approving of the company's current behavior). Plus, there's Sergey's "60h/w or GTFO" note from a few months back.
The issue is that if you keep hiring leadership/people from the rest of the corporate world (which is basically unavoidable if you are growing) then you'll end up trending towards the median of corporate behaviour over time.
It's mostly unavoidable, unless you never hire external managers (which would be very very difficult to do).
That is a very charitable way to look at it, when I worked their I started from that point as well. "Hey, this thing you just did, you did it really badly, can we workshop some ways to not do this so badly in the future?"
And yet, again and again they would do something similar again and still do it badly. As the examples piled up, I was able to have more pointed and more direct conversations with the executives tasked with doing these things. After a year or so, the evidence was pretty conclusive, it was neither that they didn't think they were bad at it, they didn't care.
There have been a lot of conversations on HN about how "managing" at Google was warped by the fact that their search advertising business was a freaking printing press for money. So much that billions of cash was generated every quarter that they just put into the bank because they didn't have anything to spend it on. There have been lots of discussions about how that twists evaluations etc.
What has been less discussed is that tens of thousands of people applied every week to work for Google. It is trivial for a manager to 'add staff' just pull them out of the candidate pipeline of people who have accepted offers. Tell HR^h^h People Operations to keep "n" candidates in the pipeline to support 'attritional effects' of management decisions. And blam! you get new employees with a lower salary than the ones you lose to attrition. It was always better to fill an open slot with a newer, cheaper, employee than to transfer one whose job/project/group had just been deleted. Always. Management explicitly pushed hard on the messaging of putting everything in the wiki because it was helpful that firing someone didn't lose any institutional knowledge because that knowledge was already online in the wiki.
As a result, it was ingrained in the management culture that "you can always replace people so don't feel bad about firing them" and "incremental revenue improvement or incremental cost reductions are not promotable events."
Google leadership spends money to create illusions for their employees to maximize their work effort, much like a dairy spends money to keep their cows milk production up. And like the dairy, they don't get too attached to any one cow, after all there are always more cows.
Argyle, the author, had their belief system completely invalidated. That is traumatic, always will be. Google's leadership doesn't care, Google's belief system is that there is already someone in the 'hired' pipeline who costs less than can do any of the things Argyle might do, or has done, and they are cheaper. So yeah, don't let the door hit you on the way out.
But Google is a big place and it was long ago, so perhaps it’s a “blind men and the elephant” thing.
Did you ever run percent when you were there? I started at Google in 2006 and one of the 'fun' things people did was run the 'percent' command that would tell you what percentage of Google employees were 'newer' than you, so if it was 10% you knew that 10% of the people were new. I was curious how it worked and found that it just counted rows in a database that had active employee names and start dates. Pretty simple hack.
The amazing thing was how quickly the number grew! And at TGIF there were the Nooglers in their propeller caps and everyone was like wow look at all those newbies. About 6 months in I noticed two things, first there was like 25% of the company was newer than I was, and that the number of employees being reported in the financial reports was about the same as when I joined. One could do the math. Waves of people would be hired, large chunks of them wouldn't survive the first year, and another chunk wouldn't survive 'slotting'. They were just no longer at the company. After a couple of years, as I remember it there were three of us, out of about 30, from the group that joined when I did, still at the company.
When I looked for it, it was pretty clear there was a tremendous amount of 'churn' in employment. I asked Lazlo Bock about it once, he was heading up 'People Operations' at the time and he assured me there were always plenty of candidates in the pipeline and Google wanted only the best and brightest. The people we had? Well they weren't always a good fit "culturally" with the company, after all Google was unlike any company that had ever existed, right?
It was just one of the more egregious times where the 'actions' and the 'words' didn't actually communicate the same message.
Prior to that, I only saw layoffs during market downturns (2001, 2008, 2012) and generally much smaller.
Another big thing at Google was data science, or "Using data to win arguments" as a prominent Google engineer once wrote. I would not be surprised that someone has code that assesses the cost of replacing people where they figure out "current pay package of existing engineer" - "recruiting costs" + "new pay package" and the manage the list of people who are now 'replacable' because that number has gone in favor of replacement.
I was pitched a project to work on when I was there called "find and expert" or something which was designed to identify individuals who were 'experts' and relied on by the organization. Reasonable thing right? Know who your experts are. But the folks putting this together were also associated with People Operations trying to replace people. It didn't take too much effort to connect the dots on that. Was it evil? Yes? No? Kind of? It was more like "we want a company where everyone is easily replaceable without risk to the company." That certainly plays well with the shareholders. Felt a bit like the Borg trying to integrate ones technical distinctiveness into the collective.
It has always been a career limiter of mine that I care about the people more than I care about the company.
This is just so wild for me as an European, because at least in Germany if you get fired (or if you quit) you need to stay 1 - 3 MONTHS at the company still.
Of course, most of the time, you can / need to stay at the company for that above mentioned varying amount of time.
Some companies are just paranoid. My company has now had several rounds of layoffs, people were kept on for a few months, got severance and everything went as harmonious as layoffs can be.
The cruelty the way some companies and now Musk with DOGE are doing it is simply not necessary and reflects a lot on the character of leadership. To me it looks like they are deeply insecure and hate their people.
Companies generally don’t become militant about a subject unless they have experienced the other side of the equation. It’s not just with layoffs, it can happen with protecting source code, licensing, network security, etc. I concede that a company could replace destroyed property and should be able to recover deleted data, then prosecute/sue to recover damages which could cost tens or hundreds of thousands(or millions depending on the level of access), but the disruption to business can be significant in some cases. Moreover, it is impossible to put an IP cat back in the bag.
For me, it seems easy to understand both sides on this one; compassion vs risk.
That's pretty cold, un-empathetic logic. If you're rigorously practice that kind of thing, you'll get the same reflected back at you.
My company has layoffs (not massive, but some). In my experience, the affected employees keep their access to everything, and typically finish up their work and participate in transition activities (knowledge transfer, etc) over a couple weeks. Yeah, they're typically also slacking a lot and socializing more, but no one around here wants to be an ass to their coworkers. I think the only people who get their access cut off are those fired for cause.
> Companies generally don’t become militant about a subject unless they have experienced the other side of the equation.
There are obvious problems with designing your processes around the literal worst case (e.g. treating everyone like they're a criminal has consequences).
On the flip side, treating them like a crook seems more likely to inspire that kind of revenge instinct. Most people would understand removing privileged access immediately but giving them a dignified exit seems more likely to prevent problems.
It's a sad reality. For some people a "dignified exit" won't do a single thing to lessen the rage they feel that they were wronged. It's a sad situation all around.
Eh. That's a bad way of thinking, but one that I think is tempting to software engineers. It's basically taking software security thinking (appropriate for things) and applying it to people in a context where the consequences are almost certainly not that bad. It's also probably downstream of some other bad ways of thinking, that probably make it appear more reasonable than it is.
> It's a sad reality. For some people a "dignified exit" won't do a single thing to lessen the rage they feel that they were wronged. It's a sad situation all around.
You know, you're not required hire those kinds of people in the first place. Hire people who get along with others.
This has nothing to do with software engineering. It's about business risk management. I'm not justifying it, just explaining the sad reality of it.
> You know, you're not required hire those kinds of people in the first place. Hire people who get along with others.
I'm glad you have a crystal ball to perfectly predict how everybody will act in future situations. But sometimes it's the people who seem the most pleasant and helpful who take layoffs the worst, because they feel the most betrayed after everything they gave emotionally in good faith. Humans are complex and they can act unpredictably.
You should note I said that way of thinking "is tempting to software engineers," not that is exclusive to them or has anything specifically to do with software engineering.
> It's about business risk management. I'm not justifying it, just explaining the sad reality of it.
The actual sad reality that some people chose to treat others unkindly pre-emptively.
> I'm glad you have a crystal ball to perfectly predict how everybody will act in future situations.
I don't, but I think you can minimize your risk, if that's what you need to avoid being an asshole. Then you have to practice trusting others.
> But sometimes it's the people who seem the most pleasant and helpful who take layoffs the worst, because they feel the most betrayed after everything they gave emotionally in good faith.
Honestly, that seems like an argument for making sure employees have good work-life balance, so they're not giving an unhealthy to the point where they feel betrayed.
But I suspect the people who think "I'll make them angry, but that's OK because I'll make sure they can't any damage," are probably also the kind of people who would knowingly exploit an over-committed employee.
I was at a company that did this. I thought it was very nice at first.
It didn’t take long to see why most companies don’t do this. It became common to have a couple people who turned their last days into a mission to poison the well and go on angry tirades. Those days became tense and messy as people trying to do work felt necessary to move it to private messages to avoid triggering anyone.
It gets really ugly when IT starts checking logs and sees outgoing employees doing things like accessing code they weren’t even working on or downloading files in volume.
This was at a company with generous severance, too, so that wasn’t the cause. A small number of people get irrationally vengeful upon being laid off. At Big Tech scale it’s virtually guaranteed that at least one of the people you lay off is going to make some bad decisions.
After the announcement, the laid off employees were given a few days in the company to allow them to say good byes. I love the CEOs comment on this ' I trusted them yesterday, I trust them today'. This was by far the kindest way of laying off employees imo. People were treated with dignity and respect.