A technical foundation in CI/CD, containers, and security tooling, paired with UX research and writing that make the complex things people build actually usable.
I started on the technical side, building pages by hand and learning how systems fit together through DevOps. Along the way, I built an automated security pipeline that caught a real vulnerability three other scanners had missed, and that's what turned "technology" into something more specific: I want to work in security.
The more I built, the more I also cared about whether anyone could actually use what I'd made, which pulled me toward UX research and user-focused writing too. I'm aiming for a technical product manager role in security because that's where all of it meets: someone who can sit with engineers and understand the constraints, sit with designers and understand the intent, and still write a spec a new hire can follow without asking five questions.
The best requirements document is the one nobody has to ask you about twice.
— a thing I believe, and try to practice
Hands-on engineering work, mostly where something could break, leak, or be exploited if it wasn't built carefully.
Three pieces that show the same instinct from different angles: understand the user, then build or evaluate something that actually serves them.
I care about writing that a reader can act on immediately, specs, documentation, and reports that don't require a follow-up meeting to decode. Two pieces published on InfluxData's engineering blog:
Breaks down how InfluxDB 3 Core and Enterprise work under the hood: the single-node architecture, flexible "diskless" storage options, the built-in Processing Engine for real-time data transformation, and the read replication and multi-node clustering that Enterprise adds for teams running at scale.
Read on InfluxData →A hands-on walkthrough for standing up InfluxDB 3 Enterprise locally with Docker, pre-configuring the Explorer UI so a team can connect without manual setup, then ingesting and querying sample data, closing with what to consider when moving from a local demo toward production.
Read on InfluxData →An original paper working through graph coloring theory from first principles: proving the greedy algorithm's Δ(G)+1 upper bound, showing how the Welsh-Powell heuristic tightens that bound in practice, and walking through Brooks' Theorem using Lovász's vertex-ordering argument. Ties the math to real systems, compiler register allocation, CI/CD job scheduling, and procedural generation all reduce to the same coloring problem.
Read on GitHub →A plain-language breakdown of a published neuroscience paper on geometric hallucinations, explaining how mathematical models of the visual cortex, built on tools like Euclidean symmetry and perturbation theory, can account for the geometric patterns people see during migraines or under certain psychoactive substances, even in total darkness.
Read on GitHub →Leadership and coordination work outside of paid roles, most of it was really just project management before I had the title for it.
A quick snapshot of the tools behind the work above. If you want the full picture, roles, dates, and results, you can download the resume itself.
Reach out directly, or say hello to the assistant in the corner, it's part of the site, not just decoration.