Lead Account Executive - Global Delivery Partnerships

We need to output HTML fragment with sections: About the role (maybe heading "About the role"), Responsibilities (What You'll Do), Requirements (Basic Qualifications, Preferred Qualifications maybe combined?), Benefits? There's mention of benefits: "You will also be eligible for various benefits." Also "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." Also "Explore our benefits." No specific benefits listed, so we should not create Benefits section unless specific content. Pay: we have OTE ranges for Chicago and San Francisco. So we can create Pay section with that info. Schedule: mention "Unless approved for full remote work, employees must spend at least 50% of their time in-office. Some roles, like those at greenlight hubs, require full-time in-office presence." That's schedule info. So we can create Schedule section. We need headings:

for each section: About the role, Responsibilities, Requirements, Pay, Schedule. Possibly also Benefits? Not specific, so omit. We need to preserve all substantive info, not invent. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. No Job ID. We must remove boilerplate like EEO etc. Remove duplicated lines. We need to parse content. Let's extract sections: About The Role: paragraph(s) after "About The Role". It includes description of team, role responsibilities high-level. We'll put that as prose under About the role heading. What You'll Do: list of duties bullet points (starting with Identify and secure..., Build relationships..., Lead high-stakes negotiations..., Expand product adoption..., Employ critical thinking..., Handle the big picture..., Partner with cross-functional teams..., Bring your analytical A-game..., Champion Uber's differentiated value proposition...). Those are bullet points. Who are we looking for? That's part of About the role? Actually after "About The Role" there is "Who are we looking for?" paragraph describing desired traits. Could be part of About the role or maybe separate but we can include in About the role prose. Basic Qualifications: list of items (Minimum of 6 years..., Experience leading..., Experience building..., Bachelor's Degree...). Those are bullet points. Preferred Qualifications: list (Experience selling into..., Experience with food delivery..., Ability to flex..., Excellent negotiation..., Speed..., Collaborative leadership..., Coachability...). Those bullet points. Pay: OTE ranges for Chicago and San Francisco. Provide details. Schedule: in-office requirement. Benefits: mention "You will also be eligible for various benefits." and "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." No specific benefits listed, so we should not create Benefits section because no specific content. However we could include a short sentence about benefits under Pay? Probably better to include a Benefits section only if specific benefits listed. Since not, we omit. We also have "Ready to Ride?" paragraph motivational, could be considered part of About the role or maybe separate but we can include as prose under About the role or maybe a separate section like "About Uber"? Not needed. We must not include boilerplate like EEO etc. Now produce HTML. Structure:

  About the role

  ... (combined paragraphs)

  Responsibilities

  • ...
  ...

  Requirements

  Maybe split into Basic and Preferred? Could combine but better to have subheadings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements heading and then maybe separate Basic and Preferred as

  or

  with headings? Could use

  Basic Qualifications:

  then list. But they said use

  for section headings; not prohibited to use other tags like

  with bold. We'll keep Requirements heading and then two

  for Basic Qualifications and Preferred Qualifications each followed by

  . Alternatively we could have Qualifications heading and then Basic and Preferred as subheadings using

  ? Not allowed? Only said use

  for section headings; we could still use

  but better to stick to

  for major sections. We'll do:

  Requirements

  Basic Qualifications:

  ...

  Preferred Qualifications:

  ...
  Pay section:

  Pay

  For Chicago, IL-based roles: The total on-target earnings (OTE) range is USD $236,667 - USD $263,333, comprising a base salary range of USD $142,000 - USD $158,000 per year and an annualized cash variable incentive target of USD $94,667 - USD $105,333. For San Francisco, CA-based roles: The OTE range is USD $263,333 - USD $291,667, comprising a base salary range of USD $158,000 - USD $175,000 per year and an annualized cash variable incentive target of USD $105,333 - USD $116,667. The cash variable incentive target is based on individual sales performance and its payment is based on the terms of the Sales Incentive Plan. An equity award and other forms of compensation may be included in the offer.

  Schedule section:

  Schedule

  Unless approved for full remote work, employees must spend at least 50% of their time in-office. Some roles, like those at greenlight hubs, require full-time in-office presence.

  We might also include a brief note about benefits? Not needed. Now ensure we preserve all substantive info: The "Who are we looking for?" paragraph content: "Someone who has proven success negotiating commercial agreements, building best-in-class partnerships with complex brands, and developing deep executive-level relationships; this person is also passionate about food and Uber, and thrives in a fast-paced, cross-functional environment." We'll include that in About the role paragraph. Also "Your primary focus will be working with our restaurant partners and internally across Product, Engineering, Marketing, Operations, Legal, and Finance to develop shared goals and strategies to grow and optimize our partnerships in the US and across mega-regions." Include. Also "Ready to Ride? This isn't the kind of place where you follow a playbook - it's where you help write one. If you're driven by impact, energized by challenge, and ready to shape how the world moves - we'd love to hear from you. You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits. Explore our benefits. Offices remain key to collaboration and Uber's culture. Unless approved for full remote work, employees must spend at least 50% of their time in-office. Some roles, like those at greenlight hubs, require full-time in-office presence. Ask your Recruiter for details about this role's requirements." Some of that is schedule; we already captured schedule. The motivational part could be included in About the role or maybe a separate section like "About Uber"? Not required. We'll incorporate into About the role paragraph after the primary focus. We must not include application instructions like "Explore our benefits." That's maybe okay as part of benefits but we don't have benefits section. Could include in About the role as a sentence? It's not substantive about role; it's a call to action. Might be considered boilerplate? It's not EEO but it's a generic encouragement. Might be okay to keep but it's not essential. Safer to omit? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." "Explore our benefits." is an application instruction? It's a call to action to explore benefits, maybe considered application instruction. Safer to omit. Also "Ready to Ride? This isn't the kind of place where you follow a playbook - it's where you help write one. If you're driven by impact, energized by challenge, and ready to shape how the world moves - we'd love to hear from you." That's also a call to action; could be considered application instruction. Might be removed. However it's also substantive about culture. The instruction says remove application instructions, not necessarily motivational statements. But "we'd love to hear from you" is application instruction. Safer to omit that sentence. We'll keep the motivational part about culture? Might be borderline. I'll keep the sentence about "Offices remain key to collaboration and Uber's culture." as it's schedule/culture. The rest we can omit. Thus About the role paragraph will include: description of team, role, who we looking for, primary focus, maybe the culture sentence. Let's craft About the role paragraph: "The Uber Eats team is looking for sharp, highly motivated individuals to join our Global Delivery Partnerships team with a focus on managing and expanding relationships with the largest global brands. As a Senior Global Account Executive, you will be responsible for building new commercial partnerships and renegotiating existing agreements that define how these iconic QSR brands grow with Uber. Who are we looking for? Someone who has proven success negotiating commercial agreements, building best-in-class partnerships with complex brands, and developing deep executive-level relationships; this person is also passionate about food and Uber, and thrives in a fast-paced, cross-functional environment. Your primary focus will be working with our restaurant partners and internally across Product, Engineering, Marketing, Operations, Legal, and Finance to develop shared goals and strategies to grow and optimize our partnerships in the US and across mega-regions. Offices remain key to collaboration and Uber's culture." That seems good. Now Responsibilities list: we need to capture each bullet from "What You'll Do". Let's list them exactly: - Identify and secure new commercial opportunities with key strategic global brands - Build relationships with C-level executives and key decision makers within partner organizations - Lead high-stakes negotiations with C-level executives and senior decision makers, structuring deals that create sustainable, mutual value. - Expand product adoption and increase marketing investment, clearly communicating the value of our newest products with a lens of creativity to differentiate our offerings - Employ critical thinking and creative problem-solving skills to navigate negotiations and difficult partner conversations - Handle the big picture and the tiny details. You are organized, timely and ensure nothing gets missed; you are also attuned to high-level strategy and consistently come up with new ways to add value to existing partnerships - Partner with cross-functional teams. Be the voice of the customer and seamlessly navigate internal processes with stakeholders from various teams such as Product, Engineering, Marketing, Operations, Legal, Finance, and more - Bring your analytical A-game. Develop business models and analyses with Ops Analysts to understand trends, provide meaningful insights, and track the impact of initiatives against our goals - Champion Uber's differentiated value proposition in reliability, global scale, and integration capabilities to influence partner investment. We'll put each as
  • . Now Requirements: Basic Qualifications list: - Minimum of 6 years of full-time experience in end-to-end Enterprise sales and/or partnerships - Experience leading conversations with executive-level external stakeholders - Experience building and executing strategic sales plans that result in success - Bachelor's Degree or equivalent Preferred Qualifications list: - Experience selling into or working with large, complex enterprise brands and organizations - Experience with food delivery and/or third-party marketplaces at a high-growth tech company - Ability to flex your analytical skills and utilize data to quantify opportunities and influence decision makers - Excellent negotiation, forecasting, and problem solving skills - Speed, resourcefulness, and a go-getter mentality. You are comfortable working in a fast-paced environment and navigating ambiguity - Collaborative leadership. You can't help but dig in tactically, flexing your analytical skills where needed, and are equally as comfortable