Software Engineer II - Web Engineer

We need to output HTML fragment with sections: About the role (maybe heading "About the role" or "About The Role And Team"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present. We have content: "About The Role And Team" paragraph describing role and team. That's about the role. So we can have

About the role

then

with that paragraph. Then "What You'll Do" is responsibilities. So

Responsibilities

then

• each bullet. Then "Basic Qualifications" and "Preferred Qualifications" maybe combine into Requirements/Qualifications? The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide. Probably we can have

  Qualifications

  then split Basic and Preferred as sub-lists? But they said use
  • for any list of duties/requirements/benefits. So we can have a list for Basic Qualifications and another for Preferred Qualifications under same heading? Or separate headings? The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Basic and Preferred into one Qualifications section with two subheadings? But we cannot use headings other than h3? We could use

    Qualifications

    then

    maybe separate paragraphs for Basic and Preferred? But they want list for requirements. Could do two

    under same heading, each preceded by a

    like "Basic Qualifications:" then list. That seems okay. Then "For New York City..." etc is Pay info. So we need a Pay section. The instruction: include Pay section only if posting actually states them. Yes, they state salary ranges for specific locations and mention bonus, equity, benefits. So we should have

    Pay

    then

    with that info. Then benefits: they mention "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. 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." So we have benefits info. So we can have

    Benefits

    then

    summarizing. Schedule: they mention "Offices remain key to collaboration... 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/location expectation. So we can have

    Schedule

    with that info. We must not include boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines. Also remove "Ready to Ride?" etc maybe considered motivational but not boilerplate? It's part of the posting but not a section heading; we could incorporate into About the role? It's more like a call to action. Might be considered boilerplate? It's not EEO/legal. It's a motivational paragraph. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Ready to Ride?" is not those; it's more like a closing motivational. Could keep as part of About the role or maybe as a separate paragraph under About the role. Probably safe to include in About the role paragraph. We must not repeat the job title as a heading. No job title given explicitly; we ignore. We must not put Job ID/requisition numbers as headings. 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 rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should not omit details, but we can rephrase? Probably we should keep the original sentences but can format into HTML. We'll keep the substance. Let's extract sections: About the role paragraph: "Uber has evolved from a ride-hailing service into an all-in-one platform, connecting users globally through various on-demand offerings across UberX and UberEats. To unite this ecosystem, we introduced Uber One-a paid membership program designed to elevate user experiences with priority service and exclusive perks. Under one unified membership, members unlock enhanced pricing, upgraded rides, dedicated customer support, premium partner benefits, and elevated service quality. With more than 50 million global Uber One members driving over half of our total company revenue, the program is a critical engine for company-wide growth across our core offerings while shaping how users interact with our expanding ecosystem and new company big bets. Join us as we drive Uber's growth and shape expansion into new verticals. In this role on the Membership team, you will help shape the future of the program by architecting next-generation member experiences and benefits in close partnership with cross-functional teams. You will oversee our platform architecture and design highly reliable, scalable systems that power new initiatives across both UberEats and UberX. If you excel at tackling complex technical challenges, crafting impactful products, and driving key business outcomes, the Membership team is the perfect fit for you." That's the about role. Responsibilities (What You'll Do): list bullet points: - Identify new impactful opportunities to evolve the Uber One program across UberEats and UberX - Collaborate with talented engineers, PMs, Data Science and Designers from across the company to design, build, and optimize products used by millions of members globally - Architect robust, highly available, and scalable systems designed to resolve ambiguous technical challenges to serve millions of users. - Align the org on complex tradeoffs between various different technical designs and solutions - Drive technical strategy for platform evolution, microservices architecture, and API design to simplify future program needs - Cultivate engineering culture and technical excellence to drive up engineering velocity and quality across the team We need to keep each as
    • . Qualifications: Basic Qualifications list: - 3+ years work experience in software engineering building large scale systems - Bachelor's (or higher) in Computer Science, Engineering, or related field. - Hands-on Web development experience, including proficiency in cutting edge web technologies (HTML5, CSS, Javascript, TypeScript), Application Servers and Web Applications - Experience in Javascript and experience developing UI with JavaScript development frameworks (e.g. React, Angular, Vue, Bootstrap, etc) - Experience with Node.js, React-Query, GraphQL, or other server-side Javascript technologies and tools - Experience in developing web apps used by hundreds of millions of users globally. - Strong focus on delivering high-quality 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. - 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. - Demonstrated leadership in building relationships with internal stakeholders and external partners to rally around a technical vision. Preferred Qualifications list: - Marketplace experience - Uber's business model is marketplace heavy and prior experience creating 0 to 1 features and optimizing marketplaces is preferred. - Experience in real-time marketplace platforms requiring high consistency and global reliability. - Impact Mindset - (1) Ability to navigate complex org and company business needs (2) Ability to identify consumer needs through user research and data understand work (3) Bringing those together to build products and systems that bring value to our customers and deliver company impact - Strong Cross Company Technical Collaboration - (1) Strong ability to collaborate and communicate technically with multiple teams across the company (2) Strong ability to deep dive into complex technical systems owned by other organizations (3) Create clean technical solutions that factor in complexities across multiple systems & ultimately solve for multiple team goals We need to preserve the exact phrasing? Probably keep as is. Pay: The posting includes: "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 Sunnyvale, CA-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." We should keep that as a paragraph under Pay. Benefits: The posting includes: "You will also be eligible for various benefits." plus earlier "You may be eligible for bonuses, equity, and other compensation, as well as a range of benefits." Also "All full-time employees are eligible to participate in a 401(k) plan." Actually that is compensation/benefits. We can combine. We could have a Benefits section with paragraph: "You will be eligible for bonuses, equity, and other compensation, as well as a range of benefits. All full-time employees are eligible to participate in a 401(k) plan." Also maybe mention "various benefits." Keep. Schedule: The posting includes: "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 keep that as Schedule section. We must not include application instructions like "Ready to Ride? ..." Actually that is not application instruction but motivational. Could keep under About the role? It appears after the qualifications and before benefits? Actually the posting: after qualifications, there is "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. 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 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. Uber is proud to be an Equal Opportunity employer...." We need to remove EEO boilerplate etc. So we will keep the motivational part and the benefits and schedule parts, but remove the EEO lines. Thus after qualifications we have: "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. 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 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 can split: The first sentence maybe part of About the role? But it's more like a call to action. Could include in About the role paragraph after the initial description. Or we could make a separate section like "About the team" but we already have About