Admit What You Don't Know

Foundational Truth

No engineer knows everything.

No architect.

No developer.

No database administrator.

No network engineer.

No security expert.

Technology evolves too quickly for anyone to master every discipline.

The strongest engineers are not those who pretend otherwise.

They are the ones who understand where their knowledge ends.

Confidence earns attention. Honesty earns trust.

---

The Three Most Powerful Words

"I don't know."

Few sentences are more difficult for young engineers to say.

Pride resists them.

Fear avoids them.

Insecurity disguises them.

Yet those three words often mark the beginning of real learning.

The moment we admit we don't know something...

We become teachable.

Until then, we're simply defending assumptions.

---

The Interview Lesson

During my career I conducted hundreds of technical interviews.

More than four hundred and fifty, by the time I stopped counting.

One pattern appeared again and again.

I'd ask a technical question.

The candidate didn't know the answer.

Instead of saying,

"I don't know,"

they would invent one.

Sometimes the definitions sounded convincing.

Sometimes they were wildly creative.

Almost always they fell apart after one or two follow-up questions.

Not because I was trying to embarrass them.

Because I already knew the answer.

The interview was never about proving I was smarter.

It was about discovering where their knowledge ended.

That is exactly what interviews are supposed to accomplish.

---

We Can Teach Technology

One realization changed the way I interviewed engineers.

Technology is teachable.

Integrity is not.

I can teach someone Active Directory.

I can teach networking.

I can teach AWS.

I can teach SQL Server.

I can teach scripting.

I can teach cloud architecture.

What I cannot teach is honesty.

I cannot teach someone to value integrity.

I cannot teach someone to admit mistakes.

Those qualities already exist long before they arrive for the interview.

They are what determine whether I can trust them after they are hired.

Knowledge can be developed. Character must already be present.

---

The Cost of Pretending

Pretending to know something rarely ends with the interview.

It follows engineers into production.

A configuration is misunderstood.

A deployment proceeds anyway.

A warning is ignored.

A change is approved without full understanding.

Eventually the system fails.

Now the engineer faces another choice.

Admit uncertainty...

Or protect pride.

One accelerates recovery.

The other delays it.

The truth eventually appears in the logs.

Or the monitoring.

Or the postmortem.

Reality has a remarkable way of exposing what we hoped nobody would discover.

---

Engineering Is Continuous Learning

Technology changes continuously.

Today's expert becomes tomorrow's beginner.

New programming languages appear.

New cloud services emerge.

New security models replace old assumptions.

The engineer who cannot say,

"I don't know,"

will eventually stop learning.

Not because opportunities disappear.

Because pride prevents curiosity.

---

Closing Thought

Every engineer has limits.

The strongest engineers know where theirs are.

There is no shame in not knowing.

The only shame is pretending you do.

The words "I don't know" are not an admission of failure. They are an invitation to learn.

Curiosity Begins Where Certainty Ends

Every engineer eventually reaches the edge of their knowledge.

That is not failure.

That is where growth begins.

The engineer who says,

"I've never seen this before."

has an opportunity.

The engineer who pretends they already understand it...

Has closed the door to learning.

Curiosity requires humility.

Humility begins with honesty.

The phrase "I don't know" is often the first sentence in every meaningful lesson.

---

Interviews Reveal Character

Technical interviews are often misunderstood.

Candidates believe they are expected to answer every question correctly.

That has never been my objective.

During my career I conducted more than four hundred and fifty technical interviews.

The goal was never to discover everything someone knew.

The goal was to discover where learning would begin.

Eventually every interview reaches a question the candidate cannot answer.

That moment is the most valuable part of the interview.

Some candidates calmly say,

"I don't know."

Others panic.

They begin inventing definitions.

Connecting unrelated technologies.

Guessing at terminology.

Trying desperately to avoid admitting uncertainty.

The unfortunate reality is simple.

The interviewer already knows the answer.

Making something up rarely demonstrates intelligence.

It demonstrates fear.

One honest sentence tells me far more about someone's character than five impressive answers ever could.

The interviewer isn't looking for perfection. They're looking for the point where learning begins.

---

Integrity Is More Valuable Than Expertise

Every technology can be learned.

Programming languages change.

Operating systems evolve.

Cloud platforms expand.

Security practices mature.

Database engines improve.

Technical knowledge has a shelf life.

Integrity does not.

When I hire an engineer, I am making a long-term investment.

I need to know that when something eventually goes wrong—and it will—that engineer will tell me the truth.

Will they admit the mistake?

Will they ask for help?

Will they help recover the system?

Or will they protect their ego while everyone else loses valuable time searching for answers?

That decision tells me far more than any certification ever could.

I can teach technology.

I cannot teach integrity.

---

Mistakes Are Expected

No engineer reaches retirement without making mistakes.

Deployments fail.

Scripts delete the wrong files.

Databases become unavailable.

Certificates expire.

Firewall rules block production traffic.

Every experienced engineer carries stories like these.

Mistakes are inevitable.

Dishonesty is optional.

The mistake usually costs time.

The cover-up costs trust.

Recovery begins the moment someone says,

"I made a mistake."

Recovery is delayed every minute someone tries to hide it.

Errors test technical skill. Integrity tests character.

---

Questions Are a Sign of Strength

Young engineers often hesitate to ask questions because they fear appearing inexperienced.

Experienced engineers ask questions constantly.

Not because they know less.

Because they understand how much remains unknown.

Questions uncover assumptions.

Questions expose risk.

Questions prevent outages.

Questions build understanding.

The engineer asking thoughtful questions is usually the engineer preventing tomorrow's incident.

---

The Best Teams Normalize "I Don't Know"

The healthiest engineering teams I've ever seen shared one characteristic.

Nobody was afraid to admit uncertainty.

People asked questions freely.

Ideas were challenged respectfully.

Evidence mattered more than ego.

Learning happened continuously.

Those teams solved difficult problems faster because nobody wasted energy pretending to know everything.

Psychological safety is not about lowering standards.

It is about removing the fear of honesty.

When people feel safe admitting uncertainty, they begin solving problems together instead of protecting their reputations.

---

Closing Thought

Knowledge grows.

Technology changes.

Experience accumulates.

One quality should remain constant.

The willingness to tell the truth.

No engineer ever became weaker by admitting they didn't know something.

Most became stronger because they chose to learn instead of pretend.

The fastest path to knowledge begins with the courage to admit where your knowledge ends.

Wisdom Begins with Humility

There is a profound difference between intelligence and wisdom.

Intelligence accumulates knowledge.

Wisdom recognizes its limits.

The more I learned throughout my career, the more I realized how much remained unknown.

Every answer uncovered another question.

Every solved problem revealed another layer of complexity.

Every new technology created another discipline to understand.

That realization never discouraged me.

It made me curious.

The wisest people are rarely the loudest. They know how much remains to be learned.

---

Pride Stops Learning

Pride has a remarkable way of disguising itself.

Sometimes it appears as confidence.

Sometimes it appears as certainty.

Sometimes it appears as silence because someone is afraid to ask a question.

Pride whispers,

"You should already know this."

Humility asks,

"Would you explain that?"

One sentence protects the ego.

The other expands the mind.

Knowledge grows only where pride allows curiosity to enter.

---

Every Expert Was Once a Beginner

It is easy to admire experienced engineers.

The architect who understands distributed systems.

The database administrator who can diagnose a query in minutes.

The network engineer who instinctively understands packet flow.

What we often forget is that every one of them once knew nothing about those subjects.

They asked questions.

They made mistakes.

They misunderstood concepts.

They learned from mentors.

They admitted uncertainty.

Experience is not evidence that someone never struggled.

It is evidence that they continued learning.

---

Build Cultures That Welcome Questions

The healthiest organizations encourage questions.

Not because people are uninformed.

Because asking questions uncovers assumptions.

Questions expose risks.

Questions improve designs.

Questions prevent expensive mistakes.

When people fear appearing uninformed, they stop asking.

When they stop asking...

Organizations stop learning.

The strongest teams create environments where saying,

"I don't understand."

is treated as the beginning of collaboration rather than the end of credibility.

---

Integrity Creates Trust

People trust those who tell the truth.

Even when the truth is,

"I don't know."

Especially when the truth is,

"I made a mistake."

Integrity does not require perfection.

It requires honesty.

Customers forgive honest mistakes.

Teams recover from honest failures.

Organizations improve because someone had the courage to speak honestly before a small problem became a large one.

Trust grows through consistency.

Every honest conversation strengthens it.

Every dishonest one weakens it.

---

Learning Never Ends

Technology changes.

Industries change.

People change.

The engineer who believes they have finished learning quietly begins falling behind.

The engineer who remains curious continues growing long after formal education ends.

Learning is not an event.

It is a lifelong habit.

The sentence,

"I don't know,"

should never be followed by a period.

It should always be followed by,

"...but let's find out."

That is the mindset that builds extraordinary careers.

---

Questions to Ask Yourself

• What am I pretending to understand?
• What question am I afraid to ask?
• What assumption have I accepted without verifying?
• Would admitting uncertainty improve this decision?
• Am I protecting my reputation or expanding my understanding?
• If I make a mistake, will I own it immediately?
• What can I learn today that I didn't know yesterday?

---

Closing Thought

There is no shame in reaching the edge of your knowledge.

That edge is where discovery begins.

Every remarkable engineer has stood there countless times.

The difference is not whether they knew the answer.

The difference is whether they had the courage to admit they didn't.

Humility opens the door that pride keeps locked. Every great engineer walks through that door again and again.

Founder's Commentary

The Best Answer I Ever Heard

After conducting more than four hundred and fifty technical interviews, people often ask me what the best answer I ever heard was.

It wasn't an explanation of BGP.

It wasn't an elegant discussion about distributed databases.

It wasn't an architect explaining cloud networking.

It was three simple words.

"I don't know."

Those words immediately changed the conversation.

Not because the interview was over.

Because the interview had finally become honest.

The purpose of a technical interview is often misunderstood.

Many candidates believe they are competing to prove they know everything.

That has never been what I was looking for.

I already knew the answers to the questions I was asking.

I wasn't testing whether someone could fool me.

I was trying to discover the edge of their knowledge.

That edge tells me something incredibly valuable.

It tells me where teaching begins.

When a candidate confidently admitted they didn't know something, I smiled.

Not because they failed.

Because I had just learned something important about their character.

They valued truth more than appearance.

That matters.

Technology changes every year.

Character rarely does.

I've watched candidates invent astonishing definitions for technologies they had clearly never encountered.

Some were genuinely creative.

Some almost sounded believable.

But every invented answer created another question.

Within minutes, the story collapsed under its own weight.

Not because I was trying to embarrass anyone.

Because truth is remarkably consistent.

Fabrication requires constant maintenance.

Reality does not.

That lesson extends far beyond interviews.

Every engineer will eventually make a mistake.

I've made plenty.

Deployments don't always go as planned.

Scripts don't always behave as expected.

Architectures sometimes reveal weaknesses that nobody anticipated.

Those moments define careers.

Not because mistakes happened.

Because of what happens next.

I've always had far more respect for the engineer who walked into my office and said,

"I made a mistake."

than the engineer who quietly hoped nobody would notice.

The first engineer became part of the solution.

The second became part of the problem.

Recovery begins with honesty.

Every minute spent protecting pride is a minute not spent restoring service.

Eventually the logs tell the truth.

The monitoring tells the truth.

The postmortem tells the truth.

Reality always catches up.

Integrity simply gets there first.

As my career progressed, I realized I was hiring for something much larger than technical skill.

I was hiring people I could trust when everything went wrong.

Could they admit uncertainty?

Could they ask for help?

Could they tell a customer the truth?

Could they own a mistake without looking for someone else to blame?

Those qualities cannot be measured by certifications.

They cannot be proven by memorizing interview questions.

They appear naturally when someone values honesty more than ego.

Looking back, I no longer believe the strongest engineers are the ones who know the most.

I believe they are the ones who never stop learning because they are never afraid to admit what they don't know.

That attitude has served me better than any certification, programming language, or technology ever could.

If there is one lesson I hope every young engineer carries throughout their career, it is this:

Never be embarrassed by the words,

"I don't know."

Be embarrassed only if you stop there.

Say,

"I don't know...

...but I'll find out."

That's the engineer I would hire every single time.

Knowledge earns respect. Integrity earns trust. In the end, trust is what every great engineer is truly hired to protect.

---