My Boss Fired Me For “Being Too Expensive” After 18 Years Leading Engineering; His Panicked Calls…

Calls for Help and a New Beginning

The first call came 2 weeks after my termination. I was in my home office updating my resume when my phone rang.

It was Graham Vickers. I let it go to voicemail.

“Victor, it’s Graham. We’re having some issues with the tenant portal.” “The junior team is working on it, but they’re having trouble understanding some of your code architecture.”

“Could you give us a call back? It would just be a quick consultation.” I deleted the message and went back to my resume.

Three more calls came that day. Each voicemail sounded increasingly desperate.

By evening, Allan texted me. “Systems been down all day. Maintenance requests aren’t processing. Graham’s losing his mind.”

The next morning, Diane from HR called. “Victor, I hope you’re doing well.”

“I’m calling because we’d like to discuss a consulting arrangement just temporary to help with some current system issues.” “The compensation would be quite generous.”

I picked up my phone. “How generous?”

“$300 per hour, minimum 4-hour engagement.” “I’ll think about it and get back to you,” I said, then hung up.

I sat at my kitchen table, staring out at the lake. Elaine placed a cup of coffee in front of me.

“What are you thinking?” “I’m thinking they’re finding out exactly what I’m worth.”

Over the next 3 days, the calls increased. Graham, Diane, and even Justin Bayview, who was still on the board, called.

The tenant portal was down. The maintenance scheduling system was throwing errors.

The automatic payment processing had failed, affecting thousands of residents. I didn’t respond to any of them.

On day four, an email arrived from Devlin Systems, a regional competitor to Veltria. They managed fewer properties but had been expanding rapidly.

The email was from their director of technology, Lawrence Develin himself. “Victor, I heard about your situation at Veltria.”

“We’ve always admired your work from afar.” “Would you be interested in discussing opportunities with us?”

“We’re looking to upgrade our entire property management infrastructure.” I replied and set up a meeting for the following day.

That evening, as Elaine and I were preparing dinner, my doorbell rang. Graham Vickers stood on my porch.

His designer glasses were slightly askew. His normally immaculate suit was wrinkled.

“Victor, I apologize for dropping by unannounced, but we have an emergency situation.” “The entire system is down. Nothing is working.”

“The team can’t figure out what’s wrong or how to fix it.” I leaned against the door frame.

“That sounds serious.” “It is. We need your help.”

“The board has authorized me to offer you a substantial consulting fee.” “$500 per hour, whatever it takes.”

I thought about the cardboard box in my garage. 18 years of work were reduced to a few mementos.

I thought about “nothing personal, just cost cutting.” I thought about the documentation team they’d never approved.

“I’m sorry to hear about your troubles,” I said quietly. “But I have an interview tomorrow. Something will turn up just like I thought.”

I closed the door on his stunned face and went back to making dinner. For the first time since my termination, I felt a sense of peace wash over me.

Not satisfaction, not vindication, just clarity. I wasn’t going to help them fix what they’d broken.

The interview with Lawrence Develin went better than expected. We met at a coffee shop in downtown Rochester, away from both companies’ offices.

“I’ve followed your work for years,” Lawrence said, stirring his coffee. “That integrated property management system you built at Veltria is legendary in our industry.”

“Nobody else has anything close to it.” “Thank you,” I said. “It took time.”

“That’s what I want to talk about: time.” “We’re looking to build something similar but we don’t want to start from scratch.”

“We need someone who understands the architecture, the integration points, and the security layers.” “Someone who can build us something better than what’s out there.”

“I’m interested.” Lawrence smiled.

“Good because I’m prepared to offer you the position of chief systems architect.” He offered full benefits, stock options, and a salary 20% higher than what I was making at Veltria.

It was a good offer. It was too good, almost.

“Why me?” I asked. “There are younger engineers out there, cheaper ones.”

Lawrence laughed. “You sound like your former employer.”

“We tried that route. Hired three bright young engineers from top schools.” “They built us something sleek and modern that crashes every time we get more than a 100 simultaneous users.”

“We don’t need cheap. We need reliable.” I accepted the offer the next day.

Meanwhile, Veltria’s problems were escalating. Allan kept me updated through occasional texts.

The system had been partially restored, but critical functions were still failing. They’d brought in an expensive consulting firm that specialized in legacy system recovery.

A week after I started at Devlin, Graham called again. “Victor, please, this is getting serious. We’ve lost access to payment records for the past 3 months.”

“Tenants are complaining about incorrect charges.” “The consulting team says they need your input on the database structure.”

I was tempted to ignore it, but something made me pick up. “Graham, I’m employed elsewhere now. Exclusive contract, I’m afraid.”

“I can’t help you.” “We’ll double whatever they’re paying you for just 2 days of your time.”

“It’s not about the money.” “Then what is it about? Revenge? Are you enjoying watching us struggle?”

I paused, considering my answer carefully. “No Graham, I’m not enjoying it.”

“But you made a business decision. You decided my experience wasn’t worth the cost.”

“Now you’re discovering what that actually means.” “The board wants to discuss bringing you back.”

“Full salary plus a signing bonus.” For a moment I felt a flicker of satisfaction, but it quickly faded.

Going back would solve nothing. The same executives who decided I was expendable would be waiting for the next opportunity to cut costs.

“I appreciate the offer but I’ve made a commitment to Develin Systems.” Graham’s voice hardened.

“You know there could be legal implications if we discover you intentionally made our systems difficult to maintain.” “Non-compete clauses, intellectual property concerns.”

There it was, the threat I’d been expecting. “The system is exactly as it was when the company repeatedly denied my requests for a documentation team,” I replied evenly.

“Every line of code belongs to Veltria as specified in my employment contract.” “I’ve taken nothing with me except my experience but feel free to have your lawyers contact mine.”

I hung up, hands shaking slightly. This was not from fear, but from anger I hadn’t allowed myself to feel until now.

The accusation that I’d somehow sabotaged them was the final insult. At Devlin, I was starting fresh.

I was building systems properly from the ground up with full documentation. I included training programs for the engineering team and redundancies that would prevent the kind of catastrophe Veltria was experiencing.

I wasn’t going to look back anymore. But I wasn’t going to help them either.

Some lessons had to be learned the hard way.