Live data from Hacker News

Poll: Why are people leaving their jobs?

news.ycombinator.com

401–410 of 773 posts

Re: Poll: Why are people leaving their jobs?

#401

For me, the proverbial final straw came when I delivered a dinosaur utility company it's first churn propensity score. Bit of background, my manager and their manager were non-technical and I had this thing running in evaluation mode for a few months with excellent lift in the top couple of percentiles. I had the statistics well grounded, and this thing was due to go in against basically nothing, renewal teams random…

> first churn propensity score

Could you expand on what this means?

Re: Poll: Why are people leaving their jobs?

#402
The shift is forcing company's to compete with compensation and benefits for labor and talent. I don't think the great resignation is hyperbole at all. The illusion of not being able to work remote or the company crumbles got shattered. Lots of folks finally retired, lots changed jobs and will do so again.

Re: Poll: Why are people leaving their jobs?

#403
post #54

I'll be departing my job at the end of the month. I had too many roles, affecting too many pieces of engineering, and my title didn't reflect my work. I needed to go down to a 4 day work week and have my title reflect my roles, but my manager attempted to call my bluff and essentially said it's not going to happen. I hinted about what my decision would have to be if these accomodations couldn't be made, but he didn't…

Is it just the title? Is it a problem that some people don't see you in that title?

Re: Poll: Why are people leaving their jobs?

#404

My old boss Eric Carlsen used to say, nobody left because of money. They may get more money if they change jobs. But they start looking because they're unhappy. So when somebody asked for more money, he'd start by asking what was bothering them.

If you're married, you can see the hilarity in this.

Re: Poll: Why are people leaving their jobs?

#405
post #54

I'll be departing my job at the end of the month. I had too many roles, affecting too many pieces of engineering, and my title didn't reflect my work. I needed to go down to a 4 day work week and have my title reflect my roles, but my manager attempted to call my bluff and essentially said it's not going to happen. I hinted about what my decision would have to be if these accomodations couldn't be made, but he didn't…

As the old tech bro addage goes: Alpha as fuck

Re: Poll: Why are people leaving their jobs?

#407

Earlier quoted context omitted.

Right, I'm rather experienced and make many multiples of 50k/yr, so its not really a compensation thing. It's more that it feels very ephemeral / tenuous as none of it is in an org chart or official. It is basically what problems management has to solve and what seniors are available at the moment. I am, officially in title and org chart an IC. In reality 10-20% of my time is IC dev work. 6 months ago it was 50%, 6 m…

It can be better, but it also can be just as chaotic sometimes. On balance overall, FAANGs are probably better at managing this "IC utilization" rate if you wanna call it that, vs just randomly expecting you to pick up and wear all the hats all the time or that hats are chaotically assigned, with no plan behind it. Certainly FAANGs aren't perfect, but at least it's easier to find "reference implementations" because t…

Right, I like the term "IC Utilization Rate". I think for me its the chaos of the hat wearing. I went about 6 months doing pure project management with 0 leadership or development work.

I periodically go long enough with 0 hands-on dev that stuff in the SDLC has changed again. So I have to go poke around and figure out why my commit message formatting is rejected, which teamcity instance we are using now, and what QA box I should be testing on.

Also the unmentioned part for me is that while 10-20% of my time is Dev at best, 50% of it is high urgency fires I am brought in to extinguish because I have the most knowledge of that part of the code base and can ship whatever improvement in 1-2 sprints without needing to spend 2 sprints on analysis first.

Re: Poll: Why are people leaving their jobs?

#408
post #54

I'll be departing my job at the end of the month. I had too many roles, affecting too many pieces of engineering, and my title didn't reflect my work. I needed to go down to a 4 day work week and have my title reflect my roles, but my manager attempted to call my bluff and essentially said it's not going to happen. I hinted about what my decision would have to be if these accomodations couldn't be made, but he didn't…

Similar thing with me. Starting at a new job in February. Left because the title did not reflect my work. There was not much room for negotiation and I had a scouted offer on the table with better comp and more interesting work.

Re: Poll: Why are people leaving their jobs?

#409
post #54

I'll be departing my job at the end of the month. I had too many roles, affecting too many pieces of engineering, and my title didn't reflect my work. I needed to go down to a 4 day work week and have my title reflect my roles, but my manager attempted to call my bluff and essentially said it's not going to happen. I hinted about what my decision would have to be if these accomodations couldn't be made, but he didn't…

I don’t get this type of management at all. The leverage is always in the developers/engineers hand. The company has essentially zero leverage when it comes to negotiating pay with highly in-demand employees. The only reality for the business is what they can feasibly pay you, and it’s likely much much more than what you’re getting now. Pretending like they have leverage in this position assumes the engineer is less informed. It doesn’t compute for me.

When I hire engineers I give them as close to the top dollar as I can and if that’s not enough there’s nothing else I can do. It’s not fun when they walk, but at least I know there was nothing else I could do.

Re: Poll: Why are people leaving their jobs?

#410
I went back to staff engineer after trying to make it as a teacher.

Teaching is not a dynamic career, at least not for me, the one full time CS teacher at the small school I was at. There’s a little more data to it though: based on the attitudes of a large enough minority of staff and majority of leadership, it wasn’t a career where one could take risks and reap rewards. Not with the amount of social capital I brought to the role, at least.

I had hoped that as a CS teacher with a huge amount of industry background I would be able to make an impact outside of my classes. The quality of the school’s IT meant that, with the right leadership, the IT team should have been crying for out something new. They certainly had the funding for it — external funding from a high net worth parent — but the will to do something novel and interesting just wasn’t there. In the end I was kept at arms length from any of the new hotness projects, which themselves were very staid and notable only in that they made enormous spends on high value equipment rather than doing anything valuable with people — the staff and pupils.

One or two individuals attached to those projects should hopefully still be able to make an impact, despite the lethargy of the old guard wanting their thumbs in the pie and their unending ability to extinguish any dynamism.

(Procurement of new hardware, for example, had to be signed off on by IT. They were the blockers to one very cool new piece of hardware but they weren’t incentivised to do anything other than get everyone to agree they were the gatekeepers. They weren’t incentivised to open the actual gates at any kind of speed.)

I’m much happier back in industry. The true joy of tech is that the business’s primary asset is the codebase, the diffs to the codebase, and the engineers driving them. We can gather around the machine and tangibly make it better through generating intellectual property using our keyboards.

With teaching, the main way of making any kind of progress like that was in the classroom. By its very nature, that is lonely work. You teach solo. You mark solo. There’s no collaboration at all with peers and 80% of the job ends up being behaviour management rather than content creation and delivery.

Interestingly, the most peer collaboration I did as a teacher — which as I said, wasn’t very much — was very much about behaviour management of the kids. That part was cool, but it’s nothing compared to churning out diffs and, moreover, collaborating with other devs to encourage and develop them to churn out their own impactful diffs.

When I put it like that, I guess I’m still a teacher but now I get paid 10x for doing it with young adults instead of old kids. (By which I mean both the high school pupils and the handful of childishly petty staff who sullied my experience.)

Post reply on HN