GTM Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content exists. The posting includes description about role, responsibilities, requirements, qualifications, skills (maybe listed), benefits (some description like "Why You’ll Love It Here"), pay not mentioned, schedule not mentioned. So we include About the role (intro paragraph), Responsibilities (list), Requirements (maybe combine qualifications and skills?), but we need separate sections if content exists. The posting includes "Key Responsibilities" list, then after that there is a block that seems like qualifications: "6–8+ years, with demonstrated ownership..." then bullet-like sentences. Also "Preferred Experience..." etc. Also "Success measures". Also "Why You’ll Love It Here" (benefits/culture). So we can map: - About the role: intro paragraph(s) before Key Responsibilities. - Responsibilities: list under Key Responsibilities. - Requirements: maybe the "6–8+ years..." block (mandatory requirements). - Qualifications/Skills: maybe the "Preferred Experience..." and "Success measures"? But we need to decide. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Qualifications separate if content distinct. Could combine qualifications and skills into one section if not enough distinct. But we have both mandatory requirements and preferred experience. Could treat Requirements as mandatory, Qualifications as preferred? Or Skills as skills list. Let's parse: Mandatory: "6–8+ years, with demonstrated ownership of complex GTM systems, cross-functional roadmap delivery, and executive stakeholder management.Demonstrated hands-on experience building automations and integrations across a marketing/RevOps stack, such as Salesforce, HubSpot, Asana, or ClayExperience designing and building AI-assisted workflows or agents in a business context, using tools like Claude, Copilot Studio, or comparable LLM platformsWorking fluency orchestrating AI agents through MCP connectors or similar across a multi-tool stackExperience building or supporting content and campaign automation workflows, from brief intake through first-draft asset generationStrong understanding of GTM and marketing operations concepts: lead routing, scoring, attribution, and campaign or project workflowsExperience operating in a B2B SaaS or subscription-based GTM environment, ideally across multiple regions, customer segments, or sales motions.Track record building effective working relationships across marketing, sales, RevOps, and IT stakeholdersAbility to influence senior Marketing and Revenue stakeholders, prioritize competing requests, and translate business needs into practical technical delivery plans without relying on direct authority.Comfortable working independently as a senior individual contributor embedded in a marketing organization, with accountability for roadmap ownership, technical judgment, documentation, stakeholder alignment, and adoption of delivered workflows." That's a block of requirements. Preferred: "Preferred Experience in a B2B SaaS GTM, marketing operations, or RevOps environmentFamiliarity with Clay, HockeyStack, or comparable enrichment and analytics platformsExperience building ABM personalization workflows at scaleExperience automating project management tools, such as Asana, to keep cross-team data accurate and up to date" Success measures: list of outcomes. Why You’ll Love It Here: benefits/culture. Thus we can have sections: - About the role (intro) - Responsibilities (list) - Requirements (mandatory) - Qualifications (preferred + success measures? maybe Qualifications includes preferred experience and success measures) - Skills (maybe we could extract skills from responsibilities? but we have no explicit skills list separate. Could combine qualifications and skills into one? But we need to follow instruction: only include sections when posting has real specific content. We have content for Requirements, Qualifications (preferred), Benefits (Why You’ll Love It Here). Skills maybe not explicit; we could skip Skills section. Pay and Schedule not present, skip. Thus output HTML with

About the role

...intro...

then

Responsibilities

• ... each responsibility...

then

Requirements

• ... each requirement...

then

Qualifications

• ... preferred experience...

then

Benefits

• ... Why You’ll Love It Here points...

We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like cookie/navigation/legal/EEO etc. The posting includes at end: "Please submit your resume and cover letter by clicking the ‘I’m interested’ link. Our recruitment process will include pre-employment actions such as background screening and reference checks. Basware. Now it all just happens." That's application instructions and boilerplate; we should remove that. Also remove duplicated lines. We need to extract intro text: Up to before "Key Responsibilities". Let's capture: "Basware is the clear market leader in Invoice Lifecycle Management, trusted by over 6,000 global customers and recognized #1 by Gartner, Forrester, and IDC. We revolutionized how the world’s largest organizations manage and automate AP, processing more than $10 trillion in invoices with unmatched accuracy, compliance, and control. If you’re inspired by innovation, growth, and a value‑driven culture, this is your chance to help shape the future of finance. Basware's Marketing Operations team builds the technical backbone behind our go-to-market motion, across inbound, outbound, and retention and expansion. That means systems integration, data orchestration, and AI-assisted workflows across the marketing and sales stack. The GTM Engineer designs and builds the automations, integrations, and AI agents that let marketing scale output without adding headcount. That includes the traditional GTM engineering work, like lead orchestration, routing, and scoring, but it also extends into agentic support for campaign creation, ABM personalization at scale, and project and database management across the wider marketing organization. The role is positioned for a global B2B SaaS environment and should bring enough experience to independently assess tradeoffs across speed, scale, data quality, privacy, AI governance, adoption, and commercial impact. This is a hands-on technical role. It partners closely with Marketing Operations, Growth Marketing, Customer Growth Marketing, and Marketing Strategy. The GTM Engineer is the go-to technical voice on what's scalable and sound, turning strategy into working systems other marketers can actually use. The role remains hands-on, but is expected to operate with senior-level ownership of GTM engineering priorities, technical decision-making, stakeholder influence, and scalable delivery across Marketing and Revenue teams. It partners closely with Marketing Operations, Growth Marketing, Customer Growth Marketing, Marketing Strategy, Sales, RevOps, and IT to turn GTM strategy into reliable systems other marketers can actually use." That's the intro. Now Responsibilities list: Under "Key Responsibilities" there are bullet-like sentences separated by periods. Let's extract each distinct responsibility: - GTM Systems Architecture & Integration: Design, build, and maintain automations and integrations across the marketing and sales stack, including Salesforce, HubSpot, Asana, Clay, intent/ABM tooling, attribution platforms, and AI-SDR tools. Own the technical integration points and roadmap so data and handoffs between systems stay reliable, scalable, auditable and low-maintenance across global GTM teams. - AI-Assisted Campaign Creation: Build agentic workflows that support campaign creation end to end, from brief intake to first-draft asset generation, using Claude Enterprise, Copilot Studio, and comparable tools. Orchestrate agents across MCP connectors to optimize AI usage across the tech stack. Partner with Growth Marketing and Customer Growth Marketing to cut manual production time on recurring campaign types, while keeping human review in the loop. - ABM Personalization at Scale: Design and build workflows that generate personalized, on-brand ABM content and outreach at scale, drawing on firmographic, intent, product usage, and customer health data. Keep personalization logic aligned with the ILM Messaging Framework and brand guidelines, and build in review checkpoints so output stays accurate and on-brand. - Asana Project & Database Enrichment: Build and maintain automations that keep Asana project and database structures clean and synced with the broader GTM stack. This reduces manual upkeep for campaign, content, and operations teams and gives marketing leadership accurate, real-time visibility into work in flight. - Cross-System Data Flow & Reporting Infrastructure: Ensure GTM systems feed clean, structured and enriched data into systems and reporting and analytics tools, supporting accurate measurement of pipeline, campaign, and content performance. - Governance, Experimentation & Iteration: Flag design or scale risk in workflows and agents before they ship, operating within the existing AI review layer and AI Innovation Board governance. Run technical experiments on automation and agent logic, and iterate based on performance data and commercial impact in partnership with GTM and marketing leadership. We should keep each as

. Now Requirements (mandatory) list: The block after responsibilities seems to be a run-on sentence. We need to split into sensible items. Let's parse: "6–8+ years, with demonstrated ownership of complex GTM systems, cross-functional roadmap delivery, and executive stakeholder management. Demonstrated hands-on experience building automations and integrations across a marketing/RevOps stack, such as Salesforce, HubSpot, Asana, or Clay Experience designing and building AI-assisted workflows or agents in a business context, using tools like Claude, Copilot Studio, or comparable LLM platforms Working fluency orchestrating AI agents through MCP connectors or similar across a multi-tool stack Experience building or supporting content and campaign automation workflows, from brief intake through first-draft asset generation Strong understanding of GTM and marketing operations concepts: lead routing, scoring, attribution, and campaign or project workflows Experience operating in a B2B SaaS or subscription-based GTM environment, ideally across multiple regions, customer segments, or sales motions. Track record building effective working relationships across marketing, sales, RevOps, and IT stakeholders Ability to influence senior Marketing and Revenue stakeholders, prioritize competing requests, and translate business needs into practical technical delivery plans without relying on direct authority. Comfortable working independently as a senior individual contributor embedded in a marketing organization, with accountability for roadmap ownership, technical judgment, documentation, stakeholder alignment, and adoption of delivered workflows." We'll make each line a

. Now Qualifications (preferred) list: The "Preferred Experience..." block plus maybe success measures? But success measures are more like outcomes; could be part of Qualifications or separate. But we have no separate heading for success measures; we could include them under Qualifications as they describe what success looks like. However the instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can put preferred experience under Qualifications. Success measures could also be under Qualifications or maybe under Benefits? But they are more about performance metrics; could be under Qualifications as well. However we might want to keep them separate if we think they are not exactly qualifications but success metrics. But we have no heading for success measures; we could incorporate them into Qualifications as bullet points. Thus Qualifications list: - Preferred Experience in a B2B SaaS GTM, marketing operations, or RevOps environment - Familiarity with Clay, HockeyStack, or comparable enrichment and analytics platforms - Experience building ABM personalization workflows at scale - Experience automating project management tools, such as Asana, to keep cross-team data accurate and up to date - Success measures: AI-assisted workflows and agents that hold up reliably in production and see real adoption across marketing functions, not just GTM and outbound - Measurable reduction in manual production time for campaign creation and ABM personalization at scale - Clean and reliably synced Asana project and database structures across marketing teams - Reliable, low-maintenance integrations across the core GTM stack - Clean, enriched data flowing into database structures, supporting accurate pipeline