I helped extend established Azure infrastructure to support new AI services. The work involved upgrading shared Terraform modules without breaking existing IaC, developing compatible modules within established policies, and addressing networking and identity requirements.
Runnable demonstrations. Clear tradeoffs. Evidence you can inspect.
FEATURED PROJECT01 — AI-ASSISTED TERRAFORM REVIEW
AI review with engineering guardrails.
A Terraform review needs questions that match the planned change. A local model selects from a fixed catalogue; Python checks those selections, and explicit policy rules decide when human review is required.
Inspect: the saved questions and final decision. Evidence: synthetic-plan evaluations and deliberately invalid responses exercise the response checks. The case study follows two model failures through their fixes.
Problem: a copied repository can hide missing or changed references. Inspect: the branch and tag comparison. Evidence: the local rehearsal detected missing, unexpected and mismatched references, including a changed tag annotation.
63 testsin the current local suite; 50 in each v1.0.0 release package
Azure DevOps collection uses simulated responses; Git reference rehearsals use real local repositories.
Read the engineering case study Readiness / acceptance evidence
The problem
A repository copy can look complete while branches, tag objects or required ownership information differ. A migration needs explicit acceptance evidence and a way to represent what is still unknown.
What I built
An offline Python assessment tool, a read-only Azure DevOps collector and a disposable local Git rehearsal. Reports connect findings to evidence, accountable roles and next actions.
Decisions & tradeoffs
Compare annotated-tag objects separately from their target commits, and retain unknowns when collection cannot establish a fact. Keep the rehearsal local so it is repeatable without credentials.
Observed result
The altered rehearsal copy exposed one missing ref, one unexpected ref and two mismatches, including a changed tag annotation. Windows and Linux produced identical release ZIPs; each extracted package passed 50 tests.
What remains outside the check
Matching refs is one acceptance check. LFS, permissions and platform metadata need separate verification. The collector’s live mode has not been exercised against a real organization.
Problem: a release needs a verifiable origin and a recovery procedure. Inspect: the signed-package checks and separate HTTP recovery lab. Evidence: trusted controls passed, invalid cases were rejected, and the recovery capture retained twelve healthy requests.
29 testsplus a real-signature check and signed-build rehearsal
Recovery runs on disposable loopback services. No production deployment is claimed.
These are independent portfolio demonstrations. Azure configuration is mock-tested, and infrastructure rehearsals use disposable local resources. The AI results establish contract compliance on a small synthetic corpus; broader model quality and reviewer time savings remain unmeasured.
02 / EXPERIENCE & APPROACH
Built on experience. Driven by curiosity.
20+ years across software engineering, infrastructure and enterprise delivery. I bring application context to platform work—and a practical focus on what makes a team’s day better.
How I work
Make changes reproducible. Give failures useful explanations. Keep credentials away from untrusted code. Document recovery before it is needed.
Outside engineering, I’m a songwriter and fiction writer. Structure and imagination have a place in both kinds of work.
2023 — 2026
Senior DevOps Consultant
Xebia
Designed Terraform automation and Azure Landing Zone deployments. Migrated TFS, Azure DevOps and Bitbucket repositories, implemented GitHub Advanced Security, and developed agentic solutions in GitHub.
2021 — 2023
DevOps / Platform Engineering Consultant
Cognizant
Led platform modernization, delivery automation and developer enablement. Mentored a remote team of five technical resources.
2016 — 2021
Software Architect / Cloud Modernization Lead
Healthcare technology organization
Led Azure modernization for healthcare applications, infrastructure automation, observability and disaster recovery planning.
I owned the migration, enabled GitHub Advanced Security, converted classic pipelines to GitHub Actions, and created initial Terraform modules and automation examples. Delivery combined permitted automation, manual work and regular stakeholder coordination.
Led and mentored a remote team of five technical resources, coordinating delivery across distributed workstreams. Provided hands-on architecture guidance and technical training for cloud delivery, Infrastructure as Code and automated deployments.
Designed and implemented Terraform automation and Azure Landing Zone deployments to standardize provisioning. Integrated GitHub Advanced Security into developer workflows and led migrations from TFS and Azure DevOps to GitHub.
Led Azure migration planning and execution for six applications across multiple services and environments, meeting target release dates. Designed, tested and documented disaster recovery procedures aligned with recovery time and data-loss objectives.
I’m looking for Senior DevOps and Platform Engineering opportunities where I can improve cloud delivery, build useful automation and help teams do their best work.