I am new to DynamoDB and after reading several docs, there is a scenario in which I am not sure which would be the best approach for designing a table.
Consider that we have some JobOffers and we should support the following data access:

• get a specific JobOffer
• get all JobOffers from a specific Company sorted by different criteria (newest/oldest/wage)
• get JobOffers from a specific Company filtered by a specific city sorted by different criteria (newest/oldest/wage)
• get all JobOffers (regardless of any Company !!!) sorted by different criteria (newest/oldest/wage)
• get JobOffers (regardless of any Company !!!) filtered by a specific city sorted by different criteria (newest/oldest/wage)

Since we need to support sorting, my understanding is that we should use Query instead of Scan. In order to use Query, we need to use a primary key. Because we need to support a search like “get all JobOffers without any filters sorted somehow”, which would be a good candidate for partition key?

As a workaround, I was thinking to use a new attribute “country” which can be used as the partition key, but since all JobOffers are specified in one country, all these items fall under the same partition, so it might be a bit redundant until we will have support for JobOffers from different countries.

Any suggestion on how to design JobOffer table (with PK and GSI/LSI) for such a scenario?