My Boss Stole My Algorithm For A Massive Pitch — So I Hardcoded A Surprise Into The Final Demo
Part 2
I stared at the thick stack of printed logs, my heart pounding a frantic rhythm against my ribs.
Brenda crossed her arms, her expression severe and unyielding.
Greg pointed a perfectly manicured finger at the highlighted timestamps on the top page.
He accused me of trying to steal proprietary code to sell to a competitor.
The audacity of his lie left me momentarily speechless.
He was projecting his own theft onto me to cover his tracks.
I took a slow, deliberate breath to steady my shaking hands.
Denying it outright would only give him an excuse to fire me on the spot.
I needed to stay employed just long enough to see the demo through.
Lowering my gaze, I adopted a posture of terrified submission.
Nerves about the board meeting were my excuse for running a final diagnostic check.
Brenda frowned, flipping through the rest of the pages.
The logs only showed a library update, nothing being downloaded or exported.
Greg’s jaw clenched in frustration.
He had hoped for a smoking gun, but all he had was a procedural violation.
Signing a formal written warning for accessing the staging server without his explicit permission was his immediate demand.
I picked up the pen, my hand trembling just enough to sell the performance.
The ink scratched loudly against the paper as I scrawled my signature.
He snatched the clipboard away, a triumphant gleam returning to his eyes.
Touching the server again before the demo this afternoon would result in me being escorted out by security, he warned.
They turned and left my cubicle, leaving me alone in the suffocating silence.
I slumped back in my chair, exhaling a long, shaky breath.
The trap was still intact on the server, hidden deep within the runtime environment.
He hadn’t found the backdoor, only the access record.
But now my administrative credentials were completely locked down.
I couldn’t monitor the system or make any adjustments.
Flying blind into the most important presentation of my life was a terrifying reality.
The clock on my monitor ticked closer to the demo time.
My palms began to sweat as I stared at the blank screen.
But had my hidden automated trigger survived his frantic security sweep?
Part 3
Megan stared at the blinking cursor, the answer to her problem suddenly crystallizing in her mind.
She didn’t need to trigger the kill switch manually during the presentation.
Automating the execution using a timed cron job on her local machine was the perfect alternative.
The script would quietly ping the staging server’s hidden endpoint at exactly 2:15 PM, right when Greg was scheduled to launch the live simulation.
Her fingers danced across the keyboard, writing the sequence in a matter of minutes.
The code was elegant, untraceable, and devastatingly precise.
She set the timer, locked her workstation, and forced herself to exhale.
The countdown had officially begun.
The morning dragged on, the air in the engineering bay thick with unspoken anxiety.
Megan sat hunched over her keyboard, her eyes scanning the sprawling database tables one last time.
Running a silent diagnostic on the primary staging server was her first priority.
The resource allocation graphs spiked and settled in a steady, reassuring rhythm.
Across the room, Greg loudly demanded a final run-through of his slide deck.
His voice boomed over the low hum of the servers, filled with unearned confidence.
Minimizing her terminal window, she watched him stride past her cubicle.
He didn’t even glance in her direction, completely absorbed in his own impending victory.
Pulling up the hidden chron job interface she had meticulously coded brought a small measure of comfort.
The countdown timer ticked away, a digital heartbeat pulsing in the corner of her screen.
Her fingers hovered over the keys, running through a mental checklist of every possible failure point.
If the load balancer shifted traffic away from the main endpoint, her trap might misfire.
Scripting a fail-safe protocol ensured the patch remained anchored to his specific session ID.
The code compiled smoothly, returning a crisp, green success message.
Leaning back in her chair, she rolled her shoulders to ease the tight knots of tension.
Brenda from HR walked by, her heels clicking sharply against the linoleum.
A tight, professional smile was offered to Megan before Brenda disappeared into Greg’s office.
They were likely finalizing the paperwork for his highly anticipated promotion.
Focusing her attention back on the network traffic logs, Megan isolated the specific IP addresses.
She pinpointed the connections assigned to the executive boardroom on the top floor.
This afternoon, Tyler and the rest of the board would be sitting exactly there.
Mapping the route her automated script would take through the internal network required absolute precision.
It was a delicate maneuver, requiring the patch to bypass three separate firewalls without triggering an alert.
Encrypting the payload to look like a standard library dependency update had taken her the entire morning.
Now, all she could do was wait and trust the architecture she had built.
She pulled up a fresh terminal window and started typing out a mundane shell script just to look busy.
The repetitive motion of coding helped calm her racing heart.
Remaining completely invisible until the exact moment the trap sprang was absolutely crucial.
Greg’s laughter echoed from his office, a harsh, grating sound that made her jaw clench.
He was already celebrating, already spending the bonus he thought he was about to receive.
Closing her eyes for a brief moment, Megan visualized the sequence of events she had engineered.
The payload was secure, the timer was set, and the target was completely oblivious.
Opening her eyes, she deleted the useless shell script she had been writing.
It was time to pack up her lunch and step away from her desk before anyone noticed her lingering.
Shutting down her local environment left only the hidden chron process running in the background.
The snare was primed, waiting silently in the dark.
She double-checked the physical connection to the primary router beneath her desk.
A loose cable now could ruin months of careful planning.
Satisfied the hardware was secure, she took a slow sip of her lukewarm coffee.
The bitter taste grounded her, pushing away the last lingering doubts.
Her phone buzzed with an automated calendar reminder for the investor presentation.
Swiping the notification away, she placed the device face down on her notebook.
She watched the breakroom slowly empty as the junior developers headed back to their desks.
Only a few senior engineers remained, too focused on their own deadlines to pay her any mind.
Checking the memory buffers one last time, she verified the execution footprint was nonexistent.
Greg’s frantic security sweep wouldn’t detect a process that wasn’t actively consuming resources yet.
The dormant code would only awaken when the exact parameters of the demo were met.
Until then, it was just another shadow in the system’s massive infrastructure.
She logged out of the network, the screens fading to black one by one.
Everything was perfectly aligned for the destruction of Greg’s career.
But Megan was a developer.
She understood the architecture of the system better than anyone else on the planet.
Greg had stolen the code, but he didn’t understand the underlying dependencies.
He didn’t know about the authentication token required to run the predictive model at full capacity.
The cascade sequence she had embedded in the routine library update was entirely unknown to him.
And he certainly didn’t know about the timed script currently counting down on her locked computer.
The rest of the morning dragged on with excruciating slowness.
The office was a hive of nervous energy as preparations for the investor demo reached a fever pitch.
Greg strutted through the aisles, shouting orders and adjusting his tie every five minutes.
He had banned Megan from the conference room, claiming her recent disciplinary issue made her a liability.
She was ordered to remain at her desk and monitor the server stability from a distance.
It was the perfect alibi.
Megan spent the hours before the demo reviewing the execution logs of her local machine.
The cron job was primed and waiting.
She checked the network latency, calculating the exact millisecond her ping would hit the server.
The precision was critical; the kill switch had to activate exactly when Greg initialized the main visualization.
If it fired too early, he would simply cancel the demo and blame a technical glitch.
Waiting too long meant he would already have claimed victory.
It had to happen in real-time, in front of the board and Tyler.
Megan stared at her screen, needing the quiet solitude to center herself amidst the chaos.
She gripped the warm mug of her cheap breakroom coffee.
The glow of the monitors illuminated her pale, determined face.
She opened the terminal window and stared at the blinking cursor.
This was the point of no return.
If her trap failed, she would be fired and blacklisted from the industry.
Greg would take her algorithm, get his promotion, and leave her with nothing.
She took a slow sip of the bitter coffee, her resolve hardening into something cold and sharp.
Letting that happen was completely out of the question.
As noon approached, the office filled with an even more frantic level of activity.
The catering team arrived, wheeling in carts of expensive pastries and artisanal coffee for the executive suites.
Megan watched them pass her cubicle, the smell of fresh croissants doing nothing to settle her stomach.
Greg emerged from his office looking like a man who had already won the lottery.
He wore a tailored charcoal suit that probably cost more than Megan’s monthly rent.
His hair was perfectly styled, not a single strand out of place.
He clapped his hands together loudly, demanding the attention of the engineering floor.
Delivering a condescending speech about teamwork and dedication, he deliberately avoided making eye contact with Megan.
Project Phoenix was discussed as if it were his own flesh and blood, a brilliant child he had nurtured into existence.
Megan stared at her screen, her fingers lightly resting on the keyboard.
She let his words wash over her, a meaningless drone of corporate doublespeak.
At 12:30 PM, the first of the executive town cars pulled up to the front entrance.
Tyler walked into the building a few minutes later, flanked by a small entourage of senior analysts.
He looked sharp, focused, and completely oblivious to the theft occurring right under his nose.
Pausing by the engineering bay, his eyes scanned the rows of cubicles.
Catching Megan’s eye, he offered a brief, polite nod before being whisked away by Greg towards the main conference room.
Greg’s obsequious laughter echoed down the hallway, grating against Megan’s nerves like sandpaper.
Brenda from HR was also hovering near the conference room, holding a sleek tablet and wearing a severe expression.
She was there to ensure everything ran smoothly from a personnel standpoint, her presence a silent threat to anyone who might disrupt the proceedings.
Megan turned her attention back to her monitors, pulling up the resource utilization graphs for the staging server.
The CPU load was holding steady at a comfortable twenty percent.
Optimal memory allocation ensured the garbage collection routines ran silently in the background.
It was a beautiful system, a symphony of logic and mathematics.
Knowing that Greg was about to parade it around as his own creation hurt deeply.
She opened a secondary terminal and checked the status of her cron job.
The countdown timer read four hours and twelve minutes.
She minimized the window, leaving it to run invisibly in the background.
The hours leading up to the presentation were a masterclass in psychological torture.
Greg kept sending urgent, panicked emails to the entire team, demanding last-minute cosmetic changes to the user interface.
He wanted the font size increased, the color palette adjusted to match the company logo, the loading animations made flashier.
Caring only about the surface, he remained entirely ignorant of the complex machinery whirring beneath it.
Megan implemented the changes with cold, mechanical efficiency.
Every modification she pushed to the server was another piece of bait on the hook.
She made sure the UI looked flawless, a perfect shiny apple with a razor blade hidden inside.
At 1:00 PM, the catering staff cleared away the lunch trays, leaving behind a tense, expectant silence.
The board members were beginning to dial into the secure video conference line.
Megan could see the active connections popping up on her network monitor.
They were logging in from New York, London, and Tokyo.
The entire global leadership team was assembled to witness the unveiling of Project Phoenix.
Greg’s career was about to either launch into the stratosphere or crash violently into the ground.
Megan’s phone buzzed on her desk.
It was a text from Tyler’s executive assistant, a company-wide broadcast reminding everyone to keep network traffic to a minimum during the demo.
Megan smiled grimly, her eyes fixed on the cron job timer.
Two hours and fifteen minutes remaining.
She began to mentally rehearse the sequence of events she expected to unfold.
Greg would start with a glossy slide deck, full of buzzwords and projected revenue charts.
He would talk about synergy, optimization, and market disruption.
Spending at least twenty minutes building up the hype was his usual tactic before even touching the actual software.
Then, he would launch the main visualization interface.
He would input a sample set of logistics data, expecting the algorithm to calculate the optimal delivery routes in real-time.
Expecting a beautiful, colorful map to populate on the giant screen in the conference room, he would wait confidently.
Instead, he was going to get the surprise of his life.
Megan’s patch was designed to intercept the main visualization call.
It would check the session token of the user executing the command.
Since Greg would be logged in under his own administrative account, the token would not match Megan’s encrypted signature.
The patch would immediately halt the routing calculation.
It wouldn’t crash the system; a crash could be blamed on a hardware failure or a random bug.
A crash would give Greg an excuse to reschedule.
Megan’s code was far more vindictive than a simple crash.
It was going to execute a specific, undeniable sequence of commands that would lay the truth bare for everyone to see.
At 1:45 PM, the heavy wooden doors of the main conference room swung shut.
The engineering floor fell dead silent, the collective breath of fifty developers held in anticipation.
Megan sat perfectly still, her hands folded in her lap.
She watched the server logs begin to scroll rapidly down her left monitor.
Greg was initiating the startup sequence.
The database connections were established, the API endpoints were verified, the memory buffers were allocated.
Everything was running exactly according to design.
The trap was armed and waiting for the final trigger.
Megan closed her eyes and focused on the rhythmic hum of the servers in the adjoining room.
She thought about all the weekends she had sacrificed, all the late nights she had spent staring at lines of code until her vision blurred.
She thought about the arrogant smirk on Greg’s face when he handed her that written warning.
He thought he had won.
He thought she was just a disposable asset, a quiet girl who would fade into the background while he stole her brilliance.
He was wrong.
The timer on her screen silently clicked down to zero.
Megan opened a hidden terminal window on her secondary monitor.
She typed in a string of administrative commands, bypassing the standard firewall protocols with practiced ease.
She wasn’t just going to monitor the server logs; she was going to watch the execution live.
The company’s security cameras were connected to the same internal network as the staging servers.
It took her less than thirty seconds to isolate the IP address for the camera in the main conference room.
She routed the feed through a proxy server to mask her location and opened the video player.
The high-definition image flickered onto her screen, providing a perfect, unobstructed view of the room.
The audio feed crackled to life, picking up the low murmur of executive voices.
Greg stood at the front of the room, bathed in the glow of the massive projection screen.
He looked confident, completely in his element as he gestured broadly toward a slide full of meaningless pie charts.
Tyler sat at the head of the long mahogany table, his hands steeple together in quiet concentration.
Several other senior executives were scattered around the table, while the faces of the global board members were displayed on secondary monitors along the wall.
Brenda stood near the door, her tablet pressed against her chest like a shield.
Megan leaned closer to her screen, her heart pounding a heavy rhythm against her ribs.
She reached out and turned up the volume on her headset.
“And that, ladies and gentlemen, is why the legacy system is no longer viable,” Greg was saying, his voice smooth and practiced.
“We are losing millions of dollars a year in inefficient routing and delayed response times.”
He clicked a button on his remote, advancing to the next slide.
“But over the last eight months, I have personally overseen the development of a solution.”
Megan’s hands clenched into tight fists, her nails digging into her palms.
“I call it Project Phoenix,” Greg announced, pausing dramatically for effect.
“It is a fully autonomous, predictive modeling engine that will reduce our logistics overhead by at least thirty percent.”
A low murmur of appreciation rippled through the room.
Tyler leaned forward, his eyes narrowing slightly as he studied the bullet points on the screen.
“Those are bold claims, Greg,” Tyler said, his voice cutting through the chatter.
“Can you back them up with a live demonstration?”
“Absolutely, Tyler,” Greg replied, a smug smile spreading across his face.
“I have prepared a simulation using real-time data from our Northeast distribution hub.”
He turned to his laptop, which was connected to the main projector.
Megan’s eyes darted from the video feed to the server logs scrolling on her other monitor.
She saw the database query hit the server.
Greg was loading the initial parameters for the simulation.
The data packets flowed smoothly, entirely uninterrupted by her hidden patch.
She needed him to feel completely secure before the floor fell out from under him.
The projector screen shifted, displaying a highly detailed map of the Northeast corridor.
Hundreds of tiny red dots appeared on the map, representing active delivery vehicles.
“As you can see, the current routing is chaotic and highly inefficient,” Greg explained, gesturing at the screen.
“Vehicles are deadheading, routes are overlapping, and fuel is being wasted.”
He looked around the room, making sure he had everyone’s undivided attention.
“Now, I will initialize the Phoenix algorithm and let it optimize the entire network in real-time.”
He reached out and pressed the enter key on his laptop.
On Megan’s screen, the server logs spiked as the main visualization executable was called.
The cron job timer on her desktop simultaneously hit zero.
The ping was sent.
Inside the conference room, the map on the projector screen froze.
The red dots stopped moving.
A loading icon appeared in the center of the screen, spinning endlessly.
Greg frowned, tapping the enter key a few more times.
“Just a slight network delay,” he muttered, his confident facade slipping for a fraction of a second.
“The algorithm is processing a massive amount of data.”
Megan watched the server logs with breathless anticipation.
Her patch had successfully intercepted the initialization command.
It was currently comparing Greg’s session token against the hardcoded master key.
The authentication failed, exactly as she had designed it to.
The kill switch was triggered.
Suddenly, the loading icon vanished from the projector screen.
The map of the Northeast corridor dissolved into a sea of static.
Greg let out a startled gasp, furiously clicking his mouse in a desperate attempt to recover the presentation.
“I apologize, it seems we have a minor visual glitch,” he stammered, his face flushing red.
But it wasn’t a glitch.
The static cleared, replaced by a stark black background.
Lines of neon green code began scrolling rapidly down the screen, mirroring the exact deployment history of Project Phoenix.
The font was massive, impossible for anyone in the room to ignore.
Tyler stood up, pushing his chair back with a loud scrape.
“What is this, Greg?” he demanded, his voice sharp and authoritative.
Greg stared at the screen in abject horror, his mouth opening and closing like a landed fish.
“I… I don’t know,” he lied, his hands shaking violently over his laptop keyboard.
“It must be a cyber attack.”
The scrolling code on the screen suddenly stopped.
A new block of text materialized in the center of the projection, the letters large and uncompromising.
It was the complete, undeniable truth.
The text illuminated the darkened conference room, burning the truth into the retinas of every executive present.
“PROJECT PHOENIX CORE ENGINE. ARCHITECT AND SOLE DEVELOPER: MEGAN.”
Below the header, a detailed statistical breakdown appeared.
“TOTAL LINES OF CODE COMMITTED: 142,854.”
“LINES CONTRIBUTED BY MEGAN: 142,854.”
“LINES CONTRIBUTED BY GREG: 0.”
A collective gasp echoed through the room, followed by a heavy, suffocating silence.
Greg lunged for his laptop, frantically hammering the escape key and trying to force a hard reboot.
The machine refused to respond, its operating system completely overridden by Megan’s patch.
He grabbed the power cable and yanked it out of the wall, desperate to sever the connection.
The projector screen simply switched to the backup power supply, the damning text glowing even brighter in the dim light.
Tyler stepped away from the table and walked slowly toward the front of the room.
He stared at the screen, his expression unreadable, then turned his gaze to the panicked project manager.
“Greg,” Tyler said, his voice dangerously quiet.
“Would you care to explain why the system you claimed to have built is currently identifying a junior engineer as its sole creator?”
Greg wiped a bead of sweat from his forehead, his charismatic veneer completely shattered.
“It’s a prank, Tyler,” Greg stammered, his voice cracking violently.
“She’s a disgruntled employee who has been trying to sabotage my work for weeks.”
He pointed a shaking finger at Brenda, who was standing frozen near the door.
“HR is fully aware of her disciplinary issues. We caught her trying to steal the code just yesterday!”
Brenda stepped forward, her severe expression faltering for the first time.
She looked at the massive block of text on the screen, then down at the tablet in her hands.
“The logs you provided yesterday showed unauthorized access to the staging server,” Brenda said slowly, her voice echoing in the quiet room.
“But they didn’t show any data extraction.”
She looked up, her eyes narrowing as she studied Greg’s terrified face.
“And frankly, Greg, if she wrote the code from scratch, it wouldn’t be theft.”
Tyler turned away from the projector and crossed his arms over his chest.
He looked directly into the camera on the conference table, addressing the board members dialing in remotely.
“Ladies and gentlemen, I apologize for this unprecedented interruption,” Tyler said, his tone perfectly professional.
“We will pause the presentation here while I conduct an immediate internal review.”
He reached down and disconnected the main audio feed, plunging the room into a tense, isolated silence.
Megan sat at her desk, her hands shaking so badly she could barely remove her headset.
She had done it.
The trap had sprung flawlessly, exposing Greg’s lies on the biggest stage possible.
But the adrenaline was rapidly fading, replaced by a cold, creeping sense of dread.
She had exposed him, but she had also hijacked a presentation to the board of directors.
She had bypassed security protocols, manipulated production servers, and humiliated a senior manager.
In the corporate world, being right rarely protected you from being fired for insubordination.
She closed the video feed and locked her terminal, waiting for the inevitable heavy footsteps of security guards.
Ten minutes later, the double doors leading to the engineering bay swung open.
It wasn’t a team of security guards.
It was Tyler, walking with long, purposeful strides, followed closely by Brenda.
The entire floor went silent as the VP of Operations navigated the maze of cubicles.
He stopped in front of Megan’s desk, towering over her small workspace.
Megan stood up slowly, her legs feeling like lead.
She kept her chin raised, refusing to show the terror clawing at her throat.
Tyler looked at her for a long moment, his eyes scanning her pale face and trembling hands.
“Did you write that code, Megan?” he asked, his voice low enough that only she and Brenda could hear.
“Yes,” she replied, her voice remarkably steady.
“Every single line.”
Tyler nodded slowly, accepting her answer without hesitation.
“And the patch that hijacked the projector?” he asked, a faint hint of amusement playing at the corners of his mouth.
“I wrote that too,” Megan admitted, bracing herself for the termination speech.
“He locked me out of the system. It was the only way to prove he was lying before he secured the promotion.”
Tyler turned to Brenda, who was already making furious notes on her tablet.
“Have Greg’s access badges revoked and escort him off the premises immediately,” Tyler ordered, his tone brokering no argument.
“We will conduct a full forensic audit of his communications, but I think we already know what we’ll find.”
Brenda nodded sharply and turned on her heel, marching back toward the conference room to deliver the killing blow.
Tyler turned his attention back to Megan.
He didn’t yell, he didn’t threaten her, and he didn’t demand an apology for the disruption.
He simply reached into his jacket pocket and pulled out a sleek, silver business card.
He placed it gently on her keyboard.
“Your methods are highly unorthodox, and you gave the board of directors a collective heart attack,” Tyler said, his expression completely serious.
“But the underlying architecture of that algorithm is the most brilliant piece of engineering I’ve seen in a decade.”
He tapped the business card twice with his index finger.
“Take the rest of the day off, Megan. Rest, recover, and celebrate.”
He offered her a rare, genuine smile.
“On Monday morning, you report directly to my office.”
He turned and walked away, leaving her standing in the stunned silence of the engineering bay.
Megan looked down at the silver card resting on her keyboard.
It was a direct line to the VP of Operations.
She reached out and traced the raised lettering with a trembling finger.
The suffocating weight that had crushed her for eight months finally lifted, replaced by the clean, sharp air of victory.
She grabbed her coat, turned off her monitors, and walked toward the exit without looking back.
THE END
Tell us what you think about this story, and share it with your friends. It might inspire them and brighten their day.
If you enjoyed this story, read this one: My Parents Stole $11,500 for a Luxury Vacation — So I Let Them Arrive at the Airport Before Canceling Everything
Disclaimer
This story is a work of fiction inspired by real events. Names, characters, and details have been altered. Any resemblance is coincidental. The author and publisher disclaim accuracy, liability, and responsibility for interpretations or reliance. If you would like to share your story, please send it to [email protected].
