Account Executive

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO etc. Also remove navigation/legal etc. We need to preserve all substantive info. We need to parse the posting. Content: - Who We Are: description of company. Could be "About the company" maybe not a required heading but we could put under "About the role"? Actually "Who We Are" is about company. Could be a section "About the company" but not in list of allowed headings. Allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can only use those headings. So we need to map content to those. We have "The Role:" description: responsibilities. So we can put under

About the role

maybe includes description of role. Or we could put responsibilities under Responsibilities heading. We have "Scope of Position:" bullet points (though not bullet). Then "What You'll Do:" list of duties. Those are responsibilities. We have "Requirements" list. We have "Benefits" list. We have "Competitive Salary: Base salary typically falls between $75,000 - $95,000k/year. Commission split is roughly 50/50, with total OTE expected to be $135-175k+All HUNGRY commissions are uncapped". That's pay info. So we need a Pay section. We have no explicit Schedule info. So we should not create Schedule section. We have no Qualifications separate from Requirements? Could treat Requirements as qualifications. But we have both Requirements and maybe Qualifications? The posting has "Requirements" list. Could also include "Qualifications" but we should not create empty. So we will include Requirements heading. Skills: maybe we could extract from requirements: attention to detail, communication skills, etc. But we already have Requirements covering those. Could still create Skills section if we have specific skill list. But we might combine. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. We need to use

for section headings. 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. We need to remove cookie/navigation/legal/EEO etc. So we must cut out the EEO paragraph at end. Also remove duplicated lines. Let's extract substantive content: Who We Are: "HUNGRY is revolutionizing workplace dining with an unwavering commitment to obsessive hospitality and flawless execution. Founded in 2016 by entrepreneurs Eman Pahlavani and Jeff Grass, HUNGRY connects corporate offices in 19 cities across the United States and Canada with top-tier chefs and local restaurants to deliver extraordinary culinary experiences. From large-format catering and memorable events to individually packaged group meals, snacks, and pantry solutions, HUNGRY ensures every detail is thoughtfully handled to prioritize quality and convenience. Rooted in a mission of social responsibility, HUNGRY fosters local economic growth while embracing eco-friendly practices. The company goes even further, donating one meal for every two purchased, making a tangible impact on communities nationwide , as it has already donated over 3 million meals to date." That's substantive. Where to put? Could be under About the role? But About the role is supposed to be about the role, not company. However we have no other heading for company. Could we create a custom heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but maybe we can use other headings? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings; we should stick to those. But we need to place company info somewhere. Perhaps we can put it under About the role as a brief intro? But that would be mixing. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid other headings, but gives examples. Safer to stick to those headings and put company info under About the role? Might be considered not accurate but still a heading. Could also put under Responsibilities? No. Alternatively, we could omit the Who Are section? But we must preserve ALL substantive information. So we need to include it somewhere. Perhaps we can treat it as a preamble

  before any headings. That's allowed: we can have prose

  before headings. The instruction: Use

  for prose. So we can have a

  containing the Who Are description, then headings for role etc. Thus we output:

  Who We Are ...

  Then sections:

  About the role

  maybe we can include a short description: "The Account Executive will be responsible for working on new business sales opportunities for HUNGRY as well as maintaining client relationships. The role calls for building rapport with decision makers and closing business with companies in the surrounding area in order to hit monthly sales quotas and contribute to the overall revenue of your team." That's from The Role. Then

  Responsibilities

  with list from Scope of Position and What You'll Do. We need to combine Scope of Position bullet points (though not bullet) and What You'll Do list. Scope of Position: "New business outreach and relationship managementCultivate new leads and opportunities to grow sales and meet quotaResponsible for achieving goals related to sales growth in designated territoryBuild brand recognition and credibilityCustomer-centric selling approach and full-service support from proposal through implementation and beyond" That seems like a run-on sentence missing punctuation. We need to preserve as is but we can split into list items for clarity. However we must not invent or summarize away detail. We can turn each phrase into a list item, preserving the text. That's okay as it's not summarizing; it's just breaking into items. The instruction: Use
  • for any list of duties/requirements/benefits. So we can make a list. Similarly What You'll Do list: "Conduct daily calls, emails, and in-person visits to prospective and current clientsProvide high-touch customer service to all prospective and current clientsCreate proposals and enter orders with an acute attention to detailEnsure order accuracy by verifying that all catering and delivery data is valid and currentDaily data entry in Customer Relationship Management (CRM) system to track sales activity and goalsObtain payment information prior to catering events and ensure payments are processed accordinglyCollaborate with internal team members & assist our network of chefs/vendors with new menu creation and organizationCollaborate with Marketing Department on promotional emails and materialsSupport Tech Team with creating and designing enhancements and improvements to the websiteRespond to inquiries and inbound leads in a timely manner" Again run-on. We'll split each sentence (they are separated by no punctuation but we can infer). We'll create list items for each duty. We need to be careful not to lose any detail. We'll just split by capital letters? Might be risky but we can approximate. Better: Keep as a single paragraph

    for responsibilities? But instruction says use

    • for any list of duties/requirements/benefits. If we have a list, we should use list. If we keep as paragraph, we might violate. Safer to use list. We'll create list items by splitting at each verb phrase that starts with a capital letter after a lowercase? Not perfect but we can try. Let's manually list duties from the text: From Scope of Position: - New business outreach and relationship management - Cultivate new leads and opportunities to grow sales and meet quota - Responsible for achieving goals related to sales growth in designated territory - Build brand recognition and credibility - Customer-centric selling approach and full-service support from proposal through implementation and beyond From What You'll Do: - Conduct daily calls, emails, and in-person visits to prospective and current clients - Provide high-touch customer service to all prospective and current clients - Create proposals and enter orders with an acute attention to detail - Ensure order accuracy by verifying that all catering and delivery data is valid and current - Daily data entry in Customer Relationship Management (CRM) system to track sales activity and goals - Obtain payment information prior to catering events and ensure payments are processed accordingly - Collaborate with internal team members & assist our network of chefs/vendors with new menu creation and organization - Collaborate with Marketing Department on promotional emails and materials - Support Tech Team with creating and designing enhancements and improvements to the website - Respond to inquiries and inbound leads in a timely manner That seems comprehensive. Now Requirements list: - Successful track record in full-cycle catering sales in a high-volume sales environment - Demonstrated account sales experience including breaking into new accounts - Experience with prospecting leads, maintaining target lists, and conducting high volume outbound calls, including cold calls - Ability to sell into multiple accounts simultaneously in a fast-paced environment - Experience creating menus for various catering needs - utilizing knowledge of food safety, portioning, and dietary restrictions - Tremendous attention to detail - Competitive drive and determination - Excellent organizational skills - Excellent oral and written communication skills - Poised and personable presentation skills - Positive, self-starter, go-getter attitude - Demonstrate our Company Values (Entrepreneurial, Simplicity, People Centered, Positivity, Integrity, Gratitude, Urgency & Determination, Quality, Efficiency) We need to keep the parentheses content. Now Benefits list: - Competitive Salary: Base salary typically falls between $75,000 - $95,000k/year. Commission split is roughly 50/50, with total OTE expected to be $135-175k+All HUNGRY commissions are uncapped - Unlimited paid time off - Medical Dental and Vision insurance - 401k (currently not matching) - Employer paid life/disability - Company Sponsored Tele-med & Tele Mental Health Benefits - Equity incentives/Stock Options Note: The first benefit includes salary info; we also have a Pay section. Might duplicate. We could put salary info under Pay section and keep other benefits under Benefits. But the instruction says include a section ONLY when posting has real specific content for it. Pay section: we have salary and commission details. So we should create Pay section with that info. Benefits section should then exclude salary/commission details. Thus we need to parse the Benefits paragraph: "Competitive Salary: Base salary typically falls between $75,000 - $95,000k/year. Commission split is roughly 50/50, with total OTE expected to be $135-175k+All HUNGRY commissions are uncappedUnlimited paid time off Medical Dental and Vision insurance 401k (currently not matching) Employer paid life/disability Company Sponsored Tele-med & Tele Mental Health BenefitsEquity incentives/Stock Options" We need to separate. Pay section: Base salary $75,000 - $95,000k/year (note typo: $95,000k maybe means $95,000? We'll keep as written). Commission split 50/50, total OTE $135-175k+, commissions uncapped. Benefits section: Unlimited