I am an Engineering Leader in the AWS Compute Services Organization. In this role, I lead the vision and strategy for an engineering organization responsible for providing foundational insights to service teams and leadership across AWS. This includes insights on AWS region build duration, builder effort, capacity planning, customer success, and automation health. As an Engineering Leader, I manage a cross-functional team including Technical Program Managers, Software Engineers, Data Scientists, Business Intelligence Engineers, and Data Engineers. I am a manager of managers, overseeing this diverse group of technical professionals to deliver critical platform, process, and mechanism capabilities to empower teams throughout AWS. My responsibilities center around establishing the strategic direction, processes, and technological solutions that equip other AWS organizations with the data and insights needed to drive operational excellence, customer success, and continuous improvement.

I led transformation initiatives around containers-as-a-service with a team of over 50 people, managed by 5 functional Engineering managers. The goal was to provide simple, secure, and scalable container services that were platform and infrastructure agnostic. During my tenure, the team grew by over 75% and the platform itself expanded by over 300%. This container platform was a key driver for cloud-native application development and a critical enabler for T-Mobile's broader digital transformation initiative. In this leadership role, I was responsible for driving best practices and processes across a number of areas, including: DevOps, On-call procedures, Product scorecards, Root cause analysis (5-Why's), and Change and incident management. Through this transformation effort, I was able to significantly scale the engineering team and the mission-critical container platform, which served as a foundational component of T-Mobile's shift towards cloud-native applications and digital modernization.

I led a technical program focused on Chaos Engineering. This involved driving the adoption and implementation of Chaos Engineering practices within the organization. In addition to my leadership of the Chaos Engineering program, I also authored and delivered a technical talk titled "Chaos Engineering – In search of failure". This bootcamp-style presentation was aimed at further promoting and driving the adoption of failure testing approaches across Amazon. Through my work on the Chaos Engineering program and the associated technical talk, I was able to evangelize the importance of failure testing and resilience engineering within the company. My efforts helped to spread awareness and best practices around Chaos Engineering, which is a critical discipline for building robust, fault-tolerant systems.

I led a team of 15 people in a role where I championed and defined a Cloud Readiness matrix. The goal of this matrix was to map out and guide the development team's journey to the cloud, as well as establish best practices for DevOps. In this leadership position, I was responsible for creating a framework that would help the development organization successfully transition to cloud-based operations. The Cloud Readiness matrix served as a roadmap, outlining the key milestones, capabilities, and best practices the teams needed to adopt as part of this cloud migration and DevOps transformation. By defining this strategic matrix, I was able to provide clear direction and a structured approach for the development teams to follow as they embraced cloud computing and DevOps ways of working. This helped ensure a coordinated, consistent, and successful cloud transformation across the organization. Through my leadership and the creation of the Cloud Readiness framework, I played a central role in guiding the organization's development teams towards cloud adoption and DevOps maturity. This work helped lay the foundation for more efficient, automated, and resilient cloud-native application delivery.

I wore multiple hats and took on increasing levels of responsibility that demonstrated my versatility and adaptability as an engineering professional. During this time, I operated both as an individual contributor and manager, allowing me to understand the needs and challenges at various stages of the software development lifecycle. In one of the key leadership positions at Citrix, I led the transformation efforts and launch of Citrix Workspace Cloud. During this time, I collaborated extensively with partner teams to onboard more than 200 customers onto the new platform. As the engineering leader for the Citrix Workspace Cloud initiative, I spearheaded the successful transformation and launch of this critical product. This involved coordinating closely with cross-functional partner teams to ensure a smooth customer onboarding process, highlighting my strong collaboration and stakeholder management skills. Through my diverse experience and leadership of the Citrix Workspace Cloud project, I proved my ability to drive complex transformational efforts, launch new products, and work effectively with both internal and external teams to achieve business objectives.

In the early phase of my engineering career, I discovered that I was better at breaking software than building it. This realization marked the beginning of my career path, where I gravitated towards roles and responsibilities that leveraged my natural aptitude for identifying and addressing software defects and vulnerabilities. This self-awareness about my strengths and interests likely led me to pursue opportunities in areas such as software testing, quality assurance, chaos engineering, and other disciplines focused on proactively uncovering and mitigating software failures. The ability to "break" software in a constructive manner has likely been a valuable asset throughout my career as an engineer. This early career insight allowed me to chart a path that aligned with my talents and preferences, setting me up for success in engineering roles where my skills in software chaos, resilience, and failure analysis could be put to the best use.

Beginning of the first phase of my career as an Engineer where I learned I am better at breaking software than building software.