Sr Software Engineer - Android
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading. Do not include Job ID. Remove boilerplate like EEO, legal, etc. Also remove application instructions like "Ready to Ride?" maybe not needed? It's not a list but it's prose; we can keep if it's substantive? It's more like a call to action; but it's not boilerplate? Might be considered application instruction. The instruction says remove application instructions. "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 application encouragement; likely considered application instruction. So we should drop that paragraph. Also "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits. Explore our benefits." That's also application encouragement; drop. Also "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 also application instruction; drop. Also EEO etc drop.
We need to preserve all substantive information: About the role and team description, responsibilities (What You'll Do), qualifications (Basic Qualifications, Preferred Qualifications), Pay (salary ranges), Benefits (mention of bonus program, equity award, 401(k), various benefits), maybe schedule (in-office requirement) but that's more like work arrangement; but we removed as application instruction? Actually schedule info is about in-office requirement; it's substantive about work arrangement. The instruction says include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. The schedule info is specific: "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 include a Schedule section with that content. However we need to check if that is considered application instruction? It's about work location expectations; it's not exactly application instruction but could be considered job details. I'd keep it.
Benefits: mention of bonus program, equity award, other types of comp, 401(k) plan, various benefits. That's substantive.
Pay: salary ranges for SF and Seattle.
We need to format sections: About The Role And Team (maybe heading "About the role"). Use
About the role
then paragraph(s). Then Responsibilities (Responsibilities
) with - items from "What You'll Do". Then Requirements/Qualifications: we could combine Basic and Preferred under Requirements or separate? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements for basic qualifications, Qualifications for preferred? Or we could put both under Requirements and Qualifications. Let's do Requirements for Basic Qualifications, Qualifications for Preferred Qualifications. Then Benefits, Pay, Schedule.
We need to ensure we don't create sections with filler. All have content.
Now extract content.
About The Role And Team paragraph: The first paragraph: "The AM&D (Autonomous Mobility & Delivery) team owns the autonomous future of Uber's Rides and Eats business, which is one of Uber's most important bets as a public company that sets the world in motion. Our goal is to eventually enable mass-scale AV commercialization globally in all 10,000+ cities Uber operates. We are just getting started. As We Gradually But Surely Move Towards This Future, There Is a Full Spectrum Of Engineering Challenges That Need To Be Tackled. For The Autonomous Mobility Product Engineering Team, Specifically How do we drive AV adoption with informative, trustworthy, and exciting experiences?How do we make sure a rider's autonomous ride-share experience is still safe, informative, and trustworthy without a human driver to interact with? From pickup, to on-trip to drop-off. We are solving problems that have never been solved before. Creating solutions that will shape the world's future in autonomous transportation. Therefore, we are looking for the best software engineering talent to join us to write this future chapter for humanity."
We need to preserve that as prose. Might need to fix formatting: there are missing spaces and capitalization but we keep as is.
Now Responsibilities: bullet points from "What You'll Do":
- Contribute to the creation of new features and platform capabilities, leveraging autonomous vehicle data and operational insights to build innovative solutions.
- Build features to drive critical business growth for AV on Uber's platform.
- Drive technical projects from inception to completion, collaborating with cross-functional partners such as product managers, data scientists, and operations teams to deliver impactful solutions.
- Balance technical trade-offs between speed, performance, and quality, making informed decisions that align with both business goals and engineering best practices.
- Cultivate engineering culture and technical excellence to drive up engineering velocity and quality across the team.
Now Basic Qualifications:
- BS/BE degree or equivalent in Computer Science, Engineering, Mathematics, or a related field
- 4+ years of Software Engineering work experience
- Extensive hands-on Android development experience, including proficiency in Java and/or Kotlin programming and code reviews
- Proven ability to lead technical projects end-to-end through all lifecycle stages, from inception through design through global deployment and productionization.
- Expertise in defining standards for testing, monitoring, and alerting systems, while overseeing the execution of complex incident management at an organizational level.
- Grit, drive, and a deep feeling of ownership
- Self-motivated with a passion to learn
- Strong communication and collaboration skills
Preferred Qualifications:
- MS or PhD in Computer Science, Engineering, Mathematics, or a related field
- Experience in working on customer-facing applications in mobility or delivery business.
- Experience in Cross-platform development (iOS and Android)
- Outstanding verbal and written communication and presentation skills
- Experience in developing mobile apps used by hundreds of millions of users globally.
- Strong focus on delivering high-quality mobile UI experiences and feature development
- Deep understanding of software engineering fundamentals, including algorithms, data structures, distributed systems, system design, and architecture.
- Proven experience in identifying architectural gaps and creating org-wide frameworks that improve developer velocity and reduce systemic technical debt.
- Demonstrated leadership in building relationships with internal stakeholders and external partners to rally around a technical vision.
Now Pay: salary ranges:
- For San Francisco, CA-based roles: The base salary range for this role is USD $202,000 per year - USD $224,000 per year.
- For Seattle, WA-based roles: The base salary range for this role is USD $202,000 per year - USD $224,000 per year.
- For all US locations, you will be eligible to participate in Uber's bonus program, and may be offered an equity award & other types of comp.
- All full-time employees are eligible to participate in a 401(k) plan.
- You will also be eligible for various benefits.
We could combine into a Pay section with those bullet points.
Benefits: maybe we already covered benefits in Pay; but we could separate Benefits: mention of bonus program, equity award, other comp, 401(k), various benefits. However Pay already includes those. To avoid duplication, we could put Pay section for salary ranges only, and Benefits section for bonus, equity, 401(k), various benefits. But the instruction says prefer few substantive sections over many thin ones. Could combine Pay and Benefits into one "Compensation and Benefits" but headings limited to given list. We have Pay and Benefits separate. We could put salary ranges in Pay, and benefits in Benefits.
Thus:
Pay:
- For San Francisco, CA-based roles: The base salary range for this role is USD $202,000 per year - USD $224,000 per year.
- For Seattle, WA-based roles: The base salary range for this role is USD $202,000 per year - USD $224,000 per year.
Benefits:
- Eligible to participate in Uber's bonus program.
- May be offered an equity award & other types of compensation.
- All full-time employees eligible to participate in a 401(k) plan.
- Eligible for various benefits.
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.
- Ask your Recruiter for details about this role's requirements. (But that's application instruction; maybe drop the last sentence). Keep only the first two bullets.
Now we need to output HTML fragment only, no markdown.
Let's craft:
About the role
The AM&D (Autonomous Mobility & Delivery) team owns the autonomous future of Uber's Rides and Eats business, which is one of Uber's most important bets as a public company that sets the world in motion. Our goal is to eventually enable mass-scale AV commercialization globally in all 10,000+ cities Uber operates. We are just getting started. As We Gradually But Surely Move Towards This Future, There Is a Full Spectrum Of Engineering Challenges That Need To Be Tackled. For The Autonomous Mobility Product Engineering Team, Specifically How do we drive AV adoption with informative, trustworthy, and exciting experiences?How do we make sure a rider's autonomous ride-share experience is still safe, informative, and trustworthy without a human driver to interact with? From pickup, to on-trip to drop-off. We are solving problems that have never been solved before. Creating solutions that will shape the world's future in autonomous transportation. Therefore, we are looking for the best software engineering talent to join us to write this future chapter for humanity.
Responsibilities
- Contribute to the creation of new features and platform capabilities, leveraging autonomous vehicle data and operational insights to build innovative solutions.
- Build features to drive critical business growth for AV on Uber's platform.
- Drive technical projects from inception to completion, collaborating with cross-functional partners such as product managers, data scientists, and operations teams to deliver impactful solutions.
- Balance technical trade-offs between speed, performance, and quality, making informed decisions that align with both business goals and engineering best practices.
- Cultivate engineering culture and technical excellence to drive up engineering velocity and quality across the team.
Requirements
- BS/BE degree or equivalent in Computer Science, Engineering, Mathematics, or a related field
- 4+ years of Software Engineering work experience
- Extensive hands-on Android development experience, including proficiency in Java and/or Kotlin programming and code reviews
- Proven ability to lead technical projects end-to-end through all lifecycle stages, from inception through design through global deployment and productionization.
- Expertise in defining standards for testing, monitoring, and alerting systems, while overseeing the execution of complex incident management at an organizational level.
- Grit, drive, and a deep feeling of ownership
- Self-motivated with a passion to learn
- Strong communication and collaboration skills
Qualifications
- MS or PhD in Computer Science, Engineering, Mathematics, or a related field
- Experience in working on customer-facing applications in mobility or delivery business.
- Experience in Cross-platform development (iOS and Android)
for prose. Do not repeat job title as heading. Do not include Job ID. Remove boilerplate like EEO, legal, etc. Also remove application instructions like "Ready to Ride?" maybe not needed? It's not a list but it's prose; we can keep if it's substantive? It's more like a call to action; but it's not boilerplate? Might be considered application instruction. The instruction says remove application instructions. "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 application encouragement; likely considered application instruction. So we should drop that paragraph. Also "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits. Explore our benefits." That's also application encouragement; drop. Also "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 also application instruction; drop. Also EEO etc drop. We need to preserve all substantive information: About the role and team description, responsibilities (What You'll Do), qualifications (Basic Qualifications, Preferred Qualifications), Pay (salary ranges), Benefits (mention of bonus program, equity award, 401(k), various benefits), maybe schedule (in-office requirement) but that's more like work arrangement; but we removed as application instruction? Actually schedule info is about in-office requirement; it's substantive about work arrangement. The instruction says include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. The schedule info is specific: "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 include a Schedule section with that content. However we need to check if that is considered application instruction? It's about work location expectations; it's not exactly application instruction but could be considered job details. I'd keep it. Benefits: mention of bonus program, equity award, other types of comp, 401(k) plan, various benefits. That's substantive. Pay: salary ranges for SF and Seattle. We need to format sections: About The Role And Team (maybe heading "About the role"). Use
About the role
then paragraph(s). Then Responsibilities (Responsibilities
) with- items from "What You'll Do". Then Requirements/Qualifications: we could combine Basic and Preferred under Requirements or separate? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements for basic qualifications, Qualifications for preferred? Or we could put both under Requirements and Qualifications. Let's do Requirements for Basic Qualifications, Qualifications for Preferred Qualifications. Then Benefits, Pay, Schedule.
We need to ensure we don't create sections with filler. All have content.
Now extract content.
About The Role And Team paragraph: The first paragraph: "The AM&D (Autonomous Mobility & Delivery) team owns the autonomous future of Uber's Rides and Eats business, which is one of Uber's most important bets as a public company that sets the world in motion. Our goal is to eventually enable mass-scale AV commercialization globally in all 10,000+ cities Uber operates. We are just getting started. As We Gradually But Surely Move Towards This Future, There Is a Full Spectrum Of Engineering Challenges That Need To Be Tackled. For The Autonomous Mobility Product Engineering Team, Specifically How do we drive AV adoption with informative, trustworthy, and exciting experiences?How do we make sure a rider's autonomous ride-share experience is still safe, informative, and trustworthy without a human driver to interact with? From pickup, to on-trip to drop-off. We are solving problems that have never been solved before. Creating solutions that will shape the world's future in autonomous transportation. Therefore, we are looking for the best software engineering talent to join us to write this future chapter for humanity."
We need to preserve that as prose. Might need to fix formatting: there are missing spaces and capitalization but we keep as is.
Now Responsibilities: bullet points from "What You'll Do":
- Contribute to the creation of new features and platform capabilities, leveraging autonomous vehicle data and operational insights to build innovative solutions.
- Build features to drive critical business growth for AV on Uber's platform.
- Drive technical projects from inception to completion, collaborating with cross-functional partners such as product managers, data scientists, and operations teams to deliver impactful solutions.
- Balance technical trade-offs between speed, performance, and quality, making informed decisions that align with both business goals and engineering best practices.
- Cultivate engineering culture and technical excellence to drive up engineering velocity and quality across the team.
Now Basic Qualifications:
- BS/BE degree or equivalent in Computer Science, Engineering, Mathematics, or a related field
- 4+ years of Software Engineering work experience
- Extensive hands-on Android development experience, including proficiency in Java and/or Kotlin programming and code reviews
- Proven ability to lead technical projects end-to-end through all lifecycle stages, from inception through design through global deployment and productionization.
- Expertise in defining standards for testing, monitoring, and alerting systems, while overseeing the execution of complex incident management at an organizational level.
- Grit, drive, and a deep feeling of ownership
- Self-motivated with a passion to learn
- Strong communication and collaboration skills
Preferred Qualifications:
- MS or PhD in Computer Science, Engineering, Mathematics, or a related field
- Experience in working on customer-facing applications in mobility or delivery business.
- Experience in Cross-platform development (iOS and Android)
- Outstanding verbal and written communication and presentation skills
- Experience in developing mobile apps used by hundreds of millions of users globally.
- Strong focus on delivering high-quality mobile UI experiences and feature development
- Deep understanding of software engineering fundamentals, including algorithms, data structures, distributed systems, system design, and architecture.
- Proven experience in identifying architectural gaps and creating org-wide frameworks that improve developer velocity and reduce systemic technical debt.
- Demonstrated leadership in building relationships with internal stakeholders and external partners to rally around a technical vision.
Now Pay: salary ranges:
- For San Francisco, CA-based roles: The base salary range for this role is USD $202,000 per year - USD $224,000 per year.
- For Seattle, WA-based roles: The base salary range for this role is USD $202,000 per year - USD $224,000 per year.
- For all US locations, you will be eligible to participate in Uber's bonus program, and may be offered an equity award & other types of comp.
- All full-time employees are eligible to participate in a 401(k) plan.
- You will also be eligible for various benefits.
We could combine into a Pay section with those bullet points.
Benefits: maybe we already covered benefits in Pay; but we could separate Benefits: mention of bonus program, equity award, other comp, 401(k), various benefits. However Pay already includes those. To avoid duplication, we could put Pay section for salary ranges only, and Benefits section for bonus, equity, 401(k), various benefits. But the instruction says prefer few substantive sections over many thin ones. Could combine Pay and Benefits into one "Compensation and Benefits" but headings limited to given list. We have Pay and Benefits separate. We could put salary ranges in Pay, and benefits in Benefits.
Thus:
Pay:
- For San Francisco, CA-based roles: The base salary range for this role is USD $202,000 per year - USD $224,000 per year.
- For Seattle, WA-based roles: The base salary range for this role is USD $202,000 per year - USD $224,000 per year.
Benefits:
- Eligible to participate in Uber's bonus program.
- May be offered an equity award & other types of compensation.
- All full-time employees eligible to participate in a 401(k) plan.
- Eligible for various benefits.
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.
- Ask your Recruiter for details about this role's requirements. (But that's application instruction; maybe drop the last sentence). Keep only the first two bullets.
Now we need to output HTML fragment only, no markdown.
Let's craft:
About the role
The AM&D (Autonomous Mobility & Delivery) team owns the autonomous future of Uber's Rides and Eats business, which is one of Uber's most important bets as a public company that sets the world in motion. Our goal is to eventually enable mass-scale AV commercialization globally in all 10,000+ cities Uber operates. We are just getting started. As We Gradually But Surely Move Towards This Future, There Is a Full Spectrum Of Engineering Challenges That Need To Be Tackled. For The Autonomous Mobility Product Engineering Team, Specifically How do we drive AV adoption with informative, trustworthy, and exciting experiences?How do we make sure a rider's autonomous ride-share experience is still safe, informative, and trustworthy without a human driver to interact with? From pickup, to on-trip to drop-off. We are solving problems that have never been solved before. Creating solutions that will shape the world's future in autonomous transportation. Therefore, we are looking for the best software engineering talent to join us to write this future chapter for humanity.
Responsibilities
- Contribute to the creation of new features and platform capabilities, leveraging autonomous vehicle data and operational insights to build innovative solutions.
- Build features to drive critical business growth for AV on Uber's platform.
- Drive technical projects from inception to completion, collaborating with cross-functional partners such as product managers, data scientists, and operations teams to deliver impactful solutions.
- Balance technical trade-offs between speed, performance, and quality, making informed decisions that align with both business goals and engineering best practices.
- Cultivate engineering culture and technical excellence to drive up engineering velocity and quality across the team.
Requirements
- BS/BE degree or equivalent in Computer Science, Engineering, Mathematics, or a related field
- 4+ years of Software Engineering work experience
- Extensive hands-on Android development experience, including proficiency in Java and/or Kotlin programming and code reviews
- Proven ability to lead technical projects end-to-end through all lifecycle stages, from inception through design through global deployment and productionization.
- Expertise in defining standards for testing, monitoring, and alerting systems, while overseeing the execution of complex incident management at an organizational level.
- Grit, drive, and a deep feeling of ownership
- Self-motivated with a passion to learn
- Strong communication and collaboration skills
Qualifications
- MS or PhD in Computer Science, Engineering, Mathematics, or a related field
- Experience in working on customer-facing applications in mobility or delivery business.
- Experience in Cross-platform development (iOS and Android)