Chapter 5: The Man They Suddenly Needed

I laughed. "Victor, did you forget something? I don't work for you anymore."

On the livestream, I watched the color drain from his face. For the first time he seemed to remember that he'd personally signed my resignation.

"Ethan, I need you." His voice softened. "This is your work too. Are you really going to stand by and watch everything you built collapse?"

I stayed quiet. That hit harder than I wanted it to. I'd poured years of experience and months of exhaustion into Helix and the company had thrown me away over one minute.

"You have engineers there," I finally said. "Use them."

"They can't fix this."

"Then perhaps you shouldn't have let your technical lead walk out the door."

Victor went silent.

I could almost picture him standing backstage, surrounded by executives who had spent weeks praising Derek's leadership while taking credit for my work.

"Ethan, this isn't the time for personal feelings. We have investors watching. Clients are watching. If the launch fails today, Meridian could lose enormous amounts of money."

"That's unfortunate."

"I'll restore your bonus."

I smiled.

"The bonus you stole from me because I spent six minutes in a bathroom?"

"Yes. I'll restore it."

"And my disciplinary record?"

"Gone."

"And the promotion?"

There was another pause.

"We'll discuss it."

I leaned back in my chair. "No, Victor. We won't."

"Ethan, please."

That single word told me everything. The man who had called my resignation impulsive was now begging me to rescue his biggest product in front of a live audience.

"Send me the current logs," I said.

Victor sounded relieved. "Thank you. I'll have them sent immediately."

"I didn't say I'd come back."

His relief disappeared.

"Then what will you do?"

"I'll look at the logs. If the problem is what I think it is, I'll tell you what needs to be done."

"Can you fix it remotely?"

"Maybe."

"Ethan, I'll pay whatever you want."

"You already had me."

I ended the call.

Less than a minute later, a secure file appeared in my inbox. I opened it and began studying the logs.

It took me less than ten minutes to find the problem.

It wasn't a hardware failure. It wasn't a server overload. It wasn't even a problem with the model itself.

Someone had pushed an outdated configuration file into the production environment.

I checked the deployment record.

The file had been uploaded at 2:17 that afternoon.

The launch team had been rehearsing all morning. The system had worked perfectly until that file appeared.

Then I saw the name of the person who approved the deployment.

Derek Cole.

I stared at the screen.

So this wasn't simply a failed launch.

Someone had changed something after I left.

I immediately downloaded the audit trail and saved a copy to my personal encrypted drive. Then I sent Victor one message.

"Roll back the configuration to yesterday's version. Do not let Derek touch the production environment."

His reply came almost instantly.

"Will that fix it?"

"It should."

"How do you know?"

"Because I built the system."

Twenty minutes later, the livestream suddenly stabilized.

The errors disappeared.

Victor returned to the stage, smiling as though nothing had happened.

The audience applauded cautiously.

But I wasn't watching Victor anymore.

I was looking at Derek's deployment record.

For the first time since I resigned, I realized something important.

They hadn't simply underestimated me.

They had made a mistake that could cost them far more than my $200,000 bonus.