Who Gets to Call Themselves an Engineer

I keep noticing the same word in places it did not used to live. A marketer I know updated their title to Growth Engineer. A former colleague who has never written a line of production code now runs a function called GTM Engineering. The job boards have caught up, and Marketing Engineer, Growth Engineer, and GTM Engineer now sit in the same search results as Software Engineer and Mechanical Engineer, drawing from a completely different pool of people. Most of the people taking these titles came from sales, marketing, and operations, the roles that the industry spent two decades describing as the opposite of technical. I tested it on myself, and within days of adding the word to my own LinkedIn the inbound messages climbed above my average and the anonymous recruiter visits climbed with them, which told me the title was doing work before anyone had checked what was behind it.

There is a small flinch that happens when someone with an accredited engineering degree reads one of these titles. There is a quieter flinch in the person adopting it, the private question of whether they have the right. I have felt the second one. I want to take that question seriously, because the answer turns out to say more about how we credential work than about who is allowed to build.

The word is older than the degree

Engineer comes through Old French from the Latin ingeniare, to contrive or devise, which sits on ingenium, meaning natural capacity, cleverness, the faculty of invention. The same root gives us ingenious. For most of its life the word described a person who devised things, the operator of an engine of war, the contriver of a clever mechanism, the one who found a way. The professional sense we now treat as the real one, the licensed discipline with a curriculum and a stamp and a governing body, is a nineteenth and twentieth century arrival. The credential captured a word that had always belonged to ingenuity first.

So when a marketer who builds a self-correcting outbound system calls herself a Growth Engineer, she is using the word closer to its oldest meaning than the licensed civil engineer does, recovering a sense of it that predates the field she is supposedly borrowing from.

Look at the work, not the title

It helps to look at what the work is rather than what the title signals. A GTM engineer wires together a stack: a data source, an enrichment layer, a scoring model, a sequence of agents that qualify and route and personalise, with exception handling for the cases the system gets wrong. A growth engineer instruments a funnel, runs the experiment, reads the result, and changes the machine. This is system design. It involves decomposing a messy human process into something explicit enough to run, anticipating where it breaks, and maintaining it as conditions shift. The fact that the building blocks are Clay and Claude and a no-code canvas rather than a compiler does not change the shape of the cognitive work, which is the same work of contrivance the root word always pointed at.

If no degree gates the title, something has to

The honest qualifier is a system that works and that you can point to. Not a certificate, not a self-description, a thing that runs and produces an outcome someone will pay for. This is a higher bar than it sounds, because a working system exposes you. It either routes the lead correctly or it does not. The portfolio of shipped, functioning machines is the credential, and it is harder to fake than a line on a CV.

The qualifiers people actually reach for are messier than that. Some lean on adjacency, the fact that they sit near engineers, attend the standups, speak the vocabulary. Some lean on tooling fluency, the ability to name the stack. These are proxies, and proxies are where the trouble starts.

The part that is uncomfortable to write

Engineer carries a masculine default in most people’s heads, built over a century when the licensed profession was overwhelmingly male, and that default does quiet work when someone self-appoints. I suspect, and I cannot prove, that a man who relabels himself a Growth Engineer is read as ambitious and forward-looking, while a woman who does the same is more likely to be asked, silently or aloud, whether she has earned it. The title is the same string of characters. The scrutiny attached to it is not evenly distributed. When a credential dissolves and self-appointment takes over, the gap left behind does not stay empty, it fills with whatever assumptions the reader already carried, and those assumptions have a gender.

This matters more now than it would have in a credentialed world, because the whole premise of these roles is self-definition. The people most able to claim the upside of a dissolving credential are the people whose claim is least questioned, and that is worth naming before it hardens into a pattern.

Does the method matter, or only the result

If two people produce the same working system, one by writing Python and one by orchestrating agents across a no-code stack, are they doing the same job? The craft instinct says the code is more real. The results instinct says the outcome is identical, so the method is private. I lean toward the outcome, with one caveat. The person who understands what the system is doing underneath, who can reason about why the agent misroutes a certain class of lead, holds something the pure assembler does not, which is the ability to repair the machine when it breaks in a way the tutorial did not cover. That understanding is the thing worth screening for, more than the syntax.

Programming an agent is engineering in the original sense

This is the parallel that made all of it click. You take an unreliable, probabilistic component and you design a system of constraints, prompts, checks, and fallbacks that makes it produce a dependable outcome. You are contriving reliability out of an unreliable part, which is close to a definition of engineering you could have used in the eighteenth century about a steam valve. The instrument changed from metal to language. The act of devising a system that works did not.

If you hire for these roles, the implication is direct. Stop using the credential as a filter, because the credential and the work have come apart. Ask for the system. Ask the person to walk you through one they built, where it broke, how they found the failure, and what they changed. Systems thinking shows up in that walk-through within a few minutes, and it cannot be faked by someone who only assembled a template. And watch your own scrutiny, because if you find yourself trusting the man’s self-appointed title and interrogating the woman’s, the bias is in the room, and it is yours to correct.

The word is being repossessed by its oldest meaning, and I find I do not mind. Ingenuity was always the point, and a century of licensing made us forget that the engineer was first a person who simply found a way. What I am still working out is whether a title can survive without a gate, or whether every dissolving credential just relocates the gatekeeping into the quieter, less accountable place behind the reader’s eyes.