Engineering, web, data and IT. Some of it paid, some of it for school, some of it mine. The three below in detail, then the rest.
I joined the Technology and Digital department in September 2026, straight out of university and into the first full-time engineering job of my career.
It is early days. I will write something worth reading here once I have enough behind me to have an honest opinion about it.
I started WebEaze in 2024 as a subscription web studio for small businesses. It has grown to more than forty responsive sites, all built in React with an eye on speed and accessibility.
I handle all of it: the design, the build, the analytics and SEO, and the automation scripts that take client onboarding from an afternoon down to a few minutes.
A summer on data pipelines. I optimized a daily Apache Spark and Java job that processes partitioned user listening logs, cutting its compute cost by 14% and bringing ingestion latency down with it. I also built an automated validation and quality control step that catches anomalies in streaming audio metadata before they reach anybody's dashboard.
It was the first time I had worked in a codebase that size. I came out of it comfortable with real code review, with testing, and with releasing in small pieces instead of one big drop.
Two summers in the IT department of an elevator company. I wrote Python and JavaScript scripts that cut help desk response times by about 30%, and built Power BI dashboards on top of Microsoft Dynamics so the leadership team could read their own numbers.
Most of the job was turning messy data into something a person could act on, which turned out to be good practice for everything since.
Read onboarding and retention data in SQL and Excel to find where people dropped off, reported on signups, retention and social impressions to support product decisions, and prototyped school-specific app features in Figma.
Built coding exercises and structured curricula in Python and Java for 150 students, lifting their test scores by about 15%. The material covers data structures, algorithms and how to break a problem down instead of guessing at it.
Built and maintained the chapter's website in React, HTML and CSS so more than 250 members could find what they needed.
Managed the lifecycle, imaging and deployment of more than 500 devices using Excel and Workday. Handled hardware and software support for faculty and staff, working through 200 or so tickets a week and cutting average resolution time by about 70%.
A volunteer super-user role: helping people on the community boards, writing help content, testing features early, and going to Spotify's offices once a year to give the teams feedback. It is how I first got connected to the company.
Helped people work out what they actually needed, ran the register, and kept the floor in shape. My first real job, and where I learned to explain a technical thing plainly.
A real project for Palmetto Goodwill. I led the IT and networking side of a thirty-person team designing a full mobile app prototype: a loyalty program, donation capture and scheduling, a store locator, and an online shopping flow.
We worked with their point-of-sale, IT and logistics people so the integrations were realistic, then handed a finished prototype and the repository to Goodwill's own development team.