Uber: Exploring driver signup and first trip conversion data from January 2016 to uncover patterns, insights, and key questions.
Uber’s Driver team is interested in predicting which driver signups are most likely to start driving. To help explore this question, we have provided a sample dataset of a cohort of driver signups in January 2016.The data was pulled a few months after they signed up to include the result of whether they actually completed their first trip. It also includes several pieces of background information gather about the driver and their car.
We would like you to use this data set to help understand what factors are best at predicting whether a signup will start to drive, and offer suggestions to operationalize those insights to help Uber.
See below for a detailed description of the dataset. Please include any code you wrote for the analysis and delete the dataset when you have finished with the challenge. Please also call out any data related assumptions or issues that you encounter.
id: driver_idcity_id: city_id this user signed up insignup_os: signup device of the user (“android”, “ios”, “website”, “other”)signup_channel: what channel did the driver sign up from (“offline”, “paid”, “organic”, “referral”)signup_timestamp: timestamp of account creation; local time in the form ‘YYYY MM DD’bgc_date: date of background check consent; in the form ‘YYYY MM DD’vehicle_added_date: date when driver’s vehicle information was uploaded; in the form ‘YYYY MM DD’first_trip_date: date of the first trip as a driver; in the form ‘YYYY MM DD’vehicle_make: make of vehicle uploaded (i.e. Honda, Ford, Kia)vehicle_model: model of vehicle uploaded (i.e. Accord, Prius, 350z)vehicle_year: year that the car was made; in the form ‘YYYY’Please work on the questions in the displayed order. Define, train and evaluate predictive models that takes as the input the data provided. You may want to split the data into training, testing and validation sets, according to your discretion.
Make sure that the solution reflects your entire thought process - it is more important how the code is structured rather than the final metrics. You are expected to spend no more than 3 hours working on this project.
See the full interview round by round, with questions for each stage.