At the dinner table, Owen explained why I would never get into the company I’d founded. He was my sister Francesca’s fiancé, boasting about Ardent Data Solutions without knowing I’d just been named its CEO. I put down my fork and told him the truth. For the first time all evening, nobody spoke.
My mother was holding a serving spoon above the mashed potatoes. Aunt Roberta had stopped reaching for the bread. Francesca sat beside Owen, staring at me with the same bewildered expression she’d worn when we were children and I told her something she couldn’t quite believe.
Owen’s smile remained in place for another second.
Then it began to fade.
“You’re joking,” he said.
I shook my head.
“No, Owen.”
He looked around the table, apparently expecting someone to laugh and rescue him from the conversation.
Nobody did.
“I’m Simone Whitaker,” I said. “I founded Ardent Data Solutions nine years ago. Last Friday, the board formally appointed me chief executive officer.”
Owen set down his wineglass.
The tiny sound it made against the table seemed unnaturally loud.
“That’s not possible.”
I looked at him.
“Which part?”
He opened his mouth, then closed it.
Across from me, Francesca slowly turned toward her fiancé.
“Owen?”
He didn’t look at her.
My mother finally lowered the serving spoon.
“Simone, sweetheart, what are you talking about?”
I glanced at the clock above the kitchen doorway.
It was nearly eight.
I’d arrived at my parents’ house intending to eat dinner, catch up with my family, and get home early enough to sleep before another demanding workweek.
Instead, I was explaining my own career to people who had apparently spent months believing I no longer had one.
I took a breath.
“Mom, I wasn’t laid off.”
She blinked.
“But the company announced those job cuts.”
“Yes. It did.”
“And you stopped answering our calls.”
“I was working.”
Owen leaned forward again.
“With all due respect, Ardent’s leadership structure is complicated. There’s the original company, the acquisition group, the new subsidiary—”
“I know,” I said.
He stopped.
“I helped design it.”
The silence returned.
I didn’t enjoy watching my family become uncomfortable. Not really. I was too tired, and the disappointment had settled too deeply.
But I would be lying if I said there wasn’t a small measure of satisfaction in seeing Owen finally run out of words.
For nearly an hour, he’d been telling everyone at that table what success looked like.
He’d been wrong about almost everything.
My name is Simone Whitaker. I’m thirty-five years old, and I live in Chicago, where winter wind comes off the lake with enough determination to make even the most confident person reconsider leaving the house.
For most of my adult life, I’ve worked in data engineering.
That description usually causes my relatives to smile politely and change the subject.
They know I work with computers. They know I spend long hours in offices. They know my job sometimes requires traveling.
Beyond that, they’ve never understood much about what I do.
And for years, I was comfortable letting them remain uncertain.
I grew up in a family where success had a recognizable appearance.
My father, Michael, managed an automotive repair business before retiring. He believed in steady employment, a dependable paycheck, and keeping your promises.
My mother worked in medical billing.
She loved order, careful planning, and knowing exactly what everyone was doing for the holidays.
My younger sister, Francesca, was the charming one.
She could walk into a room full of strangers and leave with three dinner invitations and someone’s grandmother promising to send her a recipe.
I was the quiet one.
The daughter who finished homework early, repaired the family computer, and preferred solving complicated problems to explaining why I found them interesting.
At seventeen, I built a simple program to organize inventory for Dad’s repair shop.
He was delighted.
He told customers his daughter had made the computer understand where all his parts were.
But when relatives asked what I planned to do with my life, he usually said, “Something with computers, I think.”
It wasn’t dismissive.
He simply didn’t know how to describe the world I was entering.
For a long time, neither did I.
I studied computer science, worked through college, and took my first job at a software company that provided analytics tools to regional businesses.
I discovered I loved making complicated systems understandable.
I liked finding connections in enormous collections of information.
I liked building tools that allowed ordinary employees to make better decisions without needing an engineering degree to interpret every report.
Most of all, I liked solving problems other people had quietly accepted as unsolvable.
At twenty-six, I left my job and founded Ardent Data Solutions with two colleagues.
Philip Chang was an exceptional systems engineer with the patience to solve problems nobody else wanted to touch.
Maya Ellis was a brilliant database architect who could identify a weak design simply by looking at a diagram.
We rented a narrow office above a printing shop on Milwaukee Avenue.
The radiator clanged throughout winter. The conference room was barely large enough for four chairs, and our first whiteboard had a crack running through one corner.
We had three laptops, a secondhand coffee machine, and enough money to keep the lights on for six months.
I handled product development and customer relationships.
Philip built the infrastructure.
Maya made certain our systems were reliable.
For the first year, we did everything ourselves.
We answered customer calls.
We fixed software problems after midnight.
We assembled office furniture on weekends and celebrated our first profitable month with pizza from the restaurant downstairs.
I remember the night we signed our first substantial contract.
It was raining so hard that water ran beneath the office window.
Philip opened a bottle of sparkling cider because none of us could afford anything more impressive.
Maya raised a paper cup.
“To building something that works.”
I smiled.
“To building something people actually need.”
That became our unofficial motto.
We weren’t trying to become famous.
We wanted to make useful software and create a company where talented people could do good work.
Over the next nine years, Ardent grew.
We hired engineers, analysts, designers, and operations specialists.
Our products helped manufacturers manage supply chains, hospitals organize complex scheduling data, and regional businesses understand information they’d previously kept in disconnected systems.
We opened a larger office.
Then another.
Eventually, we began working with national clients.
I spent most of those years as chief technology officer.
I preferred the engineering work to public appearances, and the company’s professional materials focused on our teams rather than on me.
That suited me.
My name appeared in corporate filings and early company announcements, but I rarely posted about work online.
My family knew I was busy.
They knew Ardent had grown.
What they didn’t understand was how much responsibility I carried.
I didn’t explain it particularly well.
Whenever Mom asked about my job, I said things were going fine.
Whenever Francesca asked whether I could take a weekend trip, I said I had a deadline.
When Aunt Roberta wanted to introduce me to a friend’s son who worked in finance, I politely declined.
Eventually, my family stopped asking detailed questions.