Aug 2019 – Jul 2022 · 2 yrs 11 mos · Hyderabad Area, India

Jun 2010 – Aug 2019 · 9 yrs 2 mos · Bangalore, India

• Responsible for architecting and designing large scale, high available, scalable platforms that enable product teams to focus on providing innovative solutions to customers problems.
• Lead the design and architecture of next gen connected identity platform that helps Users move seamless between Intuit platform and external ecosystems.
• Lead data ingestion and cataloging platform for Intuit Data Fabric.
• Lead architecture for delivering personalised messages to all Customers and Prospects across all channels and touch points.
• Lead Design for implementing a robust and flexible Content and Privacy system for use across the ecosystem.
• Lead the Design and Architecture for Financial Data Platform to acquire data from disparate external data providers and expose the data as a set of API's to product teams to enable "Never Enter Data" experience to Customers.
• Re-architected an existing legacy platform to be service enabled, resilient and scalable
• Drive cross-cutting changes and improvents across the whole org. e.g. CI/CD and release automation. Operational excellence.
• Mentor, coach and grow senior technical talent.

Apr 2008 – Jun 2010 · 2 yrs 2 mos · Bagalore, India

• Architect responsible for defining and driving architecture with in Advertising Products Group.
• Designed and architected a scalable, robust and extensible platform for validating the quality of the Ads submitted by the advertisers.
• Collaborated with sciences team to improve relevancy of the ad listings shown on “Domain Match” (parked domain) sites.
• Drove Patent initiative to encourage patent filing, conducted IP camps with external counsel for presenting ideas and getting their feedback.
• Drove Continuous Integration (CI) initiative and achieved commit and secondary builds across APG.
• Mentor and coach technical talent.

Jul 2006 – Mar 2008 · 1 yr 8 mos · Bangalore, India

• Responsible for design and architecture of Flexible Payments Service (FPS) (part of the AWS suite of services). FPS is a payments web-service targeted at developers to incorporate payments capability into their applications.
• Re-architected the platform to move/migrate the underlying database to a more robust and stable option, there by improving the overall availability and stability of the service. Ensured that the designs continued to be scalable with the new architecture and data migration was done with minimum downtime and high quality.
• Re-organised the code base from 200 odd disorganised projects to 120 projects aligned across subsystem boundaries.
• Re-designed and implemented the web based application used by support staff to MVC architecture and leveraging latest tools and frameworks like Spring, Spring MVC, Velocity etc.
• Technical excellence - Drove adoption of development best practices including continuous integration with “pre-tested” commit. Drove tech talks initiative and presented a few topics myself.

Mar 2003 – Jul 2006 · 3 yrs 4 mos · Farmington Hills, MI, USA

• Lead Architect for GOLD - the next generation platform of Gale’s On Line Delivery System, which will enable the company to create products more easily, scale efficiently and economically and tier the features according to the market.
• Responsible for overall architecture, design and development principles, selection of technologies, integration of multiple sub-systems working with the respective architects.
• Designed and proposed high-level n-tier architecture with each layer/tier providing a specific functionality - presentation, federated content access/middle tier (FCA), content and billing tiers.
• Designed FCA layer there by enabling access to different Content sources (Search Engines and Repositories) and hence new content could be integrated into the existing Products very easily. This Design was reviewed by many business units. ICE was used as the distributed platform and Spring was used to decouple the components from ICE. ICE - Internet communication engine was used for its versioning, scalable, highly efficient, cross platform capabilities. Spring extensions were designed and implemented to minimise the dependency on ICE.
• Implemented best practices around CI and "pre-commit" builds to detect and catch integration issues across different subsystems as soon as possible.

Jul 1996 – Jan 2003 · 6 yrs 6 mos

Jan 1996 – Jan 2006 · 10 yrs

Jun 1994 – Jun 1996 · 2 yrs