Insane that a company will pay you a 20% premium to hire someone that they’ll spend 6-months training just to watch said person fly off to another firm.
Contracting is even worse. Bring someone on to do menial piecework at 2x-5x the median company salary, then kick them out so you can bring on another person who has no idea how your company operates to do the same entry-level jobs. All so you don’t have to tell investors how many people are actually on your payroll.
No wonder the business failure rate is so fucking high.
And then they act like it’s the employees who are wrong. I bet every single one of the job hoppers enjoying these huge salary benefits would prefer to just chill in the same job forever if it achieved the same thing.
Its nice to be both secure in your job and confident in your work. Changing positions is exhausting, both in the job-hunting process and the re-training process once you land a new gig. Then you’re back at the bottom of the “knows what I’m doing here” totem pole.
One big reason I’m at 6 years and counting in my current gig is the enjoyment I’ve had in building a system and maintaining it consistently. Its nice to know the folks in the business appreciate my work. And if I have to wave another company’s job offer under my boss’s nose from time to time in order to keep my salary competitive, I think that’s more just a disconnect between management and staff I’m obligated to make for them every couple of years. At least they’re receptive and responsive to my demands, which is more than I can say of prior employers.
I can only speak for myself, but that’s exactly why I left my last job. I loved it and the people I worked with, but I couldn’t afford that pay rate with such poor benefits.
On my way out, they told me that they wished they had 10 more employees like me.
They didn’t want it bad enough to pay even one employee a little more, though. I am not the only person who left recently lmao
Absolutely! I had a job some 3 years back that said if I continue to perform well, I could probably be promoted in 2 years.
This was on the heels of no bonuses or raises that year (well, for the team I was on).
2 years? Also that was the team’s reward after a year of work? This was a Fortune 500 company with over $10B in revenue.
The next month…layoffs. We spent the month figuring out all the tribal knowledge that went out the door.
The next month after that…contractors must take 2 unpaid days off every month and holiday closures don’t count towards that.
The next month they said, “Good news! We’re renewing your contract.” - Nope. I’m out.
Last I heard everyone on my team also left in the following 3 months, the director of the department also left, and the VP got forced out and replaced.
It’s an absolute cluster. It’s also led to me just not caring about the job or company anymore (not like I should).
I love supporting the team and my immediate coworkers, but I’m not there to make friends. For all we know our entire project gets canned one day anyway.
It’s a sad state of affairs to basically take advantage of this situation, but like…company loyalty doesn’t pay my bills.
There are also a second hand caste of contractors, it’s the ones that work as ordinary employees but employed by another company so that they don’t get benefits
I’ve been on both sides of the contracting game. While I certainly have broad skills and a speedy comprehension, I’ve never been on a job site where the guy handling the software for the last 10 years understood it worse than I did after the first six months.
I also can’t help notice the deplorable state of documentation, at least in my corner of the O&G accounting software field. So there are plenty of instances in which a contractor will roll in, throw something patchwork together, dump it on the client, and then leave me to support the rickety piece of crap for the next five years. I get to play Inspector Gadget as I parse through miles of spagetti code, trying to run down why some obscure command has decided to produce a vague error.
Did the contractors know more about some niche javascript package than I did when the project started? Absolutely. Do the contractors care that I’m going to be the one shoring up this antiquated, sloppily implemented code injection until we retire the system? They do not. Would the $300/hr for a year of fussy support been more valuable if applied to a $40-$80/hr on-site tech who stays with the firm for the next five years? Yes.
Sounds like organizational failures all over the place, not the fault of contractors.
You’re not wrong. This falls on the managers heads as much as it falls anywhere.
I’m not blaming contractors for being contractors. A lot of these folks are straight out of college and new to their respective fields. It isn’t there fault that Deloitte or Accenture or whomever spent six weeks teaching them to make power point presentations rather than giving them a proper six month seasoning in proper standard business practices. Even less so when the folks running my own company never bothered to learn how to do things properly themselves and don’t appear to know who to ask.
But the consequences of the practice of hiring a flood of pricey contractors to do implementation and then leaving the maintenance to a bare-bones staff is misery for everyone involved.
So management and current team let in garbage code
Management doesn’t know shit for shit about coding. The current team doesn’t get to vet and approve the code that’s released (as if we’ve got the time given our existing maintenance roles). They only get to handle the final product that’s delivered. That is a central problem with the business model. Trust is invested in contractors that isn’t earned or deserved. Meanwhile, the expectations of functionality are transferred to the skeleton crew staff once they leave.
I don’t think adding another employee to an environment with broken communication and no code reviews will improve anything.
I think you can’t get to an environment of effective communication and consistent code dev/review standards if half your workforce evaporates at the end of the contract period. As it stands, we’ve got managers stacked six roles high while the actual applications have maybe 1-1.5 employees assigned to each. So who knows the systems well enough to review the other guy’s code?
Having a mentor-mentee relationship on each app would be much preferable to a contractor-for-a-year/single-support-specialist-for-a-lifetime situation we’re dealing with now.
Well no, ideally contractors should do everything this person says they do. They should provide expertise that teams don’t have, and by the time they leave the team shouldn’t need them anymore.
The problem is less the contractors and more the people handling the contracts. Sometimes it’s between client and contractor, sometimes contracting company. You can’t blame the contractor for being hired to do a job, blame the person claiming there’s a need for contractors.
Insane that a company will pay you a 20% premium to hire someone that they’ll spend 6-months training just to watch said person fly off to another firm.
Contracting is even worse. Bring someone on to do menial piecework at 2x-5x the median company salary, then kick them out so you can bring on another person who has no idea how your company operates to do the same entry-level jobs. All so you don’t have to tell investors how many people are actually on your payroll.
No wonder the business failure rate is so fucking high.
And then they act like it’s the employees who are wrong. I bet every single one of the job hoppers enjoying these huge salary benefits would prefer to just chill in the same job forever if it achieved the same thing.
Its nice to be both secure in your job and confident in your work. Changing positions is exhausting, both in the job-hunting process and the re-training process once you land a new gig. Then you’re back at the bottom of the “knows what I’m doing here” totem pole.
One big reason I’m at 6 years and counting in my current gig is the enjoyment I’ve had in building a system and maintaining it consistently. Its nice to know the folks in the business appreciate my work. And if I have to wave another company’s job offer under my boss’s nose from time to time in order to keep my salary competitive, I think that’s more just a disconnect between management and staff I’m obligated to make for them every couple of years. At least they’re receptive and responsive to my demands, which is more than I can say of prior employers.
I can only speak for myself, but that’s exactly why I left my last job. I loved it and the people I worked with, but I couldn’t afford that pay rate with such poor benefits.
On my way out, they told me that they wished they had 10 more employees like me.
They didn’t want it bad enough to pay even one employee a little more, though. I am not the only person who left recently lmao
Absolutely! I had a job some 3 years back that said if I continue to perform well, I could probably be promoted in 2 years.
This was on the heels of no bonuses or raises that year (well, for the team I was on).
2 years? Also that was the team’s reward after a year of work? This was a Fortune 500 company with over $10B in revenue.
The next month…layoffs. We spent the month figuring out all the tribal knowledge that went out the door.
The next month after that…contractors must take 2 unpaid days off every month and holiday closures don’t count towards that.
The next month they said, “Good news! We’re renewing your contract.” - Nope. I’m out.
Last I heard everyone on my team also left in the following 3 months, the director of the department also left, and the VP got forced out and replaced.
Endless cycle of garbage.
It’s an absolute cluster. It’s also led to me just not caring about the job or company anymore (not like I should).
I love supporting the team and my immediate coworkers, but I’m not there to make friends. For all we know our entire project gets canned one day anyway.
It’s a sad state of affairs to basically take advantage of this situation, but like…company loyalty doesn’t pay my bills.
There are also a second
handcaste of contractors, it’s the ones that work as ordinary employees but employed by another company so that they don’t get benefitsdeleted by creator
I’ve been on both sides of the contracting game. While I certainly have broad skills and a speedy comprehension, I’ve never been on a job site where the guy handling the software for the last 10 years understood it worse than I did after the first six months.
I also can’t help notice the deplorable state of documentation, at least in my corner of the O&G accounting software field. So there are plenty of instances in which a contractor will roll in, throw something patchwork together, dump it on the client, and then leave me to support the rickety piece of crap for the next five years. I get to play Inspector Gadget as I parse through miles of spagetti code, trying to run down why some obscure command has decided to produce a vague error.
Did the contractors know more about some niche javascript package than I did when the project started? Absolutely. Do the contractors care that I’m going to be the one shoring up this antiquated, sloppily implemented code injection until we retire the system? They do not. Would the $300/hr for a year of fussy support been more valuable if applied to a $40-$80/hr on-site tech who stays with the firm for the next five years? Yes.
deleted by creator
You’re not wrong. This falls on the managers heads as much as it falls anywhere.
I’m not blaming contractors for being contractors. A lot of these folks are straight out of college and new to their respective fields. It isn’t there fault that Deloitte or Accenture or whomever spent six weeks teaching them to make power point presentations rather than giving them a proper six month seasoning in proper standard business practices. Even less so when the folks running my own company never bothered to learn how to do things properly themselves and don’t appear to know who to ask.
But the consequences of the practice of hiring a flood of pricey contractors to do implementation and then leaving the maintenance to a bare-bones staff is misery for everyone involved.
Management doesn’t know shit for shit about coding. The current team doesn’t get to vet and approve the code that’s released (as if we’ve got the time given our existing maintenance roles). They only get to handle the final product that’s delivered. That is a central problem with the business model. Trust is invested in contractors that isn’t earned or deserved. Meanwhile, the expectations of functionality are transferred to the skeleton crew staff once they leave.
I think you can’t get to an environment of effective communication and consistent code dev/review standards if half your workforce evaporates at the end of the contract period. As it stands, we’ve got managers stacked six roles high while the actual applications have maybe 1-1.5 employees assigned to each. So who knows the systems well enough to review the other guy’s code?
Having a mentor-mentee relationship on each app would be much preferable to a contractor-for-a-year/single-support-specialist-for-a-lifetime situation we’re dealing with now.
deleted by creator
I’ve had three major jobs in my last fifteen years, and these guys are the least worst. Also, the pay doesn’t suck.
Mate, you’re either the unicorn of contractors or straight-up lying to yourself, and us.
Well no, ideally contractors should do everything this person says they do. They should provide expertise that teams don’t have, and by the time they leave the team shouldn’t need them anymore.
The problem is less the contractors and more the people handling the contracts. Sometimes it’s between client and contractor, sometimes contracting company. You can’t blame the contractor for being hired to do a job, blame the person claiming there’s a need for contractors.
Careful, big balls swinging here!
deleted by creator