Software Engineer building reliable backend systems.

Problem

Most engineers consume identity infrastructure (Auth0, Okta, Cognito) but never build it. I wanted to understand the hard parts — multi-tenancy, RBAC, token lifecycle — by building the thing rather than the thing that uses it.

Approach

• Backend authentication and authorization services with tenant isolation and role-based access control
• Admin console for managing tenants, roles, and permissions across the platform
• Designed as a self-directed system-design exercise, prioritizing the infrastructure patterns real IAM providers solve

Problem

Wanted a fully offline mobile game with a real AI opponent — not a toy demo — structured the way a production Android app should be, with clean module boundaries and testable game logic.

Approach

• Multi-module Gradle architecture (:core-game, :core-ai, :data, :app) separating game rules, AI, persistence, and UI
• MVI pattern for predictable, testable state management
• Room for local persistence, Hilt for dependency injection
• Three AI difficulty levels with distinct decision strategies