Every career has a couple of stories you don’t tell in interviews. Not because they make you look bad, but because they take too long and the ending confuses people.
This is one of mine. It comes in two acts, both from my early twenties, both about the word loyalty. Bring coffee.
Act One: In Which I Learn That an Office Is Not a Home
My first real job was IT help desk at a large oil company. Big building. Big logo. The kind of place where you tell your relatives the name and they nod like you’ve done something impressive with your life.
I loved it. I was the guy who reset your password and then stayed twenty extra minutes to explain why it expired. I knew where the good coffee machine was. I knew which floor had the printer that jammed out of spite. I was, in my own head, essential infrastructure.
Then the company merged with another company.
If you have never lived through a merger from the bottom of the org chart, let me describe it: it feels like weather. Nobody asks your opinion about weather. It simply happens to you, and then someone from HR explains it to you in a small room with a box of tissues that was clearly purchased in bulk.
I was let go. First job of my life, and I got the speech about “redundant functions.”
I cried. There, I said it. Twenty-something years old, walking out of a building I was genuinely proud to walk into, holding a cardboard box like a sad movie extra. I wasn’t crying about money. I was crying because I had confused a workplace with a place where I belonged.
That day I learned the sentence that has followed me ever since:
A workplace is a workplace. Home is home. Don’t ask one to be the other.
I thought that lesson would protect me forever. Reader, it did not even protect me for a year.
Act Two: In Which I Do the Right Thing and Am Punished Promptly
Five or six months later I landed at a systems integrator as a field engineer. This was the good kind of chaos. Servers, clients, backups, a bag heavy enough to count as strength training, and a different customer site every week. I was on the road constantly and I was happy.
One of those customers liked my work. Really liked it. The kind of liking where the IT manager starts saying things like “you know, we’ve been thinking about hiring someone internally” while you’re on your knees behind a rack.
Eventually it stopped being hints and became an actual offer. A systems engineer role. In-house. Better title, better stability, no more carrying a laptop bag through Istanbul traffic like a courier with a certification.
I said no.
Not “let me think about it.” Not “let’s talk numbers.” A polite, immediate no, with a reason attached: you are my employer’s customer. I’m standing in your server room because my company sent me here. Taking a job from you would be using their trust as my personal job board. It wouldn’t sit right with me.
They took it gracefully. I went back to my regular life feeling quietly good about myself, which is always the first sign that the universe is loading something.
Two or three months later, that customer and my employer had a falling out. Pricing, service model, the usual arguments that sound very technical and are actually about money. The contract ended. The customer hired an internal systems engineer, just not me.
And somewhere in the middle of all that separation, the story of the offer reached the owners of my company.
The Meeting
They called me in. The tone was not friendly.
“You got an offer from our customer. Why didn’t you tell us?”
And here is where my Act One lesson walked into the room, sat down, and confidently ruined my life.
I said: “The offer came to me. It was mine to refuse, and I refused it. Why would I need to report it?”
I genuinely believed that was the strongest possible answer. In my head it was airtight. I had been offered something and turned it down for their benefit. I hadn’t negotiated. I hadn’t leaked pricing. I hadn’t left. The story had exactly one act of loyalty in it, and I was the one who performed it.
They saw a different movie entirely. In their version, an employee had a private conversation with a customer who later walked away, and didn’t mention it.
Same day, I was fired. The stated reason, and I want you to appreciate the craftsmanship here:
“We are a family, and you betrayed us.”
Fired from a family. On the same day. With no severance, but plenty of emotional vocabulary.
The Part Where I Admit I Wasn’t Innocent Either
I’ve had two decades to chew on this, and I’m not going to pretend I was a flawless martyr. I was young and politically naive, and there’s a distinction I couldn’t see back then:
Mentioning it would have been smart. It was not morally required.
Those are two very different things, and young me collapsed them into one. I confused “I don’t owe you this” with “there’s no advantage in telling you.”
One sentence would have changed the whole story. Something as boring as: “By the way, the customer asked if I’d join them. I said no, it wouldn’t be right while we’re serving them.”
Ten seconds. In the hallway. Between coffees. That sentence turns a suspicious silence into a story about how solid your engineer is. Same facts, completely different narrative — and the person who controls when a fact gets told controls what it means.
I hadn’t learned that yet. I thought doing the right thing was enough, and that the right thing announces itself. It doesn’t. The right thing is famously bad at PR.
Why “We Are a Family” Still Makes Me Flinch
Here’s what bothers me, and it isn’t the firing. Companies part ways with people. That’s life. Act One already taught me that lesson with a tissue box.
What bothers me is the language.
“Family” was used as a one-way street. When they needed weekend work, unpaid overtime, a field engineer driving across the city at 8 PM because a server was down — family. When I declined a job offer to protect their customer relationship at my own cost — that was just my job, unremarkable, expected.
But the moment they felt uncomfortable, “family” transformed into a weapon. Not “you violated policy.” Not “we’ve lost confidence.” Betrayal. A word from a domain where you can’t defend yourself, because you can’t file an appeal against someone’s feelings.
That’s the trick. Familism borrows the emotional obligations of a family and quietly leaves out the guarantees. Real families don’t have a probation period. Real families don’t restructure you out on a Tuesday.
Which is why, after 26 years in IT, I’ve become boringly fond of professionalism.
“We are professionals” sounds colder than “we are a family.” It is also far more honest, and in practice far kinder. Professional means: here’s the scope, here’s the compensation, here’s the notice period, here’s what I owe you and what you owe me. When someone leaves, nobody has to perform heartbreak. Nobody gets accused of treason for updating their CV.
Cold contracts have kept more people employed and respected than warm speeches ever have.
The irony I keep coming back to: in that entire story, the only actual act of loyalty was my refusal. It was performed by the person the family later expelled for disloyalty. I’ve stopped being bitter about it — mostly — but I do think about it whenever I hear a company describe itself as a family in a job posting. My eyebrow moves on its own now. It’s involuntary. Like a reflex test.
Today, when someone on my team gets approached by a client, I want them to tell me — not because they owe me a confession, but because I’d rather hear it from them than from the hallway. And if they take the offer? I’d rather they leave as a professional I can call next year than as a “family member” I have to be dramatic about.
So let me hand this to you, because I’ve argued with myself long enough.
Was I wrong? Should I have mentioned the offer even though I turned it down? Or was my silence exactly as harmless as I thought it was?
What would you have done, at twenty-three, in someone else’s server room?