GTM Engineer, RevOps

We need to output HTML fragment with sections: About the role? Actually we have sections: Company Overview, Role Overview, Key Responsibilities, What You'll Bring, Nice To Have, What We Offer, Company Values. Also maybe "Location" etc but we should not repeat job title. We should not include metadata like Job ID. We need to preserve substantive info. Remove boilerplate: Application Process, EEO, etc. We need headings using

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can choose headings that match content: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings where appropriate. However we need to map content to those headings. The posting includes Company Overview, Role Overview, Key Responsibilities, What You'll Bring (requirements/qualifications/skills), Nice To Have (maybe extra), What We Offer (benefits), Company Values (maybe not needed). We should not create sections with filler. So we need sections: About the role (maybe combine Company Overview + Role Overview?), Responsibilities (Key Responsibilities), Requirements (What You'll Bring), Qualifications (maybe same as Requirements?), Skills (maybe specific skills), Benefits (What We Offer). Pay and Schedule not present, so omit. We must not repeat job title as heading. So no heading for "Go-to-Market Engineer, Revenue Operations". Also not include location as heading; could be in a short

maybe. We need to preserve all substantive info. So we need to include company overview text, role overview, responsibilities list, what you'll bring (requirements), nice to have maybe as part of qualifications? Could be separate but we can include as part of Requirements or Qualifications. Since we prefer few substantive sections, we could combine Requirements and Qualifications into one section maybe "Requirements". But we have to use headings from list; we can choose which to include. We'll include: About the role, Responsibilities, Requirements, Benefits. Possibly also Skills? But we can embed skills within Requirements. We must not create sections with filler. So we need to ensure each heading has real content. Let's draft:

About the role

Company overview: ... plus role overview.

We need to include company overview paragraph and role overview paragraph. Then

Responsibilities

• ... each responsibility.

Then

Requirements

• ... each requirement from What You'll Bring.

Maybe also include Nice To Have as part of Requirements? Could add a note but better to include as part of Requirements but we could separate as "Preferred qualifications". But heading list doesn't have Preferred qualifications; we could still use Requirements for both required and nice-to-have but we need to differentiate? Not required. We'll just include all items from What You'll Bring and Nice To Have under Requirements, maybe separate with note? But we must preserve all info; we can include both required and nice-to-have as list items, maybe prefix with (Nice to have). That's okay. Then

Benefits

• ... each benefit from What We Offer.

We should not include Company Values as separate heading unless we have heading for it; not in list, but we could omit as it's not required heading; but we need to preserve substantive info. Could include under About the role or Benefits? Probably better to add a section "Company Values" but not in allowed headings list; but instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to add other headings but they'd deviate. Safer to stick to those headings. We could incorporate Company Values into About the role or Benefits. Probably include a brief paragraph under About the role. We must not include boilerplate: Application Process, EEO, etc. Let's extract text. Company Overview: "The built world generates more data than almost any other industry. Almost none of it is being used. Rentana is changing that, building the AI copilot for real estate that distills billions of real-world signals into revenue intelligence, so operators can optimize every lever across their portfolio and actually talk to their data. Our founding team has built four multi-billion dollar software companies and two proptech exits, including Dynasty (sold to AppFolio) and Urbandoor (sold to Airbnb). Our founding engineers include the first engineer at Airtable and the engineer who led the largest code migration in Stripe's history. Customers love Rentana: we are the top-rated revenue management platform on Revyse, with NMHC Top 50 real estate owners and operators on the platform within 1 year of public launch." Role Overview: "We're hiring our first dedicated RevOps unicorn, and we're calling it a GTM Engineer because that's closer to what the job actually is. You’ll be maintaining our CRM HubSpot and building the connective tissue between it and everything else: product usage data, customer success signals, sales activity, marketing touches, and a growing stack of AI tools. You’ll have real ownership from day one partnering with Sales and Marketing to set and implement our GTM strategy." Key Responsibilities list (bullet points): - Sales and Marketing team support. As the team grows, you're the first line for "why isn't this working" and "how do I do X in HubSpot." You'll field those requests, but more importantly, use the pattern in them to find and fix the bigger process gaps behind the individual asks for Sales and for Rentana overall. - Data and systems of truth. You'll own contact and company enrichment end to end. Familiarity with how to implement and manage go to market tools such as Clay, Kernel, FullEnrich, ZoomInfo, LinkedIn Sales Navigator, HubSpot and more. Own data quality end to end, enrichment and hygiene. That means running audits and verification projects, building rule-based exclusion logic, and producing clean, import-ready records rather than just plugging in a vendor tool. Ensure new hires are set up and the whole team is fluent in their tools. - Sales process and structure. As the first RevOps hire, you'll design how territories are carved up, how books get built and reassigned as the team grows, and how deals move through stages with consistent, enforced criteria. - HubSpot administration. Custom objects, workflows and automations, user profiles and permissions, properties, the day-to-day upkeep of the platform is yours. Build and maintain Lists/Segments as living marketing infrastructure: campaign audiences, filter logic across multiple groups. That includes fielding the small stuff (a broken automation, a rep who needs a new view) as well as the bigger architecture decisions. - Managing all data for account based marketing. - Cross-functional operations. Sales, marketing, customer success, and product all generate data that matters to the other three and Finance, Product, and Implementation all need visibility into what GTM is doing too. - AI-driven automation. You'll be the person testing and rolling out new tools Clay for enrichment, Claude for whatever process is still eating hours it shouldn't and turning them into systems the rest of the team can rely on without thinking about how they work. - Dashboards and reporting. You'll build and maintain the dashboards inside HubSpot that Sales, CS, Marketing, and leadership actually look at, pipeline, rep performance, forecast accuracy, campaign performance, and sit down with those stakeholders regularly. What You'll Bring: - Willingness to work in person in our NYC office with the CEO and Operations team - 2–5+ years in RevOps, sales operations, or a GTM systems role, ideally at a company where you built process rather than just maintained it - Deep hands-on HubSpot experience, workflows, properties, reporting, and enough of the data model to know when something's about to break before it does - Real comfort with modern GTM tooling: Airtable, Clay, Kernel, ZoomInfo, LinkedIn Sales Navigator, and AI tools generally. Comfort with marketing-ops tooling as well. HubSpot Marketing Hub, whatever CMS/content systems are in use, and reporting workarounds for platform gaps. - A genuine interest in AI and automation - Strong SQL or spreadsheet-level data skills; you should be comfortable pulling and shaping your own data rather than waiting on someone else to do it - Willingness to roll up your sleeves, this role includes real, hands-on account and contact research when the automated tools come up short, and the instinct to turn what you learn from that manual work into a scalable process the rest of the team can run without you - The instincts of a builder, you see a messy process and want to fix it, not just document it - Sharp written and verbal communication; you'll be translating between sales, marketing, CS, and product regularly Nice To Have: - Experience in proptech or real estate, especially anything touching multifamily operations - Experience being a first or early RevOps hire, you know what it's like to build without a template - Familiarity with Clay-style enrichment workflows or building automations with tools like Zapier, Make, or n8n What We Offer: - The opportunity to be part of a pioneering team in a high-growth industry, shaping the future of AI in real estate. - Direct collaboration with the startup’s top leadership, offering a unique insight into business management and strategic decision-making. - A competitive salary with equity options. - Comprehensive benefits package including health, dental, and vision insurance. - A dynamic, innovative, and supportive work environment. Company Values list (maybe we can incorporate into About the role as a paragraph). We'll include a short paragraph after role overview. Now craft HTML. We need to output only HTML fragment, no /, no markdown fences. We'll start with

for location maybe? Not required but we can include location as a short p. Let's produce:

About the role

[Company overview + role overview + company values]

But we need to keep paragraphs readable; we can have multiple

inside the section? The instruction: Use

for prose. So we can have multiple

elements under the section. That's fine. Thus:

About the role

The built world generates more data than almost any other industry. Almost none of it is being used. Rentana is changing that, building the AI copilot for real estate that distills billions of real-world signals into revenue intelligence, so operators can optimize every lever across their portfolio and actually talk to their data. Our founding team has built four multi-billion dollar software companies and two proptech exits, including Dynasty (sold to AppFolio) and Urbandoor (sold to Airbnb). Our founding engineers include the first engineer at Airtable and the engineer who led the largest code migration in Stripe's history. Customers love Rentana: we are the top-rated revenue management platform on Revyse, with NMHC Top 50 real estate owners and operators on the platform within 1 year of public launch.

We're hiring our first dedicated RevOps unicorn, and we're calling it a GTM Engineer because that's closer to what the job actually is. You’ll be maintaining our CRM HubSpot and building the connective tissue between it and everything else: product usage data, customer success signals, sales activity, marketing touches, and a growing stack of AI tools. You’ll have real ownership from day one partnering with Sales and Marketing to set and implement our GTM strategy.

Our values: Fast and Transparent – speed paired with transparency; Solve It – take ownership and deliver; Customer Obsessed – listen to real problems; Candid but kind – direct, caring feedback; Win Together – share credit