“Companies love you when you are good at your job, but hate you when you seek a raise for being overworked” — Employee maliciously complies by doing the bare minimum after being punished for overperforming

A man with a beard in a teal shirt sits at a desk, appearing stressed and employee overworked, with his eyes closed and hand on his forehead, as his laptop and whiteboard sit in the background.

There’s a particular kind of corporate logic that punishes you for being good.

Not openly. No one calls you in to say your work is too strong. It’s subtler than that. The reward for doing your job well is more of everyone else’s job. The reward for absorbing more of everyone else’s job is a quiet recalculation somewhere above you, until the extra work you did stops counting on paper.

Companies say they want high performers. What a lot of them actually want is cheap, predictable, controllable output — and a high performer who notices the gap between those two things is an inconvenience, not an asset.

Because the moment your numbers prove you’re worth more than they’re paying you, the numbers become the problem. Not the pay. The numbers.

When being good at your job becomes the problem

A man with a beard in a teal shirt sits at a desk, appearing stressed and employee overworked, with his eyes closed and hand on his forehead, as his laptop and whiteboard sit in the background.

This is the corporate version of when a measure becomes a target: set a metric to reward performance and people game it. Except the worker in this story did the opposite of gaming it. He smashed it honestly — and got told, in writing, that the company would rather rewrite the math than pay him for the result.

The story comes from a post on r/MaliciousCompliance, where a remote employee at an auto-parts company laid out four years of being rewarded with more work and then penalized for doing it too well. He opens with the thesis the whole thing proves:

“I worked remotely for an auto parts company for almost 4 years, finally getting a promotion after the company merged with another. But even though I performed my duties better than the others in my department, I was effectively punished for being so good.”

To understand how good he was, you have to see the mess he was good inside of. The company sold classic and hard-to-find car parts the world over — and then someone in management bought a shiny new software suite that promptly set the whole operation on fire.

“I started working for a company founded in my area that had a reach around the world for classic auto parts. Sure, we had supplier issues, shipping delays, you name it. But the reputation of this company for being such a large source of hard-to-find car parts – from Model-T and A Fords all the way up to modern muscle cars and everything in between. One of the brilliant minds in the management team decided to purchase a new sales/parts/service program for us, and it went downhill from there. Where one program would say we had 10 pieces of one item, inventory would say we had none, and where our accounting program would say a vendor was due payment, another would say nothing was owed. No one really knew what was going on until after the culprit manager had left with a hefty severance package.”

Note who paid for that disaster, and who didn’t. The manager who caused it left cushioned by a payout. Everyone below him inherited the wreckage — including the people who’d eventually be cut to clean it up.

“We started losing business, customers, vendors … and I – as a case manager – had to field calls daily trying to give whatever company line I was told to give to make the customers happy. We had a high turn-over rate because of this and the company almost went bankrupt. Enter Big Auto Parts (name changed for reasons), and BAP came in with promises to fix everything. They did, for the most part. They paid off vendors, closed out accounts, worked to repair bad relationships with everyone, and let go 60% of the staff from the building in my town. Sad, yes, but unfortunately that’s the price of business.”

He says that last part without bitterness — that’s just the price of business. Hold onto how reasonable he is about it. It’s the reason what comes later reads as principle, not a tantrum.

From phone lines to indispensable

After the merger he got promoted into a new specialist role, sharing the work with one colleague. Here’s how the two of them split it.

“About 6 months after the merger, I was promoted to Customer Operations Specialist. I no longer took calls, but I had to make them for any number of reasons. When I started this new position, there was another person there (I’ll call her Lucy) as well. We had different duties in the same department – I would research the issue that came up and she would call the customer to work out a solution. For a quick example, if an item they ordered was out of stock or delayed, I would find a different part or call the supplier for an ETA. This would go to Lucy and she would call to ask the customer if they wanted to wait or accept a comparable item.”

That arrangement lasted about three weeks. Then Lucy bailed, and he quietly became the whole department.

“It only took three weeks for Lucy to decide she didn’t fit in and left the company. This left a big hole to fill, and because I was used to calling customers, I was asked to do double duty. It worked out surprisingly well because I was already familiar with the situations and could make better suggestions while on the phone with the customers. My supervisor did recognize my success and put me in for a small raise, which I did get. I was making good money doing something I really enjoyed.”

This is the high point. For one stretch, the system worked the way it’s supposed to: he did more, he did it well, someone noticed, and he got paid a little better for it. Remember this moment, because it’s the last time effort and reward move in the same direction.

As the company grew, he didn’t just clear his own work. He started spotting the system-level problems above his pay grade and flagging them.

“The company started growing, and with it, more work needed to be done by everyone. We had a ticket system that, while not perfect, was adequate. Occasionally there would be a hiccup in the system and hundreds, and sometimes thousands, of irrelevant tickets would come across my desk. I started noticing patterns and would call them out to my supervisor so someone with a higher pay scale than I could fix the underlying issue and we could all go home happy at the end of the day.”

Then they handed him other people’s jobs too — and he turned out to be better at those than the people who owned them. Note the line he plants at the end here; he’s telling you exactly where this is going.

“Part of this growth meant that there were some areas in my department that would get too many tickets for the assigned person to handle solo, so I was asked to cross-train and learn these other areas. It didn’t take long and soon I was doing other people’s jobs better than them. I think it was a combination of me wanting to succeed and them wanting to do the bare minimum – and this plays into my malicious compliance near the end of this story.”

The number that became a problem

Here’s where the metrics matter, because they’re the whole point. The job set a floor — a minimum number of calls and points to clear the weekly bonus. He didn’t clear it. He vaulted clean over it.

“We had a point system that tracked how many tickets we worked, how long we spent on them, and whether the ticket needed a follow up or could be closed as satisfied. The majority of my tickets could be closed because of one reason or another and I always hit the metrics asked in order to secure a weekly bonus of $2.50 more per hour. Meeting my bonus put me at above the $20 per hour range every week with very few exceptions, so I was satisfied thinking I was doing a good job. They required me to make a minimum of 200 calls to customers and pass 2400 points to make the bonus, and every week, I would make between 300-500 calls and hit nearly 7000 points.”

Read that again. Triple the required calls. Nearly three times the points needed. The metric was doing exactly what a metric is for — telling management, in clean weekly figures, precisely how much one person was worth.

Which is the moment a good number turns into a threat. It was now documenting, in the company’s own system, that they were getting far more than they paid for.

The exit he already had lined up

What management didn’t know is that he wasn’t trapped. He had a whole other life he was good at, a reputation that reached the top of the company, and an escape route quietly opening up through his wife.

“In my youth, I got a degree from a local community college in video production and that has always been my passion, but I was good at my current job and happy to be there. I got to take bi-annual trips to the corporate office (spring and winter) up north, made lots of friends, and even the owners of the company knew me by name due to my performance. My wife had changed jobs and was working for the local sheriff, and one day she emailed me that there was an opening in the media department. I applied and went through the 3 month process for possible employment, letting my current employer know they would be receiving a background check call. The process went smoothly, even resulting in me getting a call from the Sheriff himself saying he was excited that I had applied.”

So while his employer was deciding his output was a liability, a second employer was personally calling to say they wanted him. That contrast is about to make all the difference.

Punishing performance, out loud

Back at the day job, his excellence had quietly been reclassified as a discipline problem.

“Back to my current company – I had been “talked to” several times about my numbers, with my supervisor telling me they were “too high” and “no one else makes nearly that amount of points.” When I said I was just following the metrics and doing my job, he let me know that changes were coming.”

Too high. Not too low. The complaint was that he was succeeding too visibly at the exact thing they paid him to do. Then the timing turned almost cinematic — the day the Sheriff’s offer came through, his supervisor sat him down to unveil the fix.

“On the day I received my call from the Sheriff about being accepted as a new employee, I had a meeting with my supervisor. Before I could tell him I was leaving, he announced that a new point system was going to be implemented and if my current week’s numbers were applied to the new schedule, my 7000 points would only equal 1800 – far below the minimum for the bonus. When I mentioned this was essentially punishing good performance, he said, “well, that’s what the company wants to do.””

There it is, said plainly. Not a misunderstanding, not a budget accident. The company would rather change what counts as good than pay for the good it was already getting. And then, as a final flourish, they reached for his earned time off.

“As I said earlier, the bonus put me above the $20 per hour line. My new job was going to start me above what I was making with the bonus, which made my decision to hand in my two weeks notice right then and there so much easier. What cemented my decision was when I found out that even though I was going to finish my scheduled 40 hour work week on a Friday, since the end of the pay week was Saturday and I wasn’t working that day, I wouldn’t get the comp-time I earned. They were going to withhold earned sick and vacation time because of a technicality, after four years of faithful service.”

The compliance

What makes the story land is that he never aimed his frustration at the wrong person. He liked his supervisor — saw him as a decent kid boxed in by orders from above.

“I actually liked my supervisor – he was younger than my married son and was disabled – a good kid with a great heart, but hated that he had to follow “procedure” in punishing hard work. I told him as much and mentioned that I would do what my original job description required, and nothing more, for my last two weeks. It was glorious.”

No sabotage. No scene. Just the literal job — the one printed in his original description — and not one ticket past it. And he used the very comp time they’d tried to deny him as the lever.

“We could take time off (if we had vacation or sick time available) if our work was done and we had nothing else to do for the rest of the day. I focused only on my originally assigned areas and once completed I would clock out – putting in my comp time to make up for not being on the clock. I was able to use up all my time by my last day there, and because I wasn’t helping anyone else, their work began to stack up. Not that I was doing it to punish any of the friends I made at that company, but simply to get the point across.”

Here’s why that’s lethal rather than petty. For months he’d been quietly carrying several people’s workloads across all the areas he’d been cross-trained into. The instant he stopped at the edge of his own role, everything he’d been invisibly holding up came due at once.

“Do what’s good for the company”

He could still see every queue he’d once kept clear. So could his supervisor’s boss, who started calling — and got an answer with no give in it.

“I could still see every ticket menu in all the areas where I had access, and their numbers began to climb out of control. I was contacted by my supervisor’s boss on more than one occasion, asking me to help out. And when I would point out that it wouldn’t be fair to take points away from the other people when I was about to leave, and that per policy, I was done with my assigned duties and could therefore leave for the rest of the day, he would stammer, trying to convince me to “do what was good for the company.” I simply said, “I’m doing what is good for me. Unless you can offer me more than what the Sheriff is willing to pay, I will only do what I am paid to do here until my last day.””

“Do what’s good for the company” only works as a plea on someone who still believes the company will do what’s good for them. He’d just been shown, in a fresh spreadsheet and a withheld stack of earned time off, that it wouldn’t. So he answered in the only currency the company had ever actually respected.

The tally

On his way out, he checked the queues one last time.

“On my last day, I checked the ticket queue once again before signing off. My area had zero tickets, and others where I worked that would average maybe ten open or unworked tickets daily, now showed hundreds.”

Zero where he’d worked. Hundreds where he’d quietly been covering. The same metrics they’d rigged against him spent his final day measuring exactly what they’d thrown away. And the verdict kept arriving long after he was gone.

“What made me feel better was about six months after I left, I got a Facebook message from one of my old coworkers that I actually liked wishing me a Merry Christmas and telling me they still had not found anyone who could do as much as I had done. But I am happy where I am and have plans to do this as long as I can, retiring one day after a long tenure here.”

That’s the part no new point system can fix. You can rewrite the math so your best worker’s effort scores as a failure. What you can’t rewrite is what happens the week after he decides to take you literally — and the queue finally tells you what he was worth all along.