Kris Thompson, circa 1975. Ontario, Canada.

Kris — BC
(Before Computers)

Kris D. Thompson

Communication Systems Engineer
Professional Engineer (P.Eng.) Ontario
Cisco Certified Internetwork Expert (CCIE) #1226

Communication Systems Engineer based in Austin, Texas, operating independently through Austin Voice Data LLC since 2010. Current focus: IoT data pipelines, cloud infrastructure, web application development, and the CLODE_MODE agent guidance platform. Available for direct engagements.


Thirty-plus years across communications, networking, cloud, and IoT. Full lifecycle — documentation through design, implementation through operations. Engineering means finding what is actually true and acting on it, regardless of assumptions, vendor recommendations, or sunk costs. I am a gifted problem solver. I use it.

// Story

Ontario, Canada — The Beginning

Raised by independent thinkers.

Grew up in Ontario, raised by community builders and independent thinkers. Early wins in math and accounting competitions. Extensive electrical work. Restoration of pioneer log homes. Outdoors camps, swim team. A foundation built on making things work, not just understanding why they do.

Queen's University at Kingston — 1984–1988

B.Sc. Electrical Engineering (Computer)

1st-year Class President of Science '88. Four years on the Engineering Society Council, finishing as VP of Society Affairs. Founded Science Quest — a summer camp for youth. Awarded the H.G. Conn Award for outstanding contribution to the Engineering Society. Elected permanent Class President of Science '88 — which means I organize the reunions. Fun.

Two summers at General Motors, Oshawa — part of the co-op education program. First summer: Paint Shop engineering, specializing in paint circulation systems. Second summer: quality control supervisor in the Body Plant, managing a team of quality inspectors overseeing welding robots.

GM was mid-transformation at the time — Japanese manufacturers had vaulted ahead on quality and the industry knew it. We were trained in quality circles, statistical process control (SPC), and related practices. Seeing that shift up close, at the production floor level, made quality a discipline rather than a department.

In third year, I received the Bell Canada Award, which came with a summer internship. That summer was spent building a database to cache special circuit lookups for early digital service circuits — a project known as Local Loop Lookup. Getting to know the last mile. Internet access engineering would later become a defining passion at Cisco Systems: connecting people and things to the internet, from the edge in.

Through these summers, I received what amounted to a co-op education alongside a top academic program. Theory and practice, running in parallel.

Toronto — Northern Telecom, 1988–1990

Systems Application Engineer

Northern Telecom was a world-class engineering organization. Our office north of Toronto alone had 300+ engineers performing disciplined project development for telecommunications customers. My client was exclusively Bell Canada, provisioning and expanding city telephone systems across the Golden Horseshoe — Toronto to Niagara Falls.

Also during this time: helped introduce the Macintosh personal computer onto engineers' desktops. Computing can be fun and flavourful.

The primary work was systems application engineering of the DMS-100 — the world's first fully digital telephone switching system. Developed skills and experience with ISDN, SS7 digital out-of-band signaling, and Subscriber Loop Carriers (SLC) — extending the reach of the digital central office into the last mile.

Achieved my Professional Engineer (P.Eng.) license in Ontario — still active.

— 1990 · Austin, Texas · In search of cultural variety and live music.

United Services Automobile Association (USAA) — San Antonio, 1991–1992

On-Site Telephony Engineer

USAA operated the world's largest call center. On-site engineer supporting the SL-100 — a DMS-100 city-class switch with a business software load. Exposure to very large business operations.

Apple Computer — Austin, Texas, 1992–1994

Info Systems & Telecom (IS&T)

In 1992, Apple Computer opened a customer support centre in Austin and I was hired to join the IS&T team. Great experience across a wide variety of networking, telecom, and servers.

Minicomputer system response time: 7–8 seconds. Unacceptable. Vendors recommended expensive, disruptive hardware and software changes. Ran a Sniffer capture, found the real cause, fixed it. Response time: under 1.5 seconds. Cost: $0. That was the day problem management became a discipline, not a job title.

Direct Response Centre (DRC)

Senior support for all Apple Networking and Communications products, working alongside the Software Development team. An extraordinary group of people doing extraordinary work.

Supported the Apple Server — Apple's first shift to a Unix-based operating system, the foundation everything Apple runs on today. Front-line support during one of the company's most significant architectural transitions.

Active participant in the early internet: WAIS, Gopher, and the tools of the moment. One day NCSA Mosaic showed up. Everything changed.

A short rotation to Cupertino to cover an engineer on sabbatical — assigned Printer and Fax escalations. Three weeks. The team held a Thank You ceremony. Forty-six escalations, forty-six resolved. It was a good three weeks.

The Cupertino rotation produced contacts at Cisco Systems. Before long, packing up and driving to California.

Cisco Systems — Three Rotations, 1994–2008

Where the internet was being built.

Three separate engagements with Cisco over fourteen years, with intentional breaks between — a personal practice I am proud of and encourage in others. Cisco kept calling back. The work was worth returning for.

Technical Assistance Center — Mountain View & San Jose, 1994–1996

Joined before Cisco crossed $1B in annual sales, as they were moving to their giant San Jose campus. CERT2 — Customer Engineering Response Team: AppleTalk, DECNET, OSI. Collaboration, fault isolation, documentation, defect resolution. We had the ability to isolate and resolve issues in our monolithic codebase within a single day. Customer Success Engineering was our division — baked into everything we did, and a cornerstone of Cisco's success. Customers are not always right, but they always come first.

Promoted to the inaugural TAC Escalation Team — the best problem solvers in the building. Quickly identified that Cisco's Knowledge Management was in disarray. Customers were getting outdated, inaccurate content. Fixed it. Worked directly with the documentation team to rebuild the foundation.

Field Engineering — Austin, Texas, 1997–2001 (Freelance)

The Network Cowboy goes into the field. Freelance consulting for Cisco TAC, reporting to a Senior VP. Award-winning Case Studies and Design Guides. Founding member of the eSupport initiative, providing thought-leadership on Level 0 support — making the website and docs actually work so customers can self-serve before picking up the phone.

Major engagements in central Texas: Dell Computer, and a return to USAA — this time on the data side, providing technical leadership to the Cisco team and the customer as they extended the life of a massive Token Ring network while preparing for the transition to Ethernet. Built a small team in Austin, recruiting the best from the University of Texas.

Remote Operations Services — 2004–2008

Cisco acquired NetSolve. I was recruited back. Joined the team supporting Cisco CallManager (enterprise PBX). Arrived to find an absence of technical process. The first upgrade plan handed to me was on a Post-It note.

With my former eSupport partner, built a Wiki to harvest and refine operational knowledge. Massive success. Transformative. That Wiki became a launching pad — my partner went on to build knowledge systems for senior U.S. government organizations. We shipped ITIL-styled process where there had been Post-It notes.

OuterNet — 2008–2010

A soft landing into independent engineering.

Joined OuterNet alongside a former Apple DRC teammate. Deeper project management and network engineering: complex routing, multi-phase system deployments, sustained engagements that required real ownership — not ticket-closing. The transition toward operating fully on my own.

Austin Voice Data LLC — 2010 to present

Basically, Kris Thompson.

Austin Voice Data is my company. The founding principle: own the right to pick and choose projects and customers. No layers. No dilution. Full accountability.

Sustained work with Texas State Agencies — DMV, TxDOT, ERS, TPWD, DPS. Voice, data, and IT security network infrastructure. Systems upgrades, new technology deployments, advanced technical support.

A business venture involving IoT-enabled exit signs introduced me to LoRaWAN — low-bandwidth, long-range wireless sensor networks. I fell in love with the data pipeline and what IoT makes possible: measuring and reporting on the physical world. It also gets you out of the office and into the field, which suits me fine.

Later joined Everynet — a global LoRaWAN network provider — as a Senior Systems Engineer to provide thought leadership, engineering discipline, and tools development. Built data pipelines for operational monitoring and a Django (Python) web application for field surveys, performance analysis, and empirical validation of RF coverage models. Replacing conjecture with measurement.

// Selected Work

Knowledge Engineering · Cisco · 1997–2001

eSupport & Cisco Design Guides

Award-winning case studies and design guides. Founding member of the eSupport initiative — the principle that customers should be able to solve problems themselves before calling in, if the documentation is actually good. Recruited and built a small team from University of Texas graduates.

Network & Systems Engineering · Public Sector · Texas

Texas State Agencies — Network & Systems Infrastructure

Network and systems engineering across multiple Texas state agencies — routers, switches, firewalls, and contact centers. Clients included TPWD, DMV, DPS, ERS, TFC, and the Texas Historical Commission (THC). The THC engagement included modernizing the small infrastructure at their physical locations throughout Texas — a hands-on opportunity to get out of the cubicle and into the field. The kind of work where quality is not optional and the system cannot go down.

DevOps · Software Modernization · Law Enforcement

Lexipol — Law Enforcement Policy Manuals

DevOps and software modernization for Lexipol, a leading provider of policy management for law enforcement agencies. Work focused on containerization, continuous integration, and continuous deployment pipelines.

It was here that I developed a considered disdain for Sprint and Scrum as practised — autocratic deviations from the principles they claim to follow. The Agile Manifesto is worth reading. Most teams implementing "Agile" have not read it.

IoT · Data Pipeline · Field Engineering

LoRaWAN Operational Monitoring — Everynet

Data pipelines for LoRaWAN network performance history. Django web application for field survey support and RF coverage validation. Replaced assumption-based coverage models with empirical measurement. The field engineers used it. It worked.

Disaster Relief · NGO

AID_REQUEST — Disaster Aid Intake System

Built a full web application for an NGO doing personal aid after disasters. Aid request intake, mapping, processing, and workflow. Purpose-driven engineering at its most direct: people needed help, the system had to work, and it did.

AI · Developer Tooling · Open Source (in progress)

CLODE_MODE — Agent Guidance Platform

AI agents, left to their own devices, produce CRAP: Context Random Agent Programming. They cause entropy in the codebase and resist staying on target. CLODE_MODE is a platform and thematic framework — a universe of characters providing values and guidance to agents — so they produce work worth keeping. Built for my own use first. Intended for release. See: clodemode.com

// Operating Principles

On problems Find the real cause. Not the vendor's preferred cause. Not the one that requires the most billable hours. The real one.
On tools FOOLS_WITH_TOOLS: Flexible Objective Oriented Logic Systems. The tool serves the objective. The objective does not serve the tool.
On AI agents Agents without values produce CRAP. Give them a framework. Hold them to it. Then verify what they built.
On credentials Professional Engineer (P.Eng.) Ontario — active, accountable, bound by a code of ethics. Cisco Certified Internetwork Expert (CCIE) #1226 — numbering began at ~#1024, placing this among the first ~200 issued worldwide. The ISP-DIAL exam had a 3% pass rate on its first 100 attempts; I was one of three who passed, then refactored the exam because it was failing qualified engineers. Also proctored the CCIE lab in Halifax for a month. Not renewed — renewal is a vendor trap. The knowledge doesn't expire because a fee wasn't paid.
On work Make a difference. Not a margin. I have no interest in abandoned shopping carts or security theatre. Measure the physical world. Fix the broken system. Ship the thing.
On independence Intentional breaks from employment are a deliberate choice, not a gap. A quality, self-led life requires owning your time. The right client understands this.

// Contact

Email kris[at]austinvoicedata[dot]com Web austinvoicedata.com Location Austin, Texas Licensing P.Eng. Ontario · CCIE #1226

I work directly with clients. No body shops. No sub-contractor chains. If you need someone to support your network lifecycle — isolate the gremlins, document the systems, implement the changes, and instrument with telemetry — let's talk.