Frontend & Mobile Engineer

Selected work / 2022—2026

I build product interfaces that hold up when the system gets complicated.

React and React Native engineer with 4+ years of experience across real-time applications, native Android integrations, payments, telephony, operational tooling, and client performance.

150K+

daily active users

Real-time mobile products at Jumbo

900K/mo

payment events

In-house payment infrastructure at Jumbo

99.3%

crash-free rate

Field-operations application at Royal Brothers

35% / 42%

JS bundle / app size reduction

Client performance work at Royal Brothers

One product, multiple engineering surfaces.

A frontend center. A wider field of view.

Application

Complex client state. End-to-end product delivery.

React Native product ownership

Native Android

The platform behavior beneath the interface.

Telephony & lifecycle integrations

Services

Features that cross the client boundary.

Payments & real-time events

Web

Operational interfaces built for real conditions.

Offline-first architecture

Public packages + private professional contributions

01

Selected work

Production ownership. Explicit decisions. Real constraints.
01 /Production
Mobile / Native / Real-time

HiRobin — AI calling assistant

Owning a React Native product across mobile architecture, Android telephony, call forwarding, payments, real-time chat, and VoIP foundations.

A calling assistant crosses mobile UI, Android platform behavior, telecom workflows, payments, and live server events. The client has to make those systems understandable to the user.

Outcome

Lead mobile contribution to a product with 1.1M installs and approximately 296K monthly active users. September 2026 snapshot.

  • React Native
  • TypeScript
  • Android native modules
  • WebSockets
  • Payments
  • Telephony
Read the case study
HiRobin / Product boundaries
InterfaceReact Native applicationOnboarding · Conversations · Subscriptions
PlatformNative AndroidDialer & telephony
Permissions & lifecycle
ServicesLive product stateEvents & chat
Payments & calling
One user journey. Multiple state owners.
Sanitized responsibility map. Shows integration surfaces, not proprietary architecture.
02 /In progress
Web / Offline / Geospatial

Operations software for unreliable networks

A React and TypeScript field-operations console designed around map-heavy workflows, offline writes, reconnect synchronization, and constrained devices.

Operational software cannot assume a stable connection or a clean linear workflow. The interface has to preserve user intent and make synchronization state understandable.

Current state

An evolving architecture record. Implementation and production validation are still in progress.

  • React
  • TypeScript
  • Leaflet
  • Zustand
  • TanStack Query
  • IndexedDB
  • WebSockets
View architecture and progress
Operations / Proposed write lifecycleIn progress
User updates a taskNetwork unavailable
  1. Save the intent locallyPersist operation in IndexedDB
    Queued
  2. Reconnect & reconcileCompare the server revision
    Syncing
  3. Confirm or surface a conflictKeep the operator in control
    Review
Architecture study: queued work stays visible until the server confirms it.
03 /Open source
Developer tools / Package safety

Safer package execution and installation

A local-first audit pipeline that inspects npm packages before execution or installation and makes the approval decision explicit.

Package runners combine retrieval and execution into one convenient step. Latch changes the order: resolve, verify, inspect, evaluate policy, then run only after approval.

Outcome

Three published packages. One shared inspection and policy engine.

  • TypeScript
  • Registry resolution
  • Integrity verification
  • Static analysis
  • Policy engine
  • CLI / CI
See the audit model
Latch / Inspect · Decide · RunLocal-first

A trust boundary, before execution.

  1. 01ResolveExact version
  2. 02VerifyArtifact integrity
  3. 03InspectStatic risk signals
  4. 04DecidePolicy & approval
Execute only when allowed

latch-core latchx / latchpm

Static risk signals inform a decision. They are not a malware verdict or a sandbox.
02

Small tools. Explicit systems.

All open source

I turn repeated client-platform problems into reusable tools. Startup and lifecycle are two places where hidden state becomes a very visible failure.

rn-bootloader

Published · v0.1.1

Give startup work an explicit order.

Phase-based React Native startup with blocking and non-blocking tasks, retry, timeout, and readiness controls.

react-native-appcycle

Published · v0.2.1

Make application lifecycle visible.

Foreground/background awareness, React-powered overlays, and native Android entry points in one lifecycle API.

03

Where I’ve built

More about me
Jan 2026 — Present

HiRobin

SDE 2 / Founding Engineer

Core React Native ownership for an AI phone assistant, spanning Android telephony, call forwarding, subscriptions, payments, real-time chat, and VoIP foundations.

Sep 2025 — Jan 2026

Buzzworthy

SDE 2

Financial-product workflows, beehive operations modules, product-discovery tooling, and maintenance of IBL Bank’s volunteering portal.

Dec 2024 — Sep 2025

Jumbo Gaming

SDE 1

Real-time React Native games for 150K+ daily active users, payment infrastructure processing approximately 900K monthly transactions, and internal Next.js analytics.

Sep 2022 — Dec 2024

Royal Brothers

Software Engineer 1 / React Native Developer

Owned field-operations software across React Native and React, improving reliability, bundle and application size, performance, and operational workflows.

04

How I work

01 /

Make state visible.

Explicit states, transitions, and ownership. From boot phases and background lifecycle to payment status and offline queues.

02 /

Design around failure.

Retry, timeout, network loss, and platform restrictions are inputs to the design. They belong in the first conversation.

03 /

Measure the client.

Smaller bundles. More reliable sessions. Responsive interactions. Performance work should end in an observable change.

Currently building deeper frontend systems

Extending my production mobile experience into offline-first workflows, geospatial interfaces, and document intelligence. Getting better at building interfaces that explain and control complex systems.

Have a difficult product problem?

Let’s make it
work in the real world.

I’m interested in roles where I can own meaningful frontend and mobile systems, and build with people who care about the details.

Open to SDE-2 / Senior Frontend & React Native roles

Bengaluru, India
Bengaluru, India-wide & suitable remote opportunities