The empty seat: why GTM engineer reqs stay open

Why does a GTM engineer req stay open for half a year?

One company in our pipeline this year arrived with a GTM engineer req open since spring. They had built an interview case study out of their real problem, brought candidates to the final round, and watched the process collapse there more than once, each time when the questions stopped being technical. After the latest of those interviews, the company's technical leader concluded that they could probably build the system themselves, and could not confidently hire someone else to.

What was missing was not effort but a definition. The role is new enough that what good looks like is rarely written down, and the people who would have to write it are the same people trying to hire for it. The req stays open because the definition is missing, and the definition is missing because producing it is most of the job. That is a hypothesis, drawn from one search and from our hiring conversations, and it does not rule out plainer explanations, a thin candidate market among them.

Why is the role unhireable as written?

The work a GTM engineer req describes is decisions, not implementation. Which accounts belong in the first tier. Which records are excluded, and who owns the exception when the system is unsure. Whether the list refreshes on a schedule or by hand. What the system is allowed to decide without asking a human. A competent builder can implement the answers in days. The req is trying to hire the answers themselves.

In our conversations with hiring managers, two candidate archetypes recur: technical candidates who build systems behind their own stack that only they can log into, and marketing candidates with deep judgment in one lane who have not had to wire two systems together. One marketing leader mid search told us they had been circling the same thought, that the role might genuinely be two roles. We agree, and one GTM engineer is not a capability is the long version.

The final round collapse fits that reading. Early rounds test skills, and skills are testable. The final round tests judgment against a specification that has not been written, so the process fails at the last step, and after two or three repetitions the pattern starts to read as a talent problem. One marketing leader described the state this produces: "I'm just a little bit suspicious of everybody."

What did our 11 coded sales conversations show?

We went back through our 2026 meeting archive, screened 420 meetings, and kept the 11 that were sales conversations, calls where we were pitching or scoping rather than delivering. We coded each one for two facts: did an unfilled or under-resourced seat come up, and did an event with a calendar position, such as a board meeting, a launch month or a proposal deadline. A seat appeared in 8 of the 11. A dated event appeared in 8 of the 11. Both together appeared in 5. No conversation arrived with neither.

Does the empty seat cause the conversation?

We coded this data to test our own earlier claim, formed on a five call sample: that the window opens only when the seat and the date arrive together. The 11 call table does not support it. Both together hold in fewer than half of the conversations, and each half alone in about three quarters, so the empty seat looks less like a selection signal than like a description of the market that talks to us.

What survived the test is a refinement about timing. The seat qualifies; the proximity of the date times it. The conversations that moved carried a specific near date: a board meeting the next day, a CFO meeting that week, a proposal due in five days. The ones anchored to a vague end of year goal sat still. That is an observation on 11 calls. The timing rule is our hypothesis for it; it does not control for deal size or for how each conversation started, and a few counterexamples would break it.

What does the open req cost per month?

There is no honest dollar figure for this, and we will not invent one. The bill is paid in time and decision debt, and it accrues monthly whether or not anyone books it.

definitionDecision debt

The backlog of decisions a role exists to make, accumulating while the seat is empty. It behaves differently from a work backlog. Work waits for hands, and a contractor can burn it down. Decisions wait for an owner, and while they wait, defaults decide instead: the tier nobody defined, the exclusion nobody wrote, the routing rule inherited from a different quarter. Every one of those defaults is a decision too, made by nobody, and the eventual hire inherits all of them on top of their own ramp.

The time cost is the visible half. In one account in our pipeline, a marketing lead had been covering paid since a contractor left in the spring, and described the channel, in their own words, as neglected for most of the year.

Decision debt is the half that compounds. The scoring model is the cleanest example: if the tiers were defined without the reps who work the leads, the score populates a field and changes nothing. The reps have to define the tiers before the model gets built, and the open req is burning the period in which that could happen.

What resolves the search?

The choice is usually framed as hire versus buy, and the full decision is at GTM engineer or agency. What matched the conversations that closed for us is a parallel path rather than a fork: start now with a team that has stood the system up before, keep the search running in the background, and plan the overlap and the step down in writing, so the outside cost has a stated end date and the handoff is on the calendar from day one.

The system gets built in the company's own accounts and runs without us, which lowers key-man risk instead of relocating it to a vendor. And by the end of the four month sprint we describe at how we work, the workflows exist, the rules of engagement are written down, and the tiers were defined with the reps who work them. The req can then stop asking one person to be a specification, a sponsor and a builder at once, and describe a real job: own this running system and extend it. Interviewing against that system, walking a candidate through the actual routing logic and asking what they would change, gives the final round something to test.

On our sample the empty seat is common enough that we treat it as qualification rather than urgency. The date is the part with a deadline. If there is a board meeting, a launch or a proposal on your calendar, the months between now and then are what the open req is spending, and decision debt is the line on that bill that does not recover.