Home / About
Nearly five decades seeing technology from every chair in the room.
Mark Kiessling has spent approximately forty-seven years in technology — as a programmer, software and systems architect, database designer, network and security practitioner, project and department leader, and technology executive. Today that experience is offered as one thing: independent judgment for the decisions that are expensive to get wrong.
Where it started
Mark's path into technology began the way a great deal of durable engineering does — by taking things apart to understand them, and putting them back together still working. The computer offered the opposite thrill: taking nothing and building whatever someone needed. He wrote his first program around 1979, stepping a cosine function from positive toward negative to plot circles on a screen and animate them by varying the radius. He has been turning ideas into working systems ever since.
That instinct never left. Over nearly five decades it grew from curiosity into discipline: understand the real problem, build exactly what serves it, and be honest about what it will and will not do. Everything that follows is an extension of that first idea.
The builder
Mark began close to the machine and never fully left it. His hands-on work runs from low-level graphics and game engines to communications software, relational database design, web systems, and enterprise architecture. That range matters for a simple reason: he can read a system the way the people who built it do, without waiting for a translation. When a vendor or a team explains why something cannot be changed, he knows which explanations are real constraints and which are habits.
The leader
Over the years Mark moved from writing systems to running the organizations that build them. He has led technical teams and departments, carried profit-and-loss and budget responsibility, drafted contracts and technical specifications, hired and evaluated technical staff, managed vendors, and directed international development resources. He has held executive technology roles including CTO and CIO. He has represented organizations in dealings with major carriers, utilities, banks, and government-related bodies. Leadership, for Mark, is not a title — it is accountability for outcomes other people depend on.
The fixer
Much of Mark's career has been spent entering confusing or failing situations, finding the real cause rather than the loudest symptom, simplifying the problem, and restoring accountability. Troubled projects, inherited systems, disputes between technical leaders, and vendor commitments that stopped adding up — these are the rooms where his experience earns its keep. The goal is never drama. It is a path leadership can understand and defend.
The advisor
What ties the builder, the leader, and the fixer together is judgment: helping people make sound decisions before committing money, staff, reputation, or years of effort. That is the whole of Judgment Technology Advisory. Mark does not sell products, take vendor commissions, or push a framework. He gives an experienced, independent reading of the situation and the questions that must be answered first.
That judgment now includes hands-on artificial-intelligence systems work — see Mark's AI Systems.
How the career actually developed.
Not a straight line — many of these responsibilities overlapped for years at a time.
Mark began close to the machine in an era when a developer had to understand hardware, memory, and the business at once, then grew into architecture, leadership, and executive responsibility. C# and .NET belong to the most recent chapter of that story — not its beginning.
Where the experience comes from.
A single career that touched most of the disciplines a modern technology decision now spans.
The person
Mark is a United States Navy veteran. He is a direct communicator and an independent thinker who values an honest answer over a comfortable one. Clients tend to work with him precisely because he will tell them what he actually sees — including when he is not the right person for the job.
Bring experience into the room before the decision is made.
Tell Mark the decision you are facing or the project that has you concerned, and who should be involved.