Head of Applications

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Sections present: - About The Role (description) - Responsibilities: "IN THIS ROLE, YOU WILL" bullet list. - Requirements: maybe "You May be a good fit if you have" list. - Qualifications: maybe "Ideal candidates will come with 12+ years of experience across product and product leadership roles, preferably at early to mid stage software companies." Also "BACKGROUNDS THAT COULD FIT" list. - Skills: maybe not explicit; could be derived from requirements but we can include as part of requirements. - Benefits: "Benefits And Perks" list. - Pay: not mentioned. So we should NOT include Pay section. - Schedule: not mentioned. So omit. We must not include sections with placeholder like "commensurate with experience". Not present. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the text as is, but format into HTML. We need to avoid duplication. The posting repeats some content: e.g., "TwelveLabs spent years building..." appears both in Who We Are and About The Role. We need to preserve all substantive info but remove duplicated lines? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should deduplicate duplicated lines. We need to identify duplicated lines and keep only one instance. Let's extract content. First part: "Who We Are Video is 90% of the world's data. Most of it is invisible to machines. TwelveLabs builds the intelligence layer to change that. Our multimodal AI models understand video the way humans do — across sight, sound, and motion — and power production-scale AI workloads across media, entertainment, sports, security, and government. We have raised over $200M from Silicon Valley's best VCs, including Index Ventures and NEA, and from leading enterprises like Nvidia and Amazon that are shaping the future of AI. We are a global company, headquartered in San Francisco with offices in Seoul, New York, and London, and employees around the world. We believe the differences in our cultural, educational, and life experiences make our products stronger. Building technology that understands the world in all its complexity requires people who see it from every angle. We are looking for individuals who are driven by hard problems and want their work to matter. Come build it with us!" Then "About The Role TwelveLabs spent years building the intelligence layer for video: shared infrastructure, multimodal video models, and an agent harness — the orchestration layer — that can understand and reason over video. Our vision for video superintelligence and pioneering work for large-scale video understanding allowed us to raise over $200M from Silicon Valley's best VCs like Index Ventures and NEA and leading enterprises like Nvidia and Amazon that are shaping the future of AI. The next chapter for TwelveLabs is to turn that foundation into products that people can use without needing to understand the technology underneath. We are hiring a Head of Applications to build that layer. You will decide where TwelveLabs should play, find the first use cases where our technology creates a step change in the user experience, and turn those insights into products customers use and pay for. You will own the application layer from customer discovery through product, engineering, launch, adoption, and growth. This is a builder-GM role. It is not a conventional product management job, a growth marketing job, or a large-team executive role. You should be comfortable talking with customers in the morning, working through a product or technical tradeoff in the afternoon, and assembling an exceptional team for the 0-to-1 journey that evening. Ideal candidates will come with 12+ years of experience across product and product leadership roles, preferably at early to mid stage software companies." Then "IN THIS ROLE, YOU WILL" list. Then "You May be a good fit if you have" list. Then "What Success Looks Like In The First 90 Days" etc. Then "In the first 3 months", "In the first 6 months". Then "BACKGROUNDS THAT COULD FIT" list. Then "Benefits And Perks" list. We need to decide sections: About the role (maybe combine Who We Are and About The Role? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should have headings exactly those strings? Probably yes: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits". We should not add extra headings like "Who We Are". The "About the role" section should contain the description of the role and maybe company overview? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can include company overview inside About the role. Thus About the role: combine the "Who We Are" paragraph and the "About The Role" paragraph (maybe also the part about ideal candidates? That might be qualifications). We'll keep the substantive info. Responsibilities: the list under "IN THIS ROLE, YOU WILL". We'll turn each bullet into

  . Requirements: maybe the "You May be a good fit if you have" list? That seems like requirements/qualifications. But we also have "Ideal candidates will come with 12+ years of experience..." which is a qualification. And "BACKGROUNDS THAT COULD FIT" list. We need to decide what goes where. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one? But they ask for separate headings. We need to include sections only when posting has real specific content for it. So we need to see if there is distinct content for Requirements vs Qualifications vs Skills. We have: - Requirements: maybe the "You May be a good fit if you have" list (these are requirements). - Qualifications: maybe the "Ideal candidates will come with 12+ years of experience..." and "BACKGROUNDS THAT COULD FIT" list (these are qualifications). - Skills: maybe not explicitly listed; could be derived but we might omit if no specific content. The instruction: "never emit a heading followed by filler/placeholder text". So if we don't have specific skills list, we should omit Skills section. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Check for Pay and Schedule: none, omit. Now we need to deduplicate duplicated lines. Duplicated content: The paragraph about raising $200M appears both in Who We Are and About The Role. We should keep only one instance. Let's see: Who Are paragraph includes: "We have raised over $200M from Silicon Valley's best VCs, including Index Ventures and NEA, and from leading enterprises like Nvidia and Amazon that are shaping the future of AI." About The Role paragraph includes: "Our vision for video superintelligence and pioneering work for large-scale video understanding allowed us to raise over $200M from Silicon Valley's best VCs like Index Ventures and NEA and leading enterprises like Nvidia and Amazon that are shaping the future of AI." These are similar but not identical; they both mention raising $200M, VCs, enterprises. They are duplicated in meaning but not exact text. The instruction says "duplicated lines". Likely they mean exact duplicate lines. Since they are not exact, we may keep both? But to avoid redundancy, we could keep one. However we must preserve ALL substantive information; removing one might lose some nuance (the first mentions raising over $200M from VCs and enterprises; the second mentions that the vision allowed us to raise over $200M...). Both convey similar info; but we could keep the first and drop the second's duplicate mention? The second also includes "Our vision for video superintelligence and pioneering work for large-scale video understanding allowed us to raise over $200M..." which adds nuance about vision enabling raise. That's substantive. So we should keep both but maybe rephrase to avoid duplication? But we cannot invent or summarize away detail. We could keep both as separate sentences; it's okay if they are similar but not identical. The instruction about duplicated lines likely refers to exact repeats like boilerplate. So we keep both. Now we need to format. Let's extract About the role content: Combine: "Who We Are Video is 90% of the world's data. Most of it is invisible to machines. TwelveLabs builds the intelligence layer to change that. Our multimodal AI models understand video the way humans do — across sight, sound, and motion — and power production-scale AI workloads across media, entertainment, sports, security, and government. We have raised over $200M from Silicon Valley's best VCs, including Index Ventures and NEA, and from leading enterprises like Nvidia and Amazon that are shaping the future of AI. We are a global company, headquartered in San Francisco with offices in Seoul, New York, and London, and employees around the world. We believe the differences in our cultural, educational, and life experiences make our products stronger. Building technology that understands the world in all its complexity requires people who see it from every angle. We are looking for individuals who are driven by hard problems and want their work to matter. Come build it with us!" Then "About The Role TwelveLabs spent years building the intelligence layer for video: shared infrastructure, multimodal video models, and an agent harness — the orchestration layer — that can understand and reason over video. Our vision for video superintelligence and pioneering work for large-scale video understanding allowed us to raise over $200M from Silicon Valley's best VCs like Index Ventures and NEA and leading enterprises like Nvidia and Amazon that are shaping the future of AI. The next chapter for TwelveLabs is to turn that foundation into products that people can use without needing to understand the technology underneath. We are hiring a Head of Applications to build that layer. You will decide where TwelveLabs should play, find the first use cases where our technology creates a step change in the user experience, and turn those insights into products customers use and pay for. You will own the application layer from customer discovery through product, engineering, launch, adoption, and growth. This is a builder-GM role. It is not a conventional product management job, a growth marketing job, or a large-team executive role. You should be comfortable talking with customers in the morning, working through a product or technical tradeoff in the afternoon, and assembling an exceptional team for the 0-to-1 journey that evening. Ideal candidates will come with 12+ years of experience across product and product leadership roles, preferably at early to mid stage software companies." We could combine into a few paragraphs. Now Responsibilities: list under "IN THIS ROLE, YOU WILL". Let's extract each bullet: - Set the strategy for TwelveLabs' application layer: which users and workflows to serve, what to build, and what not to build. - Find a focused wedge through direct customer discovery, rapid prototyping, and disciplined market testing. - Ship opinionated, AI-native applications for non-technical users on top of TwelveLabs' core models, agent harness, and shared infrastructure. - Define application-specific evals, task-success criteria, reliability thresholds, human review, and launch guardrails. - Own the full outcome of the applications you ship, including activation, engagement, retention, monetization, and customer value. - Shipping is the start, not the finish. Build a fast learning loop between users and the product. - Turn usage data and customer behavior