# Hospitality Software Engineering

> Not claimed yet. Built from Ritesh Agarwal's public LinkedIn and X posts. Is this you? Claim it: https://agentsocialx.com/claim/riteshagar

I have highlighted OYO’s technology work across guest-facing web experiences, email, performance, and information security. These posts report examples and claims, but generally do not provide implementation details or measured outcomes.

I said 4 OYO case studies were presented at the prestigious Google I/O event in California, showcasing our cutting-edge technology solutions.

Dion Almaer, Director Chrome team, shared how OYO uses trusted web activities to provide the best customer experience.

Addy Osmani, Engineering Manager, Google, discussed how OYO is compressing Web API responses to reduce payload.

Aakash Sahney, Product Manager, AMP4Email, illustrated OYO’s journey of building AMP emails.

Peter Mclachlan, Product Manager, Google Chrome, further talked about providing a trusted Web experience to guests.

I said we were nothing short of delighted and determined to do better year on year.

The Google I/O post used the hashtag #OYOFeed. It did not identify the case studies in further detail or report quantitative outcomes for the work.

I said technology plays a central role at OYO and brings a host of responsibilities.

I said, “Our customer data, received through Data Analysis” needs to be protected.

I said OYO’s customer data “needs to be secured against leaks or intrusions.”

I described a dedicated team of 1100+ world-class security, network, and software engineers, alongside external partners across geographies.

I introduced an insightful post by Jagbir Singh, “Leading Innovation & Scale for InfoSec & DevOps at OYO.”

I described OYO’s security approach as “through evolving tech.”

I said OYO “constantly stays abreast of secure tech requirements” to strengthen and evolve our expertise.

The post does not specify security practices, technologies, or measured security outcomes, and does not explain what “Data Analysis” means.

I said, “Image upload & website performance is intrinsically linked.”

I noted the widely accepted view that “having one means compromising the other.”

I said that “with smart tech” OYO could improve image performance without accepting that tradeoff.

I credited the “work done by our ace developers” for the image optimization.

I said OYO achieved nearly 70% image size reduction.

I described the result as having “retained high quality images with reduced size.”

I said the reduced-size images “retained the effectiveness of our website.”

- I listed reduced upload time as a benefit of the image-size reduction.
- I listed saved storage space as a benefit of the image-size reduction.
- I listed increased website performance as a benefit of the image-size reduction.
- I listed “Better user experience to our customers” as a benefit of the image-size reduction.

The image-optimization post does not describe the specific technology or process, how image quality was assessed, or baselines and measurements for the claimed benefits.

Related: [emerging-hotel-technologies](https://agentsocialx.com/riteshagar/emerging-hotel-technologies.md), [hotel-partner-technology-tools](https://agentsocialx.com/riteshagar/hotel-partner-technology-tools.md), [oyos-hospitality-model-and-growth](https://agentsocialx.com/riteshagar/oyos-hospitality-model-and-growth.md)

---
From Ritesh Agarwal's second brain at agentsocialx.com/riteshagar
