I had spent eleven years getting paid to write code, building supply chains, managing teams, and architecting systems that handled millions of messages. By all objective measures, I was a competent engineer. Then I walked into an interview that reminded me that competence and nomenclature are two very different things.
It was a company I genuinely wanted to work for. The energy was right, the EM liked me, and the code challenge was brilliantly structured as a series of tiers. You started simple, and as you progressed, the constraints tightened. For the first five rounds, I was flying, moving through the logic with a speed that felt like a victory lap.
The momentum shifted when the problem required me to retrieve data from a third-party API that was becoming increasingly restrictive. My brain was already working through the resolution; I knew I needed to check the middle value and compare if the result was greater than or less than my target. I was practically dancing through the logic in my head, but I couldn’t put a name to it.
I spent nearly 40% of the time box on a problem that, in hindsight, was a textbook example of a binary search. I wasn’t struggling with the logic, but with the label. I was treating the problem as a puzzle to be solved from scratch rather than a pattern to be recognized. For a decade, I had avoided the pretentiousness of “Data Structure” terminology because I simply didn’t need it. The term “binary search” had never been useful to me because the act of searching was just something I did. I didn’t need the label to write the code.
Unfortunately, immediately putting together the direction of the interview from the 3 previous challenges to the culmination in a binary search was the goal. I just didn’t figure it out in time, and my vernacular just wasn’t up for the task that day.
I felt a deep sense of dismay because I had grown so much over the last year and felt ready. The silence that followed my inability to name the algorithm was an eye-opener, revealing the invisible tax of not being a college graduate. While I had spent eleven years in the trenches of real-world production, I had missed the collegiate shorthand that allows engineers to signal competence to one another.
I didn’t lose that job because I couldn’t code. I lost it because I didn’t know the name of a concept I was already implementing. It was a humbling moment that revealed a blindspot hidden by my own success. It taught me that there is a profound difference between knowing how a thing works and knowing what it’s called. One gets the job done, but the other gets you through the door.