01
Built the team
Grew and ran an Android team of 6 engineers and 4 QA at Paytm — hired, structured and led from zero. On-call rotation, incident response and postmortems were mine to run.
6 engineers · 4 QA
01Introduction
Immediate joinerPune, India
Nishant
Pardamwar
Lead Android Engineer
Payments · Fintech · Ticketing
Ten years building Android products that survive production — and the teams, standards and tooling that ship them.
- Experience
- 10+ years
- Leadership
- 6 eng · 4 QA
- Delivery
- Scrum, 4 verticals
- Biggest win
- Chat · 30M+ WAU
ScrollDown
01
30M+
Weekly active users
Carried by the Chat offline-first re-architecture
02
75%
Faster home load
Chat Home, via database and sync-layer redesign
03
10+
Years shipping Android
Consumer payments, fintech and ticketing
04
1.6k
StackOverflow reputation
Across Android, Compose and MCP articles
—Position
The hardest Android problems I have solved were never about the app. They were about the network being the enemy, about hardware I did not control, and about a team of six trying to ship faster than the org chart allowed.
02Profile
Ten years, three industries,
one through-line
B.E. Computer Science
North Maharashtra University, 2015
Ten years in Android, eight of them inside Paytm across consumer payments. I owned architecture, delivery and production operations for four consumer payments verticals — and the offline-first re-architecture of Chat that helped carry the app past 30M weekly actives.
Before that: ticketing and a business app running on third-party POS terminals, driving their barcode scanners and receipt printers. Before that: Arduino, GPS and GSM. The through-line is shipping software that works on hardware you don't control, for users who are not technical.
Lately I've been building the other half of the job — the agentic tooling that makes Android teams faster. MCP servers over ADB, Claude Code agents that turn a build into store assets, spec-driven development against local models.
We made Chat usable before every payment in Paytm. The app carried past 30M weekly actives on the back of that change.
01
Own the whole outcome
Architecture through release through on-call. I do not hand over a problem at the boundary of my comfort zone.
02
Make the team faster, not just the code
Standards other teams adopt beat heroics one team can sustain. CI gates, coverage, architecture docs.
03
Give the boring work to agents
Screenshot generation, device testing, release chores. Automate the handoffs that quietly eat a quarter.
04
Design for the worst network
Offline-first is not a feature flag — it is the architecture that made Chat usable before every payment, and carried the app to 30M+ weekly actives. On a payments app the bad network is the normal case, not the exception.
03Experience
Where I have actually
owned the outcome
Open a role to see scope, measured impact, and the stack it was built on.
Sep 2015 → Present
5 companies · 3 industries
Period
Role
Headline
Detail
Scope
- Built and led a team of 6 Android engineers and 4 QA from scratch.
- Partnered with a 4-person iOS team; worked across 15–20 engineers in 5+ teams.
- Owned architecture, delivery and production stability for four consumer payments verticals.
- Ran the full Scrum ceremony cycle and owned sprint commitments and delivery sign-off.
Impact
30M+ WAU
Re-architected Chat to an offline-first architecture, making it usable ahead of every payment in Paytm — the change that carried the app to 30M+ weekly active users.
−75% load time
Reduced Chat Home load time by 75% and background sync time by 68% through a database and sync-layer redesign.
+3% repeat txns
Refactored Scan & Pay, adding 3% to repeat user transactions.
+5% daily volume
Shipped the Received Payment screen, lifting daily transaction volume by 5%.
5+ teams
Drove org-wide adoption of Compose, Hilt, KMP and Compose Multiplatform across 5+ teams, and authored the architecture and quality standards other teams adopted.
58% coverage
Established CI/CD with test automation, code coverage, static analysis and binary-size reporting on every PR — raising Pre-Payment coverage to 58%.
−250KB
Drove the XML to Compose migration, reducing app size by roughly 250KB.
Stack
KotlinJetpack ComposeKMPHiltRoomCoroutinesOffline-FirstKtorCI/CD
04Leadership
Led teams and delivery,
not just wrote the code
Eight years at Paytm: built a team from zero, ran delivery for four product verticals, and set standards that other teams adopted. Roughly 30% of my work has been leadership rather than implementation.
- people led
- 10
- people led
- teams influenced
- 5+
- teams influenced
- verticals owned
- 4
- verticals owned
- coverage shipped
- 58%
- coverage shipped
02
Worked across the org, not just my team
Partnered with a 4-person iOS team and collaborated across 15–20 engineers in 5+ teams, sitting where Android met payments, promo, home, core platform and auth.
5+ teams · 15–20 engineers
03
Owned delivery, not just the code
Ran the full Scrum ceremony cycle for four product verticals — planning, standups, review, retrospectives — and owned sprint commitments and delivery sign-off.
4 verticals · full cycle
04
Set standards others adopted
Drove org-wide adoption of Compose, Hilt, KMP and Compose Multiplatform, and authored the architecture and quality standards other teams built on.
5+ teams adopted
05
Raised the engineering floor
Put test automation, code coverage, static analysis and binary-size reporting on every PR. Coverage on Pre-Payment went to 58% — a standard that outlived my team.
58% coverage on every PR
06
Knowledge shared, not hoarded
1.6k Stack Overflow reputation at ~101k reach, articles on Navigation3, MCP servers and Compose, plus open-source Android and AI tooling projects others build on.
1.6k rep · 101k reach
05AI & agentic
The half of the job that
did not exist a decade ago
Agentic work is not a side interest. It is how I removed whole categories of toil from release, device testing and developer workflow.
01
ADB MCP Server
Model Context Protocol
An MCP server that hands an LLM real Android devices: tap, swipe, screenshot, UI-hierarchy inspection.
- Agents drive and test real devices instead of emulators
- Replaces manual exploratory passes with scripted, repeatable runs
02
Engineering MCP Service
Internal platform
Connected LLMs to Jira, BitBucket and the engineering wiki so developers could query and act on project state in plain language.
- Automated developer workflows across the engineering org
- Shipped at Paytm under my ownership
03
Store Asset Agents
Claude Code
Agents and skills that take a build and auto-generate Play Store screenshot sets and promo videos, replacing a manual design handoff.
- Design handoff removed from the release critical path
- Spec-driven development against local models via Ollama and llama.cpp
The loop
Spec
Agent
Build
Device
Release
Write the spec, let an agent build it, then give that agent a real device to verify against. The bottleneck moves from typing to judgement — and judgement is the part worth spending senior time on.
Runs with
Claude Code, OpenCode, Ollama and llama.cpp — used together, with local models for anything that should not leave the machine.
06Open source
What I put back
into the commons
Navigation3, MCP servers and Compose are where I write most — the topics where the docs are thin and the production reality is the interesting part.
GitHub
Open-source Android & AI tooling
Android libraries, tooling and agentic utilities I maintain in public.
Browse repositories
StackOverflow
Writing on Navigation3, MCP servers and Compose
1.6k reputation at roughly 101k reach across Android, Compose and MCP.
Read answers
Practice
Spec-driven development with coding agents
Running Claude Code and OpenCode against a spec, with Ollama and llama.cpp for local models.
See how I work
07Skills
Ten years of stack,
sorted by what it is for
The tools turn over every eighteen months. The architecture instincts do not.
01
Languages & Android
- Kotlin
- Java
- Jetpack Compose
- Coroutines & Flow
- Media3 / ExoPlayer
02
Architecture
- MVVM
- MVI
- Clean Architecture
- Design Patterns
- Offline-First
03
Data, DI & networking
- Room
- Paging
- WorkManager
- Hilt / Dagger
- Koin
- Retrofit
- Ktor
- MQTT
- RxJava
04
Cross-platform
- Kotlin Multiplatform
- Compose Multiplatform
05
Testing & delivery
- TDD
- Unit & UI Testing
- Code Coverage
- CI/CD Pipelines
- Release Management
- Crashlytics
06
Operations
- Custom Metrics
- Production Monitoring
- On-Call Rotation
- Incident Response
- Postmortems
07
AI & agentic engineering
- MCP Servers
- Claude Code Agents
- Spec-Driven Development
- Ollama
- llama.cpp
08
Embedded & hardware
- Embedded Systems
- Arduino
- GPS
- Telematics
- POS Terminals
- Barcode Scanning
- Receipt Printing
09
Tools
- Gradle
- Git
- ADB
- Jira
- BitBucket
08Shipped apps
Side projects that earned
their own downloads
H&N Interactive is my independent studio — designed, built and maintained end to end.
09 — Contact
Let’s talk about
your Android problem.
Available immediately. A payments codebase that needs an owner, a team whose Android standards need raising, or a build that has become frightening — I would like to hear about it.
Direct
Elsewhere