Connect with me on LinkedIn

Jeremiah Walters

Leads people first, builds systems that serve them
Portrait of Jeremiah Walters

Senior Software Engineer & Delivery Lead at Microsoft, in Azure Reliability. I lead delivery for a multi-squad program building an AI-powered risk-analysis agent platform that Azure engineering and SRE leadership rely on every day — owning the roadmap and the engineering behind it — and I write the guardrails that keep agents honest: retrieval, tool use, and evaluation workflows that verify an agent's work before anyone has to trust it.

By the numbers

The numbers matter. The people behind them matter more.

~8 Years at Microsoft Across Azure, Seattle area

Experience

Senior Software Engineer & Delivery Lead
Microsoft (Azure Reliability)  |  Nov 2024 – Present
  • AI Agent Platforms
  • Evaluation Workflows
  • Retrieval & Tool Use
  • Throttling & Reliability
  • Python · TypeScript
  • Technical Program Leadership
  • Cross-Team Delivery
  • Roadmaps & Milestones

Leads delivery for a program of 10+ engineers across squads building an AI-powered risk-analysis agent platform used daily by Azure engineering and SRE leadership. Writes scanner rules for throttling and retry anti-patterns, and builds evaluation workflows so agent output is verified before it is trusted — technical program leadership across squads as much as hands-on engineering.

  • 8 static-analysis scanners / scanner rules in production pipelines
  • 253 audited detections at a 91.7% true-positive rate
  • False-positive rate tuned from 3.2% down to 0.4% through hand review of findings

Key takeaway: An agent's output is a claim, not a result. Verification is what makes trust scale.

Cloud Engineer, FastTrack for Azure
Microsoft  |  Jun 2022 – Nov 2024

Technical lead for enterprise engineering teams on complex production issues across compute, networking, storage, and data, through to resolution. Built knowledge bases and best-practice guides that scaled across a large customer base, and turned recurring pain points into prioritized tooling improvements with product and engineering teams.

Key takeaway: Enterprise problems get solved in rooms before they get solved in code. Align the people, then fix the system.

Azure Cloud Engineer
Microsoft (Azure Customer Engineering)  |  Jul 2018 – Jun 2022

Diagnosed and resolved global production incidents in distributed customer workloads, and fed recurring patterns back to engineering to prevent recurrence.

Key takeaway: Reproduce it, isolate it, prove the fix. If it keeps happening, it is a pattern, not an incident.

Frontend / Full-Stack Developer
Mercutio (ecommerce agency)  |  Apr 2017 – Feb 2018

Built full-stack ecommerce experiences in JavaScript for outdoor and specialty retail: discovery, cart, checkout, authentication, and account management.

Key takeaway: Done and live beats perfect and planned. Real customers on real deadlines teach you what shipping means.

Selected Work

failure-lab jtwalters25/failure-lab

A retry-storm simulator plus hand-reviewed scanner findings for retry anti-patterns in public code. The eval-first method, in miniature.

intent-engine jtwalters25/intent-engine

Deterministic, explainable intent-aware re-ranking: same catalog, different intent, different order, across streaming, music, e-commerce, ride matching, and food delivery.

clause jtwalters25/clause

Contract-clause intelligence: semantic clause-vs-playbook matching with calibrated STANDARD / REVIEW / BLOCK verdicts and an automated canary gate for safe rollouts.

readiness-as-code jtwalters25/readiness-as-code

Continuous review compliance as a folder in your repo: JSON definitions, a Python scanner, and a CI template. No infrastructure, no SaaS.

More on GitHub: github.com/jtwalters25

Writing

Keep a Brag Doc That Doesn't Lie

Every claim labeled Confirmed, Inferred or Missing. Precise credit instead of inflated credit, a weekly rhythm, and how to make it safe to share outside your company.

The Senior‑to‑Principal Gap: It's Not More Code

Notes from the middle of the climb: problems over tasks, multiplying others, why impact has a blast radius, and strategy you can explain in a paragraph.

Leading a Team Without Being Anyone's Manager

Outcomes without authority, and without becoming the janitor. What a lead actually owns, influence without authority, nudges instead of nagging, and telling the truth upward.

Validate the Slice, Not the Vision

Big ideas are cheap now. Proof still isn't. What a slice actually is, three that taught me something, and when slicing is the wrong call.

When AI Agents Cost More Than the Work They Automate

Field notes from a failed attempt to make an engineering workflow agentic: a coordinator that spent its whole budget before the A/B test started, why reusing existing skills beat adding agents, and a rule change that passed every test but found nothing in real repos.

Education / The Path

Bartending
Before engineering — the non-traditional start.
Software Development
Code Fellows  |  Seattle, WA
Data Analytics Certificate
University of Washington
Azure AI Engineer Associate
Microsoft Certified

The non-traditional route is the point: bartending before engineering. Code Fellows turned a career change into a craft, and the bar left its mark — read the room, stay calm when it slams, and never serve something you haven't checked. That instinct never left; it is why verification comes first now.

My Philosophy

People first. Always.

Empathy. Synergy. Service. Curiosity.

Most Proud Of

My children

Everything else on this page is downstream of showing up for them and building a life they can be proud of.

Trusted to lead

Colleagues, managers, and teams hand me the hard problems and the people side of shipping, and trust me to land both. That trust is earned in outages, in reviews, and in rooms where the stakes are real.

Intent Engine

A system I designed in early 2026 for translating intent, human or agent, into deterministic, verifiable execution. This year the industry shipped its own versions of the idea. The instinct was right, and the receipts are public.

How I Structure My Time

    Illustrative split, not measured data. The order, though, is honest.

    Attributes

    Qualities colleagues endorse
    • Technical program leadership
    • Cross-team delivery
    • Eval-first thinker
    • Calm in an outage
    • Ships and iterates
    • Raises the bar on verification
    Personal areas of growth
    • C# depth
    • Saying no to side quests