← Lyft
Something new at Lyft

Add a selector for luggage needs so airport riders finish requests

You’re the software engineer. Your team is in the room. Printed Oct 13, 2026.

Rider-stated trip needs must fit inside offers that change in real time.

Airport riders need confidence that an option fits their trip, while pricing and fulfillment must not imply supply that is unavailable.

Who you’d be doing this for

“I had two bags and a teammate with me, so I kept reopening options and still wasn’t sure what would work.”

Mazen Hosseini · Consultant

A frequent business traveler requesting rides between airports, hotels, and client sites.

What is at stake

Airport-bound riders abandon the request flow after comparing options that do not reflect luggage or group needs. You must weigh clearer rider intent against real-time offer accuracy and request-flow speed.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • rider clarity vs. supply certainty
  • new request signals vs. latency budgets
  • fast learning vs. durable service boundaries
  • selection detail vs. flow simplicity

Why Lyft

The rideshare rider app is where airport travelers decide whether available rides fit the trip they need to take.

Written with these in mind

customer-minded backend engineermarketplace systems engineerfull-stack product engineer

Not your kind of problem? 66 more at Lyft, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.