I build things that work.
I lead people who grow.
I never stop watching.
Builder. Observer. The person in the room who noticed what everyone else missed.
"He does what he says he'll do. Every time. And he always notices the person everyone else walked past."
Twenty years is a long time to watch how things actually work — not how they're supposed to work, not how the manual describes them, but how systems behave under real pressure with real people depending on them. Evan Heil spent those twenty years inside a single organization, which tells you something: he's not someone who runs from problems. He's someone who stays and solves them.
He came up from the production floor, which means he understood operations before he understood infrastructure. That sequence matters. When most IT leaders think about systems, they think top-down — architecture, policy, implementation. Evan thinks bottom-up: who touches this at 3 AM when something breaks, and what do they actually need? That inversion shapes every decision he makes.
What people who've worked with him tend to notice first isn't the technical breadth — though it's considerable — it's the consistency. He doesn't perform accountability. He doesn't perform leadership. He builds teams that don't need to be managed because they've been genuinely developed, equipped with tools and trust in equal measure, and then left to do their work.
He's also learned to treat AI as he treats any good tool: reach for it when it shortens the distance between the idea and the outcome, and put it down when it doesn't. That judgment — knowing when the tool adds value and when it just adds noise — is what separates it from familiarity.
He also makes things. Broadcast motion graphics, brand identity systems for streaming creators, digital compositing work distributed across online communities under aliases that predate his career. The same instinct that drives the IoT architecture in his home drives the animated overlay kit he produced for a Twitch streamer in Canada: build something that disappears into the background and just works, and let the person in front of it shine.
Learns by watching. Decodes systems, technologies, and people through pattern recognition and stored reference — without needing a formal instruction set to start.
Creates things designed to disappear. The satisfaction lives in the architecture, not the artifact — in knowing it works at 3 AM when no one's watching.
Notices asymmetry and acts on it. Has a documented instinct for the person being overlooked — in a room, on a team, in an org chart.
Leads by teaching and expanding capability. Earns loyalty not through authority but through consistency: does what he says, says what he means, gets out of the way.
A selection of creative and systems work spanning motion graphics, brand identity, enterprise systems, and digital compositing. Produced across professional, academic, and personal contexts under multiple brands.
When a legacy Classic ASP/Oracle platform hit end of supportable life and vendors couldn't deliver a fix in time, built and deployed a replacement .NET 8 Razor Pages system on personal initiative — AD-integrated auth, parameterized data access, real-time shift visibility restored before the gap could stall production.
End-to-end streamer brand system: logo design, OBS stream elements, animated overlays, and a five-tier subscription badge system built around a maple leaf mark — a nod to the streamer's Canadian identity. Each badge tier color-coded with a consistent medal ribbon device.
Sole-contributor platform migration consolidating 13 fragmented Excel inventories into one governed system trusted by 82+ users. Automated workflows watch for conflicting data and flag it the moment it appears.
Full brand kit including logo, scene elements, and animated notification overlays with neon glow borders and lightning animation coursing the perimeter — delivered as looping WEBMs for live OBS integration.
A self-service HR kiosk rebuilt from an AI-assisted first draft into a hardened, production-grade system — six languages, zero-login access, and a graceful fallback that keeps working even when a translation isn't ready yet.
Longevity at one organization isn't stagnation — it's depth. Each role added a different layer to the same foundation: how technology actually serves people under pressure.
Leads a four-person IS team providing operational coverage across multiple production shifts, with a ~$1.4M annual IT budget and relationships with 12+ technology vendors. When a legacy platform became a blocker and vendors couldn't deliver a fix in time, built and deployed a replacement .NET 8 OEE tracking system — then went on to independently architect a full SharePoint Online rebuild, consolidating 13 fragmented inventories into one governed platform serving 82+ users, and reverse-engineered an undocumented legacy label-printing service into a validated internal tool. Remains personally involved in end-user support and administers enterprise physical security platforms including Milestone XProtect and Lenel. Maintains IATF 16949 and ISO 14001 compliance documentation for the IS section and develops annual business plans, org structure recommendations, and semiannual budget forecasts.
Managed a technician team supporting 24/7 production operations. Served as primary support lead for MES and WMS platforms, including JIT-driven production scheduling. Coordinated IT integration for AGV and ASRS implementations alongside engineering, operations, and external vendors. Applied structured problem-solving to reduce downtime and improve system availability.
Progressed through technical and coordination roles providing direct end-user ticket and production peripheral support, alongside ERP (QAD, Glovia), MES (Tutelar Ujigami), and WMS deployments. Contributed to system design, testing, and user adoption across the enterprise.
Led inventory control operations for multiple Honda production lines. Applied Lean, Gemba, 5S, and JIT scheduling principles to manage supply chain and reduce waste. This operational foundation — knowing how production actually runs — directly shaped every technology decision that followed.
Franklin University · Columbus, OH · 2024
Dean's List · GPA 3.7
Coursera · February 2026
Coursera · Feb–Mar 2026
The things worth paying attention to — the trajectories, the questions without clean answers, and the places where the modern and the old ways are still negotiating terms.
The convergence of reusable spaceflight, fusion energy, generative AI, and quantum computing isn't a product cycle — it's a Kardashev-scale transition. The interesting question isn't whether it happens. It's who governs what comes after, and whether the governance structures we have are remotely adequate to the task.
The best infrastructure is the kind you stop noticing. A smart home that works invisibly, a team that doesn't need constant direction, a workflow that nobody has to think about — the design goal in all three cases is the same: reduce friction until the system becomes ambient. That's harder than it looks and more satisfying than most things.
Space resource extraction is coming faster than most policy frameworks are prepared to handle. The economic incentives are enormous; the legal architecture is genuinely unresolved. This is the asteroid mining question, and it's more interesting than it sounds — it's really a question about what property rights look like when there's no pre-existing sovereignty to anchor them.
Whether consciousness is a property of biological substrate specifically or of information processing patterns more generally is an open question — and not a trivially dismissible one. The answer has significant implications for how we think about AI development, about what we owe to other minds, and about what "mind" even means outside the context of neurons.
Running three days a week on a structured plan toward quarter-marathon distance. The same instinct that goes into systems architecture applies here: build a reliable foundation, iterate deliberately, track meaningful metrics, and resist the optimization drift that turns a functional training plan into an over-engineered one.
There's something worth preserving in how things were made before abstraction layers made it possible to not understand what you're building. The appreciation for craft, for material, for the physical consequence of design decisions — those instincts don't become obsolete when the tools change. They become rarer, which makes them more valuable.
Available for conversations about IT leadership, systems integration, creative technology, and implementation roles. Based in Canal Winchester, Ohio — open to remote and hybrid opportunities.