Overcoming the Fear of Ignorance: Insights from a Non‑Technical Tech Leader
A former non‑technical executive reflects on a VP interview, the pressure to appear technically proficient, cultural biases against non‑coding founders, and why admitting ignorance and asking questions can be more valuable than pretending expertise in tech‑driven startups.
Last week I sat with two of the four technical leads at my company to interview a candidate for the Vice President position. Everyone else in the room was a typical "technical" person—able to code, solve programming problems, and with a computer‑science background—while my last line of PHP code dated back to 2004 and had been rewritten by a real programmer within six months.
During the interview Thomas, one of the technical leads, asked how to design a system that can handle upgrades and scaling (adding new data) without affecting users, and what challenges such a design would face.
The candidate replied that storing the data wouldn’t be a problem—Amazon S3 could handle it—but the real difficulty lay in how the application would use the data. He mentioned pre‑processing each view, warned that reverse sorting could become slow, and suggested using an in‑memory transformation with a three‑letter abbreviation (unspecified).
When I asked for clarification on the three‑letter term, the candidate explained it and continued. I felt embarrassed; years earlier I had panicked when asked technical questions in front of my team, a common experience among managers and CEOs who feel they must know every answer.
In some companies, a highly politicized, hierarchical culture forces managers to appear flawless, but in startups this tradition should be rejected. Non‑technical founders often feel inferior, and many articles mock the idea that a founder should understand code.
Quotes from Hacker News, Jason Freedman, David Cummings, and others illustrate the stigma: "Founders who don’t code," "Don’t look for a technical co‑founder, learn to code yourself," and similar headlines.
These pieces made me feel ashamed, prompting me to consider a two‑week crash course on Khan Academy. In the early days of the internet I was a terrible web designer, cobbling together PHP with Dreamweaver and stolen snippets—perhaps the most technical work I ever did.
Unlike those authors, I never spent weeks learning Ruby on Rails or building a small app, even though I had hundreds of hours available to improve my computer‑science knowledge for interviews, presentations, or blog posts.
Nevertheless, our company, Moz, has become a relatively successful tech firm with some of the smartest engineers in Seattle, handling challenging software problems quite well.
A popular Quora question asks, "What are the most common misconceptions in software development?" I would add the belief that only technically proficient people can manage or lead software teams. Some claim a great software company cannot be founded or led by a non‑technical person, but I disagree—many founders and leaders succeed without deep technical understanding.
Small teams without technical expertise can still achieve remarkable market traction, raising large funds and hiring top talent, proving that non‑technical CEOs can learn on the job and delegate technical decisions to experts.
Is software special? Perhaps. Does knowing how to write a line of code or store data in a database significantly increase a founder’s chances of success? Maybe. Yet many other professional skills positively impact entrepreneurship, often unrelated to programming.
I still feel embarrassed about gaps in my knowledge, but I now accept my ignorance, stop fearing it, and use it as motivation. Making good decisions requires understanding problems and possible solutions, which often means asking many questions—even seemingly foolish ones.
In power‑centered companies this approach can meet resistance, but it has helped me across various technical challenges. My favorite answer to tough questions is, "I don’t know, but I will find out."
Regardless of your role in a startup, showing ignorance openly is better than hiding it, even for those perceived as all‑knowing. Dismissing someone because they don’t code has become a trend at places like Facebook and Google, driven by tech media and venture capitalists, a view I do not share.
Consequently, I plan to watch computer‑science lectures on Khan Academy.
Fear of Ignorance – English translation of the original article.
21CTO
21CTO (21CTO.com) offers developers community, training, and services, making it your go‑to learning and service platform.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
