I’ve said this before, and I’ll say it again, and again.
I’m not an engineer.
I don’t know how to code.
I love using software though.
In fact, I’m obsessed with software that enables Semitechnicals to do stuff previously only possible with code.
Does that make me “non-technical”?
Well, in my opinion, everybody, especially if they work in tech, has some level of technical aptitude and sits somewhere on the technicality spectrum.
Semitechnicals act as a bridge between the more technical teams – typically data and engineering – and the less technical teams, particularly GTM teams, as they’re the ones putting data to use in their everyday tools.
Today, many different teams act as that bridge team, and they go by many different names. However, Ops still remains the easiest term that encapsulates the work done by bridge teams.
You can call them RevOps, BizOps, MarketingOps, GTM Engineering, Value Engineering, or whatever else you fancy; the job remains pretty much the same, and the people executing it are all, well, semitechnicals.
Semitechnicals don’t build features or orchestrate data pipelines – instead, they set up processes that enable more technical and less technical teams to collaborate effectively.
Semitechnicals understand the priorities, constraints, and workflows of both. They have a sound understanding of all the systems and can translate requirements into automated, well-documented workflows.
Most importantly though, semitechnicals know what’s good for the business.
They help GTM teams utilize technical assets (like internal tools and data models) in their everyday tools to drive growth. At the same time, semitechnicals help data and engineering teams understand the impact of their work on the business.
So, who is a Semitechnical?
A semitechnical is someone who uses software and data to solve everyday business problems.
A semitechnical doesn’t code like an engineer, but they do think like one — enough to architect, automate, and document critical workflows.
They have a sound understanding of data foundations.
They can read and write enough HTML, SQL, and JSON to get their way around whatever tools and data they need to.
Moreover, throw any piece of software at them, and they will use the heck out of it!
But…
That’s just one flavor of a semitechnical
I know this guy called William Classic. He’s one of the few people I know who uses AI every day to get better at his craft – telling stories and uplifting brands via amazing videos.
He not only has the technical ability to work with video equipment of all types, but also knows how to amplify the impact of his work by incorporating software in his process.
And in this line of work, process is everything.
William might not know what SQL stands for, but he is damn fucking technical when it comes to using powerful creative tools.
He has this rare ability to take the content he consumes and blend the ideas with his own to create masterful work.
So, would you consider William “non-technical”?
Wanna share your semitechnical perspective? Leave a comment here or on LinkedIn.
