About Me & Resume

Background & Focus

I am a Systems and Security Engineer focused on building robust, deterministic Linux infrastructure, self-hosted cloud environments, and autonomous execution systems. My work centers on declarative system architecture (NixOS), defensive tradecraft, security log analysis, and quantitative trading logic.

I value clarity over complexity. Whether configuring mail infrastructure, hardening network perimeters, or writing quantitative engines, I believe in empirical verification, strict state management, and minimal friction.


Core Technical Capabilities

1. Systems & Infrastructure Engineering

  • Declarative Management: NixOS 25.11 architecture, Nix Flakes, custom system modules, systemd service lifecycle orchestration.
  • Containerization & Virtualization: Docker, Podman, systemd-nspawn, container networking, isolated service bindings.
  • Networking & Mesh: WireGuard VPN mesh networks, Cloudflare Tunnels, Postfix MTA, Dovecot IMAP/Sieve, Nginx reverse proxying, DNS-01 ACME automation.

2. Cybersecurity & Defensive Tradecraft

  • Security Operations & Monitoring: OCSF schema mapping, log analysis, SIEM rule construction (Splunk SPL, KQL, EQL, Sigma).
  • Red Team / Blue Team Knowledge: MITRE ATT&CK framework mapping, initial access vectors, lateral movement analysis, detection engineering, and incident response playbooks.
  • System Hardening: SSH key-only policies, Fail2Ban brute-force mitigation, IP tables firewalling, real-IP proxy restoration, security headers.

3. Automated & Algorithmic Systems

  • Stateless Engine Architecture: Building 100% stateless execution engines integrated with Alpaca API, historical market data streams, and automated risk allocation rules.
  • Tool & Script Building: Python, Node.js, Shell scripting, automated system diagnostic suites.

Engineering Principles

  1. Declarative Over Imperative: State should be explicit, versioned, and reproducible. Manual drift is a bug.
  2. Empirical Verification: Diagnostics must be grounded in raw runtime logs and verified test outputs, never assumptions.
  3. Subtle Tooling, Maximum Reliability: Infrastructure should work silently, cleanly, and predictably under failure conditions.