Earlier quoted context omitted.
It's a business not a charity. Did the company not pay them for their work already?
I'm with you, so long as this "work family" and other crap ends.
Did PagerDuty ever say "Work family" or is this just a strawman?
PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
51–60 of 183 posts
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#52I 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…
It’s an extraordinary claim that the big tech cos aren’t cutting the VPs in charge of the units being cut. Is this actually true?
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#53Earlier quoted context omitted.
Scheduling, Groups, Escalation. Yea you could probably do something with IFTTT but I'd rather just pay a little bit and not deal with the hastle.
If it was "a little bit", I agree. Their business plan is a few bucks shy of $500/user/year.
If you're a business paying software engineer salaries, that 500 / user is basically pennies compared to paying someone to maintain a homegrown system
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#54> 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. This pattern of laying people off for short term gains is for the birds. It affects the entire industry when patterns like this become normalized. If you wonder why engineers don't stay around more than three years or have perceivably less loyalt…
What if they are laying off to make room for better developers?
If they weren't able to hire these "better developers" in the first place what is going to change now?
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#55> 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. This pattern of laying people off for short term gains is for the birds. It affects the entire industry when patterns like this become normalized. If you wonder why engineers don't stay around more than three years or have perceivably less loyalt…
Pagerduty doesn't have a big moat, either. They've just cut loose a bunch of people who know the intimate details of how to build a product exactly like theirs, ripe for the plucking by a competitor who knows they have a business with healthy margins. Looking forward to more competition in this space, PD is not as cheap as it should be.
We need a competitor. I find PagerDuty to be over priced for what they are, and Atlassian is doing their best to destroy all of their services including OpsGenie which was very good until Atlassian bought them
Those are the big 2 in the space, who else is there?
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#56> Revenue Officer to Exit Is that an exec taking responsibility? Respect, I guess.
The difference between that and a scapegoat is not abundantly clear.
Yes it is. A scapegoat is a “lightning rod” of blame. In this case, people were laid off beside them, so scapegoat isn’t an accurate term.
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#57Earlier quoted context omitted.
What if they are laying off to make room for better developers?
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)
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#58Earlier quoted context omitted.
Pagerduty doesn't have a big moat, either. They've just cut loose a bunch of people who know the intimate details of how to build a product exactly like theirs, ripe for the plucking by a competitor who knows they have a business with healthy margins. Looking forward to more competition in this space, PD is not as cheap as it should be.
We need a competitor. I find PagerDuty to be over priced for what they are, and Atlassian is doing their best to destroy all of their services including OpsGenie which was very good until Atlassian bought them Those are the big 2 in the space, who else is there?
victor ops? but we switched from them TO pagerduty alas
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#59Earlier quoted context omitted.
The difference between that and a scapegoat is not abundantly clear.
I mean, I don't think it's fair to call a CRO a scapegoat... it's literally their job.
I'd say making money is the CEO's primary job. You can't just hire a "CRO" or whatever other random C title and blame them when things go south at the company. I doubt the person fired had that much influence on company headcount, product strategy and operational budgets.
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#60Earlier quoted context omitted.
We need a competitor. I find PagerDuty to be over priced for what they are, and Atlassian is doing their best to destroy all of their services including OpsGenie which was very good until Atlassian bought them Those are the big 2 in the space, who else is there?
victor ops? but we switched from them TO pagerduty alas
They've been on life support since being acquired by Splunk unfortunately.