// experience / progression / impact

I learned the system from the people depending on it.

A decade across infrastructure, Kubernetes, observability, and developer platforms took me from troubleshooting into platform engineering and agentic systems. I do my best work embedded with the people who will use what I build: in their environment, against their real problems, shipping alongside them.

Download résumé ↓Start a conversation →

10+

years technical delivery

10

CNCF certifications

60%

account adoption

End-to-end

customer → architecture

01 — Career progression

Closer to the architecture with every move.

The titles changed. The direction did not. Each stage moved me from resolving individual symptoms toward building the platforms, feedback loops, and intelligent systems behind them.

Stage 01 / Foundation

Learn the system from the failure.

What I learned

The reported symptom is rarely the whole problem. Good support means reconstructing the user journey, gathering evidence, and staying with the issue until the system makes sense.

What changed

I stopped treating tickets as isolated events and started looking for repeated failure patterns.

What I built

Diagnostic instincts, escalation paths, customer communication, and a durable habit of tracing problems across boundaries.

Why I moved on

Recurring issues kept pointing upstream. I wanted to change the systems creating the queue, not only resolve what arrived in it.

Evidence / Bullhorn + LogMeIn · technical support

02 — Professional record

01

Port

Technical Success Manager

Jul 2025 — Present

Partner with enterprise engineering organizations adopting internal developer platforms, from technical discovery through measurable adoption.

  • ▹Built API-driven tooling for health scoring and recurring-issue detection across a strategic enterprise portfolio.
  • ▹Grew one account from 7% to 18% platform adoption, culminating in a customer-initiated renewal.
  • ▹Helped another enterprise account reach 60% platform adoption.
  • ▹Translate field evidence across Kubernetes, CI/CD, identity, APIs, and cloud infrastructure into product direction; contribute to Port's open-source CLI.

Internal developer platforms · Kubernetes · CI/CD · REST APIs · Python

02

RapDev

Datadog Engineer

Feb 2022 — Jul 2025

Designed and delivered enterprise observability migrations, integrations, and production troubleshooting across complex customer environments.

  • ▹Designed Python automation for repeatable enterprise migrations.
  • ▹Integrated observability platforms into production cloud and Kubernetes environments.
  • ▹Diagnosed distributed-system issues across infrastructure, networking, APIs, and telemetry pipelines.

Datadog · Python · Kubernetes · Cloud infrastructure · Observability

03

Connected2Fiber

Support Engineer → DevOps Engineer

Jul 2018 — Feb 2022

Progressed from the company's first support engineer into DevOps, building the infrastructure and tooling behind growing operations.

  • ▹Built cloud infrastructure, automation, and operational tooling.
  • ▹Turned recurring support patterns into engineering and systems improvements.
  • ▹Developed the production instincts that now shape how I design platforms.

DevOps · Cloud infrastructure · Automation · Production support

04

LogMeIn

Technical Account Manager

Feb 2017 — Jul 2018

Served as the technical bridge between enterprise customers and engineering teams.

  • ▹Built the customer communication and technical consulting foundation that still shapes how I deliver software.
  • ▹Translated enterprise requirements and production problems between customer and product teams.

Enterprise customers · Technical consulting · Escalation management

Earlier: Technical Support Representative, LogMeIn · Technical Support Analyst, Bullhorn (2014 — 2017)

03 — How I work

From messy signal to durable capability.

01LISTEN

Listen

Start in the real environment with the people experiencing the friction.

02TRACE

Trace

Follow evidence across APIs, infrastructure, workflows, and organizational boundaries.

03BUILD

Build

Ship the smallest system that resolves the cause—not merely the reported symptom.

04HARDEN

Harden

Add telemetry, automation, documentation, and ownership so the fix survives handoff.

04 — The throughline

Technical depth in service of adoption.

The job title changed—from support to DevOps, observability engineering, and technical success—but the work kept moving in one direction: find where people are losing time, understand the system deeply enough to change it, and leave behind a path that works without heroics.