Oct 2024 – Jul 2025 · 9 mos · United States · On-site

• Second stint at Intuit! I managed two scrum teams of 12+ data engineers. Our charter was to build and launch several high quality data pipelines and dashboards that deliver critical business insights for Intuit’s assisted offerings TurboTax Live and QuickBooks Live. We were also responsible for building innovative GenAI powered tools that use OSS models from AI Marketplace, to support strategic initiatives in Data Engineering.

Jul 2021 – Sep 2024 · 3 yrs 2 mos · Palo Alto, California, United States · Hybrid

• I manage a team of full stack engineers within the Engineering Ops and Tools development division (CIBG) of VMware. We build and operate highly scalable and available tooling systems to boost the productivity of developers within various business units in VMware, shipping up-to 10 releases every year.
• Under my leadership, the team onboarded our customers to a state-of-the-art CI/CD system (micro services-based Unified Test Platform) that enables any developer to run any test at any time, leading to 2X code velocity, in-built retries, and near 0% result flakiness.

Nov 2019 – Jun 2021 · 1 yr 7 mos · Cupertino, California, United States · Hybrid

• Here is what I have had the opportunity of learning at Apple so far:
• ◆ How big data pipelines are built, validated and come together.
• ◆ The tech stack that has worked out well for such pipelines, in successful companies, and the best ways to go about validating them.
• ◆ Dealing with end to end complexities and challenges across functions, which are all doing something or the other with data - either by being a platform solution provider or by being a vertical, leveraging that platform solution.
• ◆ Most importantly, I am learning and witnessing the immense amount of rigor and discipline that goes into making complex data pipelines actually successful.
• Technologies : Kafka, Kafka Connect, Kubernetes, Hive, and Presto.

Sep 2019 – Nov 2019 · 2 mos

• Loved it here, but left because of the long commute.

Sep 2013 – Sep 2019 · 6 yrs · Mountain View, CA

• Given the criticality, and the distributed nature of most of our projects at Intuit, it is important that our services are highly available and highly resilient. This makes chaos engineering/FMEA an important discipline for us.
• I lead the effort in this department, by bringing in the mindset of “FMEA as a habit”, for multiple tracks in Intuit, and changed the game by truly identifying gaps in operational readiness of our components by introducing a holistic approach to FMEA, that went beyond just bringing up and down instances. This level of detail allowed me and my team to identify and expose many system design flaws in the projects I worked on, and gave me an opportunity to delve deep into literally every component in the tech stack that was in my purview – Kafka / Cassandra / Redis / Consul / SQS / Other AWS services.
• Through course of the year, I designed and implemented a generic FMEA infrastructure that can be used by anyone, as long as their applications are hosted on AWS, and have a consistent naming pattern. I successfully piloted usage of the infrastructure on multiple tracks within Intuit.
• Prior to that, I was with the QuickBooks online team, where I was involved in leading a team that was involved in designing and implementing a global test strategy for validating services invokable via REST and GraphQL.
• I also had the opportunity to work on an ambitious disaster recovery project of one of Intuit’s flagship products, that reduced the RTO from more than 24 hours to a few minutes!

Jan 2013 – Jun 2013 · 5 mos · San Francisco Bay Area

• Responsibilities:
• Define, develop and execute end-to-end test strategy for RESTful web services and file-based integrations with Xoom's partners.(the scope includes regression, integration, and stress testing)
• Technologies/Tools Used : TestNG, Core Java, Perforce, Maven, Jenkins etc .

Nov 2012 – Dec 2012 · 1 mo · Burlingame,California

• Worked as a consultant for Bankrate, on their 'Quadrant' project.
• Quadrant is an end-2-end Java web application, that is used to generate Auto/Home insurance leads. It supports various carriers / insurance providers. It is developed in Java/J2EE using Web Services,MySQL and NoSql.
• Responsibilities:
• Prototyped invoking functions in an existing .NET DLL from a servlet. This involved analyzing the various JNI wrappers available and doing the final prototype using JNI4NET.
• Designed/Developed the entire pipeline.(Middle layer business logic in Servlets, and Data persistence layer written in Redis).
• Technologies:
• JNI4Net, .NET to Java Marshalling, Redis, Webservices, Java 7 and Tomcat 7.0

Feb 2010 – Apr 2011 · 1 yr 2 mos

• Second stint at Misys! Developed an application development and run-time framework that provides capabilities to build, configure, integrate, and deploy a new generation of financial Solutions across multiple computing platforms.
• Technologies/Tools used : Eclipse Plugin Development, Spring, Hibernate, JXFS, Dynasty, Hudson, Webservices, JBoss 5, Websphere.

Jun 2009 – Jan 2010 · 7 mos

• Stores (Development) and Implementation Tools :
• Technologies/Tools Used: WingS, GWT, JavaFx, Swing,Oracle ADF, JSF, Struts, OBIEE etc.
• Responsibilities:
• a)Involved in design of SIM 13.0 for Brazil Localization.
• b)Worked on reducing Total Cost of Ownership and Total Cost of Implementation for Retail enterprise applications.

May 2008 – Dec 2009 · 1 yr 7 mos

• Localization Development:
• Technologies/Tools used : Swing,OC4J,Oracle 10, Eclipse, CVS, Enterprise Architect,
• StarUML, Toad, SQLDeveloper, WinCVS, Source Insight.
• Responsibilities: I was responsible for customizing the ORSIM module to suit the Indian market.
• Truly end to end ownership - Designed, developed, tested, supported, documented and shipped the product with very minimum guidance! Still have fond memories of my work during the time!

Jul 2007 – Jun 2008 · 11 mos

• Oracle Store Inventory Management (Sustenance Engineering): (July 2007 to May 2008)
• Technologies/Tools used: Swing,Oc4J,Oracle 10, Eclipse, CVS.
• Responsibilities: The primary responsibility here was to fix issues and provide enhancements to customers on time. It involved getting an overall picture of the module and also a knowledge of how it integrates with the other modules. Tasks included handling customer escalations, peer reviewing code, documenting defects and making sure that defect fixes were in alignment with functional spec.