#by Throwawayyyyyyy11235

[prorevenge]

Underpay me, lie to derail a competing job offer and then try to humiliate me in front of the entire department? Say goodbye to your dignity and (eventually) job/business!

I'm going to leave out specific details about the company and people in question here, as some people also know about this story and I don't want to be identified.

TL;dr:

Company I'm loyal to takes advantage of my delayed graduation to underpay me

They lie to me so that I don't take a better job offer

They then claim my performance is an issue as an excuse to delay my pay raise

When I finally resign, my supervisor tries and spectacularly fails to make me look bad, and instead looks like a horrible, volatile boss.

Her department rapidly bleeds its experts in the months following my departure (I like to think this is in part because of my publicly awful treatment).

Chapter 1: The Good Years

BoringCorp hired me as an intern in the second year of my six year nightmare of college (long story). I was installed as a low-level support technician in the internal IT department, as I was a "wild card" hire, based on a recommendation and didn't have the usual qualifications.

In the three years I worked in the IT department (part time), I reimagined large aspects of how internal IT managed a plethora of internal services at the company. I designed and built several complex software systems to automate inter-department processes, systems management, security and compliance auditing and the like. Over those years I built a significant reputation for myself across many departments, including HR, the security team, engineering, marketing, etc. as someone who could not just "get stuff done", but also improve lots of other things in the process.

Chapter 2: The Downward Turn

Upon graduating, I was encouraged by my team lead (who is an awesome person) to look for a role better aligned to my skill set, and secured a role in the engineering department's systems engineering/automation team. I was offered a graduate salary, something I was unhappy with, as while technically a graduate, I had almost four years' experience in the industry at that point, and had demonstrated significant technical ability. Engineers from other departments often asked me to troubleshoot their code, so it wasn't like I was an unknown at this stage. Regardless, I accepted on the condition that I would be rapidly advanced.

As soon as I started with my new team, it was apparent that the company's engineering department was in some serious strife. Our single team of less than 10 people maintained a mostly undocumented codebase, supporting the deployment and automation of tens of millions of dollars of live customer sites... And stuff was always breaking.

Being the perfectionist and pathological problem solver I am, I immediately started looking for root causes. Most of the rest of the team, who were principally software engineers with no IT or systems background, or otherwise very inexperienced (grads with no work experience and first time interns), continued to chip away at the surface, without considering the source of our problems. This caused some friction with management, but I managed to convince them of the value of my work.

Six months in, I had identified major issues with our documentation, written up some basic (and easy-to-use) documentation standards, and even documented a large chunk of our projects. I had set up an incident logging process, and tried to pare back on our alerting/pager system to reduce "alert fatigue" and get more prompt responses from on-call team members during outages. No pay raise or even any acknowledgement of my efforts.

Chapter 3: The Struggles Begin

No one was interested in my work. No one documented anything, despite my making it as easy as possible. People kept adding bad code to fix short term problems, and despite my repeated pleas (literally every day at standup) this problem continued. Eventually I became pretty despondent about the whole thing and just started chipping away like everyone else, and commiserating with another new hire (senior engineer) who had significantly more experience than me and was equally horrified at the state of things.

I was then contacted by a recruiter for another company. Now at this point, note that I was still feeling a degree of allegiance to BoringCorp - they had treated me very well in years gone by, and I wanted to do right by them, despite their current struggles. So I kept my manager (who we shall call 'Z') in the loop about interviewing, and when I was offered a job with almost double my "graduate" salary, I told her first and gave her plenty of time for a counter offer. She assured me that they would match the offered salary within a month, and that the process was actually already underway (more on this later).

I turned down the job offer, which resulted in getting my ear chewed off by the recruiter and a very uncomfortable phone call from the CTO of the other company, almost begging me to join.

... Three weeks later, no news. I followed up. "We are looking into it, but I want you to communicate to the team why you haven't been around as much." Well, for starters the company had flexible working arrangements, and I had made it clear on multiple occasions that I was working from home. In addition, the reason I worked from home so much, is that my teammates, all of whom bar two were paid much more than me, would pester me with basic technical questions. I was sick of having my work disrupted so I could give first-year college tutorials on computer networking.

I explained this to my manager as diplomatically as possible (I avoided ripping into her about the ridiculous and offensive pay difference), and she asked me to "communicate more". Yeah, okay. I did that.

Chapter 4: The Last Straw+Camel

Three more weeks. Two past the deadline. No news. I follow up again - and hear basically the same complaint, despite having communicated very clearly and (grudgingly) worked from home less.

I started looking for a new job, again. Within three weeks I was five interviews deep in the process for an overseas company, and had a salary offer of four times my original salary. This was based not just on spoken interviews but also technical testing and work samples, so it wasn't just me overselling myself. At this point I became very angry at the degree to which BoringCorp was undervaluing me. I accepted the competing offer on the spot and started making plans to move. I also went back to working from home when I felt like it.

Fast forward two weeks, and I'm ready to put in my notice. I do so, and almost immediately I get an aggravated-sounding text message on my personal phone stating "we haven't seen you much this week and I expect you to be in for a meeting tomorrow." Clearly this set alarm bells ringing that it was a termination meeting and they were going to try to cheat me of my final pay.

Having worked in IT (and in fact having automated a significant chunk of HR processing), I was very familiar with the company's user offboarding processes. I looked for a work ticket logging my departure... And there wasn't one. Strange - policy dictates that one must be created. It occurred to me that in the past, handling dismissals, these tickets were raised with very restricted access permissions, so that the soon-to-be ex-employee had no prior warning.

Of course, I still happened to have some admin credentials in my password safe (used for automation, and which I had thankfully forgotten to delete). Upon logging in with those, sure enough, I found my very own ticket! Turns out they weren't trying to fire me, instead my supervisor (Z) wanted to put me on "involuntary paid leave" for the duration of my notice period. She also wanted me to clear out my desk during the daytime, in front of my colleagues, and deny my the chance to say proper farewells, etc.

Well, knowledge is power here. I spent the first hour backing up all of my personal data off my work laptop. I then wiped the disk clean and rotated the disk encryption keys, to ensure none of my data or personal project work could be recovered. I drove to work at 2am, cleaned out my desk and took everything home in complete privacy, and then went to sleep.

The next day, I walked in at 7:30am, dropped my wiped laptop with my old team and said my farewells. Also took the time to explain why I was basically getting booted out of the building. There was a lot of unhappiness - towards Z.

Then I went and said farewell to my current team. They were horrified by the situation and also were rather displeased with Z. I caught up with some of my closer friends that I'd worked with over the years and said my goodbyes to them as well. We had a nice, relaxed morning chatting about the good ole times and drinking coffee.

Then the meeting came along... Well, suffice to say, Z was rather disappointed that I had already handed in my laptop and cleared my desk. She grudgingly said I could stay for the rest of the day, seeing as I had already done everything I needed to do, and left in a huff.

Epilogue: The Aftermath

A few months had gone by, and I was now happily settled into my new job. I learned through contacts at the company that since my very rude expulsion, many senior engineers have left. They'd had to restructure the department to try to fix their product delivery issues, and were still unable to fix anything because all of the people who knew the functionality of the system (myself because of my documentation push, and the other engineers who built it) had left in disgust at the poor morale and working environment.

Last I heard, Z was still in her current role, but the company was bleeding cash and constantly downsizing. I don't imagine management was too chuffed with her performance.

(source) (story by Throwawayyyyyyy11235)

#prorevenge #by Throwawayyyyyyy11235 #pro revenge #revenge stories #pro revenge stories #pro #revenge #last10