Infrastructure & Systems Engineer | RHCE (RHEL 10) | Linux, Ansible, Rust & Python | Industrial Edge Systems
I design, automate, and troubleshoot systems where correctness, predictability, and observability matter.
My background spans Linux infrastructure, systems programming, industrial IoT, and automation. With over five years of development experience, I focus on building reliable software that interacts with operating systems, hardware, and potentially destructive system operations.
My engineering philosophy is straightforward:
Fail loudly. Verify the resulting state. Never report success without evidence.
I favor explicit invariants, deterministic behavior, minimal dependencies, and systems that remain understandable when something goes wrong.
Rust | Linux LVM2 | State Convergence | Safety Verification
A declarative state-convergence engine for Linux Logical Volume Manager (LVM2), designed to replace fragile sequences of storage commands with explicit, inspectable execution plans.
Key design principles:
- State-aware planning: inspect existing storage configuration and determine the operations required to reach a desired state.
- Conservative execution: detect unexpected or partially configured states and refuse potentially unsafe transitions.
- Explicit authorization: separate planning and verification from privileged execution.
- Post-execution validation: examine the resulting system state rather than relying exclusively on command exit codes.
- Failure transparency: preserve execution information and make partial transitions visible to the operator.
- High-assurance testing: use Kani for targeted arithmetic-safety verification, Proptest for property-based testing, and fuzzing to exercise edge cases.
The project is under active long-term development. Planned work includes operator-directed recovery of interrupted execution plans.
Windows APIs | C | Python | Industrial Automation
Systems-level tooling developed around industrial software and hardware integration.
My work in industrial environments has included reverse-engineering undocumented hardware interfaces, managing legacy process behavior through Windows APIs, and building concurrent telemetry pipelines for manufacturing equipment.
One independently developed integration recovered approximately 360 hours of annual production capacity by addressing operational inefficiencies in a manufacturing environment.
Linux Hardening | SELinux | Minimal Operating Systems
A Linux hardening and minimal-system project focused on reproducibility, controlled system behavior, and reducing unnecessary attack surface.
My related Linux security work includes exploring and configuring:
- SELinux mandatory access controls.
- Minimal RHEL-family and Fedora installations.
- LUKS2 disk encryption and TPM-backed authentication.
- USBGuard device authorization policies.
- System snapshots and rollback mechanisms.
- Custom
systemdservices and restrictive service configurations.
| Domain | Technologies and Practices |
|---|---|
| Linux Infrastructure | RHEL 10, AlmaLinux, Fedora, systemd, SELinux, LVM2, virtualization |
| Automation & IaC | Ansible, YAML, declarative configuration, infrastructure automation |
| Systems Programming | Rust, C, Python, Bash, Windows native APIs |
| Software Assurance | Kani, Proptest, kani-fuzz, invariant testing, defensive programming |
| Industrial Systems | Industrial IoT, hardware API integration, concurrent telemetry, ETL |
| Networking & Operations | Linux networking, troubleshooting, monitoring, service management |
| Additional Experience | JavaScript development, Kubernetes fundamentals, cloud architecture studies |
Correctness over apparent success. An operation is not successful simply because a command exited with code zero. Where possible, the resulting state should be independently verified.
Explicit failure boundaries. Unexpected state is a reason to stop and investigate, not permission to improvise destructive recovery actions.
Automation without unnecessary opacity. Good automation reduces operational effort while preserving the information necessary to diagnose failures.
Minimal complexity. I prefer well-understood primitives, clear interfaces, and maintainable systems over unnecessary abstraction.
Verification within defined limits. Formal methods, property-based testing, and fuzzing are valuable tools for establishing specific guarantees. Their scope and assumptions should remain explicit.
- Red Hat Certified Engineer (RHCE), RHEL 10 — Verify credential
- Red Hat Certified System Administrator (RHCSA), RHEL 10 — Verify credential
Currently studying: AWS Certified Solutions Architect – Associate and HashiCorp Terraform Associate.
Additional training: WithYouWithMe Cyber & Tech Program alumnus.
My Linux expertise has been developed through independent study, extensive hands-on lab work, virtualization environments, automation projects, and real-world engineering problems.
I'm particularly interested in:
- Linux systems and operating-system security.
- Rust systems programming and software verification.
- Declarative infrastructure and reliable state reconciliation.
- Industrial automation and hardware/software integration.
- Reproducible, locally controlled, and resilient infrastructure.
I'm interested in technically demanding engineering work where reliability, transparency, and a deep understanding of system behavior are essential.
If you're working on Linux infrastructure, systems software, security-sensitive tooling, or industrial automation, feel free to reach out.

