About

Twenty-five years of building things that run.

Solutions Consultant and Full-Stack Developer based in Wausau, Wisconsin. Twenty-five years across enterprise infrastructure, automation, cloud, and identity. MCSE-certified. Microsoft Azure-certified. The work below is the through-line.

Jonathan Nelson

I'm Jonathan Nelson, a Solutions Consultant and Full-Stack Developer based in Wausau, Wisconsin. I started in 2000 — graduated from CEI College in Anaheim, picked up MCSE early, and have been designing, deploying, and running enterprise IT ever since. Today I run Integratech and pick the engagements where senior practitioners actually move the needle.

The work has been wide. Banks, law offices, healthcare-adjacent firms, environmental services, mid-market IT shops, and the corporate operations of small founders. VMware, HP ProLiant, Cisco and Meraki, Active Directory, Microsoft 365, Azure. Genetec Security Center for the security-engineering stretch. The common thread is the same: a system that has to keep running, with a small team and a real budget.

Right now the most interesting work is at the intersection of LLM-powered workflows, internal tools, and operational automation. Systems that take a brittle hand-off between humans and replace it with a pipeline that observes itself and tells you when something drifts. Full-stack TypeScript and Python, n8n and custom webhooks, Postgres, the SQL that holds the whole thing together. The sweet spot is engagements where the technical lift is real but the team is too small to carry a dedicated platform engineer.

Principles

How I work.

01

Operational discipline.

The system has to survive after I leave. That means logging, alerts, runbooks, naming, and the boring kind of testing — not the demo. If I'm not willing to put my own pager on it, I won't ship it.

02

Foresight.

I plan for the second migration, not the first launch. Schemas with room to grow. Auth with room for SSO. Integrations with retry and replay. The point is to write a system that the next engineer — including me, twelve months in — can extend without rewriting.

03

Collaborative problem-solving.

Twenty-five years of getting paid to make things work means I've learned how to work alongside the people who already run the business. I document. I hand off. I ask the question that surfaces what's actually broken, not what was reported. Senior practitioner means I do the unglamorous parts on purpose.

Stack

What I reach for.

Enterprise infrastructure

VMware vSphereHP ProLiantWindows ServerHyper-VData Center OperationsHigh AvailabilityPatching & Lifecycle ManagementBackup & Disaster Recovery

Cloud & identity

Microsoft AzureAWSActive DirectoryMicrosoft 365Entra IDGoogle WorkspaceGAMCloud Console

Database & integration

SQLREST APIsWebhooksFastAPIPostmanSystem IntegrationData Migration

Networking & security

CiscoCisco MerakiMeraki MXIP SubnettingGenetec Security CenterEnterprise Access ControlNetwork MonitoringMXToolbox

Leadership & operations

Team LeadershipDirect-Report ManagementCross-Functional Project CoordinationVendor & Stakeholder EngagementProcess ImprovementQMS / OSHA / AHERA / GDPR AwarenessConnectWiseSOP Development

Development & automation

PythonPHPJavaScript / TypeScriptPowerShellGoogle Apps ScriptReactNext.jsn8nZapierHubSpotZohoActiveCampaign

Credentials

Education & certifications.

  1. Education

    CEI College — Anaheim, CA · 2000

  2. Certification

    Microsoft Certified Systems Engineer (MCSE)

  3. Certification

    Microsoft Azure

  4. Certification

    CompTIA A+

  5. Certification

    HP Technical Certifications

  6. Certification

    Kyocera Technical Certifications

Off the clock

Outside the work, mostly Wausau — woods, lakes, the kind of weather that makes you appreciate the systems that stay up.

Want a senior practitioner who also writes the docs?