What being a Principal Engineer means to me

I didn’t start writing code a decade ago with the aim of becoming a “Developer”, “Programmer”, “Engineer”, or “Leader”.

I just started tinkering like a child running a paint covered finger across a canvas, aimlessly exploring the possible.

Writing a <p> tag for the first time and seeing the words appear in my browser produced a rush of familiar feelings.

These feelings were the byproduct of using my creativity to change the world by willing something into existence, the act of creating something from nothing, no matter how small.

This alone was intrinsically motivating, but it was only the beginning of my journey.

Shortly after I made my first website, I discovered my why.

My why connected my new found passion for programming with all of the graphic design, video and audio production, TV sales, and tech-odd jobs I went through to date.

It felt like I stumbled onto a grand unifying answer that perfectly weaved together my past, present, and future career decisions.

I love helping people with technology.

As boring as it may sound, I believe the simplicity of this statement is beautiful because of the deeper meaning that can be found by parsing it apart.

Before all else, I love helping people.

I meet them where they are, learn what’s on their mind, what’s in their heart, where they want to go, and work to get them there.

I know that the effectiveness of my assistance is directly related to the quality of the relationships I have before, during, and after it, so I aim for those I come in contact with to not only hear me say “I care” but feel it.

I inspire, lift, and empower because I believe there is no force for innovation as potent as a loved person with passion and the confidence to wield it for a greater good.

I imagine being able to make such a positive impact on people that the shock wave reverberates through countless decisions they go on to make in and out of software.

That is what I strive to do, and that is what I have calibrated my mind to relentlessly optimize toward achieving.

Crafting people > crafting software

Working with technology deeply resonates with my soul because of its divine-like transformative power.

It allows humanity to go beyond our own design’s limitations and truly change our reality at scale.

But it takes creativity, craftsmanship, and collaboration to give people the super powers necessary to achieve the impossible, and it takes strategy to ensure they keep them.

As a Principal Engineer, I will use my technical expertise to help design, implement, and oversee the software systems that put my company’s dreams within reach, but though this is a highly technical leadership role, I will always put brains before code.

I will always be a beacon for the human good we are made of and the human good we build tools to support.

At the time of writing, this will be the pinnacle of my “people-first technical leadership” at work and having this opportunity to reach farther than ever before means the world to me.