I'm an Android & Backend Developer who ships end-to-end systems — secure Spring Boot APIs on the backend, native Jetpack Compose apps on the frontend. I care about getting the architecture right, not just getting it to work.
What I bring to a team:
- Architecting JWT & OAuth2 secured backend services from the ground up
- Building native Android apps with MVVM, Clean Architecture, and Jetpack Compose
- Integrating AI/LLM capabilities into production applications
- Writing clean, testable code — proper layering, meaningful tests, no shortcuts
Full-stack AI-powered note-taking platform — Spring Boot + Android
End-to-end notes platform where AI generates summaries, flashcards, and smart tags from user content. Every endpoint is JWT-secured, every user's data is fully isolated, and performance-critical paths are Redis-cached.
| What I Built | Tech Used |
|---|---|
| RESTful API with JWT authentication & refresh tokens | Spring Boot, Spring Security |
| AI-powered note processing (summaries, flashcards, tags) | Google Gemini API |
| Redis caching layer for performance optimization | Redis, Spring Cache |
| Native Android app with offline-first architecture | Kotlin, Jetpack Compose, Room DB |
| Comprehensive unit & integration test suite | JUnit 5, Mockito |
Stack: Spring Boot Spring Security JWT PostgreSQL Redis Android Jetpack Compose Google Gemini
Secure healthcare backend — Multi-provider OAuth2 authentication
Healthcare backend with multi-provider OAuth2 integration. Users authenticate via Google or GitHub alongside traditional JWT login — designed with a clean foundation for future role-based access control.
| What I Built | Tech Used |
|---|---|
| Multi-provider OAuth2 login (Google, GitHub) | Spring Security OAuth2 Client |
| JWT-based authentication with token management | Spring Security, JWT |
| Structured relational schema for healthcare entities | PostgreSQL, JPA/Hibernate |
| Clean REST API with dual auth strategy (JWT + OAuth2) | Spring Boot |
Stack: Spring Boot Spring Security JWT OAuth2 PostgreSQL REST APIs
Zero-knowledge encrypted vault — Client-side AES-256 GCM + Firebase sync
All encryption happens on-device before anything touches the network. Passwords are encrypted with AES-256 GCM, keys are derived via PBKDF2 from the master password, and only ciphertext is stored in Firebase — zero plaintext ever leaves the device.
| What I Built | Tech Used |
|---|---|
| Client-side AES-256 GCM encryption engine | Java Crypto, Android Keystore |
| PBKDF2 key derivation from master password | PBKDF2WithHmacSHA256 |
| Encrypted cloud storage — only ciphertext synced | Firebase Firestore |
| Zero-knowledge architecture — server never sees plaintext | Kotlin |
Stack: Android Kotlin AES-256 GCM PBKDF2 Firebase
Offline-first Android apps — MVVM + Room DB
News App: REST API integration with Room DB caching — content loads instantly, even offline.
Expense Tracker: Local-first financial tracker with income/expense categorization and visual breakdowns.
Stack: Android Kotlin Room DB Retrofit MVVM Material Design
| Domain | Technologies |
|---|---|
| Languages |     |
| Android |    |
| Backend |    |
| Security |    |
| Databases & Tools |        |
- 🏗️ System Design & Backend Architecture — scaling Spring Boot services
- 🤖 AI Integrations — building LLM-powered features into production apps
- 🔐 Advanced Auth Flows — OAuth2 + JWT refresh token rotation
- 📱 Clean Architecture Android — modularizing with domain-driven design