Ideas are a start. I build the rest.

I'm Dhillon. I build mobile apps, web products, and AI tools that turn complicated workflows into something useful.

Explore my work

Selected work

Built, shipped, and still building.

Elevate AIMOBILE APP

Your coaching.
Remembered.

Spoken feedbackStructured knowledgeA personal AI coach
CAPTURE. RECALL. APPLY.Product workflow

Elevate AI

Make every coaching session count.

In development

Spoken coaching feedback becomes organized notes, personal guidance, and a growing memory an athlete can return to.

Inside the build

The problem

Useful coaching advice gets lost between sessions. Athletes need a way to recall what they were told and apply it at the next practice.

What I built

The mobile app and backend connect voice capture, transcription, structured feedback, and a personal AI coach that retrieves the athlete's own coaching history.

Engineering decisions

  • Audio processing uses asynchronous webhooks so a long transcription does not block a request.
  • Athlete, coach, and academy accounts use separate permissions, with coaches reviewing notes before sending.
  • Search, chat, and weekly focus summaries draw from the same coaching history.

Built with

TypeScript, React Native, Expo, Supabase, AssemblyAI, and AI APIs.

Development status

In active development. The illustration above explains the workflow; it is not a screenshot of the app.

Jadex DevOSJADEX FUSION
request / draft pull request
01Scope the requestSlack / Jira
02Approve the planhuman review
03Run and test the changeisolated worker
04Review the diffdraft PR
Publication requires approval.
ENGINEERING WORKSPACEWorkflow overview

Jadex DevOS

From an engineering request to a tested change.

Internal pilot

I'm building DevOS as the next generation of Jadex Fusion's engineering workflow. It turns a scoped Slack or Jira request into a proposed change with a diff and test results for review.

Inside the build

The problem

An engineering request can start in a Slack thread, while requirements live in Jira and the change lives in a separate repository. Reviewers need to see how those pieces connect.

What I built

A workspace that carries the ticket and its acceptance criteria into an isolated agent run, then keeps the plan, diff, and test output together for review.

Engineering decisions

  • Jira holds the ticket and acceptance criteria. Postgres stores run state, approvals, usage, and audit events.
  • Workers run with repository scopes and budgets. A reviewer can inspect the diff and checks before approving a draft pull request.
  • Repository connections support GitHub and Bitbucket Cloud.

Built with

TypeScript, Node.js, Postgres, Git, and Docker.

Pilot status

The request-to-review workflow has been rehearsed with test integrations. Workspace access is limited to the internal pilot.

Inside the buildRideshare for New York CityPrelaunch

I co-founded MOVR and help build its rider and driver iPhone apps, shared backend, and web dashboard for dispatch and support.

Riders can request a fare quote, arrange pickup, and follow the trip on a live map. Drivers can manage availability and trips. MOVR plans to charge drivers a monthly membership in place of a per-ride platform commission.

The launch site shows both app experiences and lets riders and drivers join separate launch lists.

React Native · Expo · Next.js · Supabase · Google Routes API · Stripe

Curious about the problem.
Hands-on with the solution.

My work spans consumer apps, websites, and developer tools. I like connecting the whole product: the experience people see, the systems behind it, and the details that make it work.

My background brings together Information Systems at Fordham, software development at Jadex Consulting, and Division I tennis, where I served as team captain and competed at number one in singles and doubles.

Download résumé

Let's build
something useful.

Have a role, a project, or an idea worth exploring? I'd like to hear about it.

Connect on LinkedIn