jawa21

I’ve never delivered for Uber Eats specifically, but I don’t know how they managed less than $2 an hour without doing obviously impractical things like trying to deliver at off hours, or in a poor area for it. I average about $27/hour. This is however, with GrubHub that has a wait list for drivers and they deliberately don’t overcrowd regions. Area really has a lot to do with it. I can imagine that if Uber doesn’t cap the amount of drivers in an area, a full on city is probably the worst example of a place to try it. I know that DoorDash is the same way in Atlanta, and the few times I have tried there, it wasn’t worth the trip. One thing you learn very fast through observations is that the “hot zones” mentioned in the article don’t matter. All they mean is that someone ordered from a place there before the map refreshed.

I guess my point here, is that the pay isn’t necessarily shit. You have to put in some leg work and learn the best areas around you as well as the times to work.

I do have a lot to say about doing this line of work with over 1k deliveries done across 3 apps, but it is kind of out of the scope of this comment unless someone asks.

They also likely wouldn’t get involved without a tremendous amount of uproar, because the instance is way too large and their work load for, well, admin stuff is likely off the charts.

Taco Bell doesn’t use a .conf file, JSON, or even XML. They still have a .ini file with a bunch of cryptic true/false values.