AI Strategist, Financial Services

We need to output HTML fragment with sections: About the role, Responsibilities, Qualifications, maybe Compensation (Pay). Also maybe Benefits? Not present. Schedule? Not present. So include sections where content exists. We must not repeat job title. No Job ID. Remove boilerplate. The posting includes a lot of intro about Perplexity; that is not part of role? The "About The Role" heading appears. We need to include content under that heading: the paragraphs describing role. Should we include the introductory paragraphs before "About The Role"? Those are company overview; not part of role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should have sections for those headings that have content. The intro about Perplexity could be considered part of "About the role"? Actually "About The Role" heading is present; after that they have description. The preceding paragraphs about Perplexity are company overview; could be omitted? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview is substantive but not part of role? It might be considered part of "About the role" or maybe we should include it as a paragraph before the heading? The spec says use headings for sections; we could include a

before first heading for general overview. That's allowed. Not required to wrap in heading. So we can keep the introductory paragraphs as a

before the first heading. We must remove cookie/navigation/legal/EEO etc. There's none. We need to output only HTML fragment, no markdown fences. Let's extract content: Intro paragraphs: "Perplexity is an AI-powered answer engine founded in December 2022 and growing rapidly as one of the world's leading AI platforms. Perplexity has raised over $1B in venture investment from some of the world's most visionary and successful leaders, including Elad Gil, Daniel Gross, Jeff Bezos, Accel, IVP, NEA, NVIDIA, Samsung, and many more. Our objective is to build accurate, trustworthy AI that powers decision-making for people and assistive AI wherever decisions are being made. Throughout human history, change and innovation have always been driven by curious people. Today, curious people use Perplexity to answer more than 780 million queries every month—a number that's growing rapidly for one simple reason: everyone can be curious." Then heading "About The Role". Content after that until "Responsibilities": "Perplexity is building the AI platform for professional finance: Perplexity Computer, our agentic platform that navigates tools, completes multi-step workflows, and connects to the market data, filings, transcripts, and research that investment professionals already rely on, and our API Platform, which powers search, retrieval, and automation across structured and unstructured financial data. At the center of this is our Applied AI / Forward Deployed motion: we work closely with buyside firms—hedge funds, private equity, and asset managers—to distill their core investment processes and embed them into bespoke solutions built on our platform. That means sitting with analysts and PMs to understand how they screen, diligence, monitor, and decide, then translating those workflows into custom skills, agents, and connector configurations that run inside their daily process—and feeding what we learn back into the product so it compounds across customers. As an AI Strategist on our Applied AI team focused on financial services, you are the subject matter expert who makes this real for investment professionals. This is a commercial and sales engineering role: you will own strategic customer engagements end to end—leading discovery, defining what to build, demonstrating frontier capabilities against real investment workflows, and driving deployments from first conversation through production and expansion. You are part customer owner, part product strategist, part sales engineer—fluent in both the language of the deal team and the language of the platform." Then "Responsibilities" heading. Content until "Qualifications": List items: - Own strategic financial-services engagements - Lead discovery with banks, PE firms, hedge funds, and asset managers: what matters to the investment team, what problems they are solving, and which workflows are worth automating - Define scope—what is the right thing to build—and own success metrics, pilot design, and commercial structure - Drive deployment and rollout across front-office teams, with real revenue responsibility alongside Sales - Be the demo and technical proof engine - Build and deliver compelling, workflow-specific demonstrations: screening, comps, diligence, earnings analysis, research synthesis, portfolio monitoring - Prototype workflows, skills, and connector configurations hands-on in Perplexity Computer and the API Platform to prove value in the customer's own use cases - Run pilots and evaluations that hold up to scrutiny from skeptical analysts and PMs - Bring domain judgment to the product - Translate how deal teams, research desks, and portfolio managers actually work into product, connector, and data-partnership priorities - Assess whether we have the right market data, filings, transcripts, and research integrations to serve each finance sub-vertical—and drive the roadmap where we do not - Codify repeatable engagement patterns: discovery templates, finance-specific reference workflows, demo libraries, and deployment playbooks - Operate as the commercial lead - Own senior relationships with investment professionals and technology leaders; move engagements through qualification, scoping, proposal, pricing, legal, and close - Create urgency, write crisp follow-ups, and know when to push and when to wait We need to format as

• . For sub-bullets we can nest
  inside
  • or just keep as separate lines? Probably nest. Then "Qualifications" heading. Content until "Nice-to-Haves" maybe we treat Nice-to-Haves as part of Qualifications? Could be separate section "Nice-to-Haves" but not in list of headings; we could include as part of Qualifications or as a separate section "Nice-to-Haves" but not required. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Nice-to-Haves not listed; we could incorporate into Qualifications as a subsection or just keep as part of Qualifications paragraph. Probably better to keep as part of Qualifications with a note. Qualifications list: - 3+ years of direct experience in investment banking, private equity, hedge funds, equity research, or institutional asset management—you have built models, written memos, and lived the workflows you will now automate - 6+ years of total experience spanning finance and some combination of technical GTM, sales engineering, solutions architecture, AI product strategy, or applied AI with customer exposure - Deep fluency in front-office workflows: screening, comps, diligence, earnings, research synthesis, portfolio construction and monitoring - Strong intuition for AI products, agents, and workflows, with the ability to understand technical systems without needing every detail pre-digested - Comfortable working shoulder-to-shoulder with Forward Deployed Engineers and technical teams: scoping builds together, pairing on prototypes, and translating customer requirements into engineering-ready specs - Demonstrated ability to turn ambiguous customer problems into scoped, executable deployment plans with clear success metrics - Strong commercial instincts and comfort operating with MDs, partners, PMs, CIOs, and CTOs - Excellent written and verbal communication; able to write proposals, customer memos, technical scopes, and launch narratives - High agency and low ego, with the ability to run multiple complex customer workstreams in parallel and make progress before the playbook exists Nice-to-Haves list: - Hands-on experience building with agentic systems, tool-use workflows, MCP, or LLM APIs - Working knowledge of institutional data platforms: FactSet, Bloomberg, S&P Capital IQ, PitchBook, Morningstar, or similar - Experience selling or deploying technology into regulated financial institutions, including security and compliance review - Founder or early-startup operating experience - Strong network across buy-side and sell-side institutions Then compensation: "Compensation Range: $215K - $250K". That's Pay section. We should not include Benefits or Schedule. Now produce HTML:

    Intro paragraphs

    About the role

    ...

    Responsibilities

    • Own strategic financial-services engagements
    • Lead discovery with banks, PE firms, hedge funds, and asset managers: what matters to the investment team, what problems they are solving, and which workflows are worth automating
    • Define scope—what is the right thing to build—and own success metrics, pilot design, and commercial structure
    • Drive deployment and rollout across front-office teams, with real revenue responsibility alongside Sales
    • Be the demo and technical proof engine
      • Build and deliver compelling, workflow-specific demonstrations: screening, comps, diligence, earnings analysis, research synthesis, portfolio monitoring
      • Prototype workflows, skills, and connector configurations hands-on in Perplexity Computer and the API Platform to prove value in the customer's own use cases
      • Run pilots and evaluations that hold up to scrutiny from skeptical analysts and PMs
    • Bring domain judgment to the product
      • Translate how deal teams, research desks, and portfolio managers actually work into product, connector, and data-partnership priorities
      • Assess whether we have the right market data, filings, transcripts, and research integrations to serve each finance sub-vertical—and drive the roadmap where we do not
      • Codify repeatable engagement patterns: discovery templates, finance-specific reference workflows, demo libraries, and deployment playbooks
    • Operate as the commercial lead
      • Own senior relationships with investment professionals and technology leaders; move engagements through qualification, scoping, proposal, pricing, legal, and close
      • Create urgency, write crisp follow-ups, and know when to push and when to wait

    Qualifications

    • 3+ years of direct experience in investment banking, private equity, hedge funds, equity research, or institutional asset management—you have built models, written memos, and lived the workflows you will now automate
    • 6+ years of total experience spanning finance and some combination of technical GTM, sales engineering, solutions architecture, AI product strategy, or applied AI with customer exposure
    • Deep fluency in front-office workflows: screening, comps, diligence, earnings, research synthesis, portfolio construction and monitoring
    • Strong intuition for AI products, agents, and workflows, with the ability to understand technical systems without needing every detail pre-digested
    • Comfortable working shoulder-to-shoulder with Forward Deployed Engineers and technical teams: scoping builds together, pairing on prototypes, and translating customer requirements into engineering-ready specs
    • Demonstrated ability to turn ambiguous customer problems into scoped, executable deployment plans with clear success metrics
    • Strong commercial instincts and comfort operating with MDs, partners, PMs, CIOs, and CTOs
    • Excellent written and verbal communication; able to write proposals, customer memos, technical scopes, and launch narratives
    • High agency and low ego, with the ability to run multiple complex customer workstreams in parallel and make progress before the playbook exists
    Maybe add a subsection for Nice-to-Haves inside Qualifications? Could add another

    Nice-to-Haves

    but not in allowed list. Safer to include as part of Qualifications as a note: maybe add a

    Nice-to-haves: ...

    . But we need to preserve all substantive info. Could add a

    Nice-to-Haves

    even if not in list; instruction says use those headings for sections