I speak fluent engineer, and fluent boardroom.
I have spent twenty five years working the gap between what a technology actually does and what a business actually needs. I started deep in the infrastructure, the domain controllers and the 2 a.m. bridge calls, then moved into the room where the buying decision gets made. I am at home in both. And when the tooling in between is slow, I tend to go build a better one.
The short version.
A title is a lossy way to describe a person. Here is what sits underneath mine.I am the person a team calls when the problem sits between two disciplines and nobody quite owns it. Deep enough in the technology that the engineers trust me. Fluent enough in the business that the executives do too. And more interested in building the fix than filing a report about it.
Why that is useful. Most people are a specialist or a generalist. I am the wiring between them. I can go deep on device security, silicon, lifecycle cost and AI on the edge, then hand a CFO the one sentence that makes the decision obvious. A colleague once put it better than I could: "technically competent, and business minded enough to sell the vision to a business user." I have spent a career making those two people the same person.
What that looks like on a Tuesday. I carry a number like everyone else. I also do the quieter work: the tool nobody asked me to build, the risk I raise before it lands, the new hire I get to their first win. It rarely fits in a single line on a scorecard. Teams remember it anyway, which is usually how I end up on the short list when someone needs a hard call checked.
How I work.
Four habits that show up whether I am in a server room, a deal, or a design review.I read a stalled deal the way I used to read a Sev 1 bridge. Cut the noise, find the single thing that actually moves it, ignore the eleven that do not. It is rarely the thing everyone is arguing about.
When something is broken for me, it is broken for a few hundred other people too. I would rather lose a weekend shipping a small tool than win an argument about who should have. A few of those tools outlived the argument.
The server room wants the firmware detail. The boardroom wants the number on the risk. Same product, two languages. I bring the one the room actually needs and keep the other in my pocket.
I will call a dead deal dead while there is still time to do something about it. Not everyone loves that in the moment. Most of them thank me by the end of the quarter.
I never really left engineering.
I came up on NetWare, Active Directory, clustering, the domain controller you do not reboot on a Friday. I moved into sales and never lost the itch to open the box and see why it works. That part I would do for free.
The flip side is simple. I would rather a room trust me because I know the thing than because of where I sit on a chart. Titles have never been the point. The work is.
Strategic. Achiever. Ideation. Relator. Intellection.
Strongest pull by a distance: the application of technology, ahead of 94 percent of the business people it has measured. Lowest on the list: running an org chart for its own sake.
Two instruments, years apart, describing the same person. None of it surprised me. It just put names to things I already do.
One move, on repeat.
The examples change every few years. The move never does.Here is the whole trick, and I have been running it for twenty five years. I find a problem a lot of people share, usually because it is slowing me down too. I turn it into something that outlives me: a framework, a template, a talk, a tool, and lately an AI package. I get it adopted. Then I go find the next one. Almost none of it was ever my actual job. That is rather the point.
From a PDF killer to shipping AI packages.
The field was burning hours in static PDFs, so I taught myself web and AI tooling and built a fast product reference app. It is now a deployed cloud app with real environments and access controls. The same instinct, scaled up, became installable AI packages that turn whole roles into something a colleague can run: an executive assistant, and a full specialist toolkit, built with the rigor of evaluation harnesses and one command install.
A framework a whole org still runs on.
In my field engineering years I conceived and led a support delivery framework: how engagements got scoped, kicked off, run, and reviewed. It was not built for one customer. It became the operating model for the region, and an evolved version of it is still in use across the organization today, years after I moved on to something else.
- Managed IP and standard engagementsauthored content, delivered by field engineers worldwide
- A customer satisfaction post mortem and recovery programevery engagement in the country, plus the coaching to get unhappy customers back on track
- New hire onboarding and mentoringa steady stream of engineers, six of them formally in a single year
- The worldwide best practices curriculum for my specialist communitybuilt it, trained the field on it
- Top rated speaker at the company's global sales conferencehundreds of sellers a year, voted best of the event
- The compete narrative and sales collateralrecognized as the worldwide authority; it changed how the field pitched
- A device evaluation frameworkturned how does it feel into numbers a customer could sign off on
- The product reference web appreplaced the PDFs, now a deployed cloud app, engineering picked it up
- Deployment and adoption playbooksreused across customer rollouts
- A seat on the worldwide seller advisory councilone of about twenty one, carrying the field's reality to the roadmap
- Installable AI packages that productize whole rolesan executive assistant and a specialist toolkit, with eval harnesses, servers, and one command install
- Reusable building blocks and a memory systemso the next package starts further ahead than the last
None of these were the job I was hired to do. They all came from the same place: if it is slowing me down, it is slowing a hundred other people down too, so I build the thing once and give it away. That is the part of me that never fit on a scorecard, and it is the part I am proudest of.
What colleagues say.
Three, kept short, chosen for what they say about the work. First name and role."One of my go to people. When I need a gut check on a hard call, you are on speed dial."Jack · GM
"I would walk into any deal with you and expect to win. Looking forward to the next one."Chris · Account Technology Strategist
"A real voice on the technical side, and a lift for the people who are not. You would not take no for an answer."Don · Sales Manager
The arc.
Twenty five years, one habit: learn the thing properly, then make it useful to someone else.Infrastructure, the deep end
NetWare, then Windows Server, Active Directory, Citrix, clustering, VMware. Eleven years of it at IBM, where I grew a customer's estate from a few hundred servers to a few thousand and became the person you called at 2 a.m., and the one you did not let touch the domain controller on a Friday.
Microsoft Premier Field Engineer
Four years keeping big customers' platforms healthy under real pressure. Credibility with engineers was not a line on a slide. It was the job description.
Technical Solutions Professional, Surface
The technical backbone behind the field's hardest pursuits. Kill the blockers, run the proof of concept, turn early customer scars into product feedback.
Surface Specialist
Carried a quota, and quietly became the person the field came to when the hard technical question or the ugly deal landed. The number was never the interesting part.
What is next
A role that uses the whole kit at once: the engineering depth, the business read, and the habit of building what a team is missing. This page is the short version of why.
How I operate.
The rules I keep coming back to, learned mostly the hard way.Understand it before you sell it.
Credibility comes after comprehension, never before. Learn the thing first. Then the pitch is just the truth, said well.
Build the fix, do not file a ticket.
A complaint helps one person once. A small tool helps everyone, quietly, for years. What is broken for me is usually broken for a few hundred others.
Say the inconvenient thing early.
I will raise the risk while there is still time to act on it. I have learned to read the room on delivery. I have not learned to stay quiet, and I am not planning to.
Lead by making others better.
Translate the hard part so the whole team can carry it. Get the new person to their first win. My best work tends to show up on someone else's scoreboard.
Outcome first, technology second.
Nobody buys the how. Start with what changes for the business, then show the technology as the reason it is true.
Ship, then improve.
My old failure mode was polishing something to death before anyone saw it. Now I get it in front of people early and let the feedback do the work.
Put me where the hard tech meets the real decision.
That is where I am most useful, and where I will make you the most. If you are building a team that needs someone who can hold their own with the engineers and the executives in the same afternoon, I would like to talk.