Sr Software Engineer - Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Content: - About The Role And Team: description of AM&D team, goal, etc. That's about role/team. - What You'll Do: responsibilities list. - Basic Qualifications: qualifications. - Preferred Qualifications: maybe skills. - Pay: salary ranges for SF and Seattle, plus bonus program, equity award, 401(k), other comp. - Benefits: mention "various benefits", "eligible to participate in Uber's bonus program, may be offered an equity award & other types of comp", "All full-time employees are eligible to participate in a 401(k) plan." Also "You will also be eligible for various benefits." Also "Explore our benefits." Also "Offices remain key to collaboration...". Also "Unless approved for full remote work, employees must spend at least 50% of their time in-office." That's schedule/remote policy. - Schedule: mention in-office requirement: at least 50% time in-office, some roles require full-time in-office. Also maybe remote work possibility. We need to decide sections. We have content for About the role (the first paragraph). Responsibilities (What You'll Do). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications) maybe as Skills? But we can treat Preferred Qualifications as Skills or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections. Possibly combine Preferred Qualifications into Skills or Qualifications. Let's map: - About the role: first paragraph. - Responsibilities: "What You'll Do" bullet points. - Requirements: Basic Qualifications. - Qualifications: maybe Preferred Qualifications? Or we could treat Preferred Qualifications as Skills. But we have both Qualifications and Skills headings allowed. Could put Preferred Qualifications under Qualifications, and maybe Skills under Skills (like specific technical skills). However the posting does not list explicit skills beyond experience areas. Could treat Preferred Qualifications as Skills. Better: Use Requirements for Basic Qualifications, Skills for Preferred Qualifications (since they are about experience/skills). Then Benefits, Pay, Schedule. We must not create sections with filler like "commensurate with experience". Not present. Now extract specifics. About the role 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 talents to join us to write this future chapter for humanity." We need to preserve all substantive info. Could keep as a paragraph. Responsibilities: "What You'll Do As a Senior Software Engineer, you will be expected to lead key projects that contribute to one or several top-line KPIs for the team. You will work closely with cross-functional partners to develop product requirements and technical designs, and push these plans into fruition. Develop a strategic roadmap that helps Uber to achieve specific business goals that advance its strategic goals that strengthens Uber's position as the Autonomous Vehicle rideshare platform of choice. Lead and guide end-to-end execution of multiple projects concurrently across multiple lines of business with deep knowledge and intuition around experience, marketplace dynamics, and platform versatility to drive key metrics from project to project. Ship new products and paradigms that move KPIs quarter over quarter while ensuring platform stability. Develop tech that future-proofs Uber's tech stack for Autonomous Vehicle use cases while making broader company-wide impact where applicable." We can break into bullet list (

• ) each sentence maybe. Requirements (Basic Qualifications): "PhD or equivalent in Computer Science, Engineering, Mathematics, or related field AND 2-years full-time Software Engineering work experience OR 5-years full-time Software Engineering work experience, WHICH INCLUDES 3-years total technical software engineering experience in one or more of the following areas: Programming language (e.g., C, C++, Java, Python, or Go) Note: The 3 years total of specialized software engineering experience may have been gained through education and full-time work experience, additional training, coursework, research, or similar (OR some combination of these). The years of specialized experience are not necessarily in addition to the years of Education & full-time work experience indicated." We need to preserve that exactly. Skills (Preferred Qualifications): list bullet points: - 5+ years of total software development experience - Extensive experience with fast-pace metrics-driven product iterations with strong reliability guardrails - Experience in crafting and developing large-scale distributed systems and scalable backend services that powers fast-pace product iterations using a microservices architecture - Extensive experience working in a fast-changing, groundbreaking domain. - Background in transportation and/or autonomous vehicle industry - Extensive experience building modular and scalable solutions that cater to a variety of clients and use cases. - Extensive experience with product engineering applications of Operations Research and Machine Learning. - Extensive experience navigating complex cross-functional collaboration: Aside from day-to-day collaboration with product and design counterparts, extensive experience working with business, legal, operations, technical project management, etc to drive consensus. - Extensive experience working closely with external partner engineering teams and their cross-functional partners. - Any level of enterprise mobile engineering experience We should keep as list. Benefits: The posting mentions: "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." Also "Explore our benefits." 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." That's more schedule/location. But benefits: "various benefits" is vague; but we can still include a Benefits section with that statement. However we must avoid filler like "various benefits" if it's not specific? The rule: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". "various benefits" is somewhat vague but not exactly placeholder; it's a statement that there are benefits. It's not a specific detail but it's still substantive? Might be considered filler. However the instruction says "Prefer a few substantive sections over many thin ones." If we include Benefits with just "You will also be eligible for various benefits." that's thin. Could combine benefits into Pay section? But Pay section is about salary, bonus, equity, 401(k). Benefits could be separate but we have little detail. Maybe we can omit Benefits section because it's not specific enough. However the posting does mention "various benefits" and "Explore our benefits." That's not specific. According to rule, we should not create a Benefits section unless the posting actually states them. It does state "You will also be eligible for various benefits." That's a statement, albeit vague. But is that considered filler? It's not a specific benefit like health insurance, etc. The rule says avoid filler/placeholder text like "varies", "TBD". "various benefits" is similar to "varies"? Might be considered vague. Safer to omit Benefits section. Pay: we have salary ranges for SF and Seattle, plus bonus program, equity award, other comp, 401(k). That's specific. Schedule: we have in-office requirement: at least 50% time in-office, some roles require full-time in-office. Also mention remote work possibility. That's schedule. Thus sections: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. We must not include Job ID etc. Now produce HTML fragment:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  ...

  Skills

  • ...
  ...

  Pay

  ...

  Schedule

  ...

  Make sure to preserve all substantive info. Let's craft each. About the role paragraph: copy exactly as given but maybe fix capitalization weirdness? We should preserve original text. It has some weird capitalization: "As We Gradually But Surely Move Towards This Future". Keep as is. We'll output:

  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 talents to join us to write this future chapter for humanity.

  Responsibilities: break into bullet points. Sentences: - Lead key projects that contribute to one or several top-line KPIs for the team. - Work closely with cross-functional partners to develop product requirements and technical designs, and push these plans into fruition. - Develop a strategic roadmap that helps Uber to achieve specific business goals that advance its strategic goals that strengthens Uber's position as the Autonomous Vehicle rideshare platform of choice. - Lead and guide end-to-end execution of multiple projects concurrently across multiple lines of business with deep knowledge and intuition around experience, marketplace dynamics, and platform versatility to drive key metrics from project to project. - Ship new products and paradigms that move KPIs quarter over quarter while ensuring platform stability. - Develop tech that future-proofs Uber's tech stack for Autonomous Vehicle use cases while making broader company-wide impact where applicable. Make each
• . Requirements: copy the Basic Qualifications paragraph exactly. We need to preserve line breaks? Use

  . Skills: list each bullet. Pay: include salary ranges and other comp. Text: "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,