Sr Account Executive, Enterprise, Higher Ed
for headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it—never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the cleaned document.
Content:
- About The Role And Team: description of Uber Transit, role description, responsibilities, etc.
- What You'll Do: list of duties.
- Basic Qualifications: list.
- Preferred Qualifications: list.
- For Los Angeles, CA-based roles: OTE range etc.
- For San Francisco, CA-based roles: OTE range etc.
- For Seattle, WA-based roles: OTE range etc.
- 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. You will also be eligible for various benefits.
- Ready to Ride? (some marketing copy)
- 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... (schedule/office requirement)
- Uber is proud to be an Equal Opportunity employer... (EEO boilerplate, remove)
- If you have a disability... (accommodation request) maybe keep? It's part of EEO/legal boilerplate; we should remove.
We need to include sections only when there is real specific content.
Potential sections:
- About the role (the initial paragraph about Uber Transit and role description). Could be a prose
.
- Responsibilities (the "What You'll Do" list). Use
- .
- Requirements (maybe combine Basic Qualifications and Preferred Qualifications? The instruction says we can have Requirements and Qualifications sections. We could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications, or combine. But we need to avoid thin sections. Could have Requirements (basic) and Qualifications (preferred). Or we could have a single Requirements section containing both basic and preferred? The instruction says use headings for e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have multiple.
- Skills: maybe not explicitly listed; we could infer from qualifications but better not to invent. If no explicit skills list, we should not create a Skills section.
- Benefits: there is mention of "various benefits", "you will also be eligible for various benefits", "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." Also "An equity award and other forms of compensation may be included in the offer." Also "You will also be eligible for various benefits." There's no explicit list of benefits (health, 401k, etc). So we have only generic statement. According to rule: 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. The posting does state benefits exist but not specifics. Is that enough? It says "various benefits" but not enumerated. That might be considered filler/placeholder? The rule says never create Benefits sections unless the posting actually states them. It does state that you will be eligible for various benefits. That's a statement, albeit vague. Should we include a Benefits section with a
saying you will be eligible for various benefits? That seems acceptable as it's not invented detail. However we must not invent details. We can include a short
summarizing that.
- Pay: we have specific OTE ranges for LA, SF, Seattle. That's specific content. So we should include a Pay section with details. Could be a
containing the ranges, maybe bullet list per location.
- Schedule: we have office requirement: "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." That's schedule/content about in-office requirement. So we can include a Schedule section with that info.
- Skills: Not explicitly listed; we could skip.
- Requirements: we have Basic Qualifications (8+ years experience, experience in transit agencies, bachelor's degree, track record, CRM proficiency). That's specific. So Requirements section.
- Qualifications: we have Preferred Qualifications (mobility services, B2G procurement, SaaS sales, resilient owner's mentality, passion for sustainable mobility). That's specific. So Qualifications section.
- About the role: we have initial paragraph describing Uber Transit and role. That's About the role.
- Responsibilities: we have "What You'll Do" list.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Benefits, Schedule.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to remove duplicated lines, boilerplate, navigation, legal, EEO, scam-warning, application instructions. Also remove "Ready to Ride?" marketing copy? That's not boilerplate but maybe considered fluff; but it's part of the posting. It says "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 marketing but not boilerplate; we could keep as part of About the role? Might be considered fluff but it's substantive? It's more of a call to action. The instruction says remove application instructions. This is not exactly application instruction but more of a motivational closing. Might be okay to keep as part of About the role or maybe we could drop as it's not essential. Safer to keep it as part of About the role? However the About the role section already has description; we could append that as a
. It's not duplicated. It's okay.
We also need to remove "Explore our benefits." That's a link/instruction; maybe remove.
We need to remove "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." That's somewhat redundant with benefits section; we could incorporate into Benefits
.
We need to remove "An equity award and other forms of compensation may be included in the offer." That's part of compensation; could be in Pay or Benefits.
We need to remove "The cash variable incentive target is based on individual sales performance and its payment is based on the terms of the Sales Incentive Plan." That's part of Pay details.
We need to remove "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." That's schedule.
We need to remove EEO boilerplate.
Now craft HTML.
Structure:
About the role
Uber Transit is a high-stakes, dedicated division focused on bridging the digital and physical worlds by integrating shared mobility into public transport networks. As a Senior Account Executive, you will lead the expansion of our collaboration with public transport agencies and local governments, taking on the challenge of navigating complex sales cycles that require immense persistence and strategic vision. This role isn't for those seeking a predictable routine; it's for builders who thrive in ambiguity and are energized by the messiness of shaping something from the ground up. You will need a mindset of extreme ownership to manage long-term relationships and coordinate with internal policy and operations teams, ensuring our partnerships drive a real-world reduction in private car dependency.
Maybe also include the "Ready to Ride?" paragraph as part of About the role? Could add another .
But we must not repeat content. Let's include it as a separate
after the description.
Responsibilities
- Lead end-to-end consultative sales processes, navigating the high-pressure environment of negotiations and long-term prospect relationship building.
- Drive growth by prospecting and qualifying opportunities with public transport agencies, often unblocking complex political and operational barriers to close deals.
- Scale transit sales processes in a rapidly changing environment, constantly iterating on territory strategies and using data to make hard calls on resource allocation.
- Collaborate cross-functionally with policy, legal, and product teams to influence our roadmap and ensure our technical solutions meet the unique demands of transit operators.
- Act as an advocate for cities, translating customer pain points into actionable insights for our tech teams while maintaining a disciplined focus on your commercial targets.
- Own your territory like a business, tracking performance through Salesforce and managing stakeholder tension to ensure seamless, high-impact implementation.
Requirements
- 8+ years of experience in enterprise sales, business development, or lead generation.
- Demonstrated experience in sales or consulting to transit agencies or local government bodies.
- Bachelor's degree or equivalent professional experience.
- Proven track record of exceeding revenue targets in a high-growth environment.
- Proficiency in CRM tools such as Salesforce.
Qualifications
- Experience in mobility services or transport technology.
- Deep expertise in B2G procurement processes and public sector stakeholder management.
- Experience selling SaaS or complex technology-based products into traditional industries.
- A resilient, owner's mentality with a passion for advancing sustainable, shared mobility.
Pay
For Los Angeles, CA-based roles: total on-target earnings (OTE) range USD $243,333 – USD $270,000 (base salary USD $146,000 – USD $162,000; annualized cash variable incentive target USD $97,333 – USD $108,000).
For San Francisco, CA-based roles: total OTE range USD $270,000 – USD $300,000 (base salary USD $162,000 – USD $180,000; annualized cash variable incentive target USD $108,000 – USD $120,000).
For Seattle, WA-based roles: total OTE range USD $243,333 – USD $270,000 (base salary USD $146,000 – USD $162,000; annualized cash variable incentive target USD $97,333 – USD $108,000).
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.
Benefits
You will be eligible for various benefits, including bonuses, equity, and other compensation as part of the total rewards package.
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
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it—never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the cleaned document. Content: - About The Role And Team: description of Uber Transit, role description, responsibilities, etc. - What You'll Do: list of duties. - Basic Qualifications: list. - Preferred Qualifications: list. - For Los Angeles, CA-based roles: OTE range etc. - For San Francisco, CA-based roles: OTE range etc. - For Seattle, WA-based roles: OTE range etc. - 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. You will also be eligible for various benefits. - Ready to Ride? (some marketing copy) - 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... (schedule/office requirement) - Uber is proud to be an Equal Opportunity employer... (EEO boilerplate, remove) - If you have a disability... (accommodation request) maybe keep? It's part of EEO/legal boilerplate; we should remove. We need to include sections only when there is real specific content. Potential sections: - About the role (the initial paragraph about Uber Transit and role description). Could be a prose
. - Responsibilities (the "What You'll Do" list). Use
- .
- Requirements (maybe combine Basic Qualifications and Preferred Qualifications? The instruction says we can have Requirements and Qualifications sections. We could put Basic Qualifications under Requirements, Preferred Qualifications under Qualifications, or combine. But we need to avoid thin sections. Could have Requirements (basic) and Qualifications (preferred). Or we could have a single Requirements section containing both basic and preferred? The instruction says use headings for e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have multiple.
- Skills: maybe not explicitly listed; we could infer from qualifications but better not to invent. If no explicit skills list, we should not create a Skills section.
- Benefits: there is mention of "various benefits", "you will also be eligible for various benefits", "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." Also "An equity award and other forms of compensation may be included in the offer." Also "You will also be eligible for various benefits." There's no explicit list of benefits (health, 401k, etc). So we have only generic statement. According to rule: 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. The posting does state benefits exist but not specifics. Is that enough? It says "various benefits" but not enumerated. That might be considered filler/placeholder? The rule says never create Benefits sections unless the posting actually states them. It does state that you will be eligible for various benefits. That's a statement, albeit vague. Should we include a Benefits section with a
saying you will be eligible for various benefits? That seems acceptable as it's not invented detail. However we must not invent details. We can include a short
summarizing that. - Pay: we have specific OTE ranges for LA, SF, Seattle. That's specific content. So we should include a Pay section with details. Could be a
containing the ranges, maybe bullet list per location. - Schedule: we have office requirement: "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." That's schedule/content about in-office requirement. So we can include a Schedule section with that info. - Skills: Not explicitly listed; we could skip. - Requirements: we have Basic Qualifications (8+ years experience, experience in transit agencies, bachelor's degree, track record, CRM proficiency). That's specific. So Requirements section. - Qualifications: we have Preferred Qualifications (mobility services, B2G procurement, SaaS sales, resilient owner's mentality, passion for sustainable mobility). That's specific. So Qualifications section. - About the role: we have initial paragraph describing Uber Transit and role. That's About the role. - Responsibilities: we have "What You'll Do" list. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Benefits, Schedule. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to remove duplicated lines, boilerplate, navigation, legal, EEO, scam-warning, application instructions. Also remove "Ready to Ride?" marketing copy? That's not boilerplate but maybe considered fluff; but it's part of the posting. It says "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 marketing but not boilerplate; we could keep as part of About the role? Might be considered fluff but it's substantive? It's more of a call to action. The instruction says remove application instructions. This is not exactly application instruction but more of a motivational closing. Might be okay to keep as part of About the role or maybe we could drop as it's not essential. Safer to keep it as part of About the role? However the About the role section already has description; we could append that as a
. It's not duplicated. It's okay. We also need to remove "Explore our benefits." That's a link/instruction; maybe remove. We need to remove "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." That's somewhat redundant with benefits section; we could incorporate into Benefits
. We need to remove "An equity award and other forms of compensation may be included in the offer." That's part of compensation; could be in Pay or Benefits. We need to remove "The cash variable incentive target is based on individual sales performance and its payment is based on the terms of the Sales Incentive Plan." That's part of Pay details. We need to remove "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." That's schedule. We need to remove EEO boilerplate. Now craft HTML. Structure:
About the role
Uber Transit is a high-stakes, dedicated division focused on bridging the digital and physical worlds by integrating shared mobility into public transport networks. As a Senior Account Executive, you will lead the expansion of our collaboration with public transport agencies and local governments, taking on the challenge of navigating complex sales cycles that require immense persistence and strategic vision. This role isn't for those seeking a predictable routine; it's for builders who thrive in ambiguity and are energized by the messiness of shaping something from the ground up. You will need a mindset of extreme ownership to manage long-term relationships and coordinate with internal policy and operations teams, ensuring our partnerships drive a real-world reduction in private car dependency.
Maybe also include the "Ready to Ride?" paragraph as part of About the role? Could add another. But we must not repeat content. Let's include it as a separate
after the description.
Responsibilities
- Lead end-to-end consultative sales processes, navigating the high-pressure environment of negotiations and long-term prospect relationship building.
- Drive growth by prospecting and qualifying opportunities with public transport agencies, often unblocking complex political and operational barriers to close deals.
- Scale transit sales processes in a rapidly changing environment, constantly iterating on territory strategies and using data to make hard calls on resource allocation.
- Collaborate cross-functionally with policy, legal, and product teams to influence our roadmap and ensure our technical solutions meet the unique demands of transit operators.
- Act as an advocate for cities, translating customer pain points into actionable insights for our tech teams while maintaining a disciplined focus on your commercial targets.
- Own your territory like a business, tracking performance through Salesforce and managing stakeholder tension to ensure seamless, high-impact implementation.
Requirements
- 8+ years of experience in enterprise sales, business development, or lead generation.
- Demonstrated experience in sales or consulting to transit agencies or local government bodies.
- Bachelor's degree or equivalent professional experience.
- Proven track record of exceeding revenue targets in a high-growth environment.
- Proficiency in CRM tools such as Salesforce.
Qualifications
- Experience in mobility services or transport technology.
- Deep expertise in B2G procurement processes and public sector stakeholder management.
- Experience selling SaaS or complex technology-based products into traditional industries.
- A resilient, owner's mentality with a passion for advancing sustainable, shared mobility.
Pay
For Los Angeles, CA-based roles: total on-target earnings (OTE) range USD $243,333 – USD $270,000 (base salary USD $146,000 – USD $162,000; annualized cash variable incentive target USD $97,333 – USD $108,000).
For San Francisco, CA-based roles: total OTE range USD $270,000 – USD $300,000 (base salary USD $162,000 – USD $180,000; annualized cash variable incentive target USD $108,000 – USD $120,000).
For Seattle, WA-based roles: total OTE range USD $243,333 – USD $270,000 (base salary USD $146,000 – USD $162,000; annualized cash variable incentive target USD $97,333 – USD $108,000).
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.
Benefits
You will be eligible for various benefits, including bonuses, equity, and other compensation as part of the total rewards package.
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