19-year-old employee boldly asks for 35% raise right after company changes policies for him, gets fired: 'I got ahead of myself, and I lost the opportunity'

• 
  via Unsplash+ (Jonathan Castañeda)

  A frustrated job candidate holds a brochure above his face that says "Looking for a Job"

  _{Image is representative only and does not depict the actual subjects of the story.}

• TIFU I asked for a 35% raise after the company changed their policy for me, and then I got fired

  
  via im_chase0
• 
  via im_chase0
• 
  via im_chase0
• 
  via im_chase0
• 
  via im_chase0

• Let's be clear about this. Proposing terms that will be beneficial to your working life should always be encouraged, but you have to be prepared for the inevitable. At a certain point, some negotiation terms will be too much for a hiring manager to accept. Normally, when this happens, they will present a counterproposal. Worst-case scenario, they draw their line in the sand and tell you in a straightforward manner that what you are suggesting is not feasible at all.

  What's particularly frustrating about this employee's story is that while he may have gotten a bit too hopeful about the prospects of negotiating a 35% raise on top of a fully remote arrangement, he likely would have accepted that rejection if his manager told him that wasn't going to happen. However, he didn't even get the opportunity to simply accept the current salary.

  Instead, the hiring manager clearly was sick and tired of him after the other negotiations. He just fired the employee entirely. That meant there was no opportunity to renegotiate, no opportunity to compromise, and no opportunity to even accept the underpaid amount. Now, he's back to square one, which is something we know all too well about here at FAIL Blog.

• 
  via im_chase0
• 
  via im_chase0
• 
  via im_chase0
• 
  via Unsplash+ (Jonathan Castañeda)

  The job candidate brushes up on his resume while sitting at his desk.

  _{Image is representative only and does not depict the actual subjects of the story.}

• 
  via im_chase0
• 
  via im_chase0
• 
  via im_chase0
• 
  via im_chase0
• 
  via im_chase0

Tags