New features: Homepage and quick filters

Congrats on the launch.

I'll be honest, I looked into this space a while back. Here's the mental model I have of this space and where I think your missing the mark:

## Framework

• Time & Location: both companies and job seekers have a main location (within a timezone) and a min-max time they are willing to work within that timezone. Ultimately, on the company side it comes down to whether they want synchronous or asynchronous working.

• % remote: some companies are ok with people never coming to the office. Others want a hybrid model. Anything other than 100% remote means there are going to be time & location restrictions.

• timezone: everyone thinks in their own timezone. Very few people think in UTC. In the US people think in terms of ET/PT. In the UK its GMT or BST. You can't expect people to have to come to you - you have to come to them or meet them half way.

## Example user journeys
In both examples, lets say our user lives in Spain. She is looking for a Director of Product role (only) and lives in the CEST+0 timezone (that's how she thinks about it). She is willing to do 9-6pm CEST or to shift her day to finish no later than 8pm (so starting at about 12pm CEST). Or, to work entirely asynchronously.

You cannot do this in one search accurately!

Journey 1: Our user wants to set up her preferences and see which companies fit ANY of those criteria.

Journey 2: Our users wants to browse companies and filter them down and look at one criteria set at a time such as the working hours.

## How well do these work on Himalayas?

1. First off, the Himalayas UI is taking priority over the UX. I've seen this happen many times. There are lots of little issues - such as the excessive use of whitespace in the header after searching, the (very) buggy filter menus, and the filter choices. The timezone filter doesn't work beyond showing a few timezones, I don't seem to be able to type them in (on Chrome or Safari). You've gone for style over substance and value. I feel like you probably hired a UI designer, not a UX designer. If I'm wrong, someone needs to pay attention to details more.

2. Himalayas is not doing enough of the translation between data and mental models of users in my opinion. Our user has to Google her own timezone into UTC. She has to wonder what the "timezone" filter means - mine or the companies? Probably the companies.. so.. err.. back to google to check my max and min preferences.

Why does the user have to do all the work to think from the company perspective and not their own? No one thinks "Ok.. I want to search for companies who are looking for people that include people who live in Spain, but who are okay to shift their timezone...". No! People think "i want to work 9-6pm CEST, 100% remotely". But that is not the Himalayas experience.

What would be better is to establish the users preferences up front (let's view this in the form of a conversation between the service and the user):

Service: Where are you based?
User: Madrid (that provides the timezone, or S could give U a choice of CEST or UTC)
S: Ok, thanks. In CEST (or UTC if you prefer) what hours do you want to do?
U: 9-6pm CEST, give or take an hour or two later to start
S: Ok. Great. (behind the scenes this can all be translated into how Himalayas and listed companies are organised in the database).
S: Do you want 100% remote or hybrid?
U: 100% remote
S: Thanks. I'll save this search. You can come up with another set of criteria if you want later.
U: Great!

Don't take this literally! I'm saying to create a bot. This is how people experience design. Right now your design is the same as all others:

"Help yourself to our database. Remember to shift your mental model to ours".

Himalayas biggest issues (in my opinion)

1. Design > UX
2. Its a database search which doesn't meet the user halfway
3. I cannot filter within Product. Which makes it almost useless when you return 34 pages of results and the user only wants to see Director of Product jobs.

I congratulate your hard work, but to me you've made the same mistakes as everyone else. More maybe. I find this frustrating because I couldn't spend the time last year on a project like this myself -and i really want to see someone actually solve the problem!

I encourage you to do proper user experience testing with a simple script based on a real users situation. Then sit down and test your site and test all these others:

• We Work Remotely
• Angel.co (allows multiple searches to be saved)
• remoteok.io
• nodesk.co
• linkedin.com
• remoteglobal.com

You will learn a lot in one day by doing this.