Jobs · Engineering · Washington

Software Engineer II - Machine Learning Engineer

Uber · Seattle, WA · 1 mo ago
Engineering$171k/yrFull-time
We need to output HTML fragment with sections: About the role (maybe "About The Role And Team" heading?), Responsibilities, Qualifications (maybe Basic Qualifications and Preferred Qualifications combined?), Benefits, Pay, Schedule. Must only include sections with real specific content. The posting includes: About The Role And Team (some description). Responsibilities: bullet list under "Key responsibilities include:" with items. Qualifications: Basic Qualifications list, Preferred Qualifications list. Pay: salary ranges for NYC, SF, Seattle, plus mention of bonus program, equity award, other comp. Benefits: mention of 401(k) plan, various benefits, bonuses, equity, other compensation, benefits. Schedule: mention of office requirement: "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. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, legal, scam warning, application instructions, "Ready to Ride?" maybe considered motivational but not boilerplate? It's part of posting but not a section; we can include as prose maybe under About the role? It's not a list; we can keep as paragraph. We must not create sections with filler like "commensurate with experience". Not present. We need to use

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

    for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can reorganize into sections. We need to decide which sections to include: About the role (maybe heading "About the role and team") - we have description paragraph. Responsibilities: list items. Qualifications: could have two sub-sections? But we can combine Basic and Preferred under a single "Qualifications" heading with two lists? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading and inside we can have two lists: Basic Qualifications and Preferred Qualifications as subheadings? But subheadings not specified; we could just have two
      with preceding

      indicating Basic and Preferred. Or we could make separate headings for Basic Qualifications and Preferred Qualifications but those aren't in the allowed list; better to keep under Qualifications. Benefits: we have info about 401(k), bonuses, equity, other compensation, various benefits. Also mention "Explore our benefits." We'll include that. Pay: salary ranges for NYC, SF, Seattle, plus bonus program, equity award, other types of comp. Also mention "You may be eligible for bonuses, equity, and other compensation". We'll include that. Schedule: office requirement. We must not include duplicated lines. Ensure we don't repeat same info. Let's extract substantive content: About The Role And Team: "Operating across key business areas like grocery and food, the Consumer Incentives team drives Uber's growth and long-term profitability. We deliver products that create seamless, affordable, and enjoyable customer experiences by building AI/ML-powered intelligence and sophisticated distributed systems at scale for hundreds of millions of global users." What You'll Do: "In this role, you will build products powered by advanced AI/ML solutions and scalable distributed systems. Your work will optimize user experiences across multiple verticals, such as grocery and food, while fostering sustainable business growth." Key responsibilities include: - Launching products to power key consumer experience and business outcomes. - Driving projects across full lifecycles spanning initial scoping, offline evaluation, experimental testing, production deployment, and post-launch maintenance. - Designing, tuning, and enhancing systems and algorithms to operate at scale. - Partnering with cross-functional stakeholders across product management, operations, and data science. Basic Qualifications: - 3+ years of experience in an AI/ML/optimization role, or a PhD in a relevant field (CS, OR, EE, Statistics, etc.) - Proficiency in at least one programming language such as Python, Go, or Java - Strong communication skills and ability to work effectively with cross-functional partners - Strong sense of ownership to drive projects end-to-end Preferred Qualifications: - Experience in designing and delivering large-scale consumer products - Experience in developing, evaluating, and deploying ML models & algorithms in production - Experience in experimental design and causal inference Pay: - For New York City, NY-based roles: The base salary range for this role is USD $171,000 per year - USD $190,000 per year. - For San Francisco, CA-based roles: The base salary range for this role is USD $171,000 per year - USD $190,000 per year. - For Seattle, WA-based roles: The base salary range for this role is USD $171,000 per year - USD $190,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. - You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits. (some duplication) Benefits: - All full-time employees are eligible to participate in a 401(k) plan. - 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. - Explore our benefits. Schedule: - 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. We should remove duplicated lines: The benefits statements appear multiple times; we should keep unique info. We need to preserve ALL substantive information; but we can deduplicate identical sentences? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicated lines are to be removed: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to keep each unique piece of info only once. Thus we need to list unique items. Let's compile unique pieces: About the role and team paragraph (two sentences). We'll keep both. What you'll do paragraph (two sentences). Keep. Responsibilities list (4 items). Keep. Basic Qualifications list (4 items). Keep. Preferred Qualifications list (3 items). Keep. Pay: salary ranges for three cities (NYC, SF, Seattle) each same range; we could note that the range is same for those three locations. But we must preserve all substantive info; we could keep each line but they are duplicated except location. They are not identical because location differs. So keep three lines. Bonus program, equity award, other comp: "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." Keep. 401(k) plan: "All full-time employees are eligible to participate in a 401(k) plan." Keep. Various benefits: "You will also be eligible for various benefits." Keep. Bonuses, equity, other compensation, range of benefits: "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." This is similar to previous but includes "range of benefits". Might be considered duplicate but not identical; we could keep both? The instruction says remove duplicated lines. This line is not exactly same as previous; but it's similar. To be safe, we could keep only one that captures both: maybe combine? But we must not invent or summarize away detail. If we combine, we might lose nuance. However the two sentences: "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." The second includes bonuses, equity, other compensation plus range of benefits. The first is just various benefits. The second is more specific. We could keep the second and drop the first as it's covered? But the first is a distinct statement about various benefits; the second mentions bonuses, equity, other compensation plus range of benefits. The first does not mention bonuses/equity. So we need to keep both to preserve that info. However the second already mentions "range of benefits" which covers various benefits. But the first says "various benefits" without specifying bonuses/equity. The second includes bonuses/equity plus range of benefits. So the first is somewhat redundant but adds no new info beyond what's in second? Actually second says "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." That includes bonuses, equity, other compensation, and a range of benefits. The first says "You will also be eligible for various benefits." That is a subset of the second (range of benefits). So the first is redundant; we can drop it per duplicated lines rule. However the first uses "will also be eligible" vs "may be eligible". Slight difference in certainty. But we might consider that as nuance. Safer to keep both? The instruction says remove duplicated lines, not necessarily similar meaning. Since they are not identical strings, we might keep both. But to avoid duplication, we could keep the more specific one and note that it also covers various benefits. However we risk losing the certainty of "will also be eligible". The second uses "may be eligible". The first says "will also be eligible". That's a difference. So we should keep both to preserve that nuance. Thus we keep both. Explore our benefits: "Explore our benefits." Keep as a sentence. Schedule: Offices remain key... etc. Keep. Now we need to format. We'll have sections:

      About the role and team

      Operating across key business areas like grocery and food, the Consumer Incentives team drives Uber's growth and long-term profitability. We deliver products that create seamless, affordable, and enjoyable customer experiences by building AI/ML-powered intelligence and sophisticated distributed systems at scale for hundreds of millions of global users.

      What you'll do

      In this role, you will build products powered by advanced AI/ML solutions and scalable distributed systems. Your work will optimize user experiences across multiple verticals, such as grocery and food, while fostering sustainable business growth.

      Responsibilities

      • Launching products to power key consumer experience and business outcomes.
      • Driving projects across full lifecycles spanning initial scoping, offline evaluation, experimental testing, production deployment, and post-launch maintenance.
      • Designing, tuning, and enhancing systems and algorithms to operate at scale.
      • Partnering with cross-functional stakeholders across product management, operations, and data science.

      Qualifications

      Basic Qualifications

      • 3+ years of experience in an AI/ML/optimization role, or a PhD in a relevant field (CS, OR, EE, Statistics, etc.)
      • Proficiency in at least one programming language such as Python, Go, or Java
      • Strong communication skills and ability to work effectively with cross-functional partners
      • Strong sense of ownership to drive projects end-to-end

      Preferred Qualifications

      • Experience in designing and delivering large-scale consumer products
      • Experience in developing, evaluating, and deploying ML models & algorithms in production
      • Experience in experimental design and causal

Similar jobs