GTM Engineer

The short version

We sell hotel software to American hotel owners. There are tens of thousands of them in the segment we care about, they're scattered across fifty states, and almost none of them sit in a clean database you can buy. Your job is to build the machine that finds them, works out what tech they already run, and gets the right message in front of the right person — without a room full of SDRs doing it by hand.

This is not an SDR job with a fancy title. You'll spend most of your week in scrapers, enrichment tools, LLM APIs and CRM automation. If sending 200 manual emails a day sounds fine to you, this is the wrong role. If it makes you want to write a script instead, keep reading.

About Hotelzify

We're a profitable B2B hospitality tech company serving 15,000+ properties across 12 countries. We sell an AI concierge, a booking engine and revenue management tools that sit on top of a hotel's existing PMS and channel manager — we don't replace their stack, we make it earn more. Our thesis is simple: hotels give away too much margin to OTAs, and direct is best.

About 74% of our revenue comes from AI products. Our fastest-growing market is the US. We're backed by All In Capital, DeVC, the founders of TBO.com, and a set of operator angels.

Who we're going after

Your entire focus is the US budget, economy and premium-economy hotel segment. Concretely:

• Independent properties and small portfolios, roughly 20-120 rooms.
• Franchisees in the economy and upper-midscale flags — Days Inn, Super 8, Travelodge, Microtel, Comfort Inn, Quality Inn, Sleep Inn, Econo Lodge, Holiday Inn Express, Fairfield, Hampton, Tru, Home2.
• Owner-operators, not corporate real estate. Frequently a family owning two to eight properties. A large share of this market sits inside AAHOA and the state hotel associations.

This is the segment that bleeds the most margin to OTAs and has the least in-house tech to fix it. It's also the segment nobody has properly mapped, which is why this is an engineering problem and not a list-buying problem. The person you're looking for is the owner or the GM — not a revenue management department, because there isn't one.

What you'll actually build

• A US hotel graph. Scrape, merge and de-duplicate property data from OTA listings, review sites, maps, franchise property directories, state association directories and public business registrations. Room count, flag, segment tier, market, owner entity, portfolio size.
• Owner resolution. Get from a property to the human who signs. In this segment that often means walking LLC records and franchise filings, not LinkedIn — coverage there is thin and you'll have to be inventive.
• Tech-signal detection. Programmatically detect which booking engine, channel manager and PMS a property runs by fingerprinting its website and booking flow. A hotel running a bad booking engine is our single best buying signal — you'll be the one who can see it at scale.
• AI-driven email at volume. Sequences on a proper ESP and dedicated sending domains, with the deliverability work that makes them survive: domain warming, inbox rotation, bounce handling, LLM-based reply classification and routing. Personalisation that references a property's actual booking flow and OTA exposure, not a first-name merge tag.
• The founder follow-up system. After an AE or SDR meets a client, the system pulls meeting notes, deal stage and property details from Zoho CRM and drafts a follow-up LinkedIn message from our CEO — so the owner sees the founder is personally engaged. The CEO reviews and sends every one. You're building the drafting, queueing and approval layer, not a bot that sends from his account. Understanding why that distinction matters is part of the job.
• CRM plumbing. Zoho CRM is our system of record. You'll own lead routing, dedupe, lifecycle stages, meeting-to-follow-up triggers and the workflows that stop leads rotting in a queue.
• The reporting layer. A dashboard that answers "which segment, state, flag and message produced pipeline this week" without anyone exporting a spreadsheet.

First 90 days

• Days 1-30: Learn the product and the American hotel owner. Sit in on sales calls. Audit our current outbound and CRM and tell us what's broken. Ship one enrichment workflow that saves the sales team real hours.
• Days 31-60: Build a tech-signal-scored list of economy and premium-economy properties for one US region. Launch an email sequence against it and instrument it end to end. Get the founder follow-up flow working for one AE.
• Days 61-90: A repeatable, measurable pipeline motion for that region, with real numbers on cost per meeting — and a plan to clone it to the next one.

What we're looking for

Must have

• You can write Python (or JS) well enough to build and maintain scrapers, call APIs and clean messy data. Scripts, not applications — but real, working code.
• You've built with LLM APIs for something practical: classification, extraction, drafting, personalisation at volume. Not just prompted a chatbot.
• Comfort in the modern GTM tooling layer — Clay, Apollo, Instantly/Smartlead, n8n/Zapier or equivalents. What you built matters more than which tool you name.
• SQL and spreadsheets deep enough to answer your own questions.
• You write clearly in English, in a register a hotel owner in Ohio will actually reply to. Half this job is copy.
• A bias toward shipping something rough this week over something perfect next quarter.
• You can be in our Indiranagar office five days a week.

Nice to have

• Any experience selling into the US from India — you'll be building for a buyer in a different time zone and a different register.
• Exposure to hospitality, travel, franchising or OTA economics.
• Selling into SMBs or any long-tail market with thousands of small owner-operator buyers.
• Zoho CRM experience, or a strong opinion about any CRM.
• Email deliverability scar tissue.

Probably not for you if

• You want a clean spec handed to you. Most weeks you'll define the problem yourself.
• You want to stay purely technical and never talk to a customer or write sales copy.
• You want to stay purely commercial and never open a terminal.
• You want to work remotely. We mean the office thing.

Why it's worth taking

• You'll own a function, not a ticket queue. There's no GTM engineering team here yet — you are it, and you'll shape what it becomes.
• Direct access to the founders. Your work shows up in revenue within weeks.
• We're profitable. You're building growth infrastructure, not burning runway to hit a vanity number.
• You'll get properly good at the thing the market is about to pay a lot for. Nobody has mapped this segment. You will.

Logistics

In office in Indiranagar, Bangalore, five days a week. This role benefits from being in the room with sales, and that's not negotiable. Standard leave, health cover, and a real tooling budget — if you need scraping proxies, enrichment credits, an ESP or an API key, you get it.

How to apply

Apply here, and include:

1. One paragraph on a GTM system you built. What broke, what you fixed, what it produced. Numbers preferred.
2. A link to code, a workflow, an automation, or a Loom walkthrough of something real. Anything you made beats a polished resume.
3. The task: pick any 20 independent or franchised economy hotels in a single US city. Tell us which booking engine each one uses and how you worked it out — and how you'd approach the same thing for 5,000 properties instead of 20. A rough spreadsheet plus five honest sentences is a complete answer.

We read every application that includes the task. We don't read the ones that don't.