Twelve-plus years from Android apps to the systems around them — and the engineers who build both.

I didn’t start my career by joining a company — I started by building one. In 2012, fresh out of my CSE degree in Dhaka, I founded Power GP BD and led it for six years. We shipped more than 100 Android applications across enterprise, B2B and consumer verticals, and earned two awards from the Facebook Startup Program along the way. One of our apps, a multimedia product called Theatre, crossed 500,000 downloads on the Play Store. Running a company taught me the thing no job could: how to own an outcome completely.

Then I went deep on craft — and the problems started getting bigger than the app. At Kutumbita I designed and built Kinship.ai entirely on my own: my first complete system, not just an Android client — real-time messaging over Socket.io, offline-first storage and background sync for factory workers who barely had a network, from architecture through Play Store release. At Samsung R&D, as Lead Software Engineer II, the system spanned devices: health-tracking apps in the Samsung Health ecosystem, wearable companions syncing losslessly over BLE to watches running a different OS (Tizen), server-side sync behind it all — and feature work in the SmartThings iOS app.

In 2022 I joined Plentina, a US fintech bringing Buy-Now-Pay-Later to the Philippines and Vietnam. I led the Android side of a system where failure has a price — payment gateway integrations, Kotlin Flow state management, and a full migration to Jetpack Compose while Compose was still in beta.

Then came Avetics Global and the most connected system yet: I owned the ground-up rewrite of two production Android apps that command live aircraft — multi-module Compose architecture, Hilt, a real-time telemetry layer over custom TCP sockets, a vendor video pipeline, and computer vision that lets a drone land on a QR code — and set the architecture standards for the six-person Android team I mentored. The domain is drones; the engineering is the same discipline any serious connected product needs.

That’s the arc: an Android engineer, then a senior mobile engineer, then someone handed steadily harder connected-system problems — devices, protocols, video, hardware — until software & systems engineer became the honest job description. Android is still where I go deepest. The systems around it are what I build.

And because founding never really leaves you, I’ve gone back to it from the other side: as an equity CTO for early-stage startups, building complete products for founders who can’t yet afford a technical team — and as a trainer, selected by Google, to 100+ developers across Asia.

What’s next? Three doors are open: a senior/staff/lead engineering role anywhere in the world, building your product as a client, or partnering as your startup’s equity CTO. Pick one — the CV is below either way.