Download CV

Initiatives

Current and recent engineering work that extends my focus on developer experience, release infrastructure, AI-native workflows, and practical systems.

Download CV View CV

Day job: release operations and developer experience at JetBrains—end-to-end ownership across CI/CD, build infrastructure, and delivery for 100+ engineers across multiple teams and cross-project programs. The initiatives below apply the same mindset to personal infrastructure, tooling, and workflow experiments.

Professional context

Where my attention goes in the role today—operating priorities, not a scorecard. The CV uses the same framing.

  • Cross-team & cross-project delivery — coordination across 100+ engineers, multiple teams, and overlapping product lines
  • Release ownership & developer workflows in distributed, multi-team environments
  • CI/CD stability — pipeline success with production-safe delivery
  • Deploy velocity — time-to-deploy as a primary lever (targeting ~2× faster)
  • Release train cadence — predictable scheduling without the long delays the program used to carry
  • Build infrastructure — AWS agents, scalability, security, and observability
  • Release sequencing, dependencies, and delivery clarity across team and project boundaries

Full experience on CV →

Personal initiatives

Personal AI Assistant / Agent Workflow Prototype

In Progress

Learn AI-native workflow design hands-on while keeping scope honest—prototype and boundaries before automation or multi-agent complexity.

Early-stage assistant concept for research, planning, and structured task support, with architecture kept intentionally small until workflows are proven.

Exploring how a personal assistant could support everyday engineering work—planning, drafting, reminders, and research—without pretending the result is a shipped product. v1 is deliberately narrow; persistence, email automation, and multi-agent orchestration stay out of scope until the core workflow is useful.

Highlights

  • MVP boundary — research and planning first; email automation and multi-agent flows deferred
  • Assistant split — Perplexity for web-grounded research; Gemini for drafting, planning, and non-search task support
  • Workflow clarity — document steps and failure modes before APIs or persistence
  • Incremental integration — APIs, storage, and automation only where they reduce friction
  • Iteration discipline — prove usefulness before expanding architecture

Tech

  • Perplexity
  • Gemini
  • Prompt design
  • API boundaries
  • Workflow design
  • Python

Home Infrastructure & Network Segmentation Lab

Ongoing

Practice blast-radius and access-control thinking at home scale—the same instincts I apply to build infra and release safety.

Hands-on lab for segmented home networking: VLANs, DNS, firewall policy, and isolation between trusted and untrusted devices.

Built and iterated on a three-zone layout (Main, IoT, Guest) to understand how segmentation behaves in practice—not just on paper. Focus is on isolation boundaries, least-privilege access, and debugging when policy or DNS order breaks connectivity.

Highlights

  • Segmentation — Main, IoT, and Guest zones to limit blast radius
  • Access control — least-privilege firewall rules; verify what blocks vs. leaks
  • DNS & routing — policy order tuned after real connectivity failures, not diagrams only
  • Zero-trust habits — assume IoT compromise; keep guest traffic isolated
  • Isolation debugging — VLAN and firewall behavior until intent matches reality

Tech

  • VLAN
  • DNS
  • Firewall policy
  • Router configuration
  • Network segmentation
  • Linux
  • macOS

Personal CV & Portfolio Infrastructure

Live

Treat the site as developer-facing infrastructure: easy to change, test, and ship—not a one-off brochure.

A production portfolio and CV site on a custom domain, built to present release engineering, DevEx, and engineering-systems experience clearly.

Designed and deployed a public engineering profile with JSON-driven content, automated tests, Docker packaging, and a GitHub Actions → GHCR → Render delivery path. Resolved Cloudflare DNS and TLS propagation issues the same way I would a production cutover: verify records, certificates, and end-to-end behavior before calling it done.

Highlights

  • Content-as-data — JSON plus page tests; no CMS, low-friction updates
  • Delivery path — GitHub Actions to GHCR, production on Render behind Cloudflare
  • Stack discipline — FastAPI and static assets; simple deploy path over unnecessary complexity
  • Positioning — DevEx, release engineering, and engineering systems—not a design portfolio
  • Production cutover — DNS and TLS propagation verified end-to-end before going live

Tech

  • FastAPI
  • Python
  • Docker
  • GitHub Actions
  • GHCR
  • Cloudflare
  • Render
  • pytest
  • Cursor

Like what you see?

Grab the CV, share the page, or reach out — I'd love to hear from you.

Get in Touch