Remote / Mobile / Open to Relocation
Backend, data, and systems developer. I build pipelines, protocol clients, and automation tools for scientific, industrial, and data-heavy workflows.
I work primarily in Python, Rust, and C++, with experience in Java and TypeScript.
I like clear logic, stable architectures, and code that behaves the same on Monday morning as it did on Friday night. I follow problems down to their root causes and pay attention to the hints systems leave behind.
- Stable Architectures — Refactoring legacy systems into modular, testable codebases.
- Data & ML Pipelines — End-to-end ETL and inference pipelines with rigorous validation and latency benchmarking.
- Cross‑Language Systems — Interoperability between Python, Rust, and Java/Spring Boot services.
- Procedural Generation — Geometry, map generation, and structural algorithms.
- Hardware & Protocols — Industrial PLC communication (EtherNet/IP) and BLE data flows.
- Modern CI/CD — Automating consistency and releases for multi-service environments.
- Systems Thinking — Modeling component interactions to remove unexpected behavior.
- Infrastructure — Deploying robust services, including ML inference APIs and containerized data pipelines.
- Complex Data — Cleaning, validating, and structuring datasets from banking, CNC, medical imaging, and IoT sources.
Production-grade 3D segmentation inference pipeline. Features dynamic-shape support, high-performance FastAPI serving, and latency benchmarking.
DICOM to mesh conversion (PLY/STL/OBJ) using marching cubes, CT metadata reconstruction, and NIfTI mask generation.
Ampla to ISA-95/B2MML multi-pass converter. Includes validation layers, CLI tools, and automated pipelines.
Concurrent Playwright scraper, FastAPI background tasks, Pydantic validation, DuckDB time‑series storage, and Streamlit visualization.
ETL for RWA diagnostics, Spring Boot backend services, and Angular dashboards for risk visibility.
NSGA‑II multi-objective evolutionary algorithm (Rayon-parallelized) and async EtherNet/IP client for PLC communication.
Status: Probably deep in a pipeline, a protocol spec, or a geometry routine.