I like owning a feature from end to end — the Compose screen, the API it calls, and the table underneath it.
As an SDE intern at Fin Tradify I worked on two production Android apps on Google Play: twelve Compose screens, eighteen API integrations, an offline-first data layer with Room, and about 15% fewer crashes by the time I left. These days I lead the development team at CSI VIT-AP, where our app, CSI Events, runs the chapter's hackathons.
| Project | What it is | Built with |
|---|---|---|
| CSI Events · API | The event app CSI VIT-AP runs its hackathons on: teams join with a code, judges score from their phones, results go live when the organizer publishes them. | Kotlin, Compose, Spring Boot, PostgreSQL |
| Patient Management | Five Spring Boot services behind a JWT gateway. Kafka carries events to analytics, billing talks gRPC, and AWS CDK deploys it all to ECS Fargate. | Spring Cloud, Kafka, gRPC, AWS |
| Fact Knowledge Layer | Reads PDFs, pulls out facts with an LLM along with the exact quote behind each one, and flags where documents agree or contradict. | Java, LLM |
| Order & Position Engine | Two services for streaming orders and real-time net positions — idempotent, throttled and safe under concurrency. | Spring Boot |
| Tomato | A food-delivery platform built at a hackathon: Android app and backend in one push. | Kotlin, Compose, Spring Boot |
Android — Kotlin, Jetpack Compose, MVVM, Hilt, Retrofit, Room, Coroutines and Flow, Firebase
Backend — Java, Spring Boot, Spring Cloud Gateway, Spring Security, Kafka, gRPC, PostgreSQL
Cloud — AWS (CDK, ECS Fargate, RDS, MSK), Docker, Kubernetes, GitHub Actions, LocalStack
Practice — clean architecture, REST and event-driven design, code review, JUnit
