Hi Winnie,
I would recommend using a Decision activity before the User Task.
In the microflow, retrieve the requester's System.UserRoles (either from System.owner or your associated Administration.Account) and check which role the user belongs to. Based on that, route the workflow to the appropriate User Task or assign the corresponding User Role.
For example:
As far as I know, there isn't a built-in way to dynamically map one user role to another directly in the User Task configuration. Using a Decision (or microflow) keeps the logic clear and easy to maintain.
Kindly mark this as the accepted answer if it helps.