Accountable for the architecture, the budget, the team, and the outcome.
I came up through this work — first as an engineer, then as an architect, and for the past several years as the person accountable for all four.
Infrastructure Strategy · IT Operations · Enterprise Architecture · Financial Stewardship · Vendor Governance · Team Leadership
What I do
My work sits where architecture, operations, money, and people meet. In multi-site environments those four things are the same problem. A design that cannot be operated by the team you actually have is not a design. A modernization that cannot be paid for is a slide deck. I have spent enough time on all four sides to keep them from pulling apart.
Most of my career has been in retail and industrial environments, where a network outage does not generate a ticket — it stops registers, idles crews, and costs money by the hour. That shapes how I build. I favor designs that degrade gracefully, vendors who answer the phone, and documentation that lets somebody else fix it at two in the morning.
How I lead
- I put numbers on things. The fastest way to get an infrastructure budget taken seriously is to show what the current state actually costs. In one large retail environment that meant building real telecom expense visibility before proposing a single change — and the change paid for itself.
- I build teams that outlast the project. Standardized documentation, clear runbooks, and no single-point-of-failure engineers. In a 1,100-location retail network that cut onboarding from two weeks to five days and removed dependencies that had been quietly sitting on one person.
- I govern vendors instead of hoping. Most of the distributed environments I have run were delivered largely by managed service providers. Managed service work rises to the level of the metrics you hold it to, and falls to the level of the ones you do not.
- I stay steady when the org does not. Reorganizations, leadership changes, and restructurings are normal in long programs. The architecture has to survive them, which means the governance around it has to be written down and not resident in anyone’s head.
I wrote A Field Guide for Engineers Moving Into IT Leadership because becoming responsible for people, budgets, and outcomes asks for a different set of skills than being the strongest engineer in the room — and almost nobody hands you those skills on the way through.
Scale and responsibility
Organization
A 39-person delivery organization — 10 on-site and 29 offshore personnel — supporting a retail footprint of 300+ stores.
Budget
A $5.2M allocated budget for network and voice hardware purchasing, covering new stores and replacement equipment. I tracked the spending and reported asset additions and removals to Accounting each month. Separately, $1.02M of recurring annual telecom cost removed without reducing service.
Program
Architectural direction on a three-year, $154M network modernization spanning more than 6,500 locations — holding technical governance through a leadership transition rather than owning the program itself.
Teams built
Three technical teams built from the ground up, totalling 19 direct reports, in an industrial services environment.
Career history
- Mar 2026 – Jul 2026 Principal Infrastructure Architect / Engineer O’Reilly Auto Parts — contract engagement, completed July 2026
-
Oct 2023 – Feb 2026
Manager, Core Technologies — Network, Voice & Database Academy Sports + Outdoors — infrastructure and IT operations leadership across 300+ stores
-
Aug 2022 – Oct 2023
Team Lead, Network Operations Tailored Brands — 1,100+ locations
-
Sep 2019 – Aug 2022
Senior Network Engineer PennComp — virtual CIO advisory across seven commercial accounts
-
Nov 2018 – Present Founder & Principal Doleman Enterprises — telecommunications brokerage; carrier partnerships, circuit delivery, and contract negotiation for commercial customers
-
Feb 2012 – Nov 2018
Senior Manager / Network Architect Brock Group — three technical teams, 19 direct reports
Capabilities
Leadership
Infrastructure and IT operations strategy, budget ownership across CAPEX and OPEX, team building and technical hiring, vendor and MSP governance, contract negotiation, SLA and KPI frameworks, business–IT alignment.
Architecture and engineering
Multi-site enterprise network design, SD-WAN, high-availability headend and core design, cloud and hybrid infrastructure, unified communications and UCaaS strategy, data center lifecycle and relocation, security architecture and network access control.
Platforms led at team level
F5 and Citrix ADC / NetScaler application delivery environments. I have been accountable for these platforms through the engineers and managed-service partners who run them, rather than as current hands-on engineering work.
Environments
National retail, oil and gas, industrial and environmental services, professional services. On-premise, cloud, and hybrid. Internal teams, managed service providers, and mixed delivery models.
Continuous learning
Infrastructure leadership means keeping current on what is arriving next, not only on what is already running. Recent coursework:
Introductory credentials, verifiable at Google Skills. Listed as evidence of continued learning, not as machine learning engineering experience.
Résumé
A conventional two-page résumé is available for applications and ATS submission.