Principal Software Engineer
CurrentAs I shifted into a Principal Engineering role, I took even further on the responsibility of scaling up the company’s Restaurant Web platform. The Monorepo (home of the restaurant platform micro-frontend apps) started as a single place to colocate our team’s micro-apps (around 5 apps in the beginning), but then grew under my stewardship to support more than 30 individual apps owned and developed by 7 different web engineering teams across 5 different timezones.I also revamped the deployment pipeline in TeamCity by parallelizing the processes and keeping the build times low as the number of apps kept growing.At the same time, I started having more conversations with other Restaurant FE teams (then expanded those conversations to cover the Diner side of the company as well) about unifying the design language and putting together a single Design System for the entire OpenTable organization. This was a massive effort to bring together all the frontend teams and figure out a common foundation that would work for all, and which would help us speak the same language in terms of Design and UI Architecture. I introduced new design system concepts (like semantic design tokens) and started to write guidelines and documentation that would later act as a single source of truth for all the UI decisions.