Go-to-market Lead - Avon.AI

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. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate. We need to parse the posting. Sections present: - About the role: there is a paragraph "About The Role" describing player-coach role, etc. So we need

About the role

then

with that content. - Responsibilities: there is "What You Will Do" with subheadings Sales, Marketing and demand generation, Build the organization. So we can put under

Responsibilities

then maybe

• each bullet? The content is paragraphs with sentences. We could break into list items for each bullet. The instruction: Use
  • for any list of duties/requirements/benefits. So we should convert duties into list items. We'll extract each duty. List items: Sales: - Own the full sales cycle with enterprise accounts in the US, from first conversation to closed deal, with a focus on banks, insurers, and other regulated companies. - Identify champions, map buying committees (business, risk, IT, procurement), and run multi-threaded processes that reach sign-off. - Run discovery and demos, scope pilots on the customer's real production conversations, and convert pilots into production contracts. - Manage the pipeline in the CRM with accurate forecasting. Marketing and demand generation: - Build the top of the funnel: outbound campaigns, events, webinars, partner referrals, and content. - Work with partners and resellers, including consulting firms and the AWS Marketplace, to source and accelerate deals. - Sharpen our positioning and messaging for the US market based on what you hear from buyers. Build the organization: - Define the sales process, playbook, and qualification criteria we will scale with. - Help recruit and onboard the next sales and marketing hires as the US business grows. - Feed structured customer and market input back to the product team. We'll put these as
  • under
    . - Requirements: There's "What We Are Looking For". That includes bullet-like sentences. We'll treat as requirements. List: - A US-based seller with a track record of closing enterprise software deals with large organizations, ideally in regulated industries such as banking, insurance, or healthcare. - Experience selling into financial companies is a strong advantage. - Startup background: you have sold an early-stage product without a large brand behind you and are comfortable building from little. - "Full stack" go-to-market: you can prospect, run marketing activities, present to executives, and negotiate contracts yourself. - Comfortable with technical products. You can explain AI agents, quality monitoring, and deployment options (SaaS and private cloud) credibly to both business and IT buyers. - Self-directed and structured: you set your own priorities, build process where none exists, and report clearly. - A connection to Israel, or experience working with an Israeli headquarters, is a plus. We'll put as
    • . - Qualifications: Not separate; maybe overlapping with requirements. The posting doesn't have a separate qualifications section. So we may not include Qualifications heading if no specific content. However we could treat "What We Are Looking For" as qualifications. But we already used Requirements. The instruction: include a section ONLY when posting has real specific content for it. We have content for Requirements. For Qualifications we could omit if not distinct. But we could also combine? Safer to omit Qualifications if no distinct heading. - Skills: Not explicitly listed; maybe covered in requirements. Could omit. - Benefits: There's a paragraph "More than just a job We believe health, happiness, and productivity go hand-in-hand. That's why we're continually looking to enhance the ways we support you with benefits programs and perks that allow every Pagayan to do the best work of their life." That's vague, not specific benefits. No concrete benefits listed. So we should not create Benefits section because no specific content. - Pay: There is "Compensation Range for New York Based Hires $135,000—$155,000 USD". Also earlier: "The pay ranges for New York-based hires are commensurate with candidate experience." That's vague but we have specific range. So we should include Pay section with that range. Also note "Pay ranges for candidates working in locations other than New York may differ based on the cost of labor in that location." That's extra detail. We'll include that as part of Pay section. - Schedule: There's "Location & Engagement: Our primary preference is a full-time role based out of our NYC office (Monday-Thursday), collaborating with the team in Tel Aviv." That's schedule info: full-time, Monday-Thursday in NYC office. So we can include Schedule section with that. We must not include filler like "commensurate with experience" as a heading; but we can include that text inside Pay section? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. So we can include Pay section with the specific range and also note about other locations. That's fine. Schedule: we have specific schedule: full-time role based out of NYC office (Monday-Thursday). So we can include. Now we need to output only HTML fragment, no /, no markdown. We'll structure:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Pay

      Compensation range for New York‑based hires: $135,000—$155,000 USD. Pay ranges for candidates working in locations other than New York may differ based on the cost of labor in that location.

      Schedule

      Primary preference is a full‑time role based out of the NYC office (Monday‑Thursday), collaborating with the team in Tel Aviv.

      We should not include Benefits, Qualifications, Skills sections. Check that we preserved all substantive info: About Pagaya, About Avon AI, About The Role, etc. The About Pagaya and Avon AI sections are company overview; not required to include as per sections? The instruction: we must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. The sections we have are limited to role-specific headings. But we could include a general

      about the company before the role sections. The instruction says use

      for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings or paragraphs outside those. We can include a

      with company overview before the role sections. That would preserve info. Thus we can start with a

      containing the combined "About Pagaya Shape the Future of Finance..." and "About Avon AI". We'll need to ensure we don't repeat job title. The job title is not given explicitly; maybe "Sales Leader" etc but not present. So fine. We'll combine the two about paragraphs into one or two

      s. Let's extract: About Pagaya Shape the Future of Finance Pagaya is building a leading artificial intelligence network to help our partners grow their businesses and better serve their customers. Pagaya is a global technology company making life-changing financial products and services available to more people nationwide, as it reshapes the financial services ecosystem. By using machine learning, a vast data network and a sophisticated AI-driven approach, Pagaya provides comprehensive consumer credit and residential real estate solutions for its partners, their customers, and investors. Its proprietary API and capital solutions integrate into its network of partners to deliver seamless user experiences and greater access to the mainstream economy. Pagaya has offices in New York and Tel Aviv. For more information, visit pagaya.com. Let's create better outcomes together! About Avon AI Avon AI was recently acquired by Pagaya, which backs our growth. Avon AI is the management and control platform for enterprise conversational AI. Enterprises are deploying AI agents faster than they can govern them. Avon AI gives them one place to manage those agents and the knowledge behind them: continuous quality monitoring of real conversations, proactive testing and simulation before changes ship, knowledge-base management, and real-time guardrails that sit inline in the conversation path to block, redact, or correct what an agent says. We are agent-agnostic. Avon AI works with agents our customers built themselves and with third-party agents they only integrate with, across any framework or vendor. Customers run us as SaaS on AWS or deploy the full platform inside their own private cloud when regulation demands it. We are a small, fast-moving team based in Tel Aviv, already deployed at banks and insurers, and working with enterprise customers in finance, healthcare, insurance, travel, and more. We'll put that as maybe two

      s. Now the About The Role paragraph: "About The Role You will be one of the first hires in our sales and marketing organization and our first person on the ground in the US. This is a player-coach role: you carry a quota and close enterprise deals yourself, and as the pipeline grows you help build the US team around you. You own the go-to-market motion end to end: generating demand, finding the champion inside a large regulated organization, mapping the stakeholders, running a complex sales process, and getting to a signed contract. You will work directly with the founders and have real influence over how we sell, what we say, and who we hire next." We'll put that in

      under About the role heading. Now ensure we didn't miss any other substantive info: The "Our Team" and "Our Values" and "More than just a job" sections are also substantive. Should we include them? The instruction: preserve ALL substantive information. So we should include them somewhere. Could add a

      for Our Team, Our Values, More than just a job. However those are generic company culture; still substantive. We'll include them as

      sections after the role-specific sections maybe under a heading like "About Pagaya" but we already have overview. Could add a

      About Pagaya

      but the instruction says use

      for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should stick to those headings? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections; but we could also have other headings? It doesn't explicitly forbid, but to be safe we can incorporate that info into existing sections or as

      without headings. The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but it's safer to just use

      paragraphs for extra info without headings. Thus we will output:

      About Pagaya ...

      About Avon AI ...

      About the role

      ...

      Responsibilities

      ...

      Requirements

      ...

      Pay

      ...

      Schedule

      ...

      Our Team ...

      Our Values ...

      More than just a job ...

      We must ensure we didn't include any boilerplate like cookie/navigation/legal/EEO etc. The text we have doesn