Senior Manager, GTM Architect

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate: EEO, accommodation, default together policy, etc. Also remove duplicated lines. Preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The paragraph describing the team and role: "SMC GTM Architect team is the engine driving growth across Snap's small-customer business... We’re looking for a Senior Manager to join the SMC GTM Architect team at Snap Inc! In this role, you’ll design, prototype, and scale the systems that power growth across Snap’s advertiser business, translating central product and engineering capabilities into repeatable GTM workflows and measurable business outcomes". That's about the role. - Responsibilities: The bullet list after "What you’ll do:" includes many items. Those are responsibilities. - Knowledge, Skills, & Abilities: That's skills/abilities. - Minimum Qualifications: qualifications. - Preferred Qualifications: could be additional qualifications or skills. Could be placed under Qualifications or maybe separate but we can combine. - Benefits: The "Our Benefits:" paragraph. - Pay: The compensation section with zones. - Schedule: The "Default Together" policy mentions office 4+ days per week. That's schedule info. However we need to check if we should include schedule section. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Default Together" policy is not exactly EEO; it's about work schedule. It might be considered schedule info. It says: "At Snap Inc. we believe that being together in person helps us build our culture faster... To reflect this, we practice a “default together” approach and expect our team members to work in an office 4+ days per week." That's schedule. So we can include a Schedule section with that content. We must not include sections with filler like "commensurate with experience". Not present. We must not invent or summarize away detail. Preserve all substantive info. We need to format using

for section headings. Use

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

  for prose. We need to decide what goes into each section. Let's extract content precisely. About the role: Could be a paragraph summarizing the role and team. We'll include the description before "What you’ll do:" maybe. Original text: "SMC GTM Architect team is the engine driving growth across Snap's small-customer business. Operating across the full advertiser lifecycle: acquisition, activation, retention, and growth, the team autonomously supports core jobs-to-be-done, driving cost savings and incremental revenue through funnel optimization, scaled outreach, lifecycle marketing, and disciplined experimentation. We are a builder-first team of technically fluent talent (Python, SQL, advanced tooling) that turns platforms and models built by Snap’s Enterprise and Monetization Product and Engineering teams into repeatable GTM workflows for Snap’s advertisers. We’re looking for a Senior Manager to join the SMC GTM Architect team at Snap Inc! In this role, you’ll design, prototype, and scale the systems that power growth across Snap’s advertiser business, translating central product and engineering capabilities into repeatable GTM workflows and measurable business outcomes" We'll put that as About the role. Responsibilities: The list after "What you’ll do:" includes items each starting with a verb. We'll make each a

• . List: - Define and evolve the long-term vision for acquisition, activation, retention, and growth across Snap’s advertisers - Architect the orchestration layer connecting CRM, BigQuery, Ads APIs, and other data platforms to enable unified account context and cross-system coordination - Leverage experimentation infrastructure to run, measure, and learn from tests rapidly, safely, and at scale - Build the personalization backbone that delivers relevant product recommendations, optimizations, and workflows to advertisers at the right moment - Develop a multichannel communications engine that coordinates timely, contextual outreach across in-product, email, and partner surfaces while balancing advertiser experience with measurable impact - Establish a unified signals foundation that brings together behavioral, contextual, and performance data to power personalization, targeting, and decisioning - Drive operational excellence through automation by building tools, APIs, and reusable triggers that reduce manual work and accelerate decision-making - Serve as the technical bridge across Sales, Growth, Business Intelligence, Finance, Product, and Engineering, translating GTM objectives into scalable systems, KPIs, and measurable business outcomes - Recruit, coach, and scale a team of technically fluent builders while fostering a culture of ownership, experimentation, and measurable impact - Present roadmap, adoption, and business outcomes to executive stakeholders and iterate based on outcomes and ROI We'll put these in
  . Knowledge, Skills, & Abilities: The section after responsibilities. Content: "Knowledge of the digital advertising lifecycle, including campaign setup, bidding, optimization, measurement, and the advertiser journey from acquisition through monetization Strong technical foundation in Python and SQL, with the ability to build systems that integrate with CRM platforms, BigQuery, cloud services, Ads APIs, and other data platforms Ability to translate technical capabilities into measurable revenue, productivity, or cost improvements Ability to design scalable systems for experimentation, personalization, multichannel communications, signals, and automated decisioning Ability to partner effectively across Sales, Growth, Business Intelligence, Finance, Product, and Engineering teams Strong business judgment and executive communication skills, including the ability to communicate roadmaps, adoption, ROI, and business outcomes Hands-on operating style with a focus on practical solutions, clear ownership, rapid execution, and simplified complexity Commitment to high standards for testing, observability, data hygiene, and continuous iteration" We'll put as
  under Skills section. Minimum Qualifications: "Bachelor’s degree in Analytics, Computer Science, or a related field, or equivalent experience 12+ years of experience designing and deploying automation systems 2+ years of experience in people management or technical leadership, including leading technical teams or large-scale programs Experience building and shipping production applications or working prototypes Experience using Python, SQL, or equivalent tools and technologies" We'll put as
  under Requirements (or Qualifications). The instruction says use headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Requirements and Qualifications. We need to decide what goes where. Typically Requirements = Minimum Qualifications, Qualifications = Preferred Qualifications. We'll follow that. Thus: -

  Requirements

  for Minimum Qualifications. -

  Qualifications

  for Preferred Qualifications. Preferred Qualifications content: "Experience working with LLMs, retrieval-augmented generation architectures, prompt engineering, evaluation frameworks, and model lifecycle management Experience using AI development tools such as Claude, Codex, or Google ADK Experience building or scaling GTM systems for digital advertising, marketing technology, or other customer lifecycle programs Experience designing systems that connect CRM platforms, cloud data warehouses, APIs, experimentation infrastructure, and cross-channel communications Experience translating behavioral, contextual, and performance signals into personalization, targeting, or automated decisioning Experience recruiting, coaching, and developing technically fluent teams of builders" We'll put as
  . Benefits: The paragraph after "Our Benefits:" includes: "Snap Inc. is its own community, so we’ve got your back! We do our best to make sure you and your loved ones have everything you need to be happy and healthy, on your own terms. Our benefits are built around your needs and include paid parental leave, comprehensive medical coverage, emotional and mental health support programs, and compensation packages that let you share in Snap’s long-term success!" We'll put as

  under Benefits. Pay: The compensation section: "Compensation In the United States, work locations are assigned a pay zone which determines the salary range for the position. The successful candidate’s starting pay will be determined based on job-related skills, experience, qualifications, work location, and market conditions. The starting pay may be negotiable within the salary range for the position. These pay zones may be modified in the future. Zone A (CA, WA, NYC): The base salary range for this position is $251,000-$377,000 annually. Zone B: The base salary range for this position is $238,000-$358,000 annually. Zone C: The base salary range for this position is $213,000-$320,000 annually. This position is eligible for equity in the form of RSUs." We'll put as

  under Pay. Schedule: The "Default Together" policy paragraph: "Default Together" Policy at Snap: At Snap Inc. we believe that being together in person helps us build our culture faster, reinforce our values, and serve our community, customers and partners better through dynamic collaboration. To reflect this, we practice a “default together” approach and expect our team members to work in an office 4+ days per week. We'll put as

  under Schedule. We must not include EEO etc. Also remove duplicated lines: The opening paragraph repeats "Snap Inc is a technology company..." twice. We should include only once? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to deduplicate. The repeated intro appears twice; we should keep only one instance. Also there is a line: "Snap Inc is a technology company. We believe the camera presents the greatest opportunity to improve the way people live and communicate. Snap contributes to human progress by empowering people to express themselves, live in the moment, learn about the world, and have fun together. The Company operates Snapchat, a visual messaging app that enhances your relationships with friends, family, and the world, and Specs Inc., a wholly-owned subsidiary dedicated to making computing more human, in addition to Bitmoji, Saturn, and other digital services." Then later: "Snap Inc is a technology company. We believe the camera presents the greatest opportunity to improve the way people live and communicate. Snap contributes to human progress by empowering people to express themselves, live in the moment, learn about the world, and have fun together. The Company's three core products are Snapchat, Lens Studio, and Spectacles." There's some variation. We need to keep substantive info but remove duplicated lines. The duplicated lines are the first two sentences repeated. We'll keep one copy of those sentences. Also the part about core products differs: first mentions Snapchat, Specs Inc., Bitmoji, Saturn; second mentions Snapchat, Lens Studio, Spectacles. Both are substantive; we should keep both but avoid duplication of the repeated sentences. Thus About the role could incorporate the company description? Actually the "About the role" section we extracted from later part about SMC GTM Architect team. The earlier company description may be considered background but not necessarily part of the role. The instruction: Preserve ALL substantive information. So we need to include that company description somewhere. Where? Possibly in About the role or maybe a separate section like "About Snap". But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could include company description in About the role paragraph (makes sense). So we will combine the company description with the role description. Thus About the role paragraph will include: - Snap Inc is a technology company. We believe the camera presents the greatest opportunity to improve the way people live and communicate. Snap contributes to human progress by empowering people to express themselves, live in the moment, learn about the world, and have fun together. The Company operates Snapchat, a visual messaging app that enhances your relationships with friends, family, and the world, and Specs Inc., a wholly-owned subsidiary dedicated to making computing more human, in addition to Bitmoji, Saturn, and other digital services. The Company's three core products are Snapchat, Lens Studio, and Spectacles. SMC GTM Architect team is the engine driving growth across