Applied AI Product Engineer

I build AI-native products end to end—from model adaptation and low-latency inference to native apps, backend systems, testing, and production release.

Nearly five years in production engineering, including 0→1 products and consumer systems used by millions.

On-device LLMs · Native iOS, macOS & Android · Production systems

Portrait of Gunveer Sandhu seated at his desk
Model behavior → native product → production release

SpellType

Local autocomplete that keeps up with typing.

I built and shipped a production macOS autocomplete system around OLMo 2 1B—adapted, evaluated, optimized, signed, notarized, and delivered end to end.

Typing context
Token healing
Persistent KV cache
OLMo 2 1B · 8-bit
Inline suggestion

Blinded 200-case evaluation · LoRA across all 16 transformer layers

SUB-200 MS
Median suggestion latency
10+ APPS
Continuous inline autocomplete
1,680
Curated training examples
~3:1
Preference in a blinded evaluation

Choose the right kind of intelligence.

Applied AI is not about putting a model everywhere. It is knowing which parts must stay deterministic, where generation adds value, and how the whole product remains dependable.

Cosmicly

Deterministic computation + production LLM workflows

Built end to end across Flutter iOS and Android clients, Supabase and PostgreSQL backend services, and Vertex AI and Gemini workflows, with authentication, realtime data, subscriptions, push notifications, localization, and production delivery.

  1. Astronomy engine
  2. Structured context
  3. Model routing
  4. Validated output

Region-aware fallbacks · bounded retries · malformed-JSON recovery · token/cost observability

NoRing

Rules-first protection inside Android’s five-second window

I designed explicit precedence for calls and messages, keeping decisions local, reviewable, and fail-safe.

  1. User rules
  2. Contacts
  3. Outgoing history
  4. Learned number patterns
  5. Allow / silence

5-second call-screening window · 5-minute repeat-caller safeguard · 10 SMS categories

Production is part of the product.

Before applied AI, I learned to ship inside platform constraints, sensitive workflows, consumer scale, security reviews, partial failures, and release pressure. That foundation still shapes every system I build.

Olly · 2023—2025

Shipping sensitive native healthcare workflows from 0→1.

As one of two frontend engineers in a five-person international team, I owned iOS delivery through App Store launch and sustained releases.

Read the Olly case study
  1. SwiftUI + UIKitNative client architecture
  2. Apple HealthConnected fertility tracking
  3. English · French · SpanishLocalization across three languages
  4. App Store launchLaunch and sustained releases
  1. 202192% → 98%crash-free usage
  2. 202210 dayssecurity reassessment
  3. 20235 appsarchitecture · reliability · releases

RailYatri & IntrCity · 2021—2023

Hardening consumer Android products used by millions.

Across five production apps, I modernized architecture, improved reliability, remediated security findings, and led two developers while remaining hands-on.

Read the RailYatri case study

GreyMonk

Built substantial TypeScript and React frontend work for engineering metrics, AI-generated insights, team and project views, and delivery signals. Partnered with backend engineers on API contracts, data models, and product behavior.

Mosaic

Resolved recurring ANRs, crashes, runtime errors, slow interactions, and reliability failures. Rebuilt several ANR-prone WebView paths as native Flutter flows and added Firebase production instrumentation and analytics.

Experience

A career built around ownership under constraint.

  1. Founder & Product Engineer

    Applied AI & Consumer Products

    Building SpellType, Cosmicly, and NoRing—products spanning model adaptation and evaluation, on-device inference, production LLM workflows, native clients, backend systems, testing, and release delivery.

  2. Product Engineer

    Shuru Technologies

    Delivered 0→1 native iOS healthcare workflows, data-heavy TypeScript and React product experiences, and production reliability work in a Flutter point-of-sale application.

  3. Mobile Application Developer (Android)

    RailYatri (Stelling Technologies)

    Worked across five production Android applications on architecture modernization, reliability, security remediation, testing, releases, and hands-on technical leadership.

2017–2021

Bachelor of Technology in Computer Science EngineeringJaypee Institute of Information Technology (JIIT), Noida

“Consumer scale and security, sensitive native workflows, then AI-native products spanning models, applications, infrastructure, and release.”

How I work

Judgment across the whole system.

Keep deterministic logic deterministic.
Use models where interpretation adds value, while keeping calculations, precedence, and product rules explicit and testable.
Design for the runtime constraint.
Continuous typing, a five-second screening window, process recreation, partial failures, and sensitive multi-step state all shape the architecture before they become edge cases.
Treat reliability as product behavior.
Cancellation, fallbacks, observability, crash reduction, security remediation, automated tests, and fail-safe paths determine what users actually experience.
Own the route to release.
Carry the work through backend boundaries, testing, CI/CD, signing, notarization, store delivery, and production updates instead of stopping at a working prototype.

Let’s build something that has to work.

I’m based in India and open to relocation and suitable global-remote roles where applied AI, native product engineering, and end-to-end ownership meet.