Should an Uber like app have two models, one for customers and one for workers

I am trying to make an uber like website, where you can sign up as a customer (someone who uses the service) or a worker (someone who provides the service). Should I create two models for each of these and then have different registration forms for each. Or should I have one generic profile model with a role field where upon registration the user could select whether they want to be a customer or a worker?

I ask because there are fields that the customer would have that would be useless to the worker and vice versa (such as the "looking for a ride now" field that only a customer would activate when they are trying to find a ride. Is it okay to give all fields to both sides with one profile model and then leave them blank if they do not apply to the customer/worker?