About

01

Engineering with product judgment.

I build across infrastructure and product, with the same attention to the system and the person using it.

Arlington / Virginia

Portrait of Isaiah Neal.

Background

Infrastructure engineer and product builder based in Arlington, Virginia.

My focus is high-assurance infrastructure for U.S. national-security missions, spanning cloud platforms, automation, and security-minded engineering. I also build products with AI.

I’m interested in the whole lifecycle: making something useful, understanding its failure modes, and keeping it maintainable once it’s in use.

Professional focus

One practice, three lenses.

  1. 01 / Infrastructure

    Infrastructure for U.S. national-security missions. Operational clarity.

    Reliable foundations, useful automation, and systems that stay understandable under pressure.

  2. 02 / Product

    Execution across the full experience.

    Product decisions, backend behavior, and interface details treated as one connected discipline.

  3. 03 / Perspective

    Security built into the shape of the work.

    Secure defaults, least privilege, failure isolation, observability, and practical threat awareness.

Tools of the trade

Cloud & platforms
AWS · Kubernetes · Terraform
Delivery & operations
CI/CD · GitOps
Languages
Go · Python

Always sharpening the fundamentals. Algorithms & data structures on LeetCode and HackerRank

Working method

Faster feedback, intact judgment.

I use Claude Code and Codex for research, implementation, and review where the operating environment allows. They shorten the feedback loop; I remain responsible for the architecture, verification, and result. I also pursue AWS certifications, practice problem-solving through LeetCode, and build hands-on labs to learn new systems concepts.

Engineering perspective

Security should shape the system, not decorate it.

Building and operating infrastructure for diplomatic technology environments taught me to treat secure defaults, least privilege, and observability as everyday engineering decisions.

Operating principles

A working standard.

  1. 01

    Good infrastructure removes drama.

    The best systems make difficult operations feel routine.

  2. 02

    Taste is a technical advantage.

    The details people struggle to name often determine whether a product feels finished.

  3. 03

    Build for the failure mode.

    The happy path gets attention; resilience is defined by everything around it.

  4. 04

    Simple is not the same as easy.

    Clarity usually comes from removing complexity, not ignoring it.

  5. 05

    Ship, then sharpen.

    Momentum matters, but unfinished thinking should never become permanent architecture.

Selected experience

Oct 2026–Present

Amazon Web Services

Amazon Dedicated Cloud Engineer I L4

Organization
Region Reliability Engineering & Automation
Location
Arlington, VA — HQ2
Environment
Amazon Dedicated Cloud

Supporting the reliability and operation of Amazon Dedicated Cloud infrastructure within AWS Region Reliability Engineering & Automation

Visit AWS

Away from the screen

Keep the system human.

Outside of work, I make time for fitness and tennis. I’m based in Arlington and spend plenty of evenings turning ideas into applications with AI.

Open console