Senior Lead Go-To-Market Architect

We need to output HTML fragment with sections: About the team, About the role, How You'll Make An Impact (maybe Responsibilities), What Makes You a Great Fit (Qualifications/Skills), Nice to haves (maybe Skills), Why this role matters at Klaviyo (maybe Benefits? Actually it's more about role impact). Also we have Pay range and Travel info: Base Pay Range For US Locations: $164,000—$246,000 USD. Also travel up to 10% travel. So we need Pay and Schedule sections if present. Pay: yes we have base pay range. Schedule: not mentioned besides travel; no explicit schedule like full-time/part-time. So we should not create Schedule section unless present. Benefits: not detailed; only mention "comprehensive range of health, welfare, and wellbeing benefits". That's generic but still a benefit statement. The instruction: never create Benefits section unless posting actually states them. It does state "comprehensive range of health, welfare, and wellbeing benefits based on eligibility." That's a benefit statement, albeit vague. Should we include? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits, albeit generic. So we can include Benefits section with that statement. However also we need to avoid filler like "commensurate with experience". The benefits statement is not filler; it's a statement. So include. We need headings: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About The Team -> could be "About the team" heading. - About The Role -> "About the role" - How You'll Make An Impact -> could be "Responsibilities" - What Makes You a Great Fit -> could be "Qualifications" or "Skills". Since it's about fit, maybe "Qualifications". We'll use "Qualifications". - Nice to haves -> could be "Skills" (nice-to-have skills). We'll use "Skills". - Why this role matters at Klaviyo -> maybe "About the role" already used; but we could treat as "Responsibilities" or maybe a separate section like "Impact". But we only have allowed headings list; we can reuse "Responsibilities" for impact. However we already used Responsibilities for How You'll Make An Impact. Could combine both under Responsibilities. But we need to avoid duplication. Better to have one Responsibilities section covering both How You'll Make An Impact and Why this role matters. But we need to preserve all info; we can combine. - Pay: Base Pay Range. - Benefits: health, welfare, wellbeing benefits. - Schedule: not present; skip. We also have Massachusetts Applicants legal notice; that's boilerplate legal; should be removed per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So drop that. Also drop "Get to Know Klaviyo" etc? That's boilerplate about company; might be considered navigation/legal? It's not EEO but it's generic marketing. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Get to Know Klaviyo" is more like company overview; could be considered navigation? It's not strictly required to keep; but we need to preserve ALL substantive information; is that substantive? It's about company mission; maybe considered boilerplate but could be considered substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "Get to know Klaviyo" is not those categories; it's more about company. However later they also have "AI fluency at Klaviyo includes responsible use..." etc. That's also policy. Might be considered boilerplate. Safer to remove generic marketing fluff that is not specific to role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview may be considered not substantive to the job posting; but it's ambiguous. Usually in these tasks, they want to keep role-specific sections and remove generic fluff like "Get to know Klaviyo", "We're Klaviyo", etc. I'd remove those. Also remove "Massachusetts Applicants" legal notice. Remove "By participating in Klaviyo’s interview process..." etc. Remove "Klaviyo is committed to a policy of equal opportunity..." etc. Remove "IMPORTANT NOTICE: Our company takes the security and privacy..." etc. Thus we keep: - About The Team - About The Role - How You'll Make An Impact - What Makes You a Great Fit - Nice to haves - Why this role matters at Klaviyo - Base Pay Range - Benefits statement (health, welfare, wellbeing benefits) - Travel info (up to 10% travel) maybe under Schedule? Travel is not schedule but could be placed under a short paragraph maybe under "About the role" or separate. Since we don't have a Schedule heading, we could include travel info in a

under About the role or as a separate short paragraph without heading. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Travel is minor metadata; we can fold into a short

maybe under About the role or after Pay. We need to output only HTML fragment, no /. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which content is list vs prose. Responsibilities (How You'll Make An Impact) includes bullet-like sentences each starting with a bold phrase? Actually they are sentences each starting with a capitalized phrase and colon? Let's extract: "Own end-to-end GTM systems architecture: Salesforce, marketing automation, sales engagement, data enrichment, and CS/support platforms, ensuring seamless integration and clean, bidirectional data flow across marketing, sales, and customer success." "Ship AI agents into production, not pilots: build and deploy agentic workflows replacing manual GTM work with intelligent, auditable automation." "Redesign core GTM processes around AI: lead-to-revenue, opportunity management, renewals/expansion, and support handoffs, evaluating and piloting AI-native tools rather than just administering the existing stack." "Stay hands-on: architect and ship meaningful pieces of the solution yourself (Apex, LWC, SOQL, integrations, AI orchestration layers), track your work transparently, and set the technical bar through code review and pairing." "Establish data quality and governance standards that keep GTM data trustworthy at scale, and build the reporting infrastructure that leadership relies on to make decisions." "Serve as the go-to domain expert and trusted advisor to Marketing, Sales, RevOps, CX, and senior/executive leadership translating complex architectural and AI tradeoffs into language that drives decisions in the room, not just documentation after the fact." "Mentor engineers and GTM Systems teammates on system design, AI-native workflow design, and technical tradeoff thinking." These could be list items. What Makes You a Great Fit: also bullet-like sentences each starting with "You've been..." etc. Could be list. Nice to haves: also bullet-like. Benefits: we have a statement: "In addition to base salary, our total compensation package may include participation in the company’s annual cash bonus plan, variable compensation (OTE) for sales and customer success roles, equity, sign-on payments, and a comprehensive range of health, welfare, and wellbeing benefits based on eligibility." That's a list of benefits; could be list. Pay: we have base pay range statement. Travel: short sentence. We'll structure:

  About the team

  ... (the About The Team paragraph)

  About the role

  ... (About The Role paragraph)

  Responsibilities

  • Own end-to-end GTM systems architecture: Salesforce, marketing automation, sales engagement, data enrichment, and CS/support platforms, ensuring seamless integration and clean, bidirectional data flow across marketing, sales, and customer success.
  • Ship AI agents into production, not pilots: build and deploy agentic workflows replacing manual GTM work with intelligent, auditable automation.
  • Redesign core GTM processes around AI: lead-to-revenue, opportunity management, renewals/expansion, and support handoffs, evaluating and piloting AI-native tools rather than just administering the existing stack.
  • Stay hands-on: architect and ship meaningful pieces of the solution yourself (Apex, LWC, SOQL, integrations, AI orchestration layers), track your work transparently, and set the technical bar through code review and pairing.
  • Establish data quality and governance standards that keep GTM data trustworthy at scale, and build the reporting infrastructure that leadership relies on to make decisions.
  • Serve as the go-to domain expert and trusted advisor to Marketing, Sales, RevOps, CX, and senior/executive leadership translating complex architectural and AI tradeoffs into language that drives decisions in the room, not just documentation after the fact.
  • Mentor engineers and GTM Systems teammates on system design, AI-native workflow design, and technical tradeoff thinking.

  Qualifications

  • You've been the technical decision-maker for a complex, multi-system GTM platform (Salesforce or similar) spanning more than one function: marketing, sales, and/or customer success.
  • You are able to both design the architecture and build meaningful parts of it yourself, hands-on with Apex, LWC, Flow, and integrations.
  • You have hands-on experience designing and building agentic AI/LLM-powered workflows for real business problems, and a clear, defensible point of view on where AI should replace human judgment in GTM workflows and where it shouldn't.
  • You can translate ambiguous, cross-functional business problems (marketing, sales, CX, revenue operations) into a technical solution and a clear set of tradeoffs, then explain your reasoning to engineers and business stakeholders alike.
  • You operate with a high degree of autonomy and influence: given a fuzzy, high-visibility problem, you can drive it from discovery through design through delivery, and you're comfortable being the person senior and executive leadership turns to for a straight answer.
  • You have a track record of raising the bar for a team's engineering practice through code review, GitHub-based workflows, and technical mentorship, even when you're the most senior technical voice in the room.

  Skills

  • Nice to haves: Salesforce Application Architect, System Architect, or similar architect-track certification (or equivalent demonstrated experience).
  • Hands-on experience with LLM/agent frameworks (LangChain, CrewAI, LlamaIndex, Agentforce, or similar) and deploying them into production environments.
  • Experience with the broader GTM tooling ecosystem, conversation intelligence (Gong), marketing automation (HubSpot), customer success (Gainsight) and data enrichment (ZoomInfo/Clearbit/Clay) and how each integrates with a CRM.
  • Familiarity with vector databases and RAG patterns for grounding AI agents in GTM and CRM knowledge.
  • Experience at a high-growth software company supporting marketing, sales, and CX systems together not just a single function.
  Maybe we should not include "Nice to haves:" prefix inside each li; just list items. The instruction: preserve ALL substantive information; we can keep the phrase "Nice to haves" as a heading? But we already have Skills heading. Could incorporate "Nice to haves" as a note. But better to keep as list items without the phrase. However we need to preserve the info; we can drop the phrase "Nice