Copyright © 2024. All rights reserved.
In my blog posts, I strive for an honest representation of my journey through a career in software engineering. There are good parts, bad parts, steps forward, and steps back. Part of my journey includes overcoming imposter syndrome. If you’re interested in hearing a bit about how I overcame my imposter syndrome, then I invite you to read on.
Imposter syndrome is a term that many of us in the tech industry are all too familiar with. It’s that nagging feeling that despite our achievements, we might not be “good enough,” and sooner or later, someone will expose us as frauds.
I’ve been extremely fortunate in my career to work alongside people that I consider to be amazing software developers. These people I consider to be far better than myself, which brings me to my first understanding.
One of the most liberating realizations that I came to truly accept is the understanding that everyone’s journey is unique. Comparing myself to others was a major source of imposter syndrome. It’s easy to look at a coworker’s success and feel inadequate, but it’s important to remember that I’m only seeing a part of their story. Each person has their own set of challenges and experiences that shape their worldview and have led them to where they are.
In my case, the change I made was to stop looking at how far another developer is ahead of me, and to start reflecting on how far I’ve come. For example, embracing the fact that being late to the software game (it wasn’t my first career) was an important part of my journey that helped shape the way I interact with people. Looking back, those experiences allowed me to develop additional soft skills that have been a tremendous asset to my software career.
Your journey is yours alone, and it’s shaped by your unique experiences and strengths. Embrace it, and understand that your value isn’t diminished by someone else’s success.
The developers I look up to always seem smart and confident. In truth, it’s because they are, and it’s demonstrated in how they solve problems, plan projects, work with others, etc. They demonstrate skills and strengths that I value, and I realized that I can value those skills and strengths while not devaluing my own.
For example, having a colleague that is a master of a technical skill, such as debugging SQL, doesn’t devalue my soft skill of communication.
Recognizing what I bring to the table, instead of what I wasn’t bringing, was a crucial step for me in overcoming imposter syndrome. Taking it a step further, recognizing the skills I had allowed me to sharpen them, while recognizing the ones I didn’t allowed me to seek opportunities to grow.
Failures and setbacks are difficult. However, realizing opportunities that arise from a step back can take you two steps forward.
Early in my career, I became a “Team Lead” to help lead a project and bring it back on schedule. Two years into my career was not enough time to gain the technical expertise to lead a software engineering project. I consider my time as “Team Lead” a failure.
My failure as a Team Lead came from not seeking out a true understanding of the product, audience, and problems we were solving. The immediate aftermath was a loss in confidence and feeling inadequate as a developer.
Reflecting on that situation reveals how it shaped my career. When I joined Eventbrite, I sought opportunities to learn about the problems we face and the history behind problems solved. I wanted context, and by seeking out context, I’m able to deliver solutions and ideas that keep our users and product at the forefront of my mind. This is a direct result of recognizing how I failed as a Team Lead and growing from that experience.
These understandings are my own experience and we all view the world through a unique set of lenses. My hope is that presenting what worked for me can create a spark for someone else. Embrace your journey, recognize your strengths, and see failure as a friend that helps you grow.
Copyright © 2024. All rights reserved.