LATIS Sales Lead, Auto, Financial Services & Travel
- for any list of duties/requirements/benefits. So we can have multiple
- inside a section? Probably okay.
We need to preserve all substantive information. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, etc.
Let's extract content:
Role description paragraph: "This role requires the ability to work lawfully in the U.S. without employment-based immigration sponsorship, now or in the future. The LATIS Sales Lead, Auto, Financial Services & Travel owns brand-direct demand creation, enterprise relationship mapping, and commercial opportunity development for LATIS-led use cases across Auto, Financial Services, and Travel/Hospitality, with room to expand into Insurance, telecom-adjacent, and subscription-heavy 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/"
We should keep the URL? Probably yes as substantive. Keep as plain text.
Responsibilities list (bullet points after "Key Responsibilities"):
- Build and maintain target-account lists across Auto, Financial Services, and Travel/Hospitality, with room to expand into Insurance, telecom-adjacent, and subscription-heavy brands.
- Map buying committees across marketing, media, CRM/lifecycle marketing, consumer insights, data science/analytics, product marketing, regional/local market strategy, sales operations (dealer/branch), and finance/forecasting.
- Create and lead senior-level brand conversations that surface enterprise LATIS use cases such as in-market/propensity audiences, household-level segmentation, competitive switching/conquesting, customer file enrichment, and market-level opportunity sizing.
- Identify and qualify enterprise opportunities involving longer consideration cycles and higher-value conversions, including dealer/branch or local-market planning, travel intent and destination affinity, and financial product cross-sell/retention modeling.
- Qualify opportunities and hand off to Solutions Engineering for feasibility, test design, and technical-commercial development, including measurement/attribution test design.
- 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.
Advanced Experience & Deal Complexity (requirements):
- 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 Auto, Financial Services, and Travel/Hospitality.
- Demonstrated experience navigating complex matrixed organizations and running overlay or co-selling motions without clear, single-buyer ownership.
Technical & Data Sophistication (skills?):
- 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.
Executive Rolodex & Buying Committee Mastery (skills?):
- An active, elite Rolodex of active C-level and SVP contacts across Auto, Financial Services, and Travel/Hospitality 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.
Strategic Account Management & Methodology (skills?):
- 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.
Also there is a line: "SAS615 2026-82423 SAS615 2026" maybe job ID, should be dropped.
Then there is paragraph about benefits: "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. A qualified applicant’s criminal history, if any, will be considered in a manner consistent with applicable laws, including local ordinances."
We should keep the sentence about comprehensive pay and benefits package? It's vague but maybe we can keep as part of About the role? But rule says do not create Benefits section unless posting actually states them. It does state benefits package exists, but no specifics. Might be considered filler. Safer to not create a Benefits section. Could we include that sentence in About the role paragraph? It's about company benefits, not role. Might be considered boilerplate? It's not standard EEO but still generic. Might be okay to keep as part of About the role? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This is not exactly EEO but it's about benefits. It's not boilerplate but it's generic. I'd keep it as part of About the role? However About the role should focus on role description. Might be better to omit that sentence entirely as it's not specific to role. The rule says preserve ALL substantive information; do NOT invent or summarize away detail. That sentence is substantive about benefits. But we cannot create a Benefits section because it's not specific. Could we embed it in a
under About the role? That would be mixing role description with benefits. Might be okay but could be considered off-topic. However we need to preserve all substantive information; we could add a
after the role description about benefits. But then we would have a section? Not a heading. Just a paragraph. That seems acceptable. Similarly there is paragraph about Charter Communications etc. That's company description, maybe we keep as About the role? Actually it's about the company. Could be considered "About the company" but not requested heading. We could include as a paragraph under About the role? Might be okay. But we must not create sections like About the role unless we have real specific content. We have role description paragraph (substantive). So we can have
About the role
then awith the role description paragraph (including ability to work lawfully, etc.) plus maybe the benefits paragraph? Might be too much. Better: Keep About the role as the role description only. Keep the benefits paragraph as a separate
without heading? That would be stray text. The instruction says output ONLY the HTML fragment; we can have multiple
and
- etc. Not required to wrap everything in sections. So we can have:
About the role
... role description ...
Responsibilities
- ...
Requirements
- ...
. Responsibilities: list as above. Requirements: combine Advanced Experience & Deal Complexity, Technical & Data Sophistication, Executive Rolodex & Buying Committee Mastery, Strategic Account Management & Methodology into a single list? Might be long but okay. We could split into Requirements and Skills but that would create more sections; but we can keep as one Requirements list. Let's draft. Check for any duplicated lines: none. Remove job ID lines: "SAS615 2026-82423 SAS615 2026". Remove. Remove the paragraph about Charter Communications etc? That's company description; maybe we keep as part of About the role? It's not about role but about company. The instruction didn't forbid company description. It says preserve ALL substantive information. So we should keep it. Could add another
after About the role? But we already have About the role heading; we could add another
under same heading? That would mix role and company. Might be okay but could be confusing. Better to add a separate heading "About the company"? Not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add About the company. So we must either drop that paragraph or incorporate it into About the role (though not ideal). The instruction: "Prefer a few substantive sections over many thin ones." So we could add a paragraph about company under About the role heading. It's still substantive. Let's do that. Thus About the role
will contain two paragraphs? We can just combine them with a space. Now the benefits paragraph: "Here, our employees don’t just have jobs, they're building careers. That’s why