The humbling reality of my mid-career pivot from PM to SWE - and why I'm betting on operational maturity over FizzBuzz metrics.
For years, my Computer Science degree sat on my resume like a quiet accusation.
I didn't ignore it. I worked with it. I excelled in tech-adjacent roles where my proximity to engineering felt safe: Technical Project Manager, Scrum Master, the person who could translate for the stakeholders without being asked to open the codebase. But eventually, that "quiet" accusation turned up the bass. My discontent became harder to ignore. Colleagues laughed at my spontaneous outbursts of dissatisfaction.
"I don't see you hunched over a desk in a two-week-old hoodie staring at code, Tiff. You're so good at what you do."
I'll take that.
I subconsciously adopted their reasoning as a mental pacifier. It was easier to call it a preference than to admit it might be fear. I stayed in the shallow end, telling myself that I didn't want to swim anyway. In reality, I was terrified of the depth between my potential and my practice.
So I stayed adjacent. I shipped projects. I shined. And I lived with the low-grade anxiety that one day someone would ask me to contribute a solution as a computer scientist… and I'd be “exposed”. Two years ago, I decided to stop hiding behind proximity and finally step into the role my degree had promised years earlier. I accepted a full-time software engineering position. What I didn't anticipate was the psychological whiplash of the most senior and junior versions of myself colliding overnight.
A trophy → Atrophy
My CompSci degree was once proof of my discipline and perseverance. Late nights alone with an aging laptop. Coding tutorials replayed at 0.8x speed so my overloaded brain could keep up. Family outings where I was physically present but mentally plagued by some confusing computer science concept. Sweet moments with my baby girl, interrupted by the intensifying pressure of a looming due date for code that refused to compile. Sacrifices well worth the cost of providing a blueprint of persistence for my daughter and newborn son on the way - rather than a cautionary tale of regret. The plan was to pivot into my new career path "at the right time" that would never arrive.
"I'll start job hunting after the baby arrives."
"I'll interview prep after we move."
"I'll start studying again after we settle in."
In the waiting, my technical edge began to rust. I became an expert at the strategy of tech while the implementation details underwent a slow, quiet stagnation. My "trophy" of discipline transformed into a resounding beacon of atrophy. My sporadic coding streaks and inconsistent refresher courses weren't enough to fill the growing gaps that I tried so desperately to patch.
Into the Deep
For years, that deficit stayed gorgeously shrouded in my occupational responsibility of leadership and strategy. I hid the rust behind the "big picture". As a PM and Scrum Master, my job wasn't to hold the wrench; technical gaps were merely blockers to be managed, not weights to be carried. Leadership discusses the business outcomes over catered lunches and the trusty engineers will carry us there. But when I finally stepped into engineering, the gorgeous shroud was gone. That burden was mine.
I was in over my head in the shallowest of waters. I suffocated in the depths of detail that was so casually exchanged at every stand up. My middle-aged mind underwent the most intense growing pains. It stung in every conversation. It seared in merge request comments on tickets that assumed at least a decade of technical muscle memory I just didn't have. The marker felt like lead in my hands during whiteboarding sessions. I spiraled in a labyrinth so foreign that I lacked the context to form a question; any map would render useless because I had no clue where I was standing. Every day was a unique learning intensive: reading mile-long documentation, interfacing with customers, learning to manage a K8s cluster, shoulder surfing Maven dependency error investigations. I wasn't just relearning to code. I was learning how to breathe in an environment that assumed I was already a deep sea diver.
There is a specific genre of pause that occurs when a full-salaried engineer asks a question so basic it momentarily disorients a senior developer. I was a seasoned birds-eye view professional in ground combat with a YAML indentation error. In those moments, I wasn't just learning. I was publicly closing a knowledge gap that felt like the Mariana Trench - with an audience. Progress was made by returning to the same hard problems night after night, long after the novelty of the role and the bursts of motivation had worn off. Learning happened in public, under real deadlines, with real consequences.
The PM Edge - Learning Velocity Over Ego
Early in this pivot, I made a decision. Ego wasn't a luxury I could afford. In tech, pride masquerades as competence. To make progress I needed to prioritize information gathering and true understanding. There was no use in novice performance theater when I was surrounded by seasoned actors. Asking an intern for a syntax refresher wasn't a failure. It was a tactical move to increase my learning velocity. As a former PM, I understood this instinctively. The goal for my teams was never to look individually capable. The goal was to reach "done" with quality and momentum. I had already learned that trust and intellectual humility move teams faster than individual brilliance. Pride doesn't ship code. Systems do. So I built one. I treated my upskilling like a program initiative: aggressive timelines, structured learning blocks, ruthless prioritization, and rapid feedback loops. I laid out my development plan in MS Project and shared it with my leadership. I leveraged documentation, code reviews, and teammates without apology. Not because I lacked confidence, but because I refused to waste time protecting it.
Writing From the Other Side of the Pivot
In the early months of this transition, I realized something unexpected: the discomfort wasn't a signal that I didn't belong. It was evidence that I was finally operating at the edge of my capacity again. The ghost I'd been running from wasn't incompetence. It was unused potential. This pivot has been humbling, to say the least. But humility isn't weakness. It's a prerequisite for growth. And in an industry obsessed with genius narratives and gatekeeping metrics, grit and emotional intelligence remain the most reliable predictors of long-term impact.
It’s quite funny. In leadership circles, we discuss the “what” and “why” for the business outcomes. It’s a world of tradeoffs and realignments. In engineering you carry the “how” which is an entirely different beast. While leadership debates the destination, the engineers are white-knuckling a broken K8s cluster so the ship stays afloat. As an engineer, sitting in these same meetings and hearing new initiatives piling in on top of other initiatives that are all “priority”, with an implied “it shouldn’t be that hard” woven into each verbalized expectation. I oftentimes have to hold back my chuckles. What completely different worlds.
This experience permanently reshaped how I think about hiring, onboarding, and technical leadership, and it's a lens I'll carry into every system and business I build going forward. I'm not just a software engineer now. I'm an engineer with a PM's brain, a systems mindset, and the scar tissue of a high pressure career pivot.
My confidence was built by keeping promises to myself.
And this time, I'm not staying adjacent to the fire.