GTM Engineer- Miami

We need to output HTML fragment with sections: About Us? Actually we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections when posting has real specific content. The posting includes "About Us" (company description) and "About The Role". Also "Requirements:" list. There's also "What This Role Is Not" and "What Great Looks Like After 90 Days". Those could be considered responsibilities? The posting includes responsibilities: "You’ll be responsible for ..." bullet list. Also "Why this role is different" etc. We need to map to sections: About the role (maybe combine About Us and About The Role?). Responsibilities: list of duties. Requirements: list. Qualifications? Might be same as Requirements? The posting includes "Bonus if you’ve worked with ..." maybe Skills. Benefits, Pay, Schedule not present, so we should not include those sections. We must not repeat job title as heading. No Job ID. Remove boilerplate. So we output:

About Us

maybe not required but we can include as part of About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says we can use those headings; but we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities...). Likely we should stick to those headings. However we have content like "About Us" and "About The Role". Could combine into "About the role". The "About Us" is company description; maybe we can put under "About the role" as description? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. They didn't forbid other headings like About Us. But they gave examples of headings to use. Safer to follow examples: include sections only when posting has real specific content. So we can have:

About the role

with content combining About Us and About The Role description.

Responsibilities

with bullet list from "You’ll be responsible for" and maybe other responsibility bullets.

Requirements

with bullet list from "Requirements:" and maybe also "Bonus if you’ve worked with ..." as Skills? Could put under Skills. We could also have

Skills

for bonus technologies. We must not include Benefits, Pay, Schedule. We must preserve all substantive info. So include all bullet points. Let's extract: About Us description: "Welcome to Reeco, where we’re transforming the back-of-house tech for the hospitality industry. Think of it like this: while hotels are all about luxury and convenience, their operations are often stuck in the ‘90s. From emailing suppliers to doing inventory with pen and paper – it’s outdated, inefficient, and expensive. That’s where we come in! With the power of AI, we help streamline operations for top brands like Hilton, Marriott, Hyatt, and IHG, so they can focus on what really matters – delivering amazing guest experiences while keeping everything running like clockwork. Why Reeco At Reeco, we live by our core values - Heart: Humility, Excellence, Ambition, Respect, Transparency, and Trust. We believe that by putting both heart and mind into everything we do, we can transform the hospitality industry. Join us and help build the future of hospitality tech." About The Role: "As our GTM Engineer, you’ll be part of the Operations team and build the systems that power how Reeco’s customer-facing teams work. You’ll work across Sales, Implementation, Customer Success, Support, and Revenue Operations to identify broken or manual processes and turn them into software, automations, integrations, and AI workflows. A major part of the role will be building and improving Reeco’s internal operating system, a custom-built platform designed specifically around how our teams work and how we manage the customer lifecycle. This is a hands-on engineering role. You won’t just receive requirements. You’ll understand the business problem, design the solution, build it, ship it, and improve it based on real usage." Why this role is different: bullet-ish paragraphs: "This is not a traditional RevOps or CRM administrator role. It sits between business operations and engineering. Improve how Sales builds and approves deals. Automate implementation workflows and handoffs. Build tools that help Support investigate customer issues faster. Create workflows across HubSpot, Intercom, Jira, Slack, and Snowflake. Build AI agents that help teams prioritize, investigate, recommend, and take action. Replace repetitive manual work with scalable internal systems. Make Reeco’s customer-facing teams faster, smarter, and more scalable through technology." Then "You’ll be responsible for" list: - Build and improve Reeco’s internal operating system and GTM tools. - Develop internal applications, workflows, and automations across the customer lifecycle. - Build API integrations, webhooks, data syncs, and event-driven workflows. - Connect systems including HubSpot, Intercom, Jira, Slack, Snowflake, and others. - Build AI and agentic workflows using company data and business context. - Turn spreadsheets, manual processes, and repetitive work into scalable software. - Work directly with Sales, Implementation, Customer Success, Support, and Operations to understand problems and build solutions. - Own projects from discovery and design through deployment, adoption, and iteration. - Partner with Product, Data, and Engineering where internal systems connect to Reeco’s core platform. Then "Requirements:" list: - 3+ years of experience in software engineering, systems engineering, solutions engineering, or a similar technical role. - Strong coding ability in Python, TypeScript/JavaScript, or similar. - Strong SQL skills. - Experience working with REST APIs, webhooks, integrations, and third-party systems. - Experience building real applications or internal tools, not only configuring SaaS platforms. - Ability to take an ambiguous business problem and independently turn it into a working solution. - Strong debugging and technical problem-solving skills. - Comfortable working directly with non-technical teams. - Strong ownership and product judgment. Then "Bonus if you’ve worked with" list: - HubSpot or Salesforce - Snowflake - Intercom - Jira - Slack APIs - LLM APIs, AI agents, or tool calling - n8n, Workato, Zapier, or similar - GTM or Revenue Operations systems - Customer Success or Support systems - B2B SaaS - Hospitality technology Then "What This Role Is Not" list: - A HubSpot administrator - A traditional RevOps analyst - A reporting-only role - An outbound automation specialist Then "What Great Looks Like After 90 Days" list: - Understand Reeco’s customer lifecycle and GTM systems. - Ship meaningful improvements to our internal operating system. - Build strong relationships across Sales, Implementation, Customer Success, Support, Product, Data, and Engineering. - Identify high-impact processes to automate or rebuild. - Own workflows across multiple systems. - Ship AI or automation capabilities into daily team usage. - Reduce manual work and improve how customer-facing teams operate. - Success is measured by business impact: faster processes, fewer manual steps, better data, stronger team adoption, and less dependency on Product Engineering for internal GTM needs. We need to decide sections: About the role (include About Us + About The Role + Why this role is different maybe). Responsibilities (the "You’ll be responsible for" list). Requirements (the Requirements list). Skills (the Bonus list). Could also include "What This Role Is Not" maybe as part of Responsibilities? But it's more clarifications; could be omitted? It's substantive but not a responsibility. Could be placed under Responsibilities as clarifications? Might be okay to include as a separate section like "What the role is not" but not in allowed headings. Probably better to incorporate into Responsibilities as notes. "What Great Looks Like After 90 Days" could be considered expectations; could be placed under Responsibilities or maybe a separate section like "Expectations". Not in allowed headings; maybe we can include under Responsibilities as additional expectations. We must not invent sections like "What Great Looks Like". So we should embed that content within Responsibilities or maybe under a heading like "Expectations" but not allowed. Safer to put under Responsibilities as additional bullet points. Thus final HTML:

About the role

Welcome to Reeco, where we’re transforming the back-of-house tech for the hospitality industry. Think of it like this: while hotels are all about luxury and convenience, their operations are often stuck in the ‘90s. From emailing suppliers to doing inventory with pen and paper – it’s outdated, inefficient, and expensive. That’s where we come in! With the power of AI, we help streamline operations for top brands like Hilton, Marriott, Hyatt, and IHG, so they can focus on what really matters – delivering amazing guest experiences while keeping everything running like clockwork. Why Reeco At Reeco, we live by our core values - Heart: Humility, Excellence, Ambition, Respect, Transparency, and Trust. We believe that by putting both heart and mind into everything we do, we can transform the hospitality industry. Join us and help build the future of hospitality tech. As our GTM Engineer, you’ll be part of the Operations team and build the systems that power how Reeco’s customer-facing teams work. You’ll work across Sales, Implementation, Customer Success, Support, and Revenue Operations to identify broken or manual processes and turn them into software, automations, integrations, and AI workflows. A major part of the role will be building and improving Reeco’s internal operating system, a custom-built platform designed specifically around how our teams work and how we manage the customer lifecycle. This is a hands-on engineering role. You won’t just receive requirements. You’ll understand the business problem, design the solution, build it, ship it, and improve it based on real usage. Why this role is different This is not a traditional RevOps or CRM administrator role. It sits between business operations and engineering. Improve how Sales builds and approves deals. Automate implementation workflows and handoffs. Build tools that help Support investigate customer issues faster. Create workflows across HubSpot, Intercom, Jira, Slack, and Snowflake. Build AI agents that help teams prioritize, investigate, recommend, and take action. Replace repetitive manual work with scalable internal systems. Make Reeco’s customer-facing teams faster, smarter, and more scalable through technology.

Responsibilities

• Build and improve Reeco’s internal operating system and GTM tools.
• Develop internal applications, workflows, and automations across the customer lifecycle.
• Build API integrations, webhooks, data syncs, and event-driven workflows.
• Connect systems including HubSpot, Intercom, Jira, Slack, Snowflake, and others.
• Build AI and agentic workflows using company data and business context.
• Turn spreadsheets, manual processes, and repetitive work into scalable software.
• Work directly with Sales, Implementation, Customer Success, Support, and Operations to understand problems and build solutions.
• Own projects from discovery and design through deployment, adoption, and iteration.
• Partner with Product, Data, and Engineering where internal systems connect to Reeco’s core platform.
• Understand Reeco’s customer lifecycle and GTM systems.
• Ship meaningful improvements to our internal operating system.
• Build strong relationships across Sales, Implementation, Customer Success, Support, Product, Data, and Engineering.
• Identify high-impact processes to automate or rebuild.