2026
University of Nevada, Reno
M.S. Cybersecurity
3.9+ GPA
My graduate studies were in incident response, secure architecture, and adversarial thinking. These concepts support me in my career today.
Hello and Welcome to my corner of the web. I'm a passionate DevOps Engineer building a more secure world. This website is designed to show you what is possible when you combine security and DevOps, and how it can benefit you. I hope you enjoy exploring my work and learning more about my journey.
01 · Education
Eight years of formal education in systems, information and adversarial thinking, is the theory that everything I ship to production is built on.
2026
M.S. Cybersecurity
3.9+ GPA
My graduate studies were in incident response, secure architecture, and adversarial thinking. These concepts support me in my career today.
2024
B.A. Information Systems
Dean’s List · 3.8+ GPA
For my undergraduate studies focused on the principles of designing, integrating, and documenting systems that all organizations need and depend on.
2020
A.S. Information Technology
Dean’s List · 3.7+ GPA
When I started my studies, I focused on systems administration, Linux fundamentals, and found a passion for automation.
02 · Experience
Three years of hands‑on experience has provided me with a wonderful first step, through frontline security operations that are the heart of a multi‑tenant SOC, to engineering the pipelines and tooling that make it all possible.
2024 — Present
SNC
Full‑time
Contribute to the data and detection infrastructure behind a multi‑tenant Security Operations Center: ingestion pipelines, SIEM platform engineering, automated reporting and the analyst‑facing tooling.
2023 — 2024
SNC
Full‑time
Frontline detection and escalation inside a Security Operations Center, triaging alerts across thousands of endpoints, network resources and identity telemetry all while escalating confirmed incidents with professional reports that help customers understand the impact and next steps.
2018 — 2023
Magnolia AV
Full‑time
Delivered in‑home technical consultations, end‑to‑end integration for residential audio/video, and networking/control systems.
03 · Stack
I may not have the deepest expertise in every tool I use, but I wouldn't include it in this list if I wasn't confident in my ability to use it to solve problems, and more so if I wasn't passionate about learning more about how to use it better every day.
18
Tracked competencies
3yrs
In the field
3
Degrees earned
24/7
SOC supported
80%
A year on the floor triaging alerts under response SLAs, then two more building the platform that feeds it. I’ve worked both sides of every ticket.
55%
I can turn observed tradecraft into detection logic and tune it against live telemetry, but authoring content is a smaller slice of my week than the pipelines feeding it.
50%
Working familiarity: feed curation, taxonomy hygiene, and pushing indicator context downstream. I know what it’s for and can operate it; I’m not deep in its internals.
85%
The deep end of my expertise. Ingest pipelines, index lifecycle and retention, query performance, cluster health and the tenant isolation boundaries underneath all of it.
70%
Batch and streaming transforms over large security datasets: normalization, enrichment joins and schema enforcement before anything reaches the SIEM.
60%
Working proficiency. I can model a schema, write the queries and run migrations for internal tooling, but deep relational tuning isn’t where my hours have gone.
45%
I build the dashboards I need (pipeline throughput, ingestion lag, tenant health), but I’d not call myself a Grafana specialist. Most of my visibility work lives in Kibana.
85%
Cluster setup, storage and networking, LXC and VM templating. I run my own multi‑node cluster, and CI for this site executes on a runner inside it.
75%
The through‑line of everything else here. If I do it twice by hand it becomes a pipeline, a role, or a script the next person can read.
70%
Deploy and operate containerized platform services: manifests, resource limits, rollout strategy, and the debugging that inevitably follows.
70%
I can reason about cloud topology (identity boundaries, network segmentation, tenant isolation), but most of my infrastructure hours are on hardware I own rather than rented.
60%
Idempotent roles for configuration management and fleet‑wide change, so environments converge on a known‑good state instead of quietly drifting apart.
60%
Infrastructure declared in code and reviewed like code, so environments are reproducible rather than hand‑built artifacts nobody dares rebuild.
65%
I design services that hold up, with attention to data contracts and tenant boundaries, but I come at it from the data and infrastructure side, not from microservice patterns.
55%
Functional, not fluent. I ship analyst‑facing views for the SOC tooling I build, but I’d defer to a dedicated front‑end engineer on anything more ambitious.
50%
An interest rather than a discipline. I care that tooling looks considered and I’ll put the hours in (this site is the evidence), but it’s the furthest thing here from my day job.
85%
Five years of in‑home consultations taught me to translate technical constraints into plain language and to set expectations I can actually meet.
75%
Queue and workflow management: intake, triage, SLA tracking, and the reporting that shows where a backlog is really accumulating.