Four-role engineering portfolio Reproducible research infrastructure, dependable ML systems, low-level C/C++ software, and compiler/runtime foundations. I build and document software where correctness, reproducibility, performance, and clear engineering decisions matter. My doctoral research, systems projects, teaching, and technical writing provide inspectable evidence across four connected roles. Each pathway groups the projects, experience, research, and writing most relevant to that employer’s needs. Work appears in more than one pathway only when the responsibilities genuinely overlap. Reproducible experiment pipelines, scientific Python, high-performance workflows, metrics, data processing, automation, artifact management, testing, and research-oriented software design. C and C++, memory management, modular interfaces, command-line tools, operating-system concepts, debugging, concurrency foundations, build systems, and low-level reasoning. Model-training pipelines, synthetic-data workflows, experiment orchestration, metrics, HPC execution, environment management, automation, reproducibility, and dependable ML infrastructure. Language implementation, parsing, intermediate representations, execution models, virtual machines, memory, optimization, performance analysis, concurrency, and runtime architecture. C memory-management laboratory with reproducible CMake builds, strict compiler diagnostics, sanitizers, static analysis, automated tests, and CI established as the foundation for allocator implementation. C++ runtime project structured for thread pools, work stealing, scheduling, concurrency diagnostics, shutdown behavior, testing, sanitizers, and repeatable benchmarking. Performance-investigation toolkit designed around controlled workloads, repeatable measurements, profiler evidence, regression detection, and defensible optimization decisions. Language-implementation project progressing from lexer and diagnostics through parsing, syntax trees, semantic analysis, intermediate representations, and runtime integration. I develop reproducible cybersecurity and machine-learning workflows combining synthetic malware-image data, generative models, controlled evaluation, artifact management, and high-performance computing execution. Teaching experience strengthens my ability to reason about technical mechanisms, diagnose misunderstandings, and communicate complex systems clearly. The portfolio emphasizes observable engineering practice rather than long technology lists. Documented environments, commands, dependencies, configurations, and clean-clone workflows. Warnings-as-errors, automated tests, sanitizers, static analysis, and explicit boundary conditions. Metrics, controlled experiments, profiling, benchmarks, and evidence-backed conclusions. Clear interfaces, invariants, failure models, tradeoffs, limitations, and architecture records. A practical guide to reading integer input safely, detecting invalid characters, handling overflow, enforcing ranges, and building reusable input functions in C. Pointers are the mechanism that allows C programs to refer to memory, share objects, manage resources, build dynamic structures, and communicate with operating systems and hardware. A systems-level walkthrough of the boundaries between lexing, parsing, semantic analysis, intermediate representation, bytecode generation, virtual-machine execution, and runtime diagnostics. Select a role pathway, inspect the supporting work, or start a conversation about an engineering opportunity.Research & Systems Software Engineer
Four Direct Paths to Relevant Evidence
Research Software Engineer
Systems Software Engineer
ML Systems & AI Infrastructure
Compiler & Runtime Engineering
Featured Work
Memory Arena & Allocator Laboratory
TaskForge Runtime
PerfScope Toolkit
PoiseLang Frontend
GenCyberSynth Research
Explore research evidence →
Systems-Focused Teaching
View relevant experience →
Evidence Before Claims
Reproducible Builds
Correctness & Testing
Measured Behavior
Engineering Decisions
Reasoning Made Inspectable
Using fgets and strtol Safely in C
Why C Pointers Matter
From Source Text to Execution: Designing a Small Language Runtime
From Research Pipelines to Runtime Foundations
Choose the role you are evaluating
01
Selected engineering evidence
View all projects
Milestone 0 complete
C · Memory · CMake · Sanitizers
Milestone 0 complete
C++ · Concurrency · Runtime · Testing
Foundation v0.1.0
C++ · Profiling · Performance · CI
Milestone 0 complete
C++ · Parsing · Compilers · Diagnostics
How the work is evaluated
Technical writing
View all articles →
Systems Software Engineer
Read article →
Compiler & Runtime EngineeringSystems Software Engineer
Read article →
Compiler & Runtime Engineering
Read article →
Evaluate the complete profile