Software engineering student building toward quant software engineering.
I am shaping my work around C++, systems programming, concurrency, algorithms, simulation, and performance. I am not presenting every repo here as finished portfolio work. The goal is to show both completed technical evidence and the low-level/quant track I am actively building.
| Project | Focus | Signal |
|---|---|---|
| CS361 Homework 8 | C++ concurrency | Parallel search using worker threads, a channel abstraction, atomics, and producer-consumer output. |
| CS361 Homework 7 | C++ concurrency | Producer/worker structure and channel-based coordination. |
| TermiDo | C systems practice | Modular C CLI project with Makefile structure, command handling, file persistence, and educational encryption. |
| Creator Intelligence Recommender System | Ranking and evaluation | End-to-end recommender pipeline with baselines, hybrid modeling, reproducible metrics, and documentation. |
| Multimodal Fashion Search Engine | Retrieval and experimentation | Completed deep learning retrieval project with TF-IDF baseline comparison and final report artifacts. |
These repos show where I am aiming next. They are intentionally labeled as in progress.
| Project | Current State | Next Useful Milestone |
|---|---|---|
| Quant SWE Prep | Early C++ practice track with foundational projects started. | Build a real order book simulator, latency timer, and simple backtester. |
| Compiler for Rust | In-progress compiler coursework workspace; not finished. | Complete parser coverage, IR output, SSA/optimization requirements, and examples. |
| SamiiOS | OS learning notes and roadmap; no serious kernel implementation yet. | Add a minimal bootable QEMU milestone with documented build/run commands. |
- C++: data structures, memory, concurrency, performance measurement
- Systems: C, Rust, compilers, OS fundamentals, process/shell concepts
- Quant engineering: market mechanics, order books, simulation, backtesting, probability
- Data work: Python, ranking metrics, reproducible experiments, model evaluation
The next step is to turn the active build track into stronger proof: one complete C++ order book/backtester, one finished compiler milestone, and one bootable OS milestone. I would rather make those projects real than oversell scaffolding.



