

Jesus Medrano, a Staff Software Engineer for Delivery, was among the original Engineers to help build Uber Eats’ Android application. Today, he’s helping scale our business across new areas, including Grocery and Pharmacy, while unifying the architecture of our iOS and Android applications. Jesus co-chairs the Los Ubers ERG, Uber’s community for Hispanic and Latinx employees and allies, and is a Board Member of Voices of San Diego, a member-based nonprofit investigative news organization.
Tell us a little bit about yourself.
“I grew up in the border towns of San Diego, California and Tijuana, Mexico. I lived an impoverished life, yet was fortunate enough to be part of a supportive family. I recall not having access to telephones, hot water, or paved roads for many years of my life. In my later childhood, we moved around often, sometimes living with relatives in a crowded situation. We also lived in poverty-stricken areas where violent crimes were common, such as a drive-by shooting done to our residence.
Fortunately, with some great mentorship, support, and luck I was able to excel in my academic life. With that, along with my curiosity and stubbornness, I was accepted to the Massachusetts Institute of Technology. Being a first-generation college graduate in my family meant my parents didn’t know much about schools or studies, but they were very proud of me nonetheless. I graduated from MIT with a Bachelor’s in Mathematics.
I started my career as an Aerospace Engineer for large autonomous drones. These massive drones would operate for a day at a time and could transverse most of the world. I analyzed flight plans and simulations to ensure safety. I also worked on fun projects that analyzed various environments from high altitudes, such as the Pacific Ocean over a hurricane. Prior to Uber, I worked as a Backend and Mobile Application Developer at Yahoo!, where I supported mapping and then led development for the Android Yahoo! flagship app.”
You’ve been at Uber for nearly 6 years. How has your role evolved?
“When I first joined I worked on our Ridesharing application, experimenting with how to start incorporating Uber Eats menu items. That led to the decision to develop an independent Android application, and our small Android team then spent a busy few months building it from scratch. We worked diligently to meet aggressive timelines and officially launched on January 6, 2015.
After, the Uber Eats organization began to grow and we were split across product teams, which have now grown to several dozen. From then our main goal was to expand features and user growth. Unlike in Ridesharing, we weren’t yet well known in many cities at the time, so we added new features as fast as we could.
Hypergrowth comes with growing pains. On the mobile side, code was becoming harder to maintain, bugs were becoming more frequent and their impact was greater. Having more Engineers distributed across sites led to inconsistent development practices. I turned my focus to solving some of these larger issues like reducing our crashes and bugs, building a consensus on coding standards, and guiding us to a consistent development process to match those of the Ridesharing and Driver applications.
There was a need to build the right processes to keep our quality high, while also scaling for new users––all while moving quickly. I took over the Uber Eats mobile release process in 2016 and founded our mobile engineering design committee, which emphasized awareness of work across teams, leading to increased participation and higher quality feedback.
Over time, this work would require longer timelines and more support across teams, resulting in the creation of the Uber Eats Mobile Platform team that I am a part of today. Our initial focus was on migrating our applications to the same architecture style used by other Uber mobile apps. Today, the focus is on finishing that migration and setting the foundation to better support more lines of business, including Grocery and Pharmacy.”
What has been one of your proudest moments? Can you share a favorite memory?