SEO & AEO Lead

We need to output HTML fragment with sections: About the role? Actually the posting includes description of company, role, responsibilities, qualifications, etc. We must use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No placeholder. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO etc. Must preserve all substantive info. We need to parse the posting and extract sections. The posting includes: - Intro about company: "We are an applied AI lab building end-to-end software agents..." That's about the company, maybe "About the role"? Actually "About the role" could be description of role and company. We'll treat as "About the role" section. - Then "The Role" description: "Search is changing rapidly..." That's responsibilities. - Then "What You’ll Do" with bullet points (list). That's responsibilities/duties. - Then sections: "Build the Organic Demand Engine", "Create Search-Optimized Experiences", "Own Technical, On-Page & Off-Page SEO", "Own AEO & AI Search", "Optimize for Pipeline, Not Traffic", "Build the System", "What Success Looks Like". Those are more detailed responsibilities. - Then "You Should Be" with bullet list of qualifications/skills. - Then "Bonus Points" with bullet list. - Then "Equal Opportunity" boilerplate to remove. - No explicit Benefits, Pay, Schedule mentioned. So we should not include those sections. Thus we will have sections: About the role, Responsibilities (maybe combine What You’ll Do and subpoints), Requirements/Qualifications (You Should Be), Skills (maybe combine with Requirements?), Bonus Points could be separate "Preferred Qualifications" but we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: Requirements = You Should Be (mandatory). Qualifications maybe same? But we need to avoid duplication. Could combine Requirements and Qualifications into one? But we must follow instruction: use those headings only when posting has real specific content. We have content for Responsibilities, Requirements (You Should Be), Skills (maybe from Bonus Points?), but Bonus Points are "Bonus Points" not required skills. Could treat as Skills? Or we could create a "Skills" section for Bonus Points. However instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements and Skills into one "Requirements" section containing both mandatory and bonus? But they said use headings like Requirements, Qualifications, Skills. Might be okay to have Requirements for mandatory, Skills for bonus. Qualifications maybe not needed if no distinct content. We'll see. We need to preserve all substantive info; not invent or summarize away detail. So we need to keep bullet points exactly as given (maybe rephrase? Must preserve info, not summarizing away detail). We can keep bullet points as

• each line. We must not include boilerplate like Equal Opportunity. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

  About the role

  We are an applied AI lab building end-to-end software agents. We're the makers of Devin, the first AI software engineer. Our team is extremely talent-dense. Among our founding team, we have world-class competitive programmers, former founders, and leaders from companies at the cutting edge of AI including Scale AI, Palantir, Cursor, Waymo, Tesla, Lunchclub, Modal, Google DeepMind, and Nuro. Building Devin is just the first step—our hardest challenges still lie ahead. If you’re excited to solve some of the world’s biggest problems and build AI that can reason on real-world tasks, apply to join us.

  Then Responsibilities: combine "The Role" paragraph and "What You’ll Do" bullet list and sub-sections? The "What You’ll Do" includes many subheadings (Build the Organic Demand Engine, Create Search-Optimized Experiences, Own Technical, On-Page & Off-Page SEO, Own AEO & AI Search, Optimize for Pipeline, Not Traffic, Build the System, What Success Looks Like). Those are detailed responsibilities. We could keep them as subheadings? But only allowed headings are the specified list; we cannot add other headings like h3 for those subheadings unless they match allowed list. The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

  for section headings (e.g. those). Likely they expect only those headings. Safer to not add extra headings; we can embed the content under Responsibilities as paragraphs and lists. Thus under Responsibilities we can have a paragraph summarizing the role description, then a

  with the bullet points from "What You’ll Do". However the bullet points are long sentences; we can keep them as list items. We must preserve all substantive info; we cannot drop any detail. So we need to include each bullet point from "What You’ll Do". Also the subheadings inside that section (like Build the Organic Demand Engine, etc.) are part of the bullet points? Actually the posting shows: What You’ll Do Build the Organic Demand Engine - Build and execute Cognition's SEO and AEO strategy across Devin, Windsurf, and our broader web presence - Build a scalable organic content engine focused on high-intent searches that can drive qualified users, accounts, and enterprise pipeline - Identify high-value keywords and search themes across enterprise software engineering, AI coding agents, agentic engineering, developer productivity, software development, and related categories - Map search intent across the enterprise buying journey—from problem discovery and education through solution evaluation, competitive research, and purchase intent - Determine the right experience for each opportunity: landing page, use-case page, comparison page, blog, guide, gated resource, template, interactive tool, demo, or other format - Own the strategy and execute against it—you won't just create roadmaps and hand them off to someone else Create Search-Optimized Experiences - Build search-optimized landing pages, solution pages, use-case pages, industry pages, comparison pages, glossary/educational experiences, and other high-intent web experiences - Develop SEO-driven blogs and editorial content in partnership with Product Marketing and subject matter experts - Turn PMM research, positioning, customer stories, product launches, and technical expertise into additional search-optimized assets - Develop gated resources—including guides, templates, benchmarks, reports, and other high-value assets—designed around specific search intent and conversion opportunities - Create search-driven product demos, interactive experiences, tools, and other experiences that help users understand Devin and Windsurf while moving them toward activation or enterprise engagement - Build and optimize conversion paths from organic search to signup, demo, contact, and other high-value actions - Develop programmatic and scalable content opportunities where they can create meaningful incremental demand without sacrificing quality Own Technical, On-Page & Off-Page SEO - Own the technical SEO roadmap across site architecture, crawlability, indexing, internal linking, structured data, page performance, redirects, canonicalization, and other technical foundations - Develop and execute an off-page SEO and authority-building strategy across backlinks, digital PR, third-party publications, industry sites, relevant communities, partnerships, and other sources of authoritative mentions - Identify the publications, websites, organizations, and other sources that influence search visibility and AI-generated answers for our target audiences - Build strategies to earn high-quality links, citations, references, and mentions that strengthen Cognition's authority - Partner with Product Marketing, Communications, Developer Marketing, and others to turn launches, research, customer stories, data, and technical insights into opportunities for external distribution and authority building - Build Cognition's information architecture so that search engines and AI systems can understand our products, use cases, expertise, and relationships between concepts Own AEO & AI Search - Own our emerging AEO / AI-search strategy across ChatGPT, Google AI Overviews, Perplexity, Claude, and other answer engines - Understand how AI systems discover, retrieve, evaluate, and cite information and develop strategies to increase Cognition's visibility in those experiences - Build authority around the categories and topics where Cognition needs to be the company buyers discover and trust - Monitor how Cognition and competitors are represented in AI-generated answers and continuously develop strategies to improve visibility and accuracy Optimize for Pipeline, Not Traffic - Measure organic performance against qualified traffic, account engagement, conversion, and pipeline—not simply sessions and rankings - Develop a framework for prioritizing search opportunities based on intent, competitive difficulty, addressable audience, and potential business impact - Continuously test page structure, content formats, calls to action, offers, internal linking, conversion paths, and other variables to improve performance - Partner with Demand Gen and RevOps to understand which organic programs are actually contributing to enterprise pipeline - Build reporting that makes it clear which topics, pages, and search strategies are creating business value Build the System - Establish the processes, tooling, briefs, templates, workflows, and measurement needed to scale organic production - Build a repeatable system for turning PMM content and subject-matter expertise into multiple search-optimized experiences - Use AI aggressively to accelerate research, content development, competitive analysis, technical audits, content refreshes, and experimentation while maintaining a high quality bar - Work directly with Web and Engineering to ship technical and structural improvements quickly What Success Looks Like - Cognition becomes one of the most visible companies in organic and AI search for the categories we care about - We build a repeatable organic content engine that consistently produces high-quality search experiences across the enterprise buying journey - Cognition ranks for the high-intent searches that matter to enterprise software engineering teams—not just broad informational keywords - Cognition builds meaningful authority across the web through high-quality links, citations, mentions, and third-party references - Organic search becomes a meaningful and measurable source of enterprise pipeline - Search-optimized pages, resources, demos, and other experiences consistently convert organic visitors into high-value actions - Cognition is consistently represented in AI-generated answers when buyers research AI software engineering, coding agents, agentic engineering, and related categories - We have a scalable operating system for identifying search opportunities, producing content, launching pages, building authority, measuring results, and iterating - Every major PMM initiative has an organic distribution and search strategy attached to it Thus we need to include all those bullet points. Now "You Should Be" bullet list: - A strong SEO operator who has built or significantly scaled organic growth at a B2B technology company - Equally comfortable with strategy and execution. You should want to identify the opportunity and then personally build the strategy, write the brief, launch the experiment, create the page, or work with an engineer to ship it - Deeply hands-on with technical SEO and modern web architecture - A strong content strategist who understands how to match search intent → content format → conversion experience - Experienced with both on-page and off-page SEO, including building authority and earning high-quality links and mentions - Commercially minded. You care about qualified pipeline and revenue, not just rankings, traffic, or impressions - Excited about the evolution of search and actively experimenting with how AI changes discovery and information retrieval - A systems thinker who can turn a collection of one-off SEO projects into a scalable content and demand-generation engine - Comfortable operating with significant autonomy and ambiguity. You'll be building this function from scratch - An excellent collaborator who can work across Product Marketing, Demand Gen, Web, Engineering, Communications, and RevOps - AI-native. You use AI to move faster, automate repetitive work, analyze large amounts of information, and raise the quality of your output Bonus Points bullet list: - Experience with enterprise B2B software, developer tools, AI, infrastructure, or cybersecurity - Experience building SEO programs for complex technical products - Experience building content engines around high-intent commercial searches - Experience with