My Boss Stole My Algorithm For A Massive Pitch — So I Hardcoded A Surprise Into The Final Demo
Part 1
My Boss Stole My Algorithm For A Massive Pitch — So I Hardcoded A Surprise Into The Final Demo.
I stared at the communal printer in the breakroom, the paper feeling heavy in my trembling hands.
The document was a draft presentation for the upcoming board meeting.
Across the top, in bold letters, it read “Project Phoenix – Developed by Greg”.
My stomach dropped into my shoes.
Project Phoenix was my code.
I had spent the last eight months working through weekends and skipping lunches to build that routing algorithm.
It was supposed to revolutionize our logistics dispatch system and save the company millions.
Greg was just the project manager.
His only contribution was asking for weekly status updates and occasionally bringing lukewarm coffee.
Now, he was claiming full credit for the most important project of my career.
I set the papers back on the printer tray.
My hands squeezed into fists at my sides.
I needed to get back to my desk before anyone noticed I was gone.
The hallway felt ten miles long.
Every step echoed on the linoleum, a rhythmic reminder of my own stupidity.
I had trusted him when he said we needed to keep the project under wraps until it was perfect.
He had convinced me to work in a secluded sandbox environment to prevent other teams from stealing our ideas.
The reality hit me like a physical blow.
He wasn’t protecting the code from the other teams.
Isolating me was his true goal, enabling him to steal it himself.
I slid into my cubicle and stared at my monitors.
Lines of elegant, efficient code stared back at me.
It was a masterpiece of predictive modeling.
I had poured my soul into every function and class.
Greg sauntered past my desk, pausing to lean against the partition.
His cologne smelled like expensive desperation.
He tapped his knuckles against the fiberglass wall.
A smug smile played across his lips.
We were presenting to Tyler, the VP of Operations, on Friday.
He casually mentioned that he would handle the actual demonstration part of the meeting.
My nails dug into my palms.
I forced a tight nod.
He turned and walked away, completely unaware that I had seen his draft presentation.
I waited until his office door clicked shut.
My fingers flew across the keyboard.
I opened the main repository to check the commit history.
The access denied error popped up on my screen in bright red text.
He had already revoked my administrative privileges.
My breathing grew shallow.
He was locking me out of my own project.
I leaned back in my chair and closed my eyes.
Panic threatened to overwhelm me, but I forced it down.
I was a software engineer.
Problems were just puzzles waiting to be solved.
I opened my local backup drive.
The core engine was still there, untouched by his greedy hands.
I started tracing the deployment pipeline.
He had copied my sandbox files into the main staging area.
But he didn’t understand the underlying architecture.
He was a manager, not a coder.
Realizing the core engine relied on a hidden authentication token was beyond him.
I spent the next three hours writing a very specific patch.
It was a harmless-looking snippet of code that checked the user ID of whoever launched the executable.
If the ID wasn’t mine, the patch would trigger a cascade.
I bundled the patch into a routine library update.
Uploading it to the staging server was easy using a temporary backdoor I had left for debugging.
The server accepted the update without throwing any flags.
My heart hammered against my ribs.
The trap was set.
All I had to do was wait for Friday.
The days dragged by with excruciating slowness.
Every time Greg walked past my desk, my muscles tensed.
He kept making passive-aggressive comments about how I needed to tidy up the documentation.
I nodded and smiled, playing the role of the obedient subordinate.
Inside, my mind was racing with contingency plans.
Wednesday afternoon brought a fresh wave of panic.
Tyler sent out a company-wide email announcing the final demo schedule.
The stakes were even higher than I had realized.
Executives from the board of directors would be dialing in remotely.
If this went well, Greg was guaranteed a massive promotion to Director of Engineering.
I would be left behind, a nameless code monkey in the basement.
Staying late that night allowed me to review every line of my patch.
It had to be flawless.
If he spotted the anomaly before the presentation, he would fire me on the spot.
The office was completely silent, the only sound the clatter of my mechanical keyboard.
I ran simulation after simulation in my local environment.
Thursday morning, the tension in the office was thick enough to cut with a knife.
Greg was frantically pacing around the conference room, testing the projector.
He barked orders at the junior staff, demanding fresh coffee and printed handouts.
I kept my head down, focusing on a menial database migration task.
My hands were shaking so badly I could barely type.
I took a deep breath and forced my fingers to steady.
Showing any weakness was something I couldn’t afford.
He needed to believe he had completely won.
At noon, I took a walk around the block to clear my head.
The cold air felt good against my flushed cheeks.
I rehearsed my plan over and over again in my mind.
The next morning, I arrived early to double-check the server logs.
Inside, the office was mostly empty, save for the hum of the air conditioning.
I pulled up the security console.
Someone had been reviewing the access logs overnight.
The hairs on the back of my neck stood up.
Greg’s admin account had been active at 2:00 AM.
He had noticed the unauthorized library update.
A shadow fell across my desk.
I looked up to see Greg standing there, flanked by Brenda from HR.
He held a thick stack of printed logs in his hands.
His face was a mask of feigned disappointment.
He dropped the stack onto my keyboard.
We need to talk about your unauthorized access, Megan.
