An essential developer looks for advice on how to leverage a raise after becoming the last one remaining at the company capable of maintaining the company's legacy backend: 'How do I turn this into a raise without looking like I am holding them hostage?'

Author image for Brad Dickson
Brad Dickson • Managing Editor
Sep 12, 2026 7:15 PM EDT

In a viral online detailed account of their situation at work, this developer looks for advice on how to turn their new status as the sole caretaker of a fragile legacy system into fair compensation without making the request sound like a threat.

Advertisement
  • 01
    An exhausted software developer works late.
    via Getty Images

    An exhausted software developer works late. 

     

    Featured likenesses do not identify those mentioned.
     

  • Leverage is a tricky thing. People like leverage when they're on the right end of it, and it works in their favor, but they really, really don't like being on the other end of it.

    When it's an employer or authority figure. Say you're looking for a raise, or a more favorable working arrangement. They'll happily use leverage against you, if they can, probably reminding you that “everyone's replaceable” to keep you in your place and from asking too much.

    Say, the leverage goes the other way. You have knowledge or experience with the inner workings of something important to the company that no one else has. You both know you're not replaceable. No matter how many times they tell you otherwise. But if you remind your employer of this, if you apply that lever in the wrong place. Well, they might just bite their nose to spite their face and retaliate and get rid of you anyway. A reaction of pure ego, no logic.

    Studies support this too. A 2012 study on leadership by Ethan Burris found that managers are more likely to retaliate against employees who challenge the manager's own already held views. And that employees who raised issues with “challenging voice” were more likely to create perceptions of threat.

    Basically, managers sometimes interpret challenging information as a threat to their authority. In this way, leverage that challenges the employer's notion of control and power over the employee becomes that threat.

    The study, conversely, found that “supportive” ways of raising issues were more likely to avoid this pitfall. So, in the case of the raise, if you simply discuss positive ideas relating to the issue with your employer: growth, responsibility, outlook, commitment, you might just “incept” the idea in their mind and get them thinking about your importance and how you deserve a raise.

    In this account of events, which was shared with a popular online workplace community, a developer described the predicament of this very sort that they now faced.

    After a senior developer's resignation, this developer is now the only employee who understands the company’s legacy backend. Much of that departing senior developer's responsibilities now fall to the developer, by default. Yet, they are still earning the same salary. They have that senior-level responsibility now, but with none of the pay.  The dev sees a serious dependency risk that could cause production failures during their absence. They don't feel like they can take any time off without things unraveling. Management, meanwhile, treats the continued operation of the site as evidence that staffing is adequate.

    The dev wants to ask for a raise to match the pressure of responsibility they now feel. But they worry that doing so will overplay their hand. Now they are left wondering how to approach the situation. Worried that any mention of the leverage they now possess could cause their employer to feel threatened.

    My coworker quit and now I am the only one who knows how to keep the entire legacy backend from imploding. How do I turn this into a raise without looking like I am holding them hostage?

    Story / Combine_7_

    So my senior lead dev put in his two weeks notice about a month ago and now I am basically the only person left who understands how the logic flow actually works in our main legacy system. We are talking about a massive spaghetti monster that has been built over eight years with zero documentation and a lot of hacky fixes that somehow kept us afloat during the last high traffic season.

     

     When he left everyone just shrugged it off like it was no big deal but now every single bug or minor update falls on my desk and my slack notifications are basically a war zone from 8am to 10pm. 

     

    The mangement team seems to think that becuse the site is still running everything is fine and I can just absorb his entire workload without any compensation change because we are a family or whatever corporate nonsense they are pushing this week.

     

    The reality is that if I decided to walk out tomorrow or even just took a sick week the entire production enviornment would probably catch fire within forty eight hours because no one else even knows where the config files are stored or how the CI pipelines are actually triggered manually when the auto scripts fail. I am currently doing the job of two and a half people while still getting paid my original mid level salary and it is starting to get old really fast. 

     

    I know I have a lot of leverage right now but I do not want to come across as a total j*rk who is shaking the company down the second things get difficult even though that is exactly what they deserve for not having a backup plan. I need to figure out how to frame this as a market adjustment or a lead role promotion instead of just saying pay me more or watch the servers melt.

     

    I have been trying to document things but honestly there is so much technical debt that it would take me six months of doing nothing else just to get a decent wiki started, and they keep piling on new feature requests like we have a full team. 

     

    I am reaching my breaking point because I am tired of being the only person who gets paged at 3 am for things that I did not even write in the first place. It feels like I am being punished for being competent enough to figure out Mike's mess while everyone else just stays in their little silos and ignores the fire. 

     

    If I go to my manager and ask for a thirty percent bump he is going to say it is not in the budget but we both know that hiring a contractor to replace me would cost them triple that and it would take months for a new guy to even find the login credentials for the db.

     

    There has to be a way to navigate this without burning bridges because I actually like the product, but I hate the way the workload has shifted. Maybe I should just stop fixing the minor stuff and let a few non-critical systems fail, so they see what happens when I am spread too thin. 

     

    It is just annoying that I have to play these games just to get paid fairly for the actual value I am providing to the stack. 

     

    I am just tired of the constant fire drills and the lack of recognition for being the literal glue holding the infra together right now. My coffee is cold, and I have three more tickets to close before I can even think about lunch.

  • 02
    The developer maintains a legacy codebase.
    via Mohammad Rahmani

    The developer maintains a legacy codebase. 


    Actor performance of story events.
     

  • 03
    A developer feels the pressure of working on an understaffed technology team.
    via Tai Bui

    A developer feels the pressure of working on an understaffed technology team.



    Picture does not depict real parties.
     

  • 04
    blacknight334 Might be a hot take here, but personally I wouldn't document anything about your system if you do get the raise, or even mention the prospect to them. At least not for a while. Depending on how your upper management reacts, and if they can be spiteful or aggressive. They may get you to document it and then replace you. Whatever happens, look after yourself first, not the company.
    via Combine_7_
  • 05
    scramblor You need to stop with the heroics to keep things working. Until management can feel the impact of their decisions, they aren't going to change. And they won't feel that impact as long as you keep playing hero. Just work 9-5 and log off after. Take vacation and sick days like you normally would.
    via Combine_7_
  • 06
    Combine_7_ OP The best part is they just announced a hiring freeze so they literally cannot replace the guy who left even if they wanted to. I am stuck in a loop.
    via Combine_7_
  • 07
    Bitcoin_CEO Book a holiday. See if it does collapse when you aren't there and how many times they try to contact you during it, maybe actually answer some of the calls so you don't put them in too foul of a mood on your return or wreck the business. Then they should see your worth and you can negotiate from there.
    via Combine_7_
  • 08
    DanielSReichenbach Aren't they technically the ones holding you hostages already in this situation? They know the state of the legacy systems. If not, they are bad managers. Act under the assumption they willfully put you into this situation. That answers how much they value you, and how much effort you should put into this. A decent company will not act like this. A badly managed one will.
    via Combine_7_
  • 09
    alloutofchewingum Get a haircut, buy a new suit & have some friend meet you at a coffee shop during the workday where you know people from work will see you, have it look official, you're discussing folders full of papers etc. Leave business cards from recruiters visible on your desk. Excuse yourself from meetings with a brusque "I need to take this call, sorry." Tell your manager you need some random half days off during the week. They'll put 2 and 2 together.
    via Combine_7_
  • 10
    Emotional-Damage-995 Look professional wearing a suite. Clean cut. Exercise and lose weight. Then mention career growth and opportunities and working on new things to your boss. Followed by appreciated and modern technology. If he does not get the hint say you want a raise to match your performance and a promotion. BTW. It is good to interview. That senior guy quitting is a signal that he saw no way out. You should too
    via Combine_7_
  • 11
    LadybuggingLB The fastest and surest way to get a raise and promotion is interview until you get another offer and they'll counteroffer. But then you've got to realize that's your last raise and promotion from them. You will have played your last card.
    via Combine_7_
  • 12
    kbchucker The reality is if you left tomorrow, they would adjust and figure it out. The spaghetti might be messy for a while, but the corporation would move on. Ask for a raise, present your case for why. Don't tell them you're the only one who knows. They don't. care about that. You deserve a raise and promotion because you are now doing the work of a senior dev. That's it. If they say no, you then get to decide if you're going to stay.
    via Combine_7_

Want More? Follow Us and Add Us as a Preferred Source on Google.

Tags

management career advice software developer organizational culture overworked developer office culture workplace asking for a raise
Scroll Down For The Next Article