Abhishek Kumar - Staff Android Engineer | ABHIKR
Skip to content
ABHIKR

Android engineering · Noida, India

Abhishek Kumar

Lead Android Engineer

Kotlin · Jetpack Compose · Architecture · Performance

I lead Android architecture for enterprise apps that
can’t afford to crash - logistics, healthcare, automotive
at global scale.

Explore engineering work Download résumé
Abhishek Kumar standing on a beach in the Andaman Islands

Android engineering · Noida, India

Abhishek Kumar

Staff Android Engineer

Kotlin · Jetpack Compose · Architecture · Performance

I build and lead Android work for enterprise apps in logistics, healthcare and automotive, the kind that get security-reviewed before they ship. Ten years in, I own the architecture standards, the startup and jank numbers, and the release gates that keep them from drifting.

Explore engineering work Download résumé
Current
IT Analyst & Lead Android Developer, TCS
Open to
Senior / Staff / Principal Android · India, UK, Europe, remote

I started on Android in 2016 and stayed. Depth on one platform is what lets me argue about module boundaries, trace a startup regression to its real cause, and tell a product team what a requirement will actually cost.

Most of my work is enterprise: apps in logistics, healthcare and automotive, where a crash is a support queue and an inaccessible screen is a procurement problem. I got WCAG-certified for mobile because that argument kept coming up and I wanted to stop guessing.

I’m based in Noida and open to Senior, Staff and Principal Android roles: India, UK, Europe or remote.

Abhishek Kumar

Abhishek Kumar. IT Analyst & Lead Android Developer, Tata Consultancy Services.

Certifications & education
WCAG 2.0 Accessibility for Mobile Apps
TCS, 2026
Design Fundamentals
TCS, 2025
B.Tech, Computer Science & Engineering
Uttarakhand Technical University, 2016
Open source 2026

AF-Bookings: an itinerary built to be read

Public repository · logtoabhikr/AF-Bookings-Case
Kotlin 2.3 Compose Material 3 Hilt Flow Coil
Constraint

Airline bookings are messy: polymorphic segments where a flight and a ground transfer occupy the same slot in a list, partial data, and a user who only wants to know when to leave for the airport.

Decision

Segments modelled as a sealed interface in a pure-Kotlin domain layer, so the compiler enforces exhaustive handling. Multi-module Clean Architecture keeps business logic away from the framework, and AssetManager is provided through Hilt specifically so no Context leaks into data.

Result

Stateless, preview-ready composables with custom-drawn timelines and parallax headers, driven by one StateFlow. Entirely public - read the architecture yourself.

Enterprise · automotive & logistics 2022–2026

Compose at scale, without a performance regression

PostNord, Tata Motors · via Tata Consultancy Services
Compose Perfetto MVVM Modularization Wear OS
Constraint

Multi-module enterprise codebases where a rewrite was never an option and cold start had drifted to 3.6 seconds. Compose adoption usually makes startup worse before it makes it better.

Decision

Incremental migration governed by architecture design reviews, with Perfetto traces as a release gate rather than a post-mortem tool. Baseline profiles and module boundaries decided from trace evidence, not preference.

Result

Cold start 3.6s → 1.6s. UI jank down 28%. 99.5%+ crash-free users sustained across releases.

Enterprise · healthcare & finance 2019–2022

Offline-first sync for apps used where signal isn’t

Horizon Blue and 10+ B2B / B2C apps · via SunTec
Room WorkManager Retrofit SSL Pinning R8
Constraint

Field and clinical users lose connectivity mid-task. Naive sync produced conflicting records and support tickets, while checkout flows were shedding users at the payment step.

Decision

Offline-first architecture with an explicit conflict policy and WorkManager-backed retry, plus a hardened network layer - SSL pinning and R8 obfuscation - because health and finance clients get security-reviewed before they get shipped.

Result

Data consistency up 35%. Checkout drop-off down 18%. API latency down 22%.

Also shipped

Public, older, still mine - and the rest of the client roster.

Aviation / travel
Air France - Flying Blue+

Owned Android development, deployment and delivery; added miles-redemption support on the booking form. MVVM over Compose/XML, Kotlin Multiplatform business logic, 4-of-14 Android team.

Explore engineering story →
Logistics
PostNord - Track & Send Parcels

Lead Android Developer. Tracking refresh +40%, accessibility ~10%→~90%, SE Parcels Customs Status shipped zero-defect in a single PR.

Explore engineering story →
Automotive
Tata Motors

Accessory Module built from scratch. 2-person Wear OS team shipped a Home screen with EV/PV details and car/lights connectivity.

Play Store · home & bath
Jaquar

Product catalogue app for Jaquar's bath and sanitaryware range; Flutter app built from scratch.

View on Play →
Architecture

Governed MVVM and Clean Architecture standards across multi-module Android codebases, and ran the design reviews that kept them from drifting.

People

Mentored and technically guided 5 Android engineers. Pull-request turnaround came down 30% as review habits changed.

Quality

Owned code review, automated testing and release quality gates. Regression defects down 25%.

Delivery

Designed and owned CI/CD on GitHub Actions, with static analysis and release workflows I maintain.

Product

Primary technical point of contact for stakeholders: translating business requirements into mobile solutions with product, backend and QA.
WCAG 2.0
Accessibility is part of the definition of done

Certified for mobile apps, and I test with TalkBack rather than assume. Uncommon for Android leads, and it keeps enterprise clients out of procurement trouble.

How I structure things

Dependencies point inward. Always.

Domain is pure Kotlin and knows nothing about Android. Data implements interfaces the domain declares. UI holds no logic worth testing twice.

It sounds academic until a project is three years old and still cheap to change.

UI
Stateless composables, one StateFlow per screen
Compose Material 3 Navigation
Domain
Pure Kotlin. No Android imports at all.
UseCases Sealed models Repository interfaces
Data
Implements what the domain declares
Room Retrofit Serialization
Measured, not claimed

Cold start,
cut in half.

A Compose migration across multi-module enterprise codebases, governed by Perfetto traces on every release rather than investigated afterwards.

3.6s → 1.6s
Cold start after Compose migration
−25%
Regression defects, via release gates
−18%
Checkout drop-off
−30%
Pull-request turnaround
Recognition
2025
Hackathon Winner & Service Award
Tata Consultancy Services
2022
Top Performer: Employee of the Month
SunTec
2020
Arctic Code Vault Contributor
GitHub

,.35)">Let’s build something that holds up.

For hiring teams

Senior, Staff or Principal Android

Architecture ownership, platform standards, mentoring. India, UK, Europe or remote.

Email me
For clients

Android audits & rescue work

Compose migration, cold-start and jank profiling, modularisation, CI/CD setup, accessibility compliance.

Start a project