Sr Software Engineer - Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes salary range for SF and Seattle, and mentions bonus program, equity award, 401(k), various benefits. So we have Pay info (salary range). Benefits info: mentions eligibility for bonus program, equity award, other comp, 401(k), various benefits. Also mentions offices, in-office requirement (50% time). That's schedule? It mentions schedule: "Unless approved for full remote work, employees must spend at least 50% of their time in-office. Some roles require full-time in-office presence." That's schedule info. So we can include Schedule section. We need sections: About the role (the initial paragraph about AM&D team). Responsibilities (What You'll Do bullet points). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications). Skills? Might be covered in qualifications; but we could create Skills if there is explicit skill list. The posting includes "Extensive experience with fast-pace metrics-driven product iterations..." etc. That's more qualifications/skills. Could put under Skills. But we need to avoid thin sections. Perhaps combine Preferred Qualifications and Skills into one? But instructions: Use headings for those categories if content exists. We have content for Preferred Qualifications. We could make a Skills section for the listed skill-like items (experience with microservices, ML, OR, cross-functional, etc). However the Preferred Qualifications already list many skill-like items. Might be redundant to split. Safer to include sections: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay, Schedule. That seems reasonable. We must not include filler. Ensure we preserve all substantive info. Let's extract content. About The Role And Team: The 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 that exactly? Probably keep as is but can format as

. Might need to fix capitalization weirdness but preserve meaning. We'll output 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

• items? The instructions: Use
  • for any list of duties/requirements/benefits. The responsibilities are a series of sentences; could treat each sentence as a list item. We'll make
    with each duty as
    • . Ensure we preserve all info. 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'll put as
      • maybe each bullet? It's a single paragraph with conditions. Could keep as

        . But instruction: Use

        • for any list of duties/requirements/benefits. This is not a list but a compound requirement. Could keep as

          . Safer to keep as

          . Qualifications (Preferred Qualifications): list of items: "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 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." Wait, the preferred qualifications section also includes salary and benefits info. Actually the salary and benefits appear after preferred qualifications. We need to separate them: The salary and benefits are separate sections. So we should extract salary and benefits out of that block. Thus Preferred Qualifications ends before "For San Francisco, CA-based roles:" which is Pay. So we need to split. Preferred Qualifications content: "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'll make each as

        • . Now Benefits: The posting says: "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 earlier: "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." Also "Explore our benefits." We'll combine. Thus Benefits section: list items: eligibility for bonus program, equity award, other compensation, 401(k) plan, various benefits. Pay: Salary range for SF and Seattle: USD $202,000 - USD $224,000 per year. Also note that for all US locations same range? It says for SF and Seattle same range. We'll include that. 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." We'll keep as

          maybe. We must not include application instructions like "Ready to Ride? ..." That's motivational but not boilerplate? It's part of posting but not a section; could be included in About the role? It's after qualifications. 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 more like a call to action; could be considered boilerplate? It's not EEO/legal but it's a motivational closing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly application instructions but could be considered a call to apply. Might be considered application instruction? Safer to omit it. Also "Explore our benefits." is application instruction? Might be considered a link. We'll omit. Also "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." That's benefits info, we already captured. Now produce HTML fragment. We'll structure:

          About the role

          ...

          Responsibilities

          • 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.

          Requirements

          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