Final-year Computing (Co-op) student building systems that turn unstructured, unreliable inputs into verified, structured output — across Python, TypeScript, AWS, and modern LLM tooling.
Real metrics from production systems I've designed and built.
Three co-op terms across data engineering, DevOps, and full-stack — currently building AI research automation at Adknown.
Sole developer of a continuous AI research automation platform preparing for public release — it scans codebases and generates dispositions with recommended fixes grounded in current external research.
Owned database performance and the CI/CD and infrastructure layer for a multi-service architecture, cutting query times and release times substantially.
Built and refined application features inside an active production codebase alongside senior developers.
Supported IT and security operations — access management, system checks, and hands-on evaluation of security tooling.
Selected projects that showcase my approach to building scalable, user-focused software.
Student housing, finally done right — now live at findyourcribb.com
A full-stack student productivity workspace for planning, tracking, and reminders
A canvas-based aquarium with entity behaviors, built into this portfolio
Academic Planning & Workload Visualization Platform
Analyzing recreational facility access across Canada to identify underserved regions
A carpooling platform designed for university students
A beautiful weather app with real-time data and glassmorphism design
Building a strong foundation in computer science while gaining real-world experience through co-op.
Engineering isn't just about making things work — it's about making them right. Here's what guides my approach.
I think about how systems evolve over time — from data models to deployment pipelines. I try to make decisions that won’t need to be undone six months later.
I don’t like doing the same thing twice. If a process is predictable, I’d rather codify it whether that’s CI/CD, deployments, or environment setup.
I try to write code that someone else can understand quickly — including future me. Clear structure, good naming, and team conventions matter more than cleverness.
"Good software starts with understanding the problem — everything else is implementation"
Technologies I work with daily, organized by domain. Not just logos — tools I've shipped production code with.
Always learning. Currently exploring: Multi-provider LLM orchestration and output normalization
I'm currently open to new opportunities. Whether you have a project in mind or just want to connect, I'd love to hear from you.