LATIS Sales Lead, Commerce, Retail & Consumer Growth

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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, cookie/navigation, application instructions. Also remove duplicated lines. We need to parse the posting. Content: - First 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. So we can have About the role section. - Then "Key Responsibilities" list: bullet points. List them: 1. Build and maintain target-account lists across Retail, Restaurants/QSR, CPG, and D2C brands. 2. Map buying committees across marketing, media, consumer insights, CRM/loyalty, customer analytics, growth/acquisition, strategy, and finance/revenue growth management. 3. 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. 4. 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. 5. Qualify opportunities and hand off to Solutions Engineering for feasibility, test design, and technical-commercial development. 6. Partner with Category Sales where vertical relationships already exist, co-selling to accelerate enterprise conversations. 7. Partner with agency/national sellers when an agency path is the right route into an account. 8. Own commercial momentum from opportunity qualification through proposal and close, with Solutions Engineering supporting design and feasibility. 9. Operate as a direct hunter with an independent outbound motion, while remaining available as an overlay resource when Category Sales opens a door. - Then "Advanced Experience & Deal Complexity" bullet points (these are requirements/qualifications). Let's treat as Requirements/Qualifications. List: - 7+ years of enterprise "hunter" sales experience specifically 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. - Then "Technical & Data Sophistication" bullet points (skills/qualifications). Could be Skills. List: - Deep fluency in identity resolution, first-party data signals, and privacy-forward architectures (e.g., zero-copy architectures, data clean rooms, pseudonymized matching, and AI/deep learning model training). - Ability to confidently translate advanced technical data applications—like propensity modeling, continuous household-state modeling, and time-sequence demand forecasting—into high-level business value for non-technical executives. - Strong understanding of data privacy landscapes, including CCPA, CPRA, and the evolving mechanics of signal loss and cookie deprecation. - Then "Executive Rolodex & Buying Committee Mastery" bullet points (skills/qualifications). Could be Skills. List: - An active, elite Rolodex of active C-level and SVP contacts across Retail, CPG, and Restaurants, specifically outside the traditional media agency bubble. - Proven capability to map and influence non-traditional buying committees, including Chief Data Officers (CDOs), Heads of Analytics, VP of CRM/Loyalty, and CFOs/Revenue Managers. - Expertise in shifting the narrative away from standard CPM/media buying toward enterprise business outcomes like customer lifetime value (LTV), acquisition efficiency, and market share expansion. - Then "Strategic Account Management & Methodology" bullet points (skills/qualifications). Could be Skills. List: - 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 proof-of-concepts (PoCs) and test designs for skeptical enterprise buyers. - Then there is a line: "SAS615 2026-82421 SAS615 2026". Likely job ID etc. Should be dropped. - Then paragraph: "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." This is generic 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 EEO/legal boilerplate; should be removed. - 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 and Benefits info. So we need Pay section (maybe also Benefits). Benefits: they mention comprehensive pay and benefits package, but not specific benefits. The instruction: never create Benefits section unless posting actually states them. It says "comprehensive pay and benefits package" but doesn't list specifics. That's vague; we should not create Benefits section because no specific benefits listed. However we could include a short paragraph about benefits under About the role? Probably better to not create Benefits section. Pay: we have base pay range and commission target. That's specific. So we create Pay section. Schedule: not mentioned, so omit. Now we need to decide sections: About the role, Responsibilities, Requirements (maybe combine Requirements and Qualifications?), Skills, Pay. We must not repeat job title. Use

for section headings. We need to use

• for any list of duties/requirements/benefits. For prose, use

  . We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: EEO, legal, cookie/navigation, application instructions, duplicated lines. We have duplicated lines? The "SAS615 2026-82421 SAS615 2026" appears twice? Actually appears once but we drop. Also there is "Here, our employees don’t just have jobs, they're building careers..." that's generic but we might keep as part of About the role? It's about company culture; could be part of About the role. However it's somewhat generic but still substantive. We'll keep it as part of About the role. Also "Get to Know Us Charter Communications provides superior communication..." that's about company; could be part of About the role. But it's somewhat generic but still substantive. We'll keep. Also "Grow Your Career Here We’re committed to growing a workforce..." that's EEO/EEO? It's about equal opportunity; might be boilerplate. The instruction: remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove that. Also "Learn about Life at Spectrum." is boilerplate. Also "Watch this video to learn more." is application instruction? Might be removed. Thus we keep only substantive parts: role description, responsibilities, experience/qualifications/skills, pay. Now we need to decide which headings: About the role, Responsibilities, Requirements, Skills, Pay. We could combine Requirements and Qualifications into Requirements (or separate). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content exists. We have qualifications (experience, deal complexity) and also technical & data sophistication, executive rolodex, strategic account management. Those could be split into Requirements (experience) and Qualifications (technical, etc.) but they all are qualifications. Safer to have Requirements (experience) and Skills (technical & data sophistication, executive rolodex, strategic account management). Or we could have Requirements (experience & deal complexity) and Qualifications (technical & data sophistication, executive rolodex, strategic account management, strategic account management & methodology). But the instruction says prefer a few substantive sections over many thin ones. So maybe combine all qualification-like content under Requirements (or Skills). Let's think: The posting has sections: Advanced Experience & Deal Complexity (experience), Technical & Data Sophistication (skills), Executive Rolodex & Buying Committee Mastery (skills), Strategic Account Management & Methodology (skills). So we could have Requirements (experience) and Skills (the rest). That seems reasonable. Thus sections: - About the role (paragraph(s)) - Responsibilities (ul) - Requirements (ul) for experience/deal complexity - Skills (ul) for technical & data sophistication, executive rolodex, strategic account management & methodology - Pay (p with details) We must not include Benefits or Schedule. Now we need to ensure we preserve all substantive info. Let's extract all substantive sentences. From About the role: - "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/" (maybe keep as link? Should we keep URL? It's substantive; we can include as maybe but not required. We'll keep as plain text or link. Probably keep as plain text. - Then the generic company culture paragraph: "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." We'll keep.