Improve TaskRabbit From Booking Confirmation Through Job Completion and Rebooking

Quick Overview

A product design question about improving TaskRabbit after a client books a Tasker, covering confirmation, the day of the job, billing, reviews and rebooking. It tests journey mapping, segment choice, two-sided marketplace trade-offs and success metrics.

Improve TaskRabbit From Booking Confirmation Through Job Completion and Rebooking

Company: DoorDash

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Improve TaskRabbit's experience for the period after a client books a task. (TaskRabbit is a marketplace where people hire local Taskers for jobs such as furniture assembly, mounting, moving help and cleaning.) ```hint Walk the timeline Trace the steps from the booking confirmation to the next booking, and note at each one what the client cannot see or control and what the Tasker needs to know. ``` ### Clarifying Questions - Where does "post-booking" end: when the job is finished, or does it include billing, the review and booking again? - Should I improve the experience for clients, for Taskers, or both? - Is the main goal fewer cancellations and disputes, more repeat bookings, or higher satisfaction? - Should I focus on particular task categories, or design across all of them? ### What a Strong Answer Covers - A defined post-booking journey and a deliberate choice of user segment - Pain points tied to specific moments between confirmation and rebooking, including cancellations and billing - Prioritized solutions that work for both clients and Taskers - A success metric linked to completed jobs and repeat bookings, with guardrails for Taskers - Risks such as privacy, safety and the hourly pricing model ### Follow-up Questions - How would your plan change if you focused on Taskers' post-booking experience instead of clients'? - If showing estimated costs raises bookings but also raises billing disputes, what would you do? - A Tasker cancels the night before a client's move. What should the product do?

Overview: A product design question about improving TaskRabbit after a client books a Tasker, covering confirmation, the day of the job, billing, reviews and rebooking. It tests journey mapping, segment choice, two-sided marketplace trade-offs and success metrics.

DoorDash logo
DoorDash
Jun 23, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Improve TaskRabbit's experience for the period after a client books a task. (TaskRabbit is a marketplace where people hire local Taskers for jobs such as furniture assembly, mounting, moving help and cleaning.)

Clarifying Questions Guidance

  • Where does "post-booking" end: when the job is finished, or does it include billing, the review and booking again?
  • Should I improve the experience for clients, for Taskers, or both?
  • Is the main goal fewer cancellations and disputes, more repeat bookings, or higher satisfaction?
  • Should I focus on particular task categories, or design across all of them?

What a Strong Answer Covers Guidance

  • A defined post-booking journey and a deliberate choice of user segment
  • Pain points tied to specific moments between confirmation and rebooking, including cancellations and billing
  • Prioritized solutions that work for both clients and Taskers
  • A success metric linked to completed jobs and repeat bookings, with guardrails for Taskers
  • Risks such as privacy, safety and the hourly pricing model

Follow-up Questions Guidance

  • How would your plan change if you focused on Taskers' post-booking experience instead of clients'?
  • If showing estimated costs raises bookings but also raises billing disputes, what would you do?
  • A Tasker cancels the night before a client's move. What should the product do?