I make it work: secure, and built around the people who use it.

certifications
Microsoft Azure Fundamentals (AZ-900) Dynamics 365 Finance & Operations Fundamentals CompTIA A+

Azure · Windows Server · Linux · Cisco · VMware · Hyper-V · Docker · SQL Server · PowerShell · Python · Bash

// 01 how I work

One approach, applied to very different problems.

Twenty-plus years across networking, systems, cloud and automation. The problems change; the core way I work them doesn't.
These five principles are that approach, in the order I apply them, each one shown in real work.

  1. Know it to the core.I take neglected systems apart until I know them cold, then rebuild them so a fault traces cleanly from the wall jack to the switch port. Untangling the mess is how I come to trust it.see it in the rack rebuilds →
  2. Secure it by default.I find exactly what a system needs to run, then grant only that and lock the rest down. Least privilege, enforced by policy rather than trust.see it in the Sage lab →
  3. Deliver it methodically.Diagnose, document, propose, verify, in that order. I work a problem end to end and write it up, so the fix is something anyone can check and repeat.see it in the kindergarten proposal →
  4. Build it around people.I don't just run technology; I shape it so it works for people without them having to think about it. Nothing beats watching someone get time back every time a solution I rolled out kicks in.see it in the QoS fix →
  5. Build the tools that build the next ones.Tools exist to move you toward a goal, and getting there usually takes tools working with other tools. I like building the one that makes the next one easier.see it in the account provisioning →

// 02 skills

teal production grey learning / lighter

Cloud & Identity

Azure (VNets, NSGs, IAM)Entra ID Conditional AccessAD & Group Policy M365 / Exchange OnlineAzure Data (Lake, SQL, Blob) IntuneDefender for Endpoint

Network & Security

Routing / switching / VLANsFirewalls (WatchGuard, pfSense, iptables) VPN · IPsecDNS · DHCP TLS / certificatesMonitoring (SNMP, SolarWinds, Snort) Linux hardening (SELinux, Fail2Ban)Incident response Cisco IOSWi-Fi / 802.11

Platforms & Virtualization

VMware / ESXiHyper-V CitrixWindows Server · Linux Backup & DR (Veeam)Docker · Kubernetes

Data & Reporting

SQL Server / T-SQLERP (Syspro, D365) Reporting (PHP, Crystal Reports)VBA / Excel Power BI

Automation & AI

PowerShellBashPython Azure CLIARMGit / GitHub Actions / CI-CD Ollama · n8n · local LLMsClaude API toolkitREST APIsJSON / YAML

Hardware & IoT

ESP32 / C++Arduino / ESP-IDF Sensors & circuitsMicrocontroller web UIs MQTT

// 03 experience by layer

From the cable to the cloud, and every layer between.

My experience mapped to the OSI model, plus the domains that cut across it. Open any layer to see the proof behind it.

L1Physical- cabling, servers, power, printers, ESP32▸
L2Data Link- switching, VLANs, STP, Wi-Fi▸
L3Network- routing, firewalls, VPN, Azure VNets▸
L4Transport- TCP/UDP, QoS, port knocking▸
L5-6Session / Presentation- TLS, certs, encryption▸
L7Application- DNS, email, web, SQL, ERP▸
L8People- teaching, documentation, the go-to▸
+Identity & Policy- AD, GPO, Entra, Conditional Access▸
+Platforms- VMware, Hyper-V, Citrix, containers▸
+Automation & AI- PowerShell, ARM, local LLMs▸
+Operations & Resilience- backup, recovery, incident response▸

// 04 documents

Written to be acted on.

all documents →

// 05 featured stories

Three times I found a way.

all stories →

// 06 beyond the keyboard

A maker, on and off the clock.

I'm a maker at heart. I like building things that have a real use and purpose, with a design that is both elegant and functional. When I'm away from the keyboard I'm usually in the woods, or out in the shop making something with my hands.

A lot of that happens at the CNC, where I enjoy the design side as much as the carving. I designed my own cribbage board and have sold dozens of them. I also turn and carve bowls, pens, and plenty of other woodworking projects, tons of them over the years. And I love dogs.

It's the same instinct that shapes how I build systems. I want what I make to last, and to actually get used.

see some of my work

// 07 contact

// reach me
~/prod/portfolio$ ./contact.sh






 Jason R. McGinn                              
 IT Coordinator · Systems & Infrastructure    
                                              
 email     mcginn@netstatedata.ca             
 web       netstatedata.ca                    
 linkedin  linkedin.com/in/jason-mcginn       
 github    github.com/jasonmcginn             
# open to roles in the Moncton area, or remote
~/prod/portfolio$
Download Resume Email me