New CEO Caught a Single Dad Sleeping on Her First Morning and Fired Him — Then Every Screen Turned Red

Chapter 17

Theme:
Font Size:
24px

Then toward him.

Then the workstation.

The place where she had almost destroyed the best relationship of her life before it even existed.

“Yes.”

Daniel exhaled.

She pointed at him.

“But if you ever work forty hours without sleeping again, I divorce you.”

“We aren’t married yet.”

“Future policy.”

“Understood.”

She pulled him upright and kissed him.

Someone behind them started applauding.

Alexandra broke the kiss.

“Who is here?”

Twenty employees emerged from behind the glass conference wall.

Daniel looked guilty.

“You planned an audience?”

“My daughter did.”

His daughter stepped forward holding her phone.

Now nine.

Grinning.

Alexandra stared.

“You recorded that?”

“Obviously.”

“You’re terrifying.”

“Dad says that about you.”

Daniel coughed.

Alexandra slowly looked toward him.

“Really?”

He pointed toward his daughter.

“Minor child.”

“She cannot be trusted.”

The girl laughed.

Their wedding was small.

Daniel wanted family.

Alexandra wanted privacy.

His daughter wanted cake.

The daughter won most negotiations.

They married in a garden outside the city.

No board members except the independent Chair.

Several engineers.

Alexandra’s parents.

Daniel’s late wife’s sister.

His daughter stood beside him.

Before Alexandra walked down the aisle, the girl approached in a pale-blue dress.

She hugged her.

Then whispered:

“Thanks for not firing Dad.”

Alexandra laughed.

“I did technically fire him for thirty seconds.”

“I know.”

The girl looked serious.

“Good thing you fixed it.”

Alexandra looked toward Daniel waiting beneath the trees.

“Yes.”

“It was.”

Years later, the original cyberattack became a case study taught in business schools and security conferences.

The popular version focused on the dramatic moment.

New CEO discovers engineer sleeping.

She threatens termination.

Screens turn red.

Engineer reveals hidden attack.

Company survives.

People loved that structure.

Daniel hated it.

“It makes me sound heroic.”

Alexandra looked at him.

“You were heroic.”

“No.”

“You stayed forty hours.”

“That was irresponsible.”

“It also saved the company.”

“Both can be true.”

She smiled.

He had learned that from her.

Or she from him.

Hard to remember.

Daniel eventually became Chief Systems Architect.

Never CTO.

He refused every time.

He wanted technical work.

Mentoring.

Architecture.

Enough authority to stop bad decisions.

Not enough meetings to become one.

Alexandra remained CEO for eleven years.

MeridianPay became one of the most trusted payment infrastructure companies in the country.

Not because it never suffered incidents.

It did.

Systems failed.

People made mistakes.

Attackers returned.

But the company learned something from the first morning of Alexandra’s leadership.

A warning from the lowest-level engineer could stop the highest-level executive.

A decision could be challenged without becoming insubordination.

And people were not praised for destroying themselves to keep systems running.

The first year after the new incident policy, recorded operational pauses increased dramatically.

Some board members worried.

Then major outages decreased.

Alexandra presented the numbers.

“Apparently letting people say no works.”

News in the same category

New CEO Caught a Single Dad Sleeping on Her First Morning and Fired Him — Then Every Screen Turned Red

20 Part