> Hiring during a soaring economy and then letting people go as the economy cools is just standard operating procedure.
If that was true, it would be a last in first out layoff, which is not the case. From what I gather it doesn't even match with the performance ratings (i.e not straight out the bottom 6% of the "stack")
This is both a wage depression maneuver, and a meager 4$ bump in stock price. I'd bet my money it is a hail mary to prevent the CEO being outed in a few quarters.
> If that was true, it would be a last in first out layoff, which is not the case.
That doesn't follow. What you hire for at one time because you think it's profitable to do so is not necessarily related to who you let go at a later time because you think it's profitable to do so. Market conditions and other factors have changed in the mean time.
> From what I gather it doesn't even match with the performance ratings (i.e not straight out the bottom 6% of the "stack")
And it shouldn't. Who it makes sense to let go of has a number of factors, not just performance. Even software developers are not a homogeneous resource, and ROI on an employee is not just about performance.
> What you hire for at one time because you think it's profitable to do so is not necessarily related to who you let go at a later time because you think it's profitable to do so
Software engineers are one of the most fungible knowledge workers around, save for transition costs.
> ROI on an employee is not just about performance.
If that was true, it would be a last in first out layoff, which is not the case. From what I gather it doesn't even match with the performance ratings (i.e not straight out the bottom 6% of the "stack")
This is both a wage depression maneuver, and a meager 4$ bump in stock price. I'd bet my money it is a hail mary to prevent the CEO being outed in a few quarters.