Arya profile portrait

Ashwani Arya

Product engineer, full-stack. I take products from prototyping to productionizing to finding and solving problems through them. React, Next.js and Three.js on the surface; Node, Express, FastAPI, Postgres and AWS underneath.

Three-time founding engineer: live video at ~100k sessions a day, $0 → $10k MRR, an AI copilot at ~30k conversations a month. Currently at AIclicks, a SaaS analytics platform, building LLM features across UI/UX, frontend and backend.

Remote from Bangalore, overlapping US and EU hours. Open to contracts and full-time product engineering roles.

View work

In production

Numbers from the founding-engineer work at GetBujo. Each one is unpacked in the case study below.

  • Live video sessions

    ~100k/day

    Wingman widget embedded in server-rendered retailer storefronts, calls surviving full-page navigations.
  • Revenue ramp

    $0 → $10,000 MRR

    First engineer on the product, from nothing shipped to paying retailers on a multi-tenant platform.
  • AI conversations

    ~30k/month

    About 80 sales agents on an iframe copilot inside Sprinklr, backed by an in-house AI service on AWS.
  • Copilot revenue line

    ~$20k MRR

    REST to WebSocket migration in four calendar days, cited as a factor in winning a long-term LG US contract.

Selected work

Live things I designed, built and deployed myself, then kept running. Open any of them; every one is in production.

Experience

Where I go deep: services and data models that hold up in production, contracts that do not break silently, and interfaces that stay fast under real load.

  • Backend development

    Node and FastAPI services, PostgreSQL and MongoDB data modeling, multi-tenant boundaries, and payment flows built to survive real-world failure modes.

  • API and contract development

    REST and WebSocket boundaries, schema-first thinking, and client typings so frontend and backend evolve without silent breakage.

  • Performance optimization

    Virtualized tables, bundle budgets, connection churn under load, and GPU profiling so heavy views and 3D scenes stay smooth in the field.

  • Data-intensive frontends

    Large datasets, streaming updates, and interactive dashboards where rendering and network strategy matter as much as pixels.

  • Frontend architecture

    Layering, state boundaries, and feature ownership so products stay maintainable as teams and traffic grow.

  • Cross-platform development

    Web, native, and embedded webviews. Shared patterns and tooling so one mental model travels across surfaces.

  • Reusable component design

    Design tokens, composable components, and Storybook as living documentation, so teams ship faster with fewer regressions.

Case studies

Longer write-ups of production work: a founding-engineer engagement spanning live video at scale, an AI copilot, and a browser extension, with the numbers each one moved.

Technology stack

What I reach for first: TypeScript, React and Next.js on the surface; Node, Express and FastAPI for services; PostgreSQL, Prisma and MongoDB for data; Docker, Nginx and AWS to run it. GSAP and Three.js when motion or 3D earns its place.

  • Systems

    • Payment Systems

    • BFF (Backend for Frontend)

    • Investment Management System

    • Design Systems

    • RESTful APIs

  • Programming Languages

    • JavaScript

    • TypeScript

    • Java

  • Frameworks

    • ReactJS

    • React Native

    • Vite

    • NextJS

    • ExpressJS

    • Spring Boot (JPA)

  • Frontend

    • Vanilla JS

    • Web APIs

    • Material UI

    • Tailwind CSS

    • Shadcn UI

  • Backend

    • NodeJS

  • Tools

    • Babel

    • Docker

    • Apache

    • PM2

    • Nginx

    • Git

    • GitHub

    • Bash

  • Databases

    • MongoDB

    • Mongoose ORM

    • PostgreSQL

    • Prisma

  • Platforms

    • AWS

    • Vercel Functions

    • CDN

  • Library

    • Jest

    • React Testing Library

    • Redux

    • Context API

    • Radio (in-house Pub/Sub engine)

    • Socket.io

  • CI/CD

    • GitHub Actions

    • Vercel Deployment

Contact

Reach out for collaborations, product work, architectural designing, or a quick hello—I am remote-first. I would love to hear from you.