The art of refining the complex into the intuitive.
I'm James Huschle — 25 years of Fortune 500 technology leadership, now applied to cloud architecture, machine learning, and AI-native systems. I've managed engineering teams, built greenfield platforms, and delivered on roadmaps that crossed departments, continents, and budget cycles. The rarest thing in technology isn't technical skill — it's someone who can translate fluently between the engineering team and the people writing the checks.
"Syntactic sugar" is a programming term for a layer of elegance added to a language — it doesn't change what the machine can do, but it profoundly changes how the human feels working with it. That idea sits at the center of everything I build. Technology should be intuitive. Systems should make sense to the people who fund them, build them, and use them.
We are at an inflection point that rewards an unusual combination of skills. Large language models are, at their core, the marriage of computation and language — and applying them to real business problems requires someone who understands all three fluently. I didn't pivot to this moment. I've been building toward it for 25 years.
I came to technology through an unusual door: a BA in English, a BS in Computer Science, and an MBA from the Carlson School at the University of Minnesota. That combination wasn't accidental. Language shapes how people understand systems. Business shapes which systems are worth building. Engineering determines whether they hold together under pressure.
At IBM I built tools that crossed international development teams and localization pipelines. At St. Paul Companies and Travelers I spent 15 years moving from systems engineer to Senior IT Director — managing organizations of 25 engineers, delivering $4.5M–$11M programs, rolling out platforms to 25,000 users across global operations. Since 2023 I've been building with the current generation of tools: serverless AWS architecture, ML pipelines on SageMaker, and AI-native systems that go well beyond chatbot wrappers.
If you need someone who can sit in the architecture review and the budget meeting and the engineering standup and speak credibly in all three rooms — that's the job I've been doing for 25 years.
Engagements range from architecture reviews and strategic advisory to hands-on delivery. Every engagement starts with understanding the business problem, not the technology solution.
The opportunity isn't chatbots. It's systems that act — that reason across tools, data sources, and workflows on behalf of the business. I build AI-native applications that go beyond wrappers: semantic evaluation engines, knowledge pipelines, edge inference systems, and agentic workflows that integrate with the systems you already run. If your AI strategy is "we added a chatbot to the website," we have work to do.
This is where language, computation, and business converge. Large language models aren't just a new tool — they're the first technology in decades that rewards the combination of linguistic fluency, engineering depth, and business judgment simultaneously. That intersection is where I work.
I hold current AWS certifications in solutions architecture and machine learning, and I've designed multi-tier serverless systems, VPC architectures, and CI/CD pipelines as hands-on work — not just coursework. What I bring beyond the technical foundation is 25 years of knowing how technology decisions play out inside organizations: what gets funded, what gets maintained, and what quietly becomes someone else's problem in three years. I design with that perspective built in.
I've run the programs where the answer was "we need to rebuild this, the right way, without stopping the business." Legacy platform migration, application portfolio rationalization, large-scale modernization with real budgets and real consequences. The technical work is the easy part. The hard part is keeping the organization moving while the floor is being replaced beneath them.
Sometimes the most valuable thing isn't someone to write the code — it's someone to tell you what to build, in what order, and why. I work with leadership teams to develop technology roadmaps, evaluate vendors, structure engineering organizations, and translate between what the business needs and what the technology team can realistically deliver.
These projects represent hands-on work from the last few years — built independently, architected from scratch, and deployed to real infrastructure. I'm releasing them publicly over the next month or two as I get each one to a standard I'm comfortable putting my name on. Know-It-All is live now. The others are coming.
Serverless ML-powered learning — built to understand meaning, not match strings.
A web application that turns terminology-heavy subjects into interactive learning experiences. Users define a knowledge domain and its terms; the system evaluates answers semantically — understanding what you meant, not just what you typed — using a custom cross-encoder model quantized for low-latency inference without a PyTorch dependency.
The architecture is a six-stack AWS CDK deployment — network, database, auth, backend, frontend, and monitoring — each independently deployable. Auth runs through a custom Cognito registration gate with pre-signup Lambda approval. CI/CD via GitHub Actions includes security scanning on every push: Bandit, Checkov, TruffleHog, and pip-audit.
If you'd like to explore it, you can register for an account at the link below. Accounts aren't provisioned automatically — registration lands in a review queue and access is granted manually. Why the gate? Two reasons, both honest: bots are a real nuisance, and the free-tier cost model depends on keeping traffic predictable. Automated signups solve neither problem and create new ones. So a human reviews each request. If you're a real person who wants to poke around, you'll hear back.
Privacy-first home security. Face recognition runs on-device — raw video never leaves your local network.
Source available on GitHub at release.
A local-first knowledge pipeline with anonymous search, LLM-assisted triage, and human review — wired via Model Context Protocol.
Source available on GitHub at release.
An MCP server that gives AI assistants structured, approval-gated access to manage a home lab network.
Source available on GitHub at release.
Converts documents to audiobooks using self-hosted text-to-speech inference. Markdown, PDF, Word — in, audio — out.
Source available on GitHub at release.
Whether you have a role in mind or just want to connect, I'm happy to have the conversation.