ASHWIN SHARMA

FROM CONSUMER PAYMENTS TO ECOMMERCE DELIVERY

PRINCIPAL PRODUCT MANAGER WORKING ACROSS PAYMENTS, SHIPPING AND LOGISTICS SOFTWARE, INTEGRATIONS, PUBLIC APIS, OPERATIONAL UX, AND PRODUCTS DESIGNED FOR AI AGENTS.

BUILDING FOR THE NEXT OPERATORPUBLIC API / COMMAND LINE / MODEL CONTEXT PROTOCOL GITHUB / ASHWINSHARMA-PM CONTRIBUTIONS / LAST 12 MONTHS / REFRESHING

ONE ORDER / MANY OPERATORSVIEW THE PRODUCT THROUGH THE PERSON OR SOFTWARE USING IT

01 ORDER RECEIVED

02 DELIVERY PROMISE

03 PARCEL DECISION

04 CARRIER SELECTION

05 LABEL + DISPATCH

06 TRACK + INFORM

07 EXCEPTIONS

THE COMPLETE PRODUCT SYSTEM

SELECTED PRODUCT SYSTEMSSHIPPED WORK / DIRECTION / PROTOTYPES / EVIDENCE

01 The integration layer behind ecommerce shipping Connected commerce platforms, order systems, and warehouse software to shipping services. SHIPPED / EVOLVING

SHIPPIT / 2023–2026 ECOMMERCE SHIPPING

PROBLEM: Retailers already run orders through commerce platforms, order-management systems, and warehouse tools. Shipping software has to meet the order where it already lives.
DECISION: Treat the integration layer as a product with its own contracts, mappings, events, failure states, and adoption experience.
WORK: Owned product direction across upstream integrations. Shipped webhook controls, event filtering, sensitive-data controls, custom-field mapping, and native automation links including Klaviyo and Zapier.
OUTCOME: Made shipping capabilities available inside the systems merchants already operate.

INTEGRATION PRODUCTSWEBHOOKSB2B ADOPTIONSYSTEM UX

02 A shipping API built for the next operator Shaping a public API that developers, integrated software, and AI agents can operate. DIRECTION / IN PROGRESS

SHIPPIT / CURRENT DEVELOPER PRODUCTS

PROBLEM: An API can carry critical work and still be hard to evolve. Weak versioning, identity, documentation, testing, and migration turn every improvement into negotiation with the past.
DECISION: Frame the public API as a product contract. Give REST, command-line tools, and Model Context Protocol tools distinct jobs on top of shared shipping capabilities.
WORK: Set direction for versioned contracts, scoped identity, structured errors, explicit states, safe next actions, idempotency, event loops, testing, diagnostics, migration, and governed agent actions.
OUTCOME: A product direction for software that can be operated by people, partners, coding agents, and approved business agents without giving each surface a different product.

API STRATEGYDEVELOPER EXPERIENCECLIMCPAI PRODUCT DIRECTION

03 Smarter parcel allocation for complex orders Designed an allocation algorithm that assigns order items to the right parcels before label creation and dispatch. SHIPPED

SHIPPIT / RECENT SHIPPING DECISION SYSTEMS

PROBLEM: An order is not always a parcel. Split items, different packaging, and warehouse reality make allocation both a decision problem and an operating task.
DECISION: Expose the parcel decision clearly, reduce repeated work, and make the system state understandable before booking.
WORK: Mapped the existing flow, designed the target interaction, and worked through the allocation rules and exceptions with engineering and operations.
OUTCOME: A more legible path from order contents to executable shipments.

WORKFLOW DESIGNDECISION LOGICPROTOTYPINGOPERATIONAL UX

04 Delivery promises before checkout Built a predictive delivery-estimate product so shoppers can understand when an order is likely to arrive before they buy. SHIPPED

SHIPPIT / 2024–2025 DELIVERY EXPERIENCE

PROBLEM: A shipping option without a credible arrival window pushes uncertainty into checkout.
DECISION: Expose a predictive estimate through reusable product and API surfaces, with fallback behaviour when confidence is limited.
WORK: Defined the product behaviour, API response, fallback logic, integration path, and partner adoption plan.
OUTCOME: A delivery promise that can appear before checkout and travel across merchant experiences.

PREDICTION PRODUCTSAPI DESIGNCHECKOUT UXADOPTION

05 Tracking that explains what happens next Redesigned a high-volume parcel-tracking surface around clarity, trust, and the next useful action. SHIPPED

SHIPPIT / RECENT POST-PURCHASE EXPERIENCE

PROBLEM: Tracking pages often expose carrier events without explaining what they mean to the person waiting.
DECISION: Design around customer questions: where the parcel is, whether it is on time, and what happens next.
WORK: Restructured status hierarchy, delivery context, event history, and exception communication.
OUTCOME: A clearer customer surface for routine progress and delivery uncertainty.

CONSUMER UXINFORMATION DESIGNSERVICE STATESTRUST

06 The mobile payment path from discovery to outcome Led the payment path inside Paytm's 70M+ monthly transacting-user super app. SHIPPED

PAYTM / JAN 2021–JUL 2023 MOBILE PAYMENTS

PROBLEM: A payment can fail before money moves. People must find the right recipient, verify who they are paying, choose a payment method, authorise securely, and understand what happened next.
DECISION: Design one confidence path: prioritise repeat payees, make search fast, show enough identity to prevent mistakes, and keep payment and outcome states clear.
WORK: Led product work across mobile-number and UPI-ID discovery, contact search, recipient ranking, bank and card integrations, amount entry, authorisation, success, failure, and repeat payments. Used behaviour data to redesign discovery: 75% of visitors attempted to search, repeat-payment success was strongest, and first-time-payment success was weakest.
OUTCOME: Turned a fragmented set of payment decisions into one mobile flow built for speed, confidence, and repeat use.

UPIMOBILE PAYMENTSFUNNEL DESIGNIDENTITY + TRUSTPRODUCT ANALYTICSTRANSACTION STATES

07 Payments with identity, context, and history Designed Paytm Chat payments for a product used by 25M+ people each week. SHIPPED

PAYTM / JAN 2021–JUL 2023 CONSUMER PAYMENTS

PROBLEM: A transaction list confirms that money moved. It loses the person, purpose, conversation, and next action around that payment.
DECISION: Organise payment history around verified payee identity and a persistent one-to-one channel.
WORK: Led product work across verified payee details, chat-based payments, shared attachments, bill splitting, reminders, repeat payments, search, and contextual notifications.
OUTCOME: Made payments easier to recognise, discuss, find, and repeat at consumer scale.

CONSUMER PRODUCTPAYMENTSIDENTITYINFORMATION DESIGNREPEAT USE

08 A code-aware product teammate inside Slack Built an internal assistant that answers how shipping products work from a living view of the codebase. PROTOTYPE / IN USE

SHIPPIT / 2026 AI PRODUCT TOOLS

PROBLEM: Product knowledge fragments across documentation, conversations, and implementation detail. The answer changes as the product changes.
DECISION: Bring code-backed product answers into the communication surface teams already use.
WORK: Designed and built the product concept, retrieval path, response shape, and Slack experience.
OUTCOME: A working example of AI reducing the distance between a product question and grounded product knowledge.

AI PRODUCTKNOWLEDGE SYSTEMSPROTOTYPINGSLACK UX

SELECTED SIGNALSSCALE / RANGE / CURRENT LEVEL

25M+ WEEKLY ACTIVE USERS CONSUMER PAYMENTS PRODUCT ~27 PRODUCT RELEASES ONE YEAR OF ECOMMERCE SHIPPING 3 YEARS SHIPPING + LOGISTICS BUILDING AT SHIPPIT 3 YEARS CONSUMER PAYMENTS JAN 2021–JUL 2023 AT PAYTM

WRITINGSHIPPING / PAYMENTS / MOBILE PRODUCT / CRAFT

Mapping a year of shipping product work on the journey How roughly 27 releases connect across an ecommerce shipping system. ECOMMERCE SHIPPING Building P2P payments via mobile number The product work behind a simpler mobile payment flow. CONSUMER PAYMENTS The challenge of designing for mobile apps Home, traffic, and UX inside a high-scale mobile product. MOBILE PRODUCT DESIGN The Craft of Working with Designers Three practices for making product and design work better together. PRODUCT CRAFT Paytm Chat - An easier, more organised way to make & store your payments Identity, context, and history around peer-to-peer payments. CONSUMER PAYMENTS

OPERATING RANGEFROM MOVING MONEY TO MOVING PARCELS

PAYMENTS

CONSUMER TRANSACTIONS / MOBILE UX / GROWTH AT SCALE

SHIPPING

ORDER-TO-DELIVERY SOFTWARE / WAREHOUSE + CUSTOMER UX

PLATFORMS

COMMERCE INTEGRATIONS / PUBLIC APIS / WEBHOOKS / DEVELOPER EXPERIENCE

AI PRODUCTS

CODE-AWARE TOOLS / CLI / MCP / GOVERNED AGENT ACTIONS

CURRENTLY BUILDING ECOMMERCE SHIPPING SOFTWARE FOR PEOPLE, INTEGRATED SYSTEMS, DEVELOPERS, AND AI AGENTS.

What makes Ashwin a Principal-level IC?

ABOUT ASHWIN

The work crosses product strategy, operational UX, decision logic, integrations, public APIs, developer experience, and AI product direction. The common thread is not ownership of more features. It is making a complex product system easier to operate and easier to change.

What has he built in shipping and logistics?

ABOUT ASHWIN

Products across the path from commerce-system integration to delivery promise, parcel allocation, carrier booking, warehouse dispatch, tracking, events, and operational exceptions.

What has he built in payments?

ABOUT ASHWIN

End-to-end mobile payment flows across payee discovery, mobile numbers, UPI IDs, bank and card integrations, amount entry, authorisation, outcome states, and repeat use inside Paytm's 70M+ monthly transacting-user super app. Separately, identity, history, reminders, contextual notifications, and bill splitting for Paytm Chat, used by 25M+ people each week.

Can he work credibly with engineers?

ABOUT ASHWIN

The evidence sits in API contracts, webhook behaviour, allocation logic, system states, structured errors, identity, versioning, observability, migration, prototypes, and code-aware tools. He works at product-behaviour depth without pretending to be the architect or engineer.

What is the API, CLI, and MCP direction?

ABOUT ASHWIN

One set of governed shipping capabilities, expressed through the right surface. REST for stable integration contracts. A command line for inspection, testing, and coding agents. Model Context Protocol tools for permissioned discovery, explanation, simulation, and controlled action.

What should I inspect first?

ABOUT ASHWIN

Start with the integration layer for platform breadth, parcel allocation for workflow depth, the API and agent work for future direction, and Paytm payments for consumer scale.