They Fired Me At 50 By Email After 18 Years ‘pack Your Desk. You’re Dead Weight’ That Night The Deal
The Showdown in San Francisco
My attorney called Monday morning. “Scott, I just got off the phone with Vortex’s general counsel. They want to meet you, me, Ethan, and their legal team.”
“When?”
“Thursday in San Francisco.”
“What are they offering?”
“They didn’t say. But Vortex’s general counsel was very interested in the engineering team. Asked if you had relationships with key technical staff. I told him you trained most of them.”
“What does that mean?”
“It means Vortex is thinking about alternatives. They might not need Nexcore at all.”
Ethan tried everything that week. Tuesday morning, Nexcore’s IT department called demanding I return the external hard drive with proprietary code. I told them to talk to my attorney.
She sent them a cease and desist letter explaining that my personal backups weren’t their leverage point. The patent was. The code was just my personal reference to confirm dates and authorship.
They backed off. Wednesday, Nexcore’s HR department sent a letter claiming my possession of proprietary development artifacts violated my employment agreement. They were trying to frame my ownership of my own code as theft.
My attorney shut that down too. But Ethan’s approach was different; he went directly after the team. Dylan called Wednesday evening, his voice shaky.
“Scott, Ethan came down to the engineering floor today. He gathered everyone in the conference room. He was really intense.”
“What did he say?”
“He said the deal might fall through because of legal complications with legacy code. Said if that happens, the whole department gets laid off. Everyone’s freaking out.”
I felt my jaw tighten. Ethan was using them as hostages. “Dylan, listen carefully. Ethan is lying to you. The deal isn’t falling apart because of me. It’s falling apart because he tried to sell technology he doesn’t own.”
“I know,” Dylan whispered. “But people are scared. Some people are panicking.”
“What are people saying?”
“Ethan tried blaming you. Said you’re holding the company hostage. But here’s the thing: nobody really bought it. Ethan wouldn’t answer when people asked direct questions.”
“He just kept repeating ‘one person’ and ‘disgruntled employee.’ People started looking at each other like something was off.” That was good. The team was seeing through Ethan’s nonsense. “How bad is it?” I asked.
“People are confused. They don’t know what to believe. But Ethan’s making it worse. He won’t give straight answers.” Dylan recorded part of the meeting on his phone because Ethan was being so weird about documentation. Smart.
“Scott, what’s really happening?”
“I can’t discuss details, but I need you to trust me. Whatever happens with this deal, I’m making sure the engineering team is protected. That’s my priority.”
“How?”
“You’ll see. Just keep documenting everything Ethan says. And tell people to stay calm. This isn’t going to end the way Ethan thinks it will.”
Over the next two days, I got more calls and texts from team members. But they weren’t angry calls demanding I stop. They were different.
One engineer said: “Ethan said you’re blocking the merger, but this feels wrong. What should we do?” Another said: “Ethan wouldn’t explain the legal issue when I asked, just said ‘Scott’s being difficult.’ What aren’t they telling us?”
Dylan sent me a screenshot of Ethan’s Slack message to the engineering channel. “Legal complications from a former employee. Can’t discuss specifics. Trust that leadership is handling it.” No details, no transparency—just corporate speak that made people more suspicious, not less.
Even the VP of engineering, the one who’d signed off on my termination, sent a careful text. “Whatever you’re planning, I hope it works out for the team.” The team wasn’t against me; they were watching, waiting, and trying to figure out who to trust. And Ethan was losing them.
Vortex Solutions headquarters was a glass tower in downtown San Francisco. Intimidating lobby, expensive everything—the kind of place where the coffee machines probably cost more than my car. I barely slept the night before.
I kept running through scenarios in my head. What if they sided with Ethan? What if I was walking into an ambush? But walking through those doors Thursday morning with my attorney beside me, I didn’t feel intimidated.
I felt like a 50-year-old engineer with 18 years of corporate battle scars and the deed to a technology empire. The conference room on the 32nd floor was set up like a tribunal. Long walnut table, leather chairs that probably cost 1,500 each, and windows overlooking the bay.
At the head sat Vortex’s general counsel: silver hair, sharp eyes that had seen every corporate maneuver in the book. And sitting next to him, looking like he’d aged five years in three days, was Ethan. Ethan’s usual navy suit was wrinkled.
His tie wasn’t quite straight. The golden boy facade was cracking under pressure. When he saw me walk in, his jaw clenched so hard I could see it from across the room.
“Scott,” Ethan said, not standing. “Didn’t realize this was going to be a joint meeting. Sit down.”
“Mr. Cole,” the general counsel said quietly. Ethan was already sitting. The comment was just to remind him who was in charge here.
The Vortex general counsel looked at me and my attorney. “Mr. Walsh, counselor, thank you for coming. As you know, Vortex is finalizing the acquisition of Nexcore Solutions. However, the patent ownership question has created complications.”
“There’s no complication,” Ethan interrupted. “This is a disgruntled former employee trying to leverage a paperwork error into a payday. We have comprehensive IP assignment clauses in all our employment contracts. This is extortion.”
My attorney slid a document across the table. “That’s Mr. Walsh’s original freelance agreement from 18 years ago. Section 4, Subsection C states that any intellectual property created by the contractor on personal equipment outside billable hours remains contractor property until formally assigned.”
“Mr. Walsh wrote the adaptive load distribution logic on his personal laptop during a weekend three days before his full-time employment began. He filed patent number 8532991 in his own name. Nexcore never requested assignment, never paid for assignment, never even acknowledged it existed until this acquisition started falling apart.”
The general counsel picked up the document and read it carefully. His expression didn’t change, but I saw his eyes narrow slightly when he got to the dates. He looked at Ethan.
“Is this accurate?”
“It’s a technicality. The spirit of the agreement was that all development work belonged to Nexcore.”
“Actually, I worked from home that weekend because the office computers were garbage,” I said. “And the spirit of the law doesn’t matter in federal court. You know that, Ethan. You just thought I was too stupid to figure out I own something valuable.”
Ethan’s face went red. “Don’t you dare.”
“Dare what? Tell the truth? You built your entire company on technology you never owned. You sold that company to Vortex for $180 million, and now you’re sitting in this conference room realizing you can’t deliver what you promised.”
“This is interference with contract! I have investors, board obligations, 47 employees who are going to lose their jobs because you’re being petty!”
“I’m not being petty, Ethan. I’m being smart. Something you should have tried before firing your lead architect.”
The silence in that room was deafening. Everyone was waiting to see who’d break first. The general counsel held up a hand.
“Gentlemen, let’s keep this professional.” He turned to me. “Mr. Walsh, what’s your actual goal here?”
Good question. Direct, no nonsense. “My goal is simple. I want the engineers protected. The people who actually built this company while Ethan took credit at investor meetings.”
