GTM Engineer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. The posting includes "About the Job:" (which is like About the role). Then "What You'll Do:" (Responsibilities). Then "What You'll Need:" (Requirements/Qualifications). Then "Benefits". No explicit Pay or Schedule. So we should include About the role, Responsibilities, Requirements, Benefits. Possibly also Skills? The "What You'll Need" includes skills/experience; we can treat as Requirements. Could also split Qualifications vs Skills but not needed. We'll follow instruction: use headings for those sections only if content present.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, privacy, employment terms, etc. Also remove "Learn more at www.zoneandco.com or follow us on LinkedIn:" etc. Also remove "Join Our Global Mission" etc. Also remove "Employment Terms", "Non-US Jurisdictions", "Privacy Statement". Also remove "At Zone, we provide the platform; you provide the grit." That's part of Benefits? Actually that is descriptive but we can keep as part of Benefits section. However we need to keep substantive info: benefits description. The posting includes a Benefits paragraph: "At Zone, we provide the platform; you provide the grit. We operate as a high-velocity, fully remote, global team where autonomy isn't just a perk, it’s the standard. We’re looking for self-driven professionals eager to navigate the complexities of a unique SaaS environment and take full command of their professional evolution. We ditch micro-management for high-trust flexibility, ensuring you have the space to innovate and scale. Our benefits are built to fuel this lifestyle, supporting your life beyond the screen so you can focus on making a global impact. Explore our offerings at https://www.zoneandco.com/careers". That's benefits description. We'll keep that.
We need to use - for any list of duties/requirements/benefits. The posting has bullet-like sentences but not explicit list. We can convert each sentence into
- . For responsibilities: list items under "What You'll Do:" with subheadings Data and integrations, Automation, AI and experimentation, Team enablement, Governance, quality, and compliance. Those could be subheadings but we only allowed
for section headings; we could still use for sub-sections? The 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 to be safe we can just treat each bullet as
- under a
under Responsibilities. We could also keep the subheadings as plain text or . Probably fine to keep them as part of - text.
Similarly for What You'll Need: list items.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from those sections.
Let's extract content.
About the Job: The paragraph after "About the Job:" includes:
"Lead Zone & Co.’s GTM Engineering function and become the driving force behind AI adoption across our go-to-market organization. You’ll own the systems, data, integrations, and automation that power scalable pipeline generation—and build the team’s ability to continuously improve and operate those systems themselves.
Zone & Co. builds finance software that runs natively inside NetSuite. We’re looking for a GTM Engineering leader who can architect the infrastructure behind our go-to-market engine, including our data and enrichment layer, integrations across the GTM tech stack, and automation supporting core inbound and outbound motions.
You’ll bring AI natively into GTM workflows, turn ideas into governed, production-ready solutions, and run structured experiments tied to measurable outcomes like pipeline, conversion, and efficiency. You’ll also lead the evolution of the team from manual prospecting toward a more technical, systems-oriented model—including developing BDRs into GTM engineers who can build, maintain, and improve the systems they rely on.
The ideal candidate thinks in systems, not isolated touchpoints. You’ll design with data quality, deliverability, compliance, reliability, and cost control in mind from the start, while creating an environment where experimentation can happen quickly and safely."
That's the About the role content.
Responsibilities: Under "What You'll Do:" with subsections:
Data and integrations:
- Connect enrichment providers, internal data sources, and AI to keep account and contact data accurate and usable.
- Design data flows using proper field mapping and data contracts rather than one-off scripts.
- Integrate systems across CRM, sequencing, marketing automation, and the data warehouse.
- Evaluate new tools and prevent redundancy in the GTM stack.
Automation:
- Build inbound lead scoring, routing, and response workflows.
- Build outbound list building, enrichment, sequencing, and conversion tracking workflows.
- Translate opportunities identified by sellers, marketers, and CS team members into production-ready solutions.
- Take ambiguous problems from reps, AEs, or marketers and turn them into working systems.
AI and experimentation:
- Design agentic workflows for enrichment, personalization, scoring, and rep productivity, using sound prompt engineering and agent design.
- Run structured experiments across channels and workflows, measure against pipeline and conversion metrics, and retire what doesn't work.
- Report on system performance using BI tools such as Tableau or Looker.
Team enablement:
- Guide BDR team as it transitions into GTM engineering.
- Teach workflow design and Clay proficiency as the team's work shifts from manual prospecting to building and maintaining systems.
- Support people across GTM who are building their own agents and automations, helping make their work governed and production-ready.
Governance, quality, and compliance:
- Design safeguards up front for deliverability, data quality, and compliance with regulations such as GDPR and CAN-SPAM.
- Scope, document, and test everything before release.
- Apply guardrails on cost, performance, and sustainability so no system runs unmonitored.
Requirements: Under "What You'll Need:":
- 4+ years of hands-on experience building GTM automation and integrations personally, not solely directing others.
- Deep expertise in Clay or a comparable enrichment or workflow platform.
- Strong Salesforce experience, including data governance.
- Working proficiency in SQL, Python, or JavaScript sufficient to build and fix workflows independently of engineering.
- Experience with a BI tool such as Tableau or Looker.
- Proven experience applying LLMs and agentic tooling to real revenue workflows.
- Understanding of sales qualification frameworks (e.g., BANT, MEDDIC) and multi-touch attribution.
- Strong understanding of deliverability, data quality, and compliance requirements (GDPR, CAN-SPAM).
- Experience managing or mentoring a team.
- Ability to translate ambiguous business problems into working systems.
- Preferred: Prior BDR or SDR experience.
Benefits: paragraph as earlier.
We must not include Pay or Schedule sections.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... (the about job paragraph(s) )
Responsibilities
- ... each bullet
...
We need to keep the subheadings? Could embed them as part of - text, maybe preceded by . That's okay.
Similarly for Requirements.
Requirements
- ... each bullet
Benefits
... benefits paragraph(s)
We must ensure we preserve all substantive information. Let's copy the about role text exactly as given, preserving punctuation.
About the role paragraph(s): There are multiple sentences; we can combine into one or multiple
. Probably one
is fine.
Let's copy:
"Lead Zone & Co.’s GTM Engineering function and become the driving force behind AI adoption across our go-to-market organization. You’ll own the systems, data, integrations, and automation that power scalable pipeline generation—and build the team’s ability to continuously improve and operate those systems themselves.
Zone & Co. builds finance software that runs natively inside NetSuite. We’re looking for a GTM Engineering leader who can architect the infrastructure behind our go-to-market engine, including our data and enrichment layer, integrations across the GTM tech stack, and automation supporting core inbound and outbound motions.
You’ll bring AI natively into GTM workflows, turn ideas into governed, production-ready solutions, and run structured experiments tied to measurable outcomes like pipeline, conversion, and efficiency. You’ll also lead the evolution of the team from manual prospecting toward a more technical, systems-oriented model—including developing BDRs into GTM engineers who can build, maintain, and improve the systems they rely on.
The ideal candidate thinks in systems, not isolated touchpoints. You’ll design with data quality, deliverability, compliance, reliability, and cost control in mind from the start, while creating an environment where experimentation can happen quickly and safely."
We need to keep line breaks? HTML will ignore; but we can keep as is.
Now Responsibilities list items: We'll list each bullet.
Data and integrations:
- Connect enrichment providers, internal data sources, and AI to keep account and contact data accurate and usable.
- Design data flows using proper field mapping and data contracts rather than one-off scripts.
- Integrate systems across CRM, sequencing, marketing automation, and the data warehouse.
- Evaluate new tools and prevent redundancy in the GTM stack.
Automation:
- Build inbound lead scoring, routing, and response workflows.
- Build outbound list building, enrichment, sequencing, and conversion tracking workflows.
- Translate opportunities identified by sellers, marketers, and CS team members into production-ready solutions.
- Take ambiguous problems from reps, AEs, or marketers and turn them into working systems.
AI and experimentation:
- Design agentic workflows for enrichment, personalization, scoring, and rep productivity, using sound prompt engineering and agent design.
- Run structured experiments across channels and workflows, measure against pipeline and conversion metrics, and retire what doesn't work.
- Report on system performance using BI tools such as Tableau or Looker.
Team enablement:
- Guide BDR team as it transitions into GTM engineering.
- Teach workflow design and Clay proficiency as the team's work shifts from manual prospecting to building and maintaining systems.
- Support people across GTM who are building their own agents and automations, helping make their work governed and production-ready.
Governance, quality, and compliance:
- Design safeguards up front for deliverability, data quality, and compliance with regulations such as GDPR and CAN-SPAM.
- Scope, document, and test everything before release.
- Apply guardrails on cost, performance, and sustainability so no system runs unmonitored.
We'll put each bullet as
- . Could also include the subheading as plain text before the list, but we can incorporate as
- Data and integrations: ...? Actually each bullet is a separate item; subheadings are not bullets. We could make subheadings as
- Data and integrations:
then subsequent bullets as - ... but that would be odd. Better to keep subheadings as plain text outside list? But instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid other text outside lists. We could put subheading as
Data and integrations:
then - ... etc. That seems acceptable.
We'll do that for each subsection.
Similarly for Requirements.
Requirements list:
- 4+ years of hands-on experience building GTM automation and integrations
for section headings; we could still use for sub-sections? The 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 to be safe we can just treat each bullet as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just treat each bullet as
- under Responsibilities. We could also keep the subheadings as plain text or . Probably fine to keep them as part of
- text.
Similarly for What You'll Need: list items.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from those sections.
Let's extract content.
About the Job: The paragraph after "About the Job:" includes:
"Lead Zone & Co.’s GTM Engineering function and become the driving force behind AI adoption across our go-to-market organization. You’ll own the systems, data, integrations, and automation that power scalable pipeline generation—and build the team’s ability to continuously improve and operate those systems themselves.
Zone & Co. builds finance software that runs natively inside NetSuite. We’re looking for a GTM Engineering leader who can architect the infrastructure behind our go-to-market engine, including our data and enrichment layer, integrations across the GTM tech stack, and automation supporting core inbound and outbound motions.
You’ll bring AI natively into GTM workflows, turn ideas into governed, production-ready solutions, and run structured experiments tied to measurable outcomes like pipeline, conversion, and efficiency. You’ll also lead the evolution of the team from manual prospecting toward a more technical, systems-oriented model—including developing BDRs into GTM engineers who can build, maintain, and improve the systems they rely on.
The ideal candidate thinks in systems, not isolated touchpoints. You’ll design with data quality, deliverability, compliance, reliability, and cost control in mind from the start, while creating an environment where experimentation can happen quickly and safely."
That's the About the role content.
Responsibilities: Under "What You'll Do:" with subsections:
Data and integrations:
- Connect enrichment providers, internal data sources, and AI to keep account and contact data accurate and usable.
- Design data flows using proper field mapping and data contracts rather than one-off scripts.
- Integrate systems across CRM, sequencing, marketing automation, and the data warehouse.
- Evaluate new tools and prevent redundancy in the GTM stack.
Automation:
- Build inbound lead scoring, routing, and response workflows.
- Build outbound list building, enrichment, sequencing, and conversion tracking workflows.
- Translate opportunities identified by sellers, marketers, and CS team members into production-ready solutions.
- Take ambiguous problems from reps, AEs, or marketers and turn them into working systems.
AI and experimentation:
- Design agentic workflows for enrichment, personalization, scoring, and rep productivity, using sound prompt engineering and agent design.
- Run structured experiments across channels and workflows, measure against pipeline and conversion metrics, and retire what doesn't work.
- Report on system performance using BI tools such as Tableau or Looker.
Team enablement:
- Guide BDR team as it transitions into GTM engineering.
- Teach workflow design and Clay proficiency as the team's work shifts from manual prospecting to building and maintaining systems.
- Support people across GTM who are building their own agents and automations, helping make their work governed and production-ready.
Governance, quality, and compliance:
- Design safeguards up front for deliverability, data quality, and compliance with regulations such as GDPR and CAN-SPAM.
- Scope, document, and test everything before release.
- Apply guardrails on cost, performance, and sustainability so no system runs unmonitored.
Requirements: Under "What You'll Need:":
- 4+ years of hands-on experience building GTM automation and integrations personally, not solely directing others.
- Deep expertise in Clay or a comparable enrichment or workflow platform.
- Strong Salesforce experience, including data governance.
- Working proficiency in SQL, Python, or JavaScript sufficient to build and fix workflows independently of engineering.
- Experience with a BI tool such as Tableau or Looker.
- Proven experience applying LLMs and agentic tooling to real revenue workflows.
- Understanding of sales qualification frameworks (e.g., BANT, MEDDIC) and multi-touch attribution.
- Strong understanding of deliverability, data quality, and compliance requirements (GDPR, CAN-SPAM).
- Experience managing or mentoring a team.
- Ability to translate ambiguous business problems into working systems.
- Preferred: Prior BDR or SDR experience.
Benefits: paragraph as earlier.
We must not include Pay or Schedule sections.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... (the about job paragraph(s) )
Responsibilities
- ... each bullet ...
- text, maybe preceded by . That's okay.
Similarly for Requirements.
Requirements
- ... each bullet
Benefits
... benefits paragraph(s)
We must ensure we preserve all substantive information. Let's copy the about role text exactly as given, preserving punctuation. About the role paragraph(s): There are multiple sentences; we can combine into oneor multiple
. Probably one
is fine. Let's copy: "Lead Zone & Co.’s GTM Engineering function and become the driving force behind AI adoption across our go-to-market organization. You’ll own the systems, data, integrations, and automation that power scalable pipeline generation—and build the team’s ability to continuously improve and operate those systems themselves. Zone & Co. builds finance software that runs natively inside NetSuite. We’re looking for a GTM Engineering leader who can architect the infrastructure behind our go-to-market engine, including our data and enrichment layer, integrations across the GTM tech stack, and automation supporting core inbound and outbound motions. You’ll bring AI natively into GTM workflows, turn ideas into governed, production-ready solutions, and run structured experiments tied to measurable outcomes like pipeline, conversion, and efficiency. You’ll also lead the evolution of the team from manual prospecting toward a more technical, systems-oriented model—including developing BDRs into GTM engineers who can build, maintain, and improve the systems they rely on. The ideal candidate thinks in systems, not isolated touchpoints. You’ll design with data quality, deliverability, compliance, reliability, and cost control in mind from the start, while creating an environment where experimentation can happen quickly and safely." We need to keep line breaks? HTML will ignore; but we can keep as is. Now Responsibilities list items: We'll list each bullet. Data and integrations: - Connect enrichment providers, internal data sources, and AI to keep account and contact data accurate and usable. - Design data flows using proper field mapping and data contracts rather than one-off scripts. - Integrate systems across CRM, sequencing, marketing automation, and the data warehouse. - Evaluate new tools and prevent redundancy in the GTM stack. Automation: - Build inbound lead scoring, routing, and response workflows. - Build outbound list building, enrichment, sequencing, and conversion tracking workflows. - Translate opportunities identified by sellers, marketers, and CS team members into production-ready solutions. - Take ambiguous problems from reps, AEs, or marketers and turn them into working systems. AI and experimentation: - Design agentic workflows for enrichment, personalization, scoring, and rep productivity, using sound prompt engineering and agent design. - Run structured experiments across channels and workflows, measure against pipeline and conversion metrics, and retire what doesn't work. - Report on system performance using BI tools such as Tableau or Looker. Team enablement: - Guide BDR team as it transitions into GTM engineering. - Teach workflow design and Clay proficiency as the team's work shifts from manual prospecting to building and maintaining systems. - Support people across GTM who are building their own agents and automations, helping make their work governed and production-ready. Governance, quality, and compliance: - Design safeguards up front for deliverability, data quality, and compliance with regulations such as GDPR and CAN-SPAM. - Scope, document, and test everything before release. - Apply guardrails on cost, performance, and sustainability so no system runs unmonitored. We'll put each bullet as
- . Could also include the subheading as plain text before the list, but we can incorporate as
- Data and integrations: ...? Actually each bullet is a separate item; subheadings are not bullets. We could make subheadings as
- Data and integrations:
then subsequent bullets as- ... but that would be odd. Better to keep subheadings as plain text outside list? But instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid other text outside lists. We could put subheading as
Data and integrations:
then- ... etc. That seems acceptable. We'll do that for each subsection. Similarly for Requirements. Requirements list: - 4+ years of hands-on experience building GTM automation and integrations