Ryan Rogers Email & Phone Number

Henderson, Nv, Us

Las Vegas, Nevada, United States

As the team lead, I was responsible for managing the lifecycle of the team's projects. This would start with collaborating with product managers and/or other stakeholders to translate the general project asks into actual requirements. We would discuss expected timelines/milestones, urgency, and level of effort.Once we had all that in place, I would bring it to the rest of the team for further refinement. This would involve breaking the project down into smaller more manageable chunks and then loosely figuring out how to fit the work into current/upcoming sprints.When working on projects, I wore many hats. I would write code, mentor the junior engineers, perform code reviews, and keep stakeholders apprised of the progress. As tickets were completed (as defined by automated tests passing, QA giving the thumbs up, and then passing UAT) I would release them to production. When the project was completed, I would present the team's work to the rest of the company when appropriate.My team dealt with a large portion of the 20+ year old code base. This included new features and bug fixes in the Symfony 4.x monolithic app, as well as creating new microservices using Symfony 6.x.During my time at Slickdeals I led a number of projects from the "wouldn't it be nice if..." stage to the revenue generation phase, too many to list here. The team was able to produce clean, maintainable, and well tested code that met the needs of the stakeholders in a timely fashion. I'm incredibly pleased with not only the work that we did, but the culture that we fostered.In the middle of May of 2023, one third of the company got laid off. Included in that third of the company was a large swath of the engineering department, myself included.

Las Vegas, Nevada, United States

I spent my time working on our legacy monolithic Java 8 app, as well as creating and working on new microservices using Java 11. While my role was mostly that of an individual contributor, I was given a handful of notable projects to spearhead.One such project was implementing event insurance to supplement our existing travel insurance offering. This involved touching a fair bit of the critical booking flow for the monolithic app, as well as completely redesigning the existing insurance microservice. The redesign was required since the existing travel insurance offering consumed a SOAP API which was no longer supported, which meant both travel and event insurance would be consuming the provider's JSON API. On top of the API changes, there were additional requirements that needed to be fulfilled to support event insurance.Another project that I led was onboarding a new supply partner for the events side of the business. This involved consuming the supplier's API to get available inventory, integrating this inventory with our current inventory management system, and ensuring that bookings would succeed with various layers of fault tolerance.

Las Vegas, Nevada, United States

As the lead engineer, it was my responsibility to guide projects from inception to a production release. This involved collaborating with stakeholders to collect requirements and to ensure that those requirements ultimately resulted in a successful product launch.A bulk of the time here was spent gradually replacing the legacy inventory management system that was currently in place. The old system was a very involved and manual process. A spreadsheet was created with a list of inventory that we needed for a given event, and then e-mailed to the supply partner. The partner would then manually fill in values for different units of inventory and e-mail the spreadsheet back. Someone would then manually enter the inventory values into the system.The new system, which was created using PHP and Symfony, would track existing inventory and automatically notify our supply partners if we were low on inventory or if inventory was selling quickly. The partner would then log into a web portal where they could see inventory that was available as the inventory that we were requesting. They would fill out the form which would submit the data to our PHP backend and then generate an API request to the Vegas.com API to make the new inventory immediately available. Tooling was also in place to keep track of all of these inventory modifications.There was a period of time when we required greater business intelligence to help us keep an eye on how we compare on both pricing and availability. To facilitate this need, I wrote a handful of web scrapers in Python. These scrapers would pull data from both our partners as well as competitors and translate that into a spreadsheet that tabulated the relevant data.

Las Vegas, Nevada, United States

roomlia was a mobile-only hotel booking app. I was the lead developer for the backend application which was written in PHP using the Symfony framework. This application managed pricing and availability (both current as well as new data ingested from our supply partners), bookings, as well as the API that the mobile app consumed.My primary responsibility here was to build the infrastructure to support expanding our product offerings. The main requirement for this was to rework the backend to allow us to go from supporting just a single room type/rate plan (known as "run of house", where the customer gets whatever room is available at the time of check-in) to supporting any room type/rate plan combination (such as "king suite with a strip view"). As a part of this, we had to also be sure to support all the different rules that a hotel can have for allowing a room to be booked, such as basic lengths of stay, full pattern lengths of stay, etc).One of the more interesting challenges here was managing the data that was pushed to us from our supply partners. Some of them used SOAP, others XML, and one or two used JSON. Even when a data format was shared between partners, the schema typically was not. Our solution to this was to use XSLT to transform the data into a common format so that all the data could flow through a supplier-agnostic pipeline.On top of this, the code had a lot of tech debt built up by the time I joined. I led the charge in migrating us from PHP 5.x to PHP 7.x, as well as migrating from Symfony 2.x to Symfony 5.x.