Archit Gupta

I’m a Senior Android Engineer with 8+ years of experience building and scaling consumer-facing mobile products across AI-powered writing assistance, social media, payments, and fintech.

Most recently, I worked as an SDE-3 at QuillBot, where I was one of the founding engineers for its first Android app. I helped ideate, architect, and build the product from the ground up across three major experiences: the main app, Android keyboard, and floating assistant. Within two years of launch, the product scaled to 8M+ downloads, 1M MAU, $3M ARR, and 80% daily retention.

I owned the QuillBot Android keyboard and worked on some particularly challenging Android problems, including IME development, isolated/multi-process architecture, AIDL and IPC, multi-process state management, Direct Boot, authentication and concurrency. I also built the client-side experiences that brought QuillBot’s AI-powered grammar checking, paraphrasing, and GenAI capabilities directly to users at the point of writing through backend APIs.

More recently, AI has also become an important part of how I develop software. I use tools such as Cursor, Claude, and ChatGPT through structured agentic workflows for codebase reconnaissance, implementation planning, development, debugging, refactoring, and review. I’m particularly interested in context engineering and turning recurring engineering knowledge and conventions into reusable agent rules and skills, while retaining human ownership of architecture, product decisions, correctness, and production quality.

Before QuillBot, I worked on ShareChat’s Android app at 50M+ DAU scale, contributing to revenue-generating products, feed and video experiences, performance improvements, architecture modernization, and A/B experiments. Earlier in my career, I worked on Android products at Paytm and Airtel Payments Bank, giving me experience across both large-scale consumer applications and payment/fintech systems.

My strongest areas are native Android, Kotlin, application architecture, concurrency, performance, complex platform-level integrations, and end-to-end product ownership. I enjoy problems where I can go beyond implementing a feature—understanding the system deeply, making architectural decisions, solving difficult engineering problems, and taking features all the way to production.

For my next opportunity, I’m primarily interested in Senior, Staff, or Lead-level Android/mobile engineering roles where I can combine deep hands-on engineering with architecture and technical ownership. I’m especially excited by teams building high-scale consumer products and by organizations that are thoughtfully incorporating AI into both their products and software-development workflows.