Independent contributor in charge of several large scale projects with vague requirements and little oversight. Started as the junior member of a team of 2, ended as the second-most senior in a team of 10 with two indirect reports. Created and lead a monthly "Level Up" course, with a classroom style on complex topics. Guarded the frontlines as a member of the 8-person SRE on-call rotation (24h) which handled live production incidents for the entire site. Promoted mid cycle 2023.

My work on the Hotel's team garnered the interest of a manager there and he pulled me in and promoted me in the process.

It was for another small team, the Vacation Rental team. We were focused on the subset of properties that were a part of VRBO, owned by Expedia. How to highlight and display these along with our regular inventory matched up with my experience on the packages team.

I built out a new request pattern to provide additional unique key value pairs for properties to display on the hotel search page. Which was also reusable on the room selection page. You can imagine the room selection page for a hotel being quite different from what you might see on a vacation rental house.

Due to a restructure though, the Hotels team became Lodging and our focus was no longer only on vacation rentals.

I began to outgrow my role at Expedia, but openings for senior positions were few and far between with engineers waiting longer than I.

Leaving was bittersweet.

I began work @ Expedia on the package team. While Expedia sells flights, hotels, and cars; the package team works with any combination of the three.

While this seems simple at a glance, Expedia was in a stage of rapid growth and experimentation. Each team's frontend code was a different toolset in a different repository with different approval committees.

I worked in Java, FTL, Handlebars, React, Ember, and Marionette.

Since our code crossed all of these, I regularly had to design migration strategies and testing plans. Including designing an Nginx setup for our team to run multiple of the apps simultaneously for testing.

I architected a way for us to move out of ruby cucumber (since we had no ruby developers) and into nightwatchJS without losing our existing Gerkin tests.

Then as the company began to move into the cloud, I started working on a series of lift and shift migrations to move backend code out of the monolith.

Finally I began working closely with the hotels team as they moved into an entirely new mobile-first progressive web app design. Written with React, GraphQL, and Kotlin microservices.

Summer Intern on the OneNote API team. Project was involved with a broken part of an existing tool. Turning their notebooks into html worked, but images didn't because they required authorization to request the URLs.

I created a randomized guid and cached a limited time access token in redis. Browser would load the new URLs with the guid, and auth for an image would be skipped if the key was included and it was in the cache.

I also worked on using phantomJS to create a snapshot of the html page for regression tests and for thumbnail tooling.

Lastly, I refactored a large portion of their codebase to stop using lambdas. They were unnecessary for the space and made debugging a multi-threaded experience.