Projects
Four curated case studies
Selected projects showing problem framing, role ownership, key technical decisions, and measurable outcomes.
Pookie Platform (Startup)
Next.js
Firebase
FastAPI
API Integrations
Problem and Context
The platform required fast MVP delivery, reliable backend services, and scalable architecture decisions as product scope evolved.
Role and Ownership
Co-Founder & Tech Lead (Jan 2026 - Present), Software Engineer (Feb 2025 - Jan 2026)
Owned full-stack delivery and architecture decisions from MVP to production, translating product requirements into reliable Next.js and FastAPI implementations.
Key Technical Decisions
- Built and shipped MVP features across authentication, data models, and third-party API integrations.
- Implemented FastAPI backend services with validation and persistence layers for core workflows.
- Led system architecture and backend prioritisation with the Product & Operations Co-Founder.
- Mentored engineers and maintained quality through sprint cycles and review standards.
Outcomes
- Delivered production-ready backend capabilities supporting core platform workflows.
- Improved technical consistency and delivery reliability across sprint cycles.
- Established a scalable technical foundation for continued product growth.
Build Your Own Kafka
Go
TCP
Kafka wire protocol
Concurrent systems
Problem and Context
The broker needed to correctly parse and encode Kafka protocol frames while supporting multiple simultaneous client connections.
Role and Ownership
Systems Project
Implemented a Kafka broker in Go, owning protocol parsing and concurrency design decisions required for correct multi-client behavior.
Key Technical Decisions
- Implemented TCP socket binding and binary message parsing for Kafka requests and responses.
- Built goroutine-based concurrent client handling for serial and parallel request processing.
- Delivered DescribeTopicPartitions and ApiVersions APIs end-to-end.
- Started extending support toward Fetch and Produce APIs.
Outcomes
- Delivered a working broker that handles core Kafka API flows with protocol-correct encoding and decoding.
- Validated concurrency approach across multiple simultaneous connections.
- Established a robust foundation for full message consumption and production support.
Build Your Own Claude Code
TypeScript
LLM APIs
Tooling
Agentic systems
Problem and Context
The system needed reliable orchestration between LLM responses, tool dispatch, and iterative reasoning over multi-step tasks.
Role and Ownership
Systems Project
Designed and built an AI coding agent in TypeScript, owning the agent loop and tool-dispatch architecture for multi-step coding tasks.
Key Technical Decisions
- Implemented a core agentic loop for iterative reasoning and response handling.
- Integrated read, write, and bash tools with schema-driven advertisement and execution.
- Built direct LLM API communication and dispatcher logic across tool and model interactions.
Outcomes
- Delivered an autonomous coding agent that can read files, write outputs, and execute shell commands.
- Validated end-to-end orchestration across multi-step coding workflows.
- Created a reusable foundation for extending toolsets and agent capabilities.
AR Scavenger Hunt
React
Firebase
Firestore
react-three-arjs
Problem and Context
The platform needed real-time camera marker detection, persistent scoring, and reliable hosting for live event usage.
Role and Ownership
GDG ANU Project
Delivered a full-stack AR event platform, owning implementation decisions for AR marker detection and live Firestore leaderboard data.
Key Technical Decisions
- Integrated react-three-arjs for marker detection and 3D rendering.
- Implemented Firestore-backed persistent player scores and live leaderboard logic.
- Delivered frontend, backend, and hosting as a complete full-stack release.
Outcomes
- Enabled event participants to play through AR marker discovery with live score tracking.
- Supported engagement at GDG ANU event through real-time leaderboard visibility.
- Demonstrated full-stack delivery capability for time-bounded event requirements.