I started working at SiriusXM in January of 2016, which was one of the most interesting experiences in my career. I went for the interview, did a test, and met with a bunch of future co-workers. On the way out I received a call from HR asking me to go back to her office where they immediately offered me the job. It was shocking and incredible!
As you may know, they are a broadcasting company which provides satellite and internet radio. I worked in Digital Experience, where our team maintained the website as well as some internal tools.
My initial role was a Front-end Developer, and about two years later I was promoted to Senior Developer. My role and responsibility grew as I began to help more on the back-end. It was fun learning about the system, getting my hands dirty with Java, and helping catapult our code into a new era. I pushed to modularize our templates, making it easier to build what we needed both on the front and back ends. Around this time, the website was also redesigned, and I played a key role in bringing the new design to life.
Once again, about two years after that, I was promoted to Lead Software Engineer. My biggest accomplishment since then was leading the team's migration from Oracle WCS to Contentful and bringing NextJS, a React framework, into the picture. The result was a full second shaved off our page load times and a 20-point jump in our Lighthouse performance score. I also drove NextJS and TypeScript adoption across a team of seven developers, partnered with Level Access to take our ADA compliance from 64% to 94%, and led the hiring process that grew the team by four engineers.
In March of 2026, all of that experience leading projects and mentoring the team paid off, and I was promoted to Engineering Manager. A big part of this new chapter has been rethinking how the team measures and protects its own velocity: I led the shift from time-based estimates to a three-pillar framework built around Complexity, Uncertainty, and Effort, which bumped our average developer capacity from 10 points a sprint to 12, and we've since rolled the framework out to teams across the org to standardize how everyone plans delivery.
I've also been leading the charge on bringing AI deep into our day-to-day workflow. I introduced Claude Code and Codex across the team to automate sprint health reporting and run two rounds of targeted code audits, surfacing 46 tickets for legacy debt and accessibility gaps, then another 25 to improve our long-term test coverage. On the more surgical side, I used Claude Code to identify, update, and verify a required field change across 200+ Contentful content types, saving our content and QA teams an estimated four hours of manual work.
I also built a Claude Code and Codex-powered code review skill wired into our MCP integration layer, connecting to Jira, GitHub Enterprise, Chrome, and Figma. It validates pull requests against ticket criteria, runs functional tests, and does visual regression comparisons against production, giving the team an end-to-end AI-assisted QA pipeline before anything ships, and it's just as handy for going from a Figma component straight to working code.
On the culture side, I introduced EasyRetro and pushed for more asynchronous communication to cut down on meeting fatigue and protect focus time, and we're now averaging a 0.7-day PR cycle time. One of my favorite wins so far was shipping our account snapshot feature a full sprint ahead of schedule, mostly by staying heads-down on clearing roadblocks for the team instead of adding more process.
During my time at SiriusXM, I've interviewed potential candidates, planned and de-risked projects, coordinated across departments, and now lead a full team of engineers day to day. What I've learned about myself is that the part of development I loved most was never just the code; it was watching a team come together to ship something great. That's exactly what led me to embrace engineering management.