Skip Navigation
108 comments
  • This was recent, and it's still pretty sore for me. I doubt anyone will be able to pinpoint who I am, but if you for some reason are in this forum and recognize me please DM me. Try to count all of the red flags.

    I was hired as a software engineer and was immediately thrown onto a "high-visibility project". My service was the middle man between two other mission critical services. Essentially downstream provided metrics and needed to get to upstream.

    I laid out several different architectures that I recommended. First was prometheus. It's literally designed to do this, downstream is spread across many servers, prometheus is literally built to do this. Upstream then can scrape prometheus, any other future dependents can also scrape. This was rejected. "We did prometheus once, it didn't work." I check, it's a single tenant instance of Prometheus running on one 24XXL AWS VM. So, they didn't know how to properly configure prometheus. I tell them I can kill 2 birds with one stone. No, prometheus bad. Rejected.

    Second, we use a highly reliable queue setup. Downstream publishes to queue, Upstream reads from queue. Seems simple enough, can have many producers and many subscribers, and we already have a kafka service. Rejected. For why, I ask. Literally "Upstream doesn't know how to work with queues". Literally got that as an answer. Read that as "We need to choose a subpar architecture because we openly admit our engineers don't have the necessary skills". I even offered to help them, to write that part of the code. Rejected.

    Third option came straight from the CTO. We love datadog here. Everyone does. Datadog. Oh you feel that pit in your stomach don't you. The mandate came down from on high that Downstream would push metrics to Datadog. I then would need to periodically scrape Datadog, and then have an API that the upstream could then periodically scrape me. I looked into Datadog's API. They don't really support this. I reach out to Datadog, talk to their engineers, and they confirm this is a horrible pattern. I bring this up, say it's just not a good decision, there are better ways. Literally rejected by the CTO himself.

    So, I build this rickity ass service, brand new built with thumbtacks and glue. Along the way more is mandated to me. We'll have literally 8x the number of metrics we originally planned for. We're well over Datadog's API limitations. I am mandated to put it into a Postgres instance. Every decision I am overridden.

    On top of this, Downstream is completely overworked and doesn't have time to answer questions about specific metrics. Upstream then asks me, who has been there now for a grand total of 4 months, and I don't know the specific questions. I refer them to Downstream for helping describe what specific metrics are and do. They report to my superiors that I am not being a team player for this. They also don't know how to use my API, I have to explain concepts like GET and POST to them, how to serialize datetimes. I end up writing some of their code for them just to make it work.

    In the end, we shipped late. There was an arbitrary deadline set by the CTO that we missed - we were not consulted on this deadline, there was no reason for the deadline beyond "We should be live on this date". We missed it by 5 days. During those 5 days I am online every waking moment, sleeping an average of 4-5 hours per night. I'm a walking zombie trying to patch this thing.

    A week after release I'm called onto a meeting with my direct boss, who reports to the CTO. He tells me that due to my "Lack of Ownership" and "Lacking team spirit" they are letting me go. I'm stunned. This entire time literally any decision I tried to make was overridden. They chose the worst possible architecture, forced me to implement it, forced me to talk to third parties about designing this anti-pattern. I had 2 other teams actively work against me, and on top of that I had no support from anyone. I was alone, and isolated. I got off that call, and I just cried. I felt like such a failure.

    I'm at a new job now, and I've realized what a toxic environment that was. Horrible engineering practices, way too much pressure on me alone. I had developed health issues that I wasn't even aware of that now have subsided. I literally tried my best, and they just let me go. I found out later that my boss who fired me was being chewed out over the horrid project, and he put 100% of the blame on me to save his own ass.

    Thanks for listening

    • A nightmare. I've never had anything quite that bad, but I've had plenty of work experience where management is making bad decisions and has no accountability.

      My current role is hourly, so I'm happy to shut the laptop exactly 8 hours into the day. Pays a lot less, sadly.

      • That 8 hours is a godsend. You reminded me of another story there. My first week, my first few days I went into office. I had about 5 hours of work because you know, onboarding. After that I sat around for an hour or two, asking people what to do, reading documentation, you know. After 7 hours I was like (to the same manager), do you have anything else for me? Or should I get going for day. He said nope! Great first day, see you tomorrow! I literally thought nothing of it, it's the first week, that's how all first weeks are. Onboarding is always slow.

        That bastard sat me down in my second week saying they had a strict 8 hour in office policy and that "I had been noticed". I reminded him that he was the one who said I could leave early and that on even that day I was in earlier than he was. I learned that it didn't matter if I showed up at 7am, if I left at 3 they would think I'm "leaving early". My ride unfortunately dropped me off every day at 7, so I ended up having to work 9 hour days every day in office so they wouldn't think I was slacking off.

    • Oh man, i felt that one. Thats full on red flags and if i were in your shoes, and being fired didnt stun me, id have sent a mail to all teams and managers involved (including ceo and cto) and shown the emails and reports showing the toxicity. Wouldnt have gone down without a final fuck you haha.

      That said, sometimes its best to let it go and start something new somewhere else, like you did.

      Im also in a semi similar scenario at the moment. They want me, and 2 others, to make a new version of their program in .net. Thats all fine and dandy. We get functional input when asked and all that.

      We chose to create .net code/windows that are executed/called from inside the old client. However, when push comes to shove there is no support whatsoever. The other client team doesnt want to implement our stuff and delays it as much as they can. The server /api team does whatever the fuck they want, constantly breaking everything and choosing anti-patterns on their end. Manager will (and suspect he has already) thrown me and the architect under the bus because we have exposed the bullshit of said server team.
      Besides functional input we are completely on our own with no support, on the contrary. We have to fight for every choice or design. And god knows when our code will get released... Its been 3 fucking years and our code has been done for a very long time.

      Hell, even release was hard. "Can i push release from devops pipelines?" "No."
      "Can i execute the needed script automatically from devops?" "No"
      "You want me to do release manually?" "Yes". " not going to happen mate".

      I also made several packages and helpful tools to make communication with the system easier, but dont you dare think anyone has promoted that internally to other teams. Hell, when i do get feedback and report that, nothing gets done with it. No ask or preasure to server team to implement the api calls.
      So many issues they could solve if they just fucking listen

      Id send the mail i was talking about here too when i get out, but im a consultant. I should not throw my company under the bus for this when we find a new project for me to do but ive been really badly wanted to do it and have the ceo in cc because fuck that

      People like you and i should not doubt ourselves because of shit like this. From your story you know your stuff and listen to what the team has to say, you consider their experiences and what they are prepared to do. Thats good skills for an architect!

      • Know that I completely empathize with everything here, even the consultancy bits. It kills me when companies won't do basic things like CI/CD. In fact, that's one of the major red flags. If a company isn't minimum doing some sort of pipeline to go to prod it's pretty much a no from me at this point. It's such an important critical security step that if you didn't do that, you're not doing a lot else either.

        Sounds like you're where I was, but you've had a longer timeline luckily. Don't let them blame you, don't let them put it on you. Sounds like you're walking that political tightrope pretty well.

        Thank you for the kind words, I've been feeling pretty low since then and your last few words made me smile :)

    • Love it when the CTO is a guy who's work experience was previously selling bikinis, but surely he'll do fine managing the technical team.

    • That sucks. It sounds like a dodged bullet and I wouldn't take it personally.

      I've seen this happen from different angles where a manager or c-suite has them hanging people out to dry so they can protect their own ego. Even if you managed to get through that situation, you'll feel like you're walking on glass for every project and that's just not a way you want to live.

      • That's exactly how it is. Every project now I'm worried everyone is against me and that one slip up will be it. My confidence is at zero and all because that of that shit manager. I appreciate the words, it's something I'll have to overcome over time.

    • So, they didn’t know how to properly configure prometheus. I tell them I can kill 2 birds with one stone. No, prometheus bad. Rejected.

      Bruh I would trust a high schooler to successfully spin up prometheus; stories like this are what make more grateful for my job, brings back memories of insane posts on r/sysadmin

      • They had one single Prometheus node for the entire company and couldn't figure out why it needed so much CPU. They never once thought that maybe they set it up incorrectly

    • Jesus fucking christ, that's incredible. I don't know what any of that software engineering stuff is, but based on your description of events, it just sounds like a waking nightmare.

      If it makes you feel better, companies like that where upper management are quick to throw people under the bus for their own fuck ups are usually not long for this world. They'll continue to make bad decisions and the effects will be felt both downstream with low employee morale and retention rates, as well as commercial loss for the company. You are much better off being valued for your work elsewhere.

    • When this job is frustrating, it can be the most frustrating of any type of job.

      Sorry and thank god you got out.

  • Not trying to brag here, but I've never been fired. I did come close though.

    At Burger King, I had a habit of forgetting to take the grate out of the oil filtration system when I cleaned out the fryers. This lead to me throwing it away on two occasions. The third time I did it they were going to fire me. Luckily one of my co-workers jumped into the trash and dug around until she found it.

    Also, the co-worker was my girlfriend of about a few months at the time. We are married now.

    • You... Threw oil away in a common trashcan?

      • No, there was a metal piece that a filter went onto (the grate). Usually the oil got filtered and put back into the fryer and topped off with some more shortening. If it was too dark, it all went into the caddy and pumped into a storage unit. What happened to it after then I don't recall.

  • I got fired for taking an approved day off. Twice.

    First was doing a temp job installing new checkout lanes and setting up the network for them at a grocery store chain. I was the ONLY contractor on the team. I was told EVERYONE had thanksgiving off, and I confirmed that included me. But then, on fucking thanksgiving, when I am at family's in another fucking state, the stupid cunt who told me I had the day off call me asking why I didnt come in and then fired me on the spot, over the phone, when I reminded her that she herself had confirmed that I also had the day off when I asked a week ago.

    Second was a WISP and fired me when I did not volunteer to work my ONE day off a week because I already had a god damn doctor's appointment scheduled and I could not reschedule. I was probably gonna quit that one anyway after securing something better at a competitor, since the owners were all MAGA fuck faces.

  • I got fired from Starbucks for not smiling enough back in the late 90s. To be fair, I have a pretty bad case of Resting removed Face, so I get it.

  • One summer break, I came home from college and needed a job. Previously, I had worked a very cushy job at a video store, but we all know what happened to those. My dad had been working odd jobs at the local race track and said they could use my help. I figured why not, it would certainly be different than the other food service jobs I had in the past. Well let me tell you, it ended up being the absolute worst version of food service I would ever experience. For starters, the company in charge of managing the food stands didn't train me properly before the first race of the season. They would just sort of put me on various tasks that had nothing to do with what would be required on race day like cleaning the booths and inventorying product. So when the first race came, I tried my best but I had no idea what I was doing. I didn't know there was a special procedure for keeping track of ice bags. I didn't know who to go to to get into the coolers to stock drinks when we ran out. Etc etc etc. They weren't happy, but it was the first race, so this time they had me shadow someone for a few small races before the next big one. Well it turns out that the rules are different for small races vs big races. And also there were 3 different tracks to learn where everything is. So shadowing for small races means I was only learning the layout and rules for all races. While all of this was happening, it was summer and things were getting hotter and hotter every day. And of course, big races mean longer hours to boot! So by the time the first big race came around, I still wasn't properly trained, they were getting 130F readings on the racetrack, and I had to work a 13 hour shift. Oh and this was a 3 day event, so all of that back-to-back. I did the first day, I somehow made it out alive and didn't make any major mistakes. I got home, I passed out, I woke up again the next morning to do it again. I got all the way through security and into the stands to start my shift... And then I passed out. Turns out I had heat exhaustion. After that weekend, they gave me my next shift. I was supposed to start next day, but also, I needed a doctor's note to return to work. They knew damn well I couldn't get one that quick. So I said fuck it and just didn't get one and didn't show up. I decided I wasn't going to work that hard for hardly any pay and make myself sick to boot. Only time I've ever been fired, but I suppose it was a mutual firing.

  • Never been fired fired as I haven't had that many jobs and jobs in academia usually don't officially fire someone... the closest one I had was pretty wild though

    I was taking a summer job in college on a clinical research project; part-time job, we got assigned working hours at the beginning of each week. I was one of the few students who did not have clearance for clinical/counseling work so I could only do lab work. My performance wasn't the best and I couldn't do anything besides processing samples, so after 2-3 weeks they stopped issuing me work schedules and I was "fired"... or at least that's what I thought. Later it turned out the lead professor and the entire project got into a massive scandal (sexual harassment, bullying, etc... got on local news) that eventually got the professor fired (tenured btw so they can't be officially fired, uni "convinced" them to leave), so every student worker was essentially laid off at that moment. Probably likely that the entire research team got something akin to a stop-work order earlier so that's why I never got work assigned for those weeks...

    So yeah, the answer was a combination of 1) I wasn't that good of a worker and more importantly 2) the entire project we were on got into a scandal and was terminated

  • The company I was working for offshored all our jobs to Manila. To be fair the only reason I got the job was because the people we were replacing had their jobs out sourced to us. Just corpo shit.

  • Does getting laid off because a vulture company scooped up the place I was working, harvested the minimum wage workers, and fired everyone with a salary once they were done scraping our institutional knowledge out count?

  • Not following new RTO for a cloud based software company with no onprem infrastructure to manage, as the IT support after covid was deemed over.

  • Because I made the mistake of saying over IM that my team lead at the call center was going to make me have a breakdown.

    Apparently, the last guy who that team lead pushed to the edge made some actionable threats, and because I expressed how his harassment was effecting me I was fired.

    The team lead was a loyal slave. He used to be a bouncer so he thanked boss and god for his new job, and doesn't even realize he's still at the bottom of the pyramid. -_-

  • The official reason for me getting fired were budget cuts, but I knew that the new department head actually wanted to hand my responsibilities to a buddy of theirs they had brought on board. Despite being there longer at the department than the new head and their buddy, as well as excellent performance reviews I had no chance to keep that job.

  • I'm a helicopter mechanic. I started a turbine helicopter engine to prove an entire shift of mechanics, quality assurance ("subject matter experts") and managers they're dumb. Then wrote a mean pass down insulting all of them, highlighting how many man hours, our time they've wasted, and how they made us all look stupid in front of the customer (US Marines.)

    At the time I was the night shift QA. I got to work and they told me we'd be replacing an engine that was bad, it wouldn't start (they left the ignition circuit breaker in, so no spark) but worse it was now leaking out of the thermocouples.

    I says, you flooded the engine; there's not supposed to be liquid fuel in that section. If you followed the procedures in our manuals you'd know how to blow the engine out to dry it then it would start.

    They'd already called the higher level engine maintenance squadron to confirm the engine was bad. I was talking to the site lead, Dave, I bet him a dollar I could start that engine. At the time I was the only person on the site with an engine turn certification. He says alright, try it.

    The Marines were already there. They determined nothing was wrong with the engine. I said, since you're here want to watch me light it off. They said yeah. I went through the flooded engine start and it started and ran up perfect.

    Next day I come in and Dave tells me I've been fired. There was one sentence in our rules that said only pilots could start engines. BUT Dave went to bat for me, explained the situation including that they certified me to run engines. He got it turned into two week suspension and a demotion, but I had so much PTO saved up he was going to pay me during it.

    I came back and was now just a mechanic. Which was alright since I never liked the rest of the QA department. I got less responsibility, got to listen to audio books and ding wrenches together. Every now and then the other QA inspectors and managers would come to me with questions and I'd get to say, "I'm sorry, I'm not paid enough to know that."

  • I was ghosted twice, by two separate employers. Does that count as being fired? I worked for a conference center (wait staff) I ran the Cafe, full cold buffet breakfast, as well as being the barista and there was a chef for any hot breakfast meals ordered, including room service deliveries for a hotel above that was super long, the building is listed at about 5000m2. The Cafe was almost in the middle. In a warehouse type structure. They originally said I would take over running the Cafe, me and the chef, for 3 months while someone went on holiday, 6 months later I still hadn't heard anything and it was such a hard task I asked to stop doing it and just do the conferences. They ghosted me.

    Second was about 15 years later, catering service I worked for, shonky af, oh have I got stories from there!! Covid hit, everything stopped, they asked me back for one job, they had my friend working slave labor for them while they pocketed the government covid payments and expected her (a single mum) to do twice the work she did before, with no breaks, she tried to tell them she had kids she couldn't do as much as they were asking, they ignored her and demanded she work every day, doing the catering for whatever functions they had (exhausting) and then all the dishes from the functions too (usually other employees do that job) she went until she burnt out and her kids needed her, she told them she couldn't work, they acted like she left rhem in the lurch and how dare she, and I was friends with her she they cut her off, stole her jacket, and ghosted me because we had become close friends. Scorched earth. They ended up begging for employees not long after that and no one would work for them. Horrible horrible people.

108 comments