Can you tell me about yourself?

I’m a web developer, certified Web Accessibility Specialist, and I’ve been doing this for 13 years. Working at digital agencies I’ve churned out multiple sites a year. Also I came into work and made the same properties better every day, working in SaaS.

What did you do in your last role?

Recent clients had handed us a mandate: build for accessibility. I worked with design and dev to catch issues with automated tooling, plus code review checklists for what tooling can’t. Tim Cook’s line — you don’t do accessibility for ROI — became our north star, but treating it as a foundation saved real time and money we’d otherwise spend on rework.

Coming from Sprout Social, I brought what worked there to grow up our dev practice. Deadlines were slipping, so I implemented sprint schedules to get design, dev, and project managers aligned on timelines.

I was the second developer hired, and I’d worked in a silo before where knowledge didn’t get shared. Within a couple weeks I rolled out code reviews with checks for browser compatibility, accessibility, and eventually carbon output and performance. Even when we shipped something with high carbon output, the whole team knew what to come back and fix . Then accessibility and compatibility regressions stopped slipping into production.

Lighthouse scores jumped 30% after we moved our marketing sites off WordPress. At Sprout we’d used Hexo for marketing and WordPress for blogs, so I knew both had their place — and Boldium’s marketing-heavy work needed Astro. We could still reach for almost any JS framework, but ship static, nearly JS-less sites that were dynamic and beautiful. SEO wins followed.

I was a lot of different people, like you are on smaller teams — but the through-line was making the work faster and more accessible for people.

What’s a recent accomplishment?

We lost a bid with one of our longest-running clients. Honestly, it stung. I was sure they’d hit problems we’d already solved. So instead of going quiet, I kept an ear out for friction on the project and offered up resources we’d already built for the other agency to use. Once the blog launched and maintenance started, I jumped in to help where I could. A few months in, the client decided we were the better fit and brought maintenance side of the work back to us.

Losing gracefully and staying useful turned out to be a better long-term play than winning the bid would have been.