Software Engineer
Backend systems for regulated pharmaceutical manufacturing.
Skills browser
Search languages, frameworks, and tooling across production backend work, OMSCS systems projects, this site, and data/ML coursework.
Engineering case studies
Written breakdowns of systems I've designed, the constraints, the tradeoffs, and the decisions behind each. Much of this work is proprietary or academic, so the engineering reasoning is the deliverable here.
Sole owner of the Java backend for a regulated pharmaceutical product: a real-time orchestration engine coordinating deterministic workflows, distributed state synchronized over async messaging, and a multi-stage persistence layer underneath.
Outcome: releases repeat through typed contracts, repository boundaries, automated tests, and generated PDF/A-3 evidence
The platform's RPC layer would have required reimplementing its module RPC factory, so the integration surface moved to authenticated HTTP: GET lists the test scenarios, POST dispatches a procedure call with JSON-configurable options and returns structured pass/fail with per-step assertions.
Outcome: integration tests run against live JVM gateways, from CI or from a single HTTP call
Built a C++17 distributed file system around explicit RPC contracts, file transfer, metadata operations, weak cache consistency, write-lock coordination, and multi-client synchronization.
Outcome: inotify watchers and async callbacks propagate changes across clients, and mutex-guarded server-side locks serialize conflicting writes
Compared trading strategies as controlled experiments: from-scratch tree learners, indicator features, bagging, hyperparameter search, and out-of-sample evaluation under market-cost assumptions.
Outcome: differences between strategies trace back to specific features and cost assumptions instead of a single accuracy number
About
A compact view of the education, production work, and technical focus behind the projects.
Four milestones from physical systems to backend software.
Completed foundational engineering, math, and science coursework before transferring into Temple University's mechanical engineering program.
Mechanical engineering degree, GPA 3.67. Modeling, systems thinking, and working problems under real physical constraints.
Systems, networking, and infrastructure work through early 2024, then backend software. Now the sole owner of the Java backend for a regulated pharmaceutical product.
Systems and machine learning coursework, GPA 3.8. Operating systems and computer networks written in raw multithreaded C, distributed systems in C++.
Contact