Case study · GTM engineering
Before we searched the market, we helped define it.
DataBahn needed a GTM Engineer in India: a role the company had never hired, in a category the market hasn't finished naming. Sourcing profiles was never the hard part. Knowing what right looked like, what it should cost and how to test for it was.
| Client | DataBahn, US-headquartered technology company |
|---|---|
| Role | GTM Engineer, the company's first in India |
| Model | Remote, US to India |
| Stakeholders | VP Marketing, Director of RevOps |
The challenge
Finding profiles was easy. Defining good was not.
With no internal precedent there was no benchmark salary, no reference profile and no interview loop. The questions came first: where does a GTM Engineer come from, what does the capability cost in India, which skills matter, and how do you tell someone who can operate the stack from someone who can own the system?
And because this was a remote hire from the US, one more: could this person work across teams, time zones and functions without becoming a remote task executor? DataBahn wanted someone to own the system.
How we ran it
Calibrate
Working sessions with the VP Marketing and Director of RevOps on stack maturity, team structure, ownership and 30/60/90-day output.
Map
About 50 adjacent profiles across Sales Ops, Marketing Ops, RevOps, GTM Ops and automation, to find where the capability lives and what it costs.
Define
The question became: can this person understand a GTM problem, design the system around it, and own the outcome?
Search
On capability and operating context, not the title. Most good candidates didn't carry it.
Refine
Every interview fed the next search iteration.
The market map
Three tiers, separated by how much of the system the operator can own.
DataBahn wasn't competing for a conventional RevOps hire. The role sat in the top band, and we shared that with the hiring team before presenting anyone, not during the offer.
Indicative India pay, lakhs a year fixed
Directional observations from about 50 profiles mapped during this search. Not a salary survey and not DataBahn's offer range.
The lesson
Benchmark the work, not the title.
For an emerging role, searching only for people who already carry the title shrinks the pool to almost nothing. The hire came from searching on capability.
Hiring a role nobody has hired before?
Start with a Role Canvas and a market map.