I have a decade of experience working at an enterprise-focused
marketing technology startup. I’ve worked on everything from
cross-browser bugs to building major features to tracking down
I believe in collaboration and a positive work environment that
forgives mistakes. I value clear communication, reproducible work, and
automation that ensures quality.
I’m entirely self-taught, picking up new skills as required. I’ve
learned about topics like internationalization, accessibility and
time zones and
and how emoji are implemented in Unicode.
I was the first employee at the company, and over time I contributed to
every level of the technology stack. The leadership respected that I
didn’t want to become a manager, and instead I was trusted to work on
problems that other teams didn’t have time to address. Beginning in
2016 I set up several hours of
every day to pair with anyone who needed help.
Site Reliability Engineer — –
I convinced my managers to let me create this role based on what I’d
learned from Google’s
SRE book. I
collaborated closely with the Platform Operations team, but my projects
were largely self-directed.
My biggest achievement was a report that examined the entire platform,
AWS costs. I found we could
save > 25% of annual hosting expenses, and identified high-value
opportunities to improve application performance.
Other stuff I accomplished:
performed several dozen root-cause analyses for performance and
ran blameless postmortems, sometimes including upper management
from across the company
used Sumo Logic to analyze
logs from AWS CloudTrail, Ruby on Rails, the Linux
syslog, and more
wrote and shared 100+ preconfigured log searches to help others
construct advanced queries
created personal monitoring dashboards and wrote guidance for other
built alerts for AWS permissions and Jenkins
evangelized code linting with tools like