Skip to content

About Tushar

From engineering to product & technology leadership.

I started my career as a software engineer and gradually moved into technical leadership, product analysis, architecture, consulting and engineering management.

Today, I work at the intersection of product and technology — helping businesses turn complex problems into practical products, scalable technology and effective engineering execution.

The journey

A career built across engineering, product and technology.

My career began in software engineering, working on enterprise applications and solving problems close to the code.

Over time, my role expanded beyond implementation. I moved into mobile engineering leadership, building teams and delivering products across Android and iOS. That experience taught me how engineering decisions, team capability and delivery discipline come together to create successful products.

I then moved closer to the product — working with enterprise stakeholders, understanding operational problems, defining product requirements and shaping platform capabilities.

From there, my work increasingly moved toward architecture, technology strategy, cross-functional leadership and consulting.

Today, as an independent Product & Technology Consultant, I bring those perspectives together — business problem, product, technology, architecture and engineering execution.

Career progression

  1. 01

    Software Engineering

  2. 02

    Mobile Engineering

  3. 03

    Engineering Leadership

  4. 04

    Product Analysis

  5. 05

    Architecture & Technology

  6. 06

    Product & Technology Leadership

  7. 07

    Independent Consulting

Each step added another perspective to the way I approach technology problems — from how something is built to why it should be built, who it serves and how a team can deliver it effectively.

How I think

Start with the problem, not the technology.

Technology is only useful when it solves the right problem.

I try to understand the business context first — what is changing, who is affected, what the customer needs and what outcome the business is trying to achieve.

From there, I work through the product and technology decisions: what should be built, what should not be built, how it should be architected and what the engineering team needs to execute it well.

The goal isn't to choose the most sophisticated solution. It's to choose a solution that is appropriate for the problem, practical to build and capable of evolving as the business grows.

What I bring

  1. 01

    Product Perspective

    Translating business and customer problems into product direction, requirements, priorities and practical roadmaps.

  2. 02

    Technology Perspective

    Making architecture and technology decisions with scalability, maintainability, integration and long-term product needs in mind.

  3. 03

    Engineering Leadership

    Building and guiding engineering teams, improving delivery practices and creating the conditions for teams to execute effectively.

  4. 04

    Customer & Stakeholder Perspective

    Working directly with stakeholders to understand challenges, communicate trade-offs and align product and technology decisions with business objectives.

Perspective

Experience changes how you look at problems.

  1. 01

    Technology decisions are business decisions.

    Architecture, infrastructure and engineering choices eventually affect cost, speed, risk and the ability to evolve a product.

  2. 02

    Product decisions need technical context.

    What looks simple from a product perspective can have significant technical implications. Understanding both sides leads to better trade-offs.

  3. 03

    Teams matter as much as technology.

    A good architecture still needs a team that can understand it, build it, operate it and evolve it.

Let's talk

Have a product or technology challenge?

Whether you're shaping a new product, rethinking an existing platform or figuring out how technology can support the next stage of growth, I'd be happy to talk.