Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding Spotahome full remote positions #60

Merged
merged 1 commit into from
Jul 1, 2021

Conversation

AlvYuste
Copy link
Contributor

@AlvYuste AlvYuste commented Jul 1, 2021

Currently, there is one open for Software Development Engineer: https://rent.spotahome.com/work-with-us/post?gh_jid=5074410002

@alexpdp7
Copy link
Member

alexpdp7 commented Jul 1, 2021

Remote positions are not superclear from the main job listing, but good enough for me!

@alexpdp7 alexpdp7 merged commit 013e413 into remote-es:master Jul 1, 2021
@uesteibar
Copy link
Contributor

I don't think this matches the criteria we've set though. In the linked page it never states whether a position is remote or not, and there's no way to filter for remote jobs 😕 I'm confused as why we accepted this when we've rejected very similar PRs (see #29).

@alexpdp7
Copy link
Member

alexpdp7 commented Jul 1, 2021

Hmmm, yes, this might be worth thinking more about. The difference with #29 is that inside the offer it seems to be clear the position is remote:

We all work full-remote from home, but we have an open space in sunny Madrid available for anyone to come.

, while (IIRC), Genially didn't have that. I think we might have some other listings with similar problems.

@AlvYuste , could you nudge your company to be a bit more clear?

@uesteibar I'm happy to revert the commit. I suggest we ping @acroca for his "vote" and decide (if they don't improve the listing, of course!). Personally, I think this particular case is fine (if not optimal)... but if you two agree, or if Albert doesn't vote, let's rollback? (we have a ton of companies now, so I guess we can start being a bit more strict...)

@alexpdp7
Copy link
Member

alexpdp7 commented Jul 1, 2021

(reopened #29 as I noticed maybe their LinkedIn jobs listing is good enough- there it talks about 100% remote [although their main careers website in their homepage doesn't...]).

Thanks for being on point, @uesteibar ...

@uesteibar
Copy link
Contributor

sounds good to me, let's wait for @acroca's input on this. My personal stance is that I'd rather not add listings that can't be searched for remote positions (at least with a cmd/ctrl + f search)

@alexpdp7
Copy link
Member

alexpdp7 commented Jul 5, 2021

As @acroca might be busy...

What you say makes sense, but I think we should consider how many offers are in the listing, and which are remote. If a company has a ton of offers and they are 50/50 remote or less, then our users might find it painful to find the remote offers. In this case, they right now have a single IT-related offer, and it's clear inside that it's remote, so I think users of this repo might prefer the company being listed than not listed.

If you want to remove them, I can remove them myself (I kinda wanted acroca to weigh in and break the tie, so I was lazy and I didn't make this argument before- sorry about that).

@uesteibar
Copy link
Contributor

if you wanna keep them, that's fine for me. I would just try and be consistent with the criteria going forward.

@acroca
Copy link
Contributor

acroca commented Jul 7, 2021

Are all the positions in that company remote? If so, I'd expect it to be mentioned at least in the job description.

If all the Spanish jobs are remote, and it's mentioned in the description, I'd say it's fine to keep it.

If some are remote and some are not, I'd ask them to make it clear if something is remote or not, as a potential applicant I'd be fine reading the job to figure out if it's remote or not, but has to be clear.

@alexpdp7
Copy link
Member

I started working on collecting data about our listing in #54 (comment) to take those decisions with some information. I suggest we continue the discussion there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants