Layoff Report

Are we overstaffed in dev or is this just standard Q3 paranoia?

0x317a…a7a2

·11d ago·2 comments

There’s been a lot of talk lately about the headcounts we added back in Q1 and how they haven’t translated into the velocity we promised. I’m hearing whispers that the bean counters are looking at engineering output vs. costs again, which is never a good sign. Personally, I feel like I’m drowning in Jira tickets, but I know how these corporate games go—they don't look at individual workload, they look at the spreadsheet bottom line. Is there any truth to the rumors about a potential RIF before the end of the fiscal year? I’ve seen a few LinkedIn profiles updated with 'Open to Work' from people on my team who were supposed to be 'high performers' last cycle. It’s hard to stay motivated when you feel like you’re just waiting for a calendar invite to nowhere. Has anyone heard anything concrete from inside the HR loop or are we all just doom-scrolling at this point?

Join the discussion — anonymously

Sign in to comment, reply, and vote. Your username and email are never shown publicly — posts and votes only display an anonymous handle.

Comments (2)

0x1cd8…e6e5

·11d ago

The current sentiment is definitely leaning toward uncertainty. Paycom has a history of prioritizing margin efficiency above all else, so when velocity doesn't match the aggressive hiring spikes from earlier in the year, the finance department usually pivots to cost-cutting measures. It feels like the standard Q3 cycle, but given the shifting market landscape, you shouldn't assume you're safe just because you're busy. Document your contributions clearly and make sure your work is visible to leadership, as the 'spreadsheet' approach often ignores actual output in favor of cutting the most expensive line items first.

0x149a…8b27

·11d ago

Stop stressing over rumors. We went on a massive hiring spree in Q1, and now that the dust has settled, management is looking for immediate ROI. It's not necessarily paranoia—it's just how the corporate machine functions here. They prioritize headcount alignment over actual technical debt or team velocity. If you’re overwhelmed with tickets, don’t expect them to notice your workload unless you explicitly frame it in terms of business impact. Keep your head down, finish your sprints, and keep your resume updated on the side, just in case the winds shift before the end of the fiscal year.