Slashdot Mirror
Federal Contractors Are $600 Screwdrivers
ideonexus writes "Last month an article appeared on Slashdot about how the government pays IT contractors twice what it pays its own workers. Missing from the article was how much the IT contractor pays its own workers. After working for a federal contractor for 10 years, a document accidentally leaked to employees by the contractor illustrated the incredible disparity between what the contractor was paying us and what they were charging the government. Like most contracts according to the GAO, the government provided our offices, utilities, computers, and training, leaving our salaries as the only overhead to the IT contractor, giving them an incredible incentive to keep them as low as possible to maximize profits. When the top 100 defense contractors cost taxpayers $306 billion, eliminating the federal contractor middle-man seems like an obvious place to start the austerity measures."
Not every kind of worker is the same. You're an educated person, but a miner, truck driver, or some other low-end worker usually can't negotiate any kind of benefits or anything. Either because no one will hear them, for fear of being fired (or flagged...), or simply because they're too... "uneducated" to know what their rights are.
A company is always bigger than a single person. And a company can afford a lawyer (or an army of them) to screw you, while you usually don't have resources to do that. That's why unions exist.
But unions need regulations, just like companies need regulations. What folks here don't seem to understand is that any "unregulated" area WILL get exploited, and the bigger guy always wins. That's the danger, not "government intrusion".
Been working Federal IT at various agencies for 20 years and the story is the same today as it was twenty years ago. You can't reach high quality/niche programmers on the Federal pay scale in the DC area. Scoff if you want, but we just had a top notch contractor successfully apply and get an offer for Federal work, only to turn down $137K plus bens. Great candidate, couldn't reach his rate. I've seen this time and time again.
That same contractor bills out near $300K per annum.
The system is skewed towards the contracting companies. Keeping Federal IT pay rates down below the industry average for our area guarantees big pay days for the contracting companies. These companies were supposed to be a panacea for the inefficient Federal worker. All that they have become is YAFE (yet another Federal entitlement).
And yes, some of the contractors have been in the same position for DECADES. Same lifetime entitlement.
And you're basing this on what evidence? I see no figures on this.
The fact is, people are pocketing a significant portion of government contract payments, and it's not the people doing the actual work. It's the guy in the suit who "manages" the teams, and says "You let ME worry about that" to everything while driving a fucking $200,000 Mercedes.
The unions and payroll have absolutely nothing to do with the inflated cost of government contracting, they're just an easy target recently vilified by the far right and other class-warfare commencing scumbag motherfuckers. So go join your party on the right, tea bagger.
For what it's worth, most union dues/benefits are paid for by the employee themselves through dues and fees. It is a rare occurrence that an employer takes care of all the costs.
Pensions are a stupid employment incentive all around, but it's not the unions' faults. Keep paying people's salary even after they retire? Yeah, that's a marvelous idea for the bottom line.
If the only way you can accept an assertion is by faith, then you are conceding that it can't be taken on its own merits
If you remember the stories about the $600 hammers, and you actually read the details, what you find out is that the hammer cost $10, and the contracting overhead cost about $500. That includes all the rules for government procurement, Federal Acquisition Regulation compliance, EEOE, small and woman/minority owned business requirements, limits on subcontracting, requirements for exhaustive financial/time accounting, etc, etc, etc.
Most of those overhead requirements are placed for good reasons, either for social policies (e.g. small business/minority business) or for fiscal or technical accountability (e.g. time accounting, facility security, etc.) But when you add them all up, you have a lot of overhead for doing government contracting that you don't have in business. It's part of the reason why government is inherently inefficient.
I was a government IT worker in the U.S. Treasury for decades. Before I retired, contractors were being brought in to replace workers in my position. One guy comes to us fresh from a front-line support position at, believe it or not, Best Buy. After a long while, he turned out to be not so bad, trainable, and useful. It took about a year to get him up to speed.
At some point, he decided he trusted me enough to talk about pay. I was shocked. Why should he treat salaries as some sort of secret? As a public employee, my pay is known to anyone who wants to look it up. I showed him how to look up what anyone in the organization made, showed him my salary, and couldn't imagine why anyone would think of this stuff as proprietary information.
In his case, though, I can see why his employer had gone to great pains to create the impression that salaries were some kind of secret. He was doing the same work as a first-tier support employee but was being paid roughly one-fourth as much money. The contract to his employer was sufficient to support employees like me (the agency was paying roughly twice the annual salary of a senior computer specialist for each contractor who reported to a job site) yet the contractor simply took the contract, took a cut, and subcontracted the rest out. The subcontractor took a cut and subcontracted the rest out. The next level subcontractor took a cut and hired an out-of-work Best Buy leftover to report to the job for a pitifully small percentage of the original contract payment.
It was a multi-level sham. I was annoyed at the waste. The contract guy was annoyed that he wasn't making any more money. Overall, contracting for these positions was a completely stupid thing to do that only accomplished just one thing - slicing off shares of pure profit to a few middlemen. Ultimately, the workers on the ground and their customers got screwed and the U.S. government got a *very* poor return for the money spent.
Naturally, once the guy was fully trained and providing real value to the organization, budget cuts forced cancellation of the support contract and he was gone in a flash. All that training time, all that productivity diverted from helping customers to bringing him up to speed was, in an instant, flushed down the toilet.
I'm sure it's not always the case, but contracting for services like this by the government is, in every case where I've gotten a close look, a completely stupid thing to do.