I’m a software engineer at DraftKings, working on infrastructure. Previously at ADP. I also build my own projects, from market research tools to a way to explore a codebase’s history.
Try something I builtScrub through a codebase’s history
Systems Design Engineering
BASc · 2018–2023
01 Experience
My work has spanned developer platforms, infrastructure, finance, and embedded software.
ADP · May 2023–Aug 2026 · Promoted September 2025
Software Engineer Intern
Quantitative Developer Intern
Embedded Software Engineer Intern
Software Developer Intern
02 Personal work
These are projects I work on outside my day job. You can try a small example of each below.
Market intelligence
Research prices, news, and prediction markets together.
I built a research workspace that connects prices, news, options, and prediction markets, then keeps the evidence beside every paper trade idea.
Request a demoTry it: select a step to inspect its evidence.
A price move starts an investigation. It does not explain the cause on its own.
Check related news and the age of each source.
Illustrative records, not live market data or trading advice.
Market research gets scattered across prices, headlines, and notes. It becomes difficult to retrace why an idea looked interesting.
Keep evidence beside the research idea, with source provenance and paper tracking visible in the workspace.
The product is private and paper only. This portfolio demonstrates the interaction with synthetic records rather than exposing the research workspace.
Relative-value research
Compare related companies and inspect the evidence.
Converge finds unusual gaps between related companies and keeps the methodology, freshness, and risk context in view before anyone acts.
Try it: switch pairs to see what changes.
The two sample paths separate. A visible gap is a starting point for research, not proof that it will close.
A gap between two companies can look persuasive before the supporting evidence has been examined.
Present relative-value research alongside methodology, freshness, and risk context.
The public demo uses sample data. Exploring its interface does not establish a current market opportunity.
Codebase intelligence
See how a repository changes over time.
Drop in a public GitHub repository and watch its structure evolve. The result is a visual story of the codebase, not another wall of diffs.
Try it: scrub through four stages of an example repository.
The example begins with a single application entry point.
A commit list describes individual edits, but makes it hard to see how the shape of a repository changed.
Make structural history something people can explore visually, using a public GitHub repository.
A structural view helps orient the reader; the source and individual diffs are still needed to understand behavior. The example here is curated, not a fetched repository.