Enterprise Account Executive

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The paragraph after "ABOUT THIS ROLE" includes description: "We are looking for a top-performing Enterprise Account Executive...". That's about the role. - Responsibilities: The bullet list after that: "Build and execute a territory plan..." etc. Those are responsibilities. - Requirements/Qualifications/Skills: The "ABOUT YOU" section includes qualifications: 5+ years experience, proven track record, etc. Also "Ideal candidates have:" list. Also "You don't need to code, but you must be 'code-literate'..." etc. Also "Deep familiarity with sales methodologies..." etc. Also "You are ready to meet customers..." etc. Also "MEET YOUR TEAM" maybe not needed. - Benefits: The "WHAT YOU CAN EXPECT FROM US" includes flexible hours, remote budget, stipend, education days, unlimited PTO, Macbook, remote team events, health benefits, 401(k) match, equity options. Also "You can find more information about our benefits per location here: Rasa Perks & Benefits". So we have benefits. - Pay: Not mentioned explicitly. No salary range. So we should NOT include Pay section. - Schedule: Not mentioned explicitly besides "Full-time - 100% Remote - Continental USA". That's schedule? It mentions full-time remote. Could be considered schedule? The rule: include Schedule section only if posting actually states them. It does state "Full-time - 100% Remote - Continental USA". That's schedule info (full-time, remote). So we could include a Schedule section with that. However they said "Prefer a few substantive sections over many thin ones." Might combine schedule into About the role? But schedule is separate. The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The posting does have schedule info: "Full-time - 100% Remote - Continental USA". That's specific. So we can include Schedule section. - Also "MEET YOUR TEAM" maybe not needed as a heading; could be part of About the role or Responsibilities? Probably not needed as separate heading. - "FREQUENTLY ASKED QUESTIONS" is boilerplate? It's not substantive; we should remove. - "ABOUT US" is company description; could be included? Not in allowed headings list. The allowed headings are only those listed. So we should not include About Us as a heading. Could we incorporate into About the role? Probably not; but we could drop it as it's not required headings. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings. So we should not include other headings like About Us, Meet Your Team, FAQ. So we drop them. Thus we need sections: About the role, Responsibilities, Requirements (maybe combine Requirements and Qualifications and Skills?), but we have separate headings allowed: Requirements, Qualifications, Skills. We need to decide how to split content. We have qualifications: 5+ years experience, proven track record, exceeding quotas, experience closing six-and-seven-figure deals, code-literate, self-driven, familiarity with sales methodologies, ready to meet customers. Skills: maybe "code-literate", "infrastructure-fluent", "sales methodologies", "self-driven", "customer-centric hunter mindset". Could be considered skills. Requirements: maybe the experience and track record. We can split: - Requirements: 5+ years experience in sales, specifically in complex technical domains; proven track record of selling large deals to Global 2000 enterprises (top 10% performance); proven history of consistently exceeding quotas ($1M+ ARR targets); experience closing six-and-seven-figure deals ($100k - $1M+ ACV). - Qualifications: You don't need to code, but you must be "code-literate" or "infrastructure-fluent."; self-driven professional who works with urgency and accountability, demonstrated by a track record of building pipeline from scratch and a creative, customer-centric hunter mindset.; Deep familiarity with sales methodologies like MEDDIC, Challenger, or Command of the Message.; You are ready to meet customers and prospects across your territory. - Skills: maybe we could list "APIs, open-source models, infrastructure integration discussion", "technical value and business outcomes bridging", "forecast and manage sales activity", "lead virtual account team", "collect and deliver customer feedback". But those are more responsibilities. Might be better to not have Skills section if content thin. But we have some skill-like items: "code-literate", "infrastructure-fluent", "sales methodologies". Those could be skills. However we already put them in Qualifications. Could combine Qualifications and Skills into one section? But we have separate headings allowed; we can choose to omit Skills if not enough distinct content. The rule: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section called "Requirements". But we have headings for Requirements, Qualifications, Skills. We could use only Requirements and Qualifications, omit Skills. Or we could use Requirements and Qualifications and maybe Skills if we have distinct content. Let's see if we can extract distinct skill items: "Ability to discuss APIs, open-source models, or infrastructure integration with engineering teams." That's a skill. "Ability to lead a virtual account team (Solutions Engineers, Customer Success, Product)". That's a skill. "Ability to forecast and manage sales activity and pipeline". That's a skill. "Ability to work closely with customer success team and develop new opportunities". That's a skill. "Ability to collect and deliver customer feedback to product team". That's a skill. These could be considered skills. However they are also responsibilities. The line between responsibilities and skills is blurry. But we can put them under Responsibilities as bullet points. The responsibilities list already includes many of those items. So we can keep responsibilities as bullet list of duties. Then we can have Qualifications for experience/background, and maybe Skills for specific abilities like code-literate, infrastructure-fluent, sales methodologies. But we already have those in Qualifications. Might be okay to have only Requirements and Qualifications sections, and Benefits, Schedule, About the role. Let's decide: Sections: - About the role: paragraph describing role. - Responsibilities: bullet list of duties (the list after "However, you can expect to:"). - Requirements: bullet list of experience/track record etc. - Qualifications: bullet list of personal attributes, code-literate, sales methodologies, readiness to meet customers. - Benefits: bullet list of benefits. - Schedule: paragraph about full-time remote. We must not repeat job title. No markdown. We need to output only HTML fragment. Let's craft. First, About the role: Use

for prose. The paragraph: "We are looking for a top-performing Enterprise Account Executive to join our team, modeled after the industry's best 'technical closers.' You will drive revenue growth by identifying, cultivating, and closing complex deals with Fortune 500 and Global 2000 enterprises. In this role, you’ll take the time to understand each prospect’s unique challenges, map them to Rasa’s platform, and clearly show how we can deliver value — both to end users and to decision-makers. You will understand and communicate how Rasa can be used across multiple industries and then manage complex deal cycles. We’re a startup, so you’ll have to be comfortable rolling up your sleeves and doing whatever is required to support our mission." That seems good. Responsibilities: Use

• . List items from "However, you can expect to:" bullet list. Let's extract each bullet: - Build and execute a territory plan to target high-value enterprise accounts. Like our top reps, you are expected to be a "full-cycle" hunter, generating your own pipeline while collaborating with SDRs and Marketing. - Navigate multi-stakeholder sales cycles (6-12 months) involving technical champions (Developers, Architects) and economic buyers (C-Suite, LOB Heads) - Bridge the gap between technical value and business outcomes. You must be comfortable discussing APIs, open-source models, or infrastructure integration with engineering teams. - Lead a virtual account team (Solutions Engineers, Customer Success, Product) to win the technical win and the commercial win - Drive and prove technical capabilities and business value of Rasa’s platform - Forecast and manage your sales activity and pipeline to consistently hit revenue targets - Work closely with our customer success team and develop new opportunities for our existing customers - Collect and deliver customer feedback to the product team Make each as
• . Requirements: bullet list from "Ideal candidates have:" but we need to separate experience/track record. Ideal candidates have: - 5+ years experience in sales, specifically in complex technical domains (e.g., AI/ML, DevOps, Database/Infra) - A proven track record of selling large deals to Global 2000 enterprises (top 10% performance) - Proven history of consistently exceeding quotas ($1M+ ARR targets) - Experience closing six-and-seven-figure deals ($100k - $1M+ ACV) We'll put those. Qualifications: bullet list from remaining "ABOUT YOU" after that. - You don't need to code, but you must be "code-literate" or "infrastructure-fluent." - you can hold your own in a room with Engineering Directors - A self-driven professional who works with urgency and accountability, demonstrated by a track record of building pipeline from scratch and a creative, customer-centric hunter mindset. - Deep familiarity with sales methodologies like MEDDIC, Challenger, or Command of the Message - You are ready to meet customers and prospects across your territory We could also include "You are excited about AI assistants, machine learning and letting people interact with machines through text and speech. You are an experienced self-starter who works well with little supervision. You should be able to use your unique personality, creativity and grit to expand our pipeline with new high profile prospects while working with our key customers to increase Rasa’s adoption." That's more about motivation; could be part of About the role or Qualifications. But we already have About the role describing role; we could add a paragraph about motivation in About the role? Might be okay to include in About the role as additional prose. However the About the role currently is a paragraph; we could add another paragraph after it about motivation. But we must not invent or summarize away detail. We can include that as separate

  under About the role? The rule: Use

  for prose. So we can have multiple

  under About the role heading? Usually a section can have multiple paragraphs. We'll keep About the role as maybe two paragraphs: first the role description, second the motivation/excited about AI etc. Let's extract that motivation paragraph: "You are excited about AI assistants, machine learning and letting people interact with machines through text and speech. You are an experienced self-starter who works well with little supervision. You should be able to use your unique personality, creativity and grit to expand our pipeline with new high profile prospects while working with our key customers to increase Rasa’s adoption." Add as second

  under About the role. Now Benefits: bullet list from "WHAT YOU CAN EXPECT FROM US". List: - Flexible hours and a dedicated remote budget - A stipend for professional development & 6 paid education days to help you grow within your role - Unlimited PTO + paid sick leave + paid public holidays - A Macbook, and other tech to help you do your job - We have regular remote team events, as well as an annual company-wide offsite