The Friday Firing

My hand froze on the doorknob when I heard David’s voice through the thin office wall, sharp and dismissive.

“She’s been a liability lately, consistently missing targets,” he stated, his tone entirely devoid of the camaraderie he showed me earlier today. I could practically smell the stale, burnt coffee fumes seeping under the door crack from the break room next door.

Then Mark chimed in, his voice low and urgent, almost a whisper. “Yeah, the Q3 numbers don’t lie. It’s disruptive. We need her gone by Friday, quietly.” That specific deadline hit me like a physical blow to the gut.

My heart hammered against my ribs, a frantic, wild drumbeat in the sudden, suffocating silence of the hallway. *Gone by Friday?* They were actually planning to fire me. After all the late nights, the projects saved, the way I trusted them implicitly. The harsh fluorescent lights above seemed to flicker mockingly.

I pressed myself flat against the cool, painted wall, trying desperately to disappear, praying they wouldn’t open the door right now. Every nerve ending felt raw and exposed. What could I even do? How could they just talk about ending my career like this?

Then Sarah’s voice cut through their conversation, mentioning something specific about accessing my old server logs.

👇 Full story continued in the comments…Sarah’s voice was softer than David’s or Mark’s, but the mention of server logs sent a fresh jolt of panic mixed with confusion through me. Why would they need *my* old server logs? I hadn’t touched that system in months, not since the migration. Was there something incriminating hidden there? Had I missed something?

“Her access was tied to the old system,” Sarah explained, her voice gaining a hint of urgency. “The Q3 failures… they match the period right after the data migration. I’ve been cross-referencing the project files, and some critical reports just vanished from the shared drive around then. If her logs show she accessed them just before they disappeared, we might have a different explanation than ‘missing targets’.”

A different explanation? My mind raced. Vanished reports? Data migration? I *had* noticed some weird glitches after the migration, missing files, corrupted links, but I’d just attributed it to typical post-migration chaos and worked around it, recreating or finding alternative sources. It hadn’t occurred to me it could be deliberate, or linked to my performance dip.

David scoffed. “Accessing them doesn’t mean she deleted them, Sarah. She’s just dropped the ball.”

“Or,” Sarah countered firmly, “someone else accessed them *using* her credentials during the chaotic handover, knowing her access was about to change. The timing is too perfect. If we can prove the files were deliberately removed, accessed under her login but potentially by someone else, it changes everything. It clears *her* name, and points to sabotage.”

Sabotage. The word hung in the air, chilling me to the bone. Not just incompetent, but potentially framed? My colleagues, the ones I’d shared coffee with and stayed late for?

Mark’s whisper returned, sharper this time. “Sabotage? Are you serious? Look, Sarah, whether she’s incompetent or framed, the results are the same – disruption, missed targets. We need stability *now*. The logs are a distraction. Friday is the deadline.”

“But if it *was* sabotage,” Sarah insisted, her voice rising slightly, “firing *her* is the wrong move! We need to find out who did it. The logs are the only way to trace it.”

I barely registered the rest of their hushed argument. Sabotage. Server logs. My credentials. It clicked into place with horrifying clarity. The missing reports, the sudden difficulty accessing key data, the projects that had seemed to fall apart through no fault of my own – it wasn’t just bad luck or incompetence. Someone had actively undermined my work, using the post-migration mess as cover. And David and Mark were so focused on the *outcome* (missed targets) that they were blind, or maybe willfully ignorant, to the *cause*. Sarah, thankfully, was not.

My initial shock and fear gave way to a cold, simmering fury. Gone by Friday because *someone else* sabotaged my work? Because David and Mark couldn’t see past the numbers?

I needed those logs. Sarah was right. They were the only way to defend myself, to prove I wasn’t a liability, but a victim of deliberate action. And I needed to act fast, before Friday.

Taking a deep, shaky breath, I straightened up. I couldn’t just cower in the hallway. I had to get ahead of this. My mind raced, forming a plan. I knew the old system’s architecture better than anyone. I knew where those logs were stored, and how to access them without triggering immediate alerts, especially if they were already looking.

Pushing away from the wall, my feet moved silently down the hallway towards the server room, not the conference room. There was no time for confrontation, not yet. My priority was securing the evidence Sarah talked about. My career, my reputation, depended on proving I wasn’t a liability, but the target of one. And I had less than three days to do it.