Senior Software Engineer, Ride-Hailing Product
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include. The posting includes: Who We Are (company description), About The Team, About The Role, What You'll Own (responsibilities), About You (requirements/qualifications), Great to have (nice-to-have), Bonus Points (domain expertise, product and business acumen), At Nuro, your base pay... (pay range, bonus, equity, benefits), At Nuro, we celebrate differences... (EEO boilerplate - should be removed). Also mention "At Nuro, your base pay is one part of your total compensation package..." includes pay range, bonus, equity, benefits. So we can have sections: About the company (maybe "About Nuro")? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly.
We need to avoid filler headings. So we should include sections that have real content: About the role (maybe combine About The Role and What You'll Own?), Responsibilities (What You'll Own), Requirements/Qualifications (About You + Great to have + Bonus Points?), Skills (maybe list Go, GCP, distributed systems), Benefits/Pay (pay range, bonus, equity, benefits). Schedule not mentioned, so omit.
We must not repeat job title as heading. No Job ID.
We must remove EEO boilerplate.
We must not include duplicated lines.
We need to preserve all substantive information.
Let's extract content:
Who We Are: Nuro is a self-driving technology company on a mission to make autonomy accessible to all. Founded in 2016, Nuro is building the world’s most scalable driver, combining cutting-edge AI with automotive-grade hardware. Nuro licenses its core technology, the Nuro Driver™, to support a wide range of applications, from robotaxis and commercial fleets to personally owned vehicles. With technology proven over years of self-driving deployments, Nuro gives the automakers and mobility platforms a clear path to AVs at commercial scale, empowering a safer, richer, and more connected future.
About The Team: A rider taps "request ride" and within seconds, an autonomous vehicle is matched, dispatched, and on its way. The On-Road Experience team owns the systems that make that moment happen. The On-road Experience team builds the real-time distributed system behind Nuro's ride-hailing product. This is foundational infrastructure where correctness and performance have consequences on a real road.
About The Role: This is the perfect role if you love architecting performant, reliable distributed systems, processing real-time vehicle data, and building the foundational APIs that enable seamless product experiences. The position demands technical excellence, a deep understanding of system design, and a knack for solving tough problems. Come join us in defining the future!
What You'll Own: Backend services for ride planning, vehicle matching, and real-time trip execution; Partner API integrations (Uber and others) routing ride requests to Nuro vehicles; Telemetry pipelines surfacing live vehicle state to riders and operations.
About You: 4+ years of backend engineering experience with strong Go proficiency; Experience designing and operating distributed systems where reliability isn't optional; End-to-end product ownership — from requirements through launch and iteration; Solid hands-on experience with GCP (CloudSQL, BigQuery, Redis, or equivalent); A track record of technical leadership: setting the bar, mentoring others, making hard trade-offs.
Great to have: dispatch, fleet, location, or delivery/ride platform experience. Even better if you've built systems where the physical world is the end user.
Bonus Points: Domain Expertise: Experience with backend services related to vehicles, location, dispatch, inventory, or order/ride/delivery. Product and Business Acumen: A keen interest in the "why" in addition to the "how." You are eager to understand and contribute to product and business requirements, capable of identifying high-impact projects from a list of potential initiatives.
At Nuro, your base pay is one part of your total compensation package. For this position, the reasonably expected base pay range is between $160,360 and $240,540 for the level at which this job has been scoped. Your base pay will depend on several factors, including your experience, qualifications, education, location, and skills. In the event that you are considered for a different level, a higher or lower pay range would apply. This position is also eligible for an annual performance bonus, equity, and a competitive benefits package.
EEO boilerplate to remove.
Thus we need sections: About Nuro (Who We Are) maybe as a heading? Not in list but we can use
for any section heading; they gave examples but not exclusive. We can use About Nuro as heading.
But they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings where applicable. However we can also use other headings if needed? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings for sections; but we can also use other headings if they fit? The examples are just examples; but they say "use for section headings". Likely they expect we use those headings where appropriate. We have content for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We don't have Schedule. We might combine Requirements and Qualifications into one? Or separate.
We need to decide which headings to include based on content.
Let's map:
- About the role: we have "About The Role" paragraph. Could be used as heading.
- Responsibilities: "What You'll Own" list.
- Requirements: maybe "About You" (mandatory).
- Qualifications: maybe "Great to have" and "Bonus Points" could be qualifications? Or we could have Skills heading for technical skills (Go, GCP, distributed systems). But we already have those in About You.
Better to follow typical structure: About the role (description), Responsibilities (list), Requirements (mandatory), Qualifications (nice-to-have), Skills (specific technologies), Benefits/Pay (compensation). But we must not create thin sections.
We have enough content for:
- About the role (paragraph)
- Responsibilities (list of 3 items)
- Requirements (list of 5 items from About You)
- Qualifications (list of 2 items from Great to have + Bonus Points? Could be combined)
- Skills (maybe list Go, GCP services, distributed systems experience)
- Pay (paragraph with range, bonus, equity, benefits)
- Benefits (maybe mention competitive benefits package) but we already included in Pay section.
We should avoid duplication. Let's think: The About You already includes Go proficiency, distributed systems experience, product ownership, GCP experience, technical leadership. That's both requirements and skills. So we could have Requirements heading with those items. Then Skills heading could be redundant. Better to combine.
Thus we could have:
About the role
... (the About The Role paragraph)
Responsibilities
- Backend services for ride planning, vehicle matching, and real-time trip execution
- Partner API integrations (Uber and others) routing ride requests to Nuro vehicles
- Telemetry pipelines surfacing live vehicle state to riders and operations
Requirements
- 4+ years of backend engineering experience with strong Go proficiency
- Experience designing and operating distributed systems where reliability isn't optional
- End-to-end product ownership — from requirements through launch and iteration
- Solid hands-on experience with GCP (CloudSQL, BigQuery, Redis, or equivalent)
- A track record of technical leadership: setting the bar, mentoring others, making hard trade-offs
Qualifications
- Dispatch, fleet, location, or delivery/ride platform experience (great to have)
- Experience building systems where the physical world is the end user (even better)
- Domain expertise: backend services related to vehicles, location, dispatch, inventory, or order/ride/delivery
- Product and business acumen: keen interest in the "why" in addition to the "how"; eager to understand and contribute to product and business requirements; capable of identifying high-impact projects
Pay
Base pay range: $160,360 – $240,540 (depending on experience, qualifications, education, location, skills). Eligible for annual performance bonus, equity, and a competitive benefits package.
We should also include About Nuro? The "Who We Are" could be considered "About the company". Not in list but maybe we can include as a heading like "About Nuro". However instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to include a heading like "About Nuro" maybe not needed because the role description already includes company info? But we have substantive info about Nuro that is not duplicated elsewhere. If we omit it, we lose substantive information. So we need to include it somewhere. Could we fold it into About the role? The About the role paragraph is separate; we could prepend a brief company description to About the role? But that would be mixing. Better to have a section "About Nuro" with that content. The instruction didn't forbid that; they just gave examples. So we can add About Nuro
with the Who We Are paragraph.
Thus final HTML fragment:
About Nuro
Nuro is a self-driving technology company on a mission to make autonomy accessible to all. Founded in 2016, Nuro is building the world’s most scalable driver, combining cutting-edge AI with automotive-grade hardware. Nuro licenses its core technology, the Nuro Driver™, to support a wide range of applications, from robotaxis and commercial fleets to personally owned vehicles. With technology proven over years of self-driving deployments, Nuro gives the automakers and mobility platforms a clear path to AVs at commercial scale, empowering a safer, richer, and more connected future.
About the role
This
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: Who We Are (company description), About The Team, About The Role, What You'll Own (responsibilities), About You (requirements/qualifications), Great to have (nice-to-have), Bonus Points (domain expertise, product and business acumen), At Nuro, your base pay... (pay range, bonus, equity, benefits), At Nuro, we celebrate differences... (EEO boilerplate - should be removed). Also mention "At Nuro, your base pay is one part of your total compensation package..." includes pay range, bonus, equity, benefits. So we can have sections: About the company (maybe "About Nuro")? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. We need to avoid filler headings. So we should include sections that have real content: About the role (maybe combine About The Role and What You'll Own?), Responsibilities (What You'll Own), Requirements/Qualifications (About You + Great to have + Bonus Points?), Skills (maybe list Go, GCP, distributed systems), Benefits/Pay (pay range, bonus, equity, benefits). Schedule not mentioned, so omit. We must not repeat job title as heading. No Job ID. We must remove EEO boilerplate. We must not include duplicated lines. We need to preserve all substantive information. Let's extract content: Who We Are: Nuro is a self-driving technology company on a mission to make autonomy accessible to all. Founded in 2016, Nuro is building the world’s most scalable driver, combining cutting-edge AI with automotive-grade hardware. Nuro licenses its core technology, the Nuro Driver™, to support a wide range of applications, from robotaxis and commercial fleets to personally owned vehicles. With technology proven over years of self-driving deployments, Nuro gives the automakers and mobility platforms a clear path to AVs at commercial scale, empowering a safer, richer, and more connected future. About The Team: A rider taps "request ride" and within seconds, an autonomous vehicle is matched, dispatched, and on its way. The On-Road Experience team owns the systems that make that moment happen. The On-road Experience team builds the real-time distributed system behind Nuro's ride-hailing product. This is foundational infrastructure where correctness and performance have consequences on a real road. About The Role: This is the perfect role if you love architecting performant, reliable distributed systems, processing real-time vehicle data, and building the foundational APIs that enable seamless product experiences. The position demands technical excellence, a deep understanding of system design, and a knack for solving tough problems. Come join us in defining the future! What You'll Own: Backend services for ride planning, vehicle matching, and real-time trip execution; Partner API integrations (Uber and others) routing ride requests to Nuro vehicles; Telemetry pipelines surfacing live vehicle state to riders and operations. About You: 4+ years of backend engineering experience with strong Go proficiency; Experience designing and operating distributed systems where reliability isn't optional; End-to-end product ownership — from requirements through launch and iteration; Solid hands-on experience with GCP (CloudSQL, BigQuery, Redis, or equivalent); A track record of technical leadership: setting the bar, mentoring others, making hard trade-offs. Great to have: dispatch, fleet, location, or delivery/ride platform experience. Even better if you've built systems where the physical world is the end user. Bonus Points: Domain Expertise: Experience with backend services related to vehicles, location, dispatch, inventory, or order/ride/delivery. Product and Business Acumen: A keen interest in the "why" in addition to the "how." You are eager to understand and contribute to product and business requirements, capable of identifying high-impact projects from a list of potential initiatives. At Nuro, your base pay is one part of your total compensation package. For this position, the reasonably expected base pay range is between $160,360 and $240,540 for the level at which this job has been scoped. Your base pay will depend on several factors, including your experience, qualifications, education, location, and skills. In the event that you are considered for a different level, a higher or lower pay range would apply. This position is also eligible for an annual performance bonus, equity, and a competitive benefits package. EEO boilerplate to remove. Thus we need sections: About Nuro (Who We Are) maybe as a heading? Not in list but we can use
for any section heading; they gave examples but not exclusive. We can use About Nuro as heading.
But they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings where applicable. However we can also use other headings if needed? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings for sections; but we can also use other headings if they fit? The examples are just examples; but they say "use for section headings". Likely they expect we use those headings where appropriate. We have content for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We don't have Schedule. We might combine Requirements and Qualifications into one? Or separate.
We need to decide which headings to include based on content.
Let's map:
- About the role: we have "About The Role" paragraph. Could be used as heading.
- Responsibilities: "What You'll Own" list.
- Requirements: maybe "About You" (mandatory).
- Qualifications: maybe "Great to have" and "Bonus Points" could be qualifications? Or we could have Skills heading for technical skills (Go, GCP, distributed systems). But we already have those in About You.
Better to follow typical structure: About the role (description), Responsibilities (list), Requirements (mandatory), Qualifications (nice-to-have), Skills (specific technologies), Benefits/Pay (compensation). But we must not create thin sections.
We have enough content for:
- About the role (paragraph)
- Responsibilities (list of 3 items)
- Requirements (list of 5 items from About You)
- Qualifications (list of 2 items from Great to have + Bonus Points? Could be combined)
- Skills (maybe list Go, GCP services, distributed systems experience)
- Pay (paragraph with range, bonus, equity, benefits)
- Benefits (maybe mention competitive benefits package) but we already included in Pay section.
We should avoid duplication. Let's think: The About You already includes Go proficiency, distributed systems experience, product ownership, GCP experience, technical leadership. That's both requirements and skills. So we could have Requirements heading with those items. Then Skills heading could be redundant. Better to combine.
Thus we could have:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings for sections; but we can also use other headings if they fit? The examples are just examples; but they say "use for section headings". Likely they expect we use those headings where appropriate. We have content for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We don't have Schedule. We might combine Requirements and Qualifications into one? Or separate.
We need to decide which headings to include based on content.
Let's map:
- About the role: we have "About The Role" paragraph. Could be used as heading.
- Responsibilities: "What You'll Own" list.
- Requirements: maybe "About You" (mandatory).
- Qualifications: maybe "Great to have" and "Bonus Points" could be qualifications? Or we could have Skills heading for technical skills (Go, GCP, distributed systems). But we already have those in About You.
Better to follow typical structure: About the role (description), Responsibilities (list), Requirements (mandatory), Qualifications (nice-to-have), Skills (specific technologies), Benefits/Pay (compensation). But we must not create thin sections.
We have enough content for:
- About the role (paragraph)
- Responsibilities (list of 3 items)
- Requirements (list of 5 items from About You)
- Qualifications (list of 2 items from Great to have + Bonus Points? Could be combined)
- Skills (maybe list Go, GCP services, distributed systems experience)
- Pay (paragraph with range, bonus, equity, benefits)
- Benefits (maybe mention competitive benefits package) but we already included in Pay section.
We should avoid duplication. Let's think: The About You already includes Go proficiency, distributed systems experience, product ownership, GCP experience, technical leadership. That's both requirements and skills. So we could have Requirements heading with those items. Then Skills heading could be redundant. Better to combine.
Thus we could have:
About the role
About the role
... (the About The Role paragraph)
Responsibilities
- Backend services for ride planning, vehicle matching, and real-time trip execution
- Partner API integrations (Uber and others) routing ride requests to Nuro vehicles
- Telemetry pipelines surfacing live vehicle state to riders and operations
Requirements
- 4+ years of backend engineering experience with strong Go proficiency
- Experience designing and operating distributed systems where reliability isn't optional
- End-to-end product ownership — from requirements through launch and iteration
- Solid hands-on experience with GCP (CloudSQL, BigQuery, Redis, or equivalent)
- A track record of technical leadership: setting the bar, mentoring others, making hard trade-offs
Qualifications
- Dispatch, fleet, location, or delivery/ride platform experience (great to have)
- Experience building systems where the physical world is the end user (even better)
- Domain expertise: backend services related to vehicles, location, dispatch, inventory, or order/ride/delivery
- Product and business acumen: keen interest in the "why" in addition to the "how"; eager to understand and contribute to product and business requirements; capable of identifying high-impact projects
Pay
Base pay range: $160,360 – $240,540 (depending on experience, qualifications, education, location, skills). Eligible for annual performance bonus, equity, and a competitive benefits package.
We should also include About Nuro? The "Who We Are" could be considered "About the company". Not in list but maybe we can include as a heading like "About Nuro". However instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to include a heading like "About Nuro" maybe not needed because the role description already includes company info? But we have substantive info about Nuro that is not duplicated elsewhere. If we omit it, we lose substantive information. So we need to include it somewhere. Could we fold it into About the role? The About the role paragraph is separate; we could prepend a brief company description to About the role? But that would be mixing. Better to have a section "About Nuro" with that content. The instruction didn't forbid that; they just gave examples. So we can add About Nuro
with the Who We Are paragraph.
Thus final HTML fragment:
About Nuro
Nuro is a self-driving technology company on a mission to make autonomy accessible to all. Founded in 2016, Nuro is building the world’s most scalable driver, combining cutting-edge AI with automotive-grade hardware. Nuro licenses its core technology, the Nuro Driver™, to support a wide range of applications, from robotaxis and commercial fleets to personally owned vehicles. With technology proven over years of self-driving deployments, Nuro gives the automakers and mobility platforms a clear path to AVs at commercial scale, empowering a safer, richer, and more connected future.
About the role
This