Live data from Hacker News

PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit

marketwatch.com

61–70 of 183 posts

Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit

#61
post #54

Earlier quoted context omitted.

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?

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.

Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit

#62
post #13

> 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?

Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit

#63
post #54

Earlier quoted context omitted.

If they weren't able to hire these "better developers" in the first place what is going to change now?

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?

Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit

#64
post #3

I know it's in fashion to have a cutesy name for your employees these days, but "Dutonian" is really stretching it haha.

Oh shit, here we go again. The Dutonians join the Googlers, Xooglers, Nooglers, Metamates, Amazonians, Mozillians, Stripes, Tweeps, Peeps, Veeps, Elasticians, SoundHounders, Vimeans, Rackers, Krakenites, Latticians and Plaids.

I work for a company called "Fetch" and I call us "Fetchens"

Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit

#65

I never understood PagerDuty. Isn't it just IFTTT with SMS and email at scale? What is their moat even?

Their moat is the same as Jira's. Despite being expensive, and easily replaced by a bevy of alternatives, management are familiar with the name and purchase it.

[dead]

Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit

#66
post #51
post #49

Earlier quoted context omitted.

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?

Sorry... "People First"

https://www.pagerduty.com/blog/pagerdutys-people-first-appro...

Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit

#67

Earlier 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."

[deleted]

Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit

#68

With 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 in the middle of India or Romania or Bali?

The problem usually is, when the rest of your systems are down then this one is likely to be down as well, making it useless. People are paying PagerDuty primarily for their uptime and reliability.

Post reply on HN