Software Engineer - GTM Engineering

Level: Junior software engineer or early-career technical operations/solutions engineer with 1–3 years of experience building internal tools, automations, or web applications.

Required skills: Python or TypeScript/JavaScript, APIs, basic databases, AI and low-code integrations such as Clay, Zapier, or Make, plus foundational knowledge of sales funnels and revenue operations.

The candidate should be familiar with implementing defined features, automating lead routing and pipeline workflows, maintaining and troubleshooting internal tools, and collaborating with Sales, Customer Success, and RevOps stakeholders.

How would you design an automated lead-routing workflow using a CRM, an enrichment service, and an automation platform such as Zapier, Make, or n8n?

I would trigger the workflow when a lead is created or updated, enrich and validate the record, then apply routing rules based on attributes such as region, company size, industry, and account ownership. I would also add idempotency, error handling, logging, and a fallback queue for records that cannot be routed automatically.

How would you safely integrate an external API into an internal GTM tool?

I would first review authentication, rate limits, pagination, webhook behavior, and error responses. Credentials would be stored securely, requests would use timeouts and retries with backoff, and the integration would include structured logging, monitoring, and tests using mocked API responses.

What steps would you take to build an AI-powered tool that summarizes sales calls or customer interactions?

I would define the required output and success criteria with Sales or Customer Success, then retrieve the source data, redact sensitive information where appropriate, and call the model through a controlled service. I would validate the output, handle failures, track usage and latency, and provide a human-review path because AI-generated summaries may be incomplete or inaccurate.

How would you prevent duplicate records when syncing contacts or accounts between systems?

I would use stable external identifiers where available and otherwise apply carefully designed matching rules using fields such as normalized email, domain, and account identifiers. The workflow should be idempotent, record synchronization results, and route ambiguous matches for manual review instead of merging automatically.

How would you troubleshoot a workflow that intermittently fails to update Salesforce or HubSpot?

I would inspect execution logs, request payloads, response codes, authentication status, rate-limit headers, and recent configuration changes. I would reproduce the failure with a representative record, identify whether the problem is data validation, permissions, a platform outage, or throttling, then add a durable fix and alerting for recurrence.

What database practices are important for maintaining reliable internal GTM tools?

I would define clear schemas, constraints, indexes, and ownership for important data, while storing raw external identifiers to support reconciliation. I would use parameterized queries, migrations, backups, audit fields, and transaction boundaries to protect data integrity and make changes safely.

How would you measure whether an automation improved a revenue workflow?

I would establish a baseline and track metrics such as processing time, routing accuracy, error rate, conversion rate, representative adoption, and manual work eliminated. I would compare results before and after launch, gather user feedback, and monitor for unintended effects such as poor data quality or missed leads.

How would you write tests for a lead-enrichment and pipeline-update service?

I would unit-test normalization, routing rules, validation, and error-handling logic, using mocks for external APIs. I would also add integration tests for representative CRM interactions and end-to-end tests covering retries, duplicate events, missing fields, rate limits, and partial failures.

What security and privacy considerations apply when building AI tools for sales and customer data?

I would apply least-privilege access, secure secret management, encryption in transit and at rest, and strict controls on which data is sent to third-party AI services. I would minimize retained data, implement audit logging and retention policies, and confirm that the workflow follows company privacy and compliance requirements.

How would you turn an ambiguous request from Sales or RevOps into an implementable feature?

I would clarify the underlying problem, users, workflow, inputs, expected outputs, edge cases, and measurable success criteria. I would propose a small first version, document assumptions and dependencies, validate the design with stakeholders, and iterate based on usage and feedback.

Engine is an AI-native travel technology company powering business travel, group travel, human agents, and AI agents for more than 40,000 customers. As a GTM Engineer, you’ll build and support AI-powered internal tools, automate sales and customer-success workflows, integrate APIs, and improve pipeline operations using Python, TypeScript/JavaScript, Clay, Zapier, Make, and platforms such as Salesforce, HubSpot, and n8n. This is a fully remote US role with a base salary of $106,250–$125,000 USD, plus equity and potential bonuses. Apply to gain ownership, work alongside high-caliber teams, and help shape the future of intelligent travel while growing at the intersection of software engineering, AI, and revenue operations.