What design pattern is appropriate for different types of users?

I'm building an application that allows a user to apply to job opportunities. There can be two types of users: applicant and company.

One example of a use case is: a company can create a JobOpportunity and an applicant can apply to it, creating a JobApplication.

Both of the users can query for their job applications and job opportunities.

My question is: I have one search (eg. getMyJobApplications) which design pattern I can implement to provide flexibility in terms of who is searching it, company or applicant?

Thanks.