I know it's in fashion to have a cutesy name for your employees these days, but "Dutonian" is really stretching it haha.
I prefer "Duters" or Duterionos"
[deleted]
PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
91–100 of 183 posts
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#92Earlier quoted context omitted.
Lots of open source options out there: https://jayaj.medium.com/top-10-yellowant-integrations-f2e52... And in a volatile macro, you may be loathe to drop talent you'll need again, so might as well have them roll something and maintain it versus outside spend. You can always migrate back to a SaaS vendor when the coffers/pipeline is more robust.
A co-worker at as past job once said: "We pay for the services we use so that if they break, the Managing Director can pick up the phone, yell at someone and something will happen. That doesn't work with Open Source."
Respectable business people don’t yell. Your Director wasn’t one
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#93Earlier quoted context omitted.
Maybe those "better developers" were suddenly laid off by even bigger corps? I've noticed a trickle down effect in our very-small hiring queue. I can't help but imagine mid-sized companies are getting access to devs that only wanted to work for FAANG before.
By your logic the people laid off from other companies would also be the kind that weren't worth keeping. If everyone is firing bad developers and looking for good developers, where do all these good developers magically come from?
I would not take it as a given that the individuals laid off were the worst performers at the company. It could be that they were highly compensated and deemed too expensive, or happened to work in the wrong department/business unit.
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#94I think I respect that at least one of the executives whose responsibility it was to NOT let this happen is being exited out. Google and others have babbled on about executives taking full responsibility for the layoffs, but I don't see any of the key SVPs or VPs taking hits on failing in their leadership. Also I understand they say to pursue other opportunities, but I think the reason for the CRO departure feels tra…
I don’t have any special sympathy to execs, but aren’t these tech layoffs driven by the abrupt increase in interest rates? Even if execs could have seen this coming 6 months before the rate increases, there probably still would have been significant layoffs and of course not even a quorum of top economists were predicting these impacts on tech at that time.
If the idea is “exec heads should role out of solidarity/catharsis/whatever” then that’s a different question than “someone failed to prevent this from happening”. Apologies if I’m misunderstanding the root causes of these layoffs.
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#95Earlier quoted context omitted.
Depends on how bad the people you laid off are. Look at it this way, if 20% of programmers are bad, and you lay off the bottom 10%, and rehire let's say at a disadvantage (50% bad), you now have a 75% bad workforce instead of an 80% bad workforce. This assumes you can identify bad workers (for some metric of bad which may or may not be ethical or sensible)
it's way easier to tell if someone is bad after you hire them vs. before though.
Stats still work out, try it yourself with whatever numbers you care to use. I'm not saying I defend layoffs I'm just pointing out the underlying logic of why a company might want to do them (I think it's missing important factors, but what you claim is not one of them)
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#96With my VP Eng hat on, PagerDuty is a useful service With my VP Operations hat on, I can't justify the pricing Wearing both hats at the same time, I built the solution my company needed inside a weekend and allocated funds elsewhere
I have seen plenty of companies that hand roll their own ops/alerting system, and sure that is a fine strategy if you can put enough resources into it, but that is mostly never the case. Do you host it separately from the rest of your infra? Does it have multi-DC failovers? Does it have a dedicated SRE/on-call team? Do you load test it? Do you test that it can send texts to one of your developers who has bad coverage…
i think these really depends on the requirements of the company. there will always be a long tail of scenarios to support, that doesn't mean every company needs support in all those scenarios. some things can be good enough
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#97Earlier quoted context omitted.
You are unlikely to successfully hire better developers after getting rid of 7% of your workforce. Better developers will stay away.
Depends on how bad the people you laid off are. Look at it this way, if 20% of programmers are bad, and you lay off the bottom 10%, and rehire let's say at a disadvantage (50% bad), you now have a 75% bad workforce instead of an 80% bad workforce. This assumes you can identify bad workers (for some metric of bad which may or may not be ethical or sensible)
This also assumes that every company lays off people and thus new hires don't select companies based in whether they recently laid off people
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#98Earlier quoted context omitted.
Depends on how bad the people you laid off are. Look at it this way, if 20% of programmers are bad, and you lay off the bottom 10%, and rehire let's say at a disadvantage (50% bad), you now have a 75% bad workforce instead of an 80% bad workforce. This assumes you can identify bad workers (for some metric of bad which may or may not be ethical or sensible)
This also assumes that every company lays off people and thus new hires don't select companies based in whether they recently laid off people
"rehire at a disadvantage"
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#99> Despite executing well over the last eight quarters, sustaining high growth and dramatically improving operating margins, there is more to do to secure PagerDuty’s future. Thank you for all your hard work and execution - please be sure to pick up your pink slip on the way out the door.
I wonder, once the hokey stick days are over, what _are_ the growth expectations by the top executives?
For publicly traded companies you can reverse engineer investors' future growth expectations by analyzing the stock price relative to their current financial statements. Those expectations then flow to top executives via the Board. Obviously not all of those expectations can be met.
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#100I never understood PagerDuty. Isn't it just IFTTT with SMS and email at scale? What is their moat even?
You need to have your own infrastructure monitored by completely different infrastructure, otherwise they will fail at the same time. Instead of having your AWS shop maintain a separate Rackspace-coloed team, etc. it is much simpler to outsource