LATIS Sales Lead, Commerce, Retail & Consumer Growth

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID/requisition numbers as headings; fold minor metadata into short

or drop it. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. We need to parse the posting. Key parts: - Opening sentence: "This role requires the ability to work lawfully in the U.S. without employment-based immigration sponsorship, now or in the future." That's a requirement (work authorization). Could go under Requirements. - Then description: "The LATIS Sales Lead, Commerce, Retail & Consumer Growth owns brand-direct demand creation, enterprise relationship mapping, and commercial opportunity development for LATIS-led use cases across Retail, Restaurants/QSR, CPG, and D2C/digitally native brands. This is a hunter role with overlay responsibility: this person builds and runs their own target-account list and outbound motion, while also co-selling with Category Sales when vertical relationships already exist and partnering with agency/national sellers when an agency path matters. Solutions Engineering supports feasibility, test design, and technical-commercial architecture, freeing this role to focus on enterprise conversations that extend beyond traditional media buyers into CRM, insights, analytics, and finance. Built on one of the nation's largest first-party signal foundations spanning approximately 30 million U.S. households and 500 million connected devices, Latis transforms real-world activity into intelligence that helps organizations understand consumer intent, context, emerging trends and shifting demand at national scale. https://latisintel.com/" That's about the role. Could be "About the role" section. - Then "Key Responsibilities" list: bullet points. - Then "Advanced Experience & Deal Complexity" (maybe Requirements/Qualifications). Then "Technical & Data Sophistication". Then "Executive Rolodex & Buying Committee Mastery". Then "Strategic Account Management & Methodology". Those are all qualifications/requirements/skills. - Then there is a line: "SAS615 2026-82421 SAS615 2026" looks like job ID/requisition numbers; we should drop or fold into short p. - Then: "Here, our employees don’t just have jobs, they're building careers. That’s why we offer a comprehensive pay and benefits package that rewards employees for their contributions to our success, supporting all aspects of their well-being at every stage of life." That's Benefits intro. - Then: "A qualified applicant’s criminal history, if any, will be considered in a manner consistent with applicable laws, including local ordinances." That's legal boilerplate; remove. - Then: "This job posting will remain open until 2026-10-30 07:09 PM (UTC) and will be extended if necessary." That's metadata; could be short p. - Then: "The base pay for this position generally is between $185,000.00 and $210,000.00. The actual compensation offered will carefully consider a wide range of factors, including your skills, qualifications, experience, and location. We comply with local wage minimums and also, certain positions are eligible for additional forms of other incentive-based compensation such as bonuses. In addition, this position has a commission earnings target starting at $140,000." That's Pay section. - Then: "Get to Know Us Charter Communications provides superior communication and entertainment products for residential and business customers through the Spectrum brand. Our offerings include Spectrum Internet®, TV, Mobile and Voice. Beyond our connectivity solutions, we also provide local news, programming and regional sports via Spectrum Networks and multiscreen advertising solutions via Spectrum Reach. When you join our team, you’ll be keeping our customers connected to what matters most in 41 states across the U.S. Watch this video to learn more." That's company overview; could be part of About the role or separate? Not a required heading; but we could include under About the role maybe. However we should not invent sections; we can include as part of About the role prose. - Then: "Grow Your Career Here We’re committed to growing a workforce that reflects the customers and communities we serve – providing opportunities for employment and advancement to all team members. Spectrum is an Equal Opportunity Employer, including job seekers with disabilities and veterans. Learn about Life at Spectrum." That's EEO boilerplate; remove. Thus sections: - About the role: include description of role, maybe also company overview. - Responsibilities: list bullet points. - Requirements: maybe combine Advanced Experience & Deal Complexity, Technical & Data Sophistication, Executive Rolodex & Buying Committee Mastery, Strategic Account Management & Methodology. Could be under Requirements or Qualifications. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to put experience under Requirements, technical fluency under Skills, etc. But we need to preserve all substantive info; we can group. Better: Use Requirements for experience and qualifications; Skills for technical & data sophistication; maybe Qualifications for executive rolodex and strategic account management? But we can also combine. We must not create empty sections. So we need to decide which headings have content. Let's extract content: About the role: The paragraph describing role and company overview. Responsibilities: bullet list under "Key Responsibilities". Let's list them: - Build and maintain target-account lists across Retail, Restaurants/QSR, CPG, and D2C brands. - Map buying committees across marketing, media, consumer insights, CRM/loyalty, customer analytics, growth/acquisition, strategy, and finance/revenue growth management. - Create and lead senior-level brand conversations that surface enterprise LATIS use cases beyond traditional media buys, e.g., audience intelligence, customer matching/enrichment, propensity modeling, lapsed customer reactivation, store/location opportunity analysis, and commerce media. - Identify and qualify enterprise opportunities where LATIS can create measurable value, including acquisition efficiency, customer enrichment/segmentation, behavioral insights, and CAC/LTV or market-prioritization impact. - Qualify opportunities and hand off to Solutions Engineering for feasibility, test design, and technical-commercial development. - Partner with Category Sales where vertical relationships already exist, co-selling to accelerate enterprise conversations. - Partner with agency/national sellers when an agency path is the right route into an account. - Own commercial momentum from opportunity qualification through proposal and close, with Solutions Engineering supporting design and feasibility. - Operate as a direct hunter with an independent outbound motion, while remaining available as an overlay resource when Category Sales opens a door. That's 9 items. Requirements: maybe "Advanced Experience & Deal Complexity": 7+ years enterprise hunter sales experience selling high-ticket data platforms, identity resolution, predictive analytics, clean rooms, or advanced programmatic/SaaS solutions. Proven track record of closing 7-figure enterprise deals ($1M+ ARR) with continuous, multi-year expansion, specifically targeting Fortune 500 brands in Retail, CPG, or QSR. Demonstrated experience navigating complex matrixed organizations and running overlay or co-selling motions without clear, single-buyer ownership. Also work authorization: ability to work lawfully in the U.S. without employment-based immigration sponsorship, now or in the future. Qualifications: maybe "Technical & Data Sophistication": deep fluency in identity resolution, first-party data signals, privacy-forward architectures (zero-copy, data clean rooms, pseudonymized matching, AI/deep learning model training). Ability to translate advanced technical data applications into high-level business value for non-technical executives. Strong understanding of data privacy landscapes, including CCPA, CPRA, and evolving mechanics of signal loss and cookie deprecation. Skills: maybe "Executive Rolodex & Buying Committee Mastery": active elite Rolodex of C-level and SVP contacts across Retail, CPG, Restaurants outside traditional media agency bubble. Proven capability to map and influence non-traditional buying committees, including CDOs, Heads of Analytics, VP of CRM/Loyalty, CFOs/Revenue Managers. Expertise in shifting narrative away from standard CPM/media buying toward enterprise business outcomes like customer LTV, acquisition efficiency, market share expansion. Also "Strategic Account Management & Methodology": mastery of complex enterprise sales methodologies to qualify out weak pipeline opportunities early and compress lengthy enterprise cycles. Experience partnering closely with Solutions Engineering and Product teams to co-architect custom PoCs and test designs for skeptical enterprise buyers. We could put those under Skills or Qualifications. Since we have both Requirements and Qualifications headings allowed, we can allocate. Let's assign: - Requirements: work authorization + Advanced Experience & Deal Complexity (experience, deals, matrixed org). - Qualifications: Technical & Data Sophistication + Executive Rolodex & Buying Committee Mastery + Strategic Account Management & Methodology. But we might also have Skills heading for something else; but we can skip Skills if no distinct content left. However we have technical fluency etc which could be Skills. But we already used Qualifications for technical etc. Could also put technical under Skills and executive rolodex under Qualifications. Let's decide: We need to avoid thin sections; better to have few substantive sections. Could combine all qualification-like content under "Qualifications". Then we might not need Skills heading. But we must not create empty headings. So we can omit Skills if we have no distinct content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Schedule? No schedule info given, so omit. Benefits: we have description: comprehensive pay and benefits package that rewards employees for contributions, supporting well-being. Also mention commission earnings target starting at $140k, bonuses etc. That's more Pay though. Benefits: maybe mention "comprehensive pay and benefits package" but not specific benefits like health, 401k. The posting only mentions pay and benefits package generically, plus commission target, bonuses. Could treat that as Pay section (base pay, commission, bonuses). Benefits could be omitted if no specific benefits. However we have "comprehensive pay and benefits package" but no details; we could still include Benefits heading with that sentence? But that is vague; but it's substantive? It says they offer a comprehensive pay and benefits package that rewards employees for contributions, supporting well-being. That's somewhat generic but still info. Might be okay to include Benefits with that sentence. However we also have Pay details. We must not create sections with filler like "commensurate with experience". This is not filler; it's a statement about benefits package. It's okay. Thus Benefits:

A comprehensive pay and benefits package that rewards employees for their contributions to our success, supporting all aspects of their well-being at every stage of life.

Pay: base pay range $185k-$210k, commission earnings target starting at $140k, bonuses etc. Schedule: none. Now we need to ensure we don't include duplicated lines, boilerplate, etc. Remove lines like "Here, our employees don’t just have jobs..." we used for Benefits. Also remove "A qualified applicant’s criminal history..." etc. Remove "This job posting will remain open..." maybe we could keep as short p under About the role? It's metadata; but instruction says fold minor metadata into a short

or drop it. Could drop it. Probably drop. Remove "Get to Know Us Charter Communications..." we could incorporate into About the role as company overview. That's fine. Remove "Grow Your Career Here..." EEO boilerplate. Remove duplicated lines like "SAS615 2026-82421 SAS615 2026" drop. Now produce HTML fragment. Structure:

About the role

... (role description + company overview)

Responsibilities

• ...