← Lyft
Complex day at Lyft

Fix charging after docking while e-assist availability sits at 71%

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

The fleet-wide OTA decision trades charging availability against uncertain field failure paths.

A fast release protects riders from empty e-assist docks, while a cautious release protects the fleet from committing the wrong charging behavior.

Who you’d be doing this for

“My morning report shows charged bikes at half the stations, and the transit director wants an answer today.”

Raghav Verma · Public Mobility Program Manager

Oversees station availability and service commitments for a city-run shared micromobility program.

What is at stake

Charging-capable e-assist availability has fallen to 71%, leaving riders to find empty docks after ending trips. You have to weigh restoring service quickly against locking in a fix that field evidence has not fully confirmed.

Why it isn’t already fixed

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

  • rider access vs. fleet-wide release certainty
  • field recovery speed vs. durable software correction
  • hardware evidence vs. remote diagnostics
  • OTA reversibility vs. peak-period availability

Why Lyft

E-assist bikes, batteries, charging stations, and dock software operate as one rider experience across the deployed micromobility fleet.

Written with these in mind

systems-minded software engineerreliability-focused product engineerembedded and distributed-systems 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.