Independent platform engineering consultant
From clickops
to engineered platforms.
I work across infrastructure, identity, data, and automation to turn messy enterprise systems into platforms teams can understand, change, and operate.
Platform experience
-
Terraform See experience →
-
Azure See experience →
-
AWS See experience →
-
Databricks See experience →
-
GitHub See experience →
-
Nutanix AHV See experience →
-
Packer See experience →
-
GitHub Actions See experience →
-
Microsoft Entra ID See experience →
-
Microsoft Intune See experience →
-
PowerShell See experience →
-
Active Directory See experience →
Recruiting?
Send the job description. I'll reply with availability and stack fit.
[email protected] →
Project inquiry?
Send a short note about the platform, timeline, and what needs to change.
[email protected] →
- Years
- 12
- Case studies
- 08
- Industries
- 9
- Based
- US
Sound familiar?
The platform works.
It just doesn't scale.
- 01
ClickOps has become the change process: important settings live in portals, not pull requests.
- 02
No one can tell which policy, tag, grant, or module is the source of truth.
- 03
Every new team needs an exception because the platform pattern is hard to reuse.
- 04
Automation exists, but it is not wired into a reviewable release path.
- 05
A platform that works for now but cannot absorb the next workload.
Selected work
Recent engagements
- 001
Fortune 500 Bank
Platform Automation Engineer · Banking
Built Nutanix AHV image and provisioning automation with Packer, Terraform, and GitLab CI, while connecting the bank's existing VMware build platform to the same network, inventory, and service-management handoffs.
- 002
US mechanical contractor
Databricks Platform Engineer · Construction & engineering services
Migrated an enterprise Azure Databricks platform off a branch-per-environment, ticket-gated Terraform setup onto a single-branch, directory-per-environment repo, with identity wired end to end through Microsoft Entra ID and self-service medallion-schema provisioning for data engineers. No workload interruption.
- 003
Enterprise Identity Company
Client Platform Engineer · Endpoint management
Built endpoint-platform automation across Intune policy as code, OpenIntuneBaseline-informed Windows hardening, Autopilot provisioning, and PatchMyPC application patching.
- 004
Fortune 500 Automotive Retail Enterprise
Senior Cloud Engineer · Automotive retail
Authored and hardened shared Azure Terraform modules for the platform team, then carried those patterns into real workload repos across multiple business units.
- 005
Fortune 500 Chemical Manufacturing Enterprise
M365 / Azure Engineer · Chemicals & energy
Engineered an Azure tenant-to-tenant migration following a business acquisition, porting portal-built infrastructure into Terraform during the cutover.
- 006
International reinsurance broker
Windows Platform & Image Pipeline Engineer · Insurance & reinsurance
Rebuilt the Windows Server image pipeline on Nutanix AHV with Packer, hardened templates at build time, and migrated CI from Jenkins to GitHub Actions.
- 007
Global game studio
Platform / Release Engineering Consultant · Gaming & online services
Helped move critical platform infrastructure from an on-premises environment into AWS, standing up networking, Terraform-backed cloud foundations, and GitHub administration paths during a high-pressure incident cutover.
- 008
Fortune 500 Healthcare and Retail Enterprise
Azure / Windows Image Pipeline Engineer · Healthcare retail
Built focused Azure and Packer platform pieces: Windows VM provisioning runbooks, managed-identity cleanup, post-build extensions, and Windows Server image baselines across vSphere and Azure paths.
Engagement model
How contracts usually work.
- 01 First 1-2 weeks
Ramp in
Read the repos, tickets, tenants, pipelines, and runbooks. Map what exists, what is risky, and where the first useful change should land.
- 02 3 months to multi-year
Build with the team
Work inside the team's normal delivery flow: PRs, reviews, pipelines, migrations, platform changes, documentation, and operational cleanup.
- 03 Throughout
Make it operable
Turn decisions into code, runbooks, release paths, and handoff notes as the work happens, not as a final-week scramble.
- 04 Close cleanly
Extend or roll off
If the scope grows, extend around the next set of priorities. If not, the team owns the next change before I leave.
FAQ
Questions before we work together.
- Do you work alone or with a team?
- Usually solo. You work directly with me day to day. If an agency or staffing firm is involved, that is the contracting path, not a delivery handoff. I embed with your team for the engagement.
- How does knowledge transfer happen?
- It happens while we build. I write the code, runbooks, release paths, and decision notes in the team's normal workflow so the platform gets easier to operate while I'm embedded, not only at the end.
- Rates and engagement model?
- W-2 or 1099 hourly, whichever is easier for your team. Through your payroll, AP, or staffing firm of choice.
- Where are you based?
- US based.
Open for work
Hiring? Let's talk.
A sentence or two about your platform and rough timeline saves us both a discovery call.