jobvandervoort

Very cool to see another GitLab spin off. Also great to see it's another OSS

Remote | many roles | remote (anywhere) | remote.com/careers

We're making it possible for anyone to hire anywhere, which is incredibly complex! Our company handbook is public, which will tell you more than anything else I can share here: remote.com/handbook

Please apply through the careers page. Feel free to ask me questions on twitter @jobvo

The employee would be employed by the EoR on paper. Hence employer _of record_. But otherwise acts as a normal employee of the actual employer.

> And how is the situation when the employees come in from time to time (commuting across borders) but work the majority of their time in another country?

This is a gross simplification, but: You must comply with where you spend the majority of your time. Spending a few days/weeks outside of your homebase is normal (see: all business travel) and doesn't make you immediately liable.

That said, this gets really complex and murky when you think about e.g. nomads or people that really split their time between countries.

Generally: no.

There are cases and/or ways where you can e.g. hire someone under a local contract without owning a local entity, but that doesn't scale much beyond that, and you'd still need to run local payroll somehow, and be locally compliant.

The one big thing the EU solves is mobility: any EU citizen can work freely from anywhere else in the EU. That's a massive hurdle to cross otherwise.

Beyond that, even between EU countries there are absolutely massive differences in labor laws, standards, etc.

If you hire someone in another country, you (employer) must fully comply with local labor laws, tax requirements, run payroll and pay any local dues in local currency.

This is only solved by either setting up a local office and hire local experts yourself, or working with an employer of record.

Source: I'm the CEO of Remote.com and we do this for other companies across the world, and run all our own entities and compliance.

Remote (remote.com) | Multiple roles | remote (anywhere)

- frontend (react), backend (elixir) engineers - several finance roles - global operations roles (HR related) - SDR and AE

remote.com/careers to apply

Can you email me with the needs? I'm sure we can work something out. I don't think the tax accountant is able to be a local liable employer, like we are.

We tend to be the most affordable employer of record with quite some margin.

Paying contractors is free through us.

FWIW we [0] employ a lot of people in the EU working remotely and a large part of them earns SF/NY salaries.

Probably a strong selection bias to the types of companies that choose to work with us.

[0]: I'm the CEO of remote.com

If your project is open source on gitlab.com - you get all paid features for free.

Remote | Elixir engineers and other roles | REMOTE from ANYWHERE | Full-time

Remote (remote.com) makes it possible to hire anyone from anywhere. We're looking for elixir engineers and operations people to join our team.

https://apply.workable.com/remote-1/

I've been using this one [0], which lays under your mattress and is surprisingly accurate (have many night time wakings due to young kid). It tracks movement, even heart rate and snoring.

You don't have to charge it, nor wear anything, which is why I got it vs. any of the wearables.

[0]: https://www.withings.com/mx/en/sleep

Fair question, and I think yes! If you mainly do your meetings remotely (which I do), you want your interactions to be as high-bandwidth as possible.

There is value, and data, in real world interactions that is lost quickly in video calls. The lower latency, the higher the resolution and quality of the audio, the more you approximate a 'real' meeting.

This is way beyond baseline requirements for e.g. remote work, but it's _nice_, just as a slightly bigger screen is _nice_.

It makes no sense. I use a $100 Logitech Webcam and _regularly_ get comments about how sharp and clear the video is, using Zoom.

There's value in a better camera, even in laptops.

Yep me, together with the author of the post, Marcelo.

It is!

Happy to chat about it in detail if you're interested.

We're working on something at Remote. While working at GitLab, I saw the issues they were having, so we're building an alternative to CXC and Safeguard.

Launching a little launch page later today, but feel free to email me if you're in need of some help: job at remote dot com.

I visited CERN once in my role at GitLab. The scale of CERN and the level of people there is really impressive.

Many teams had implemented very complicated pipelines doing all sorts of things. Including using GitLab to design, validate and eventually produce hardware that was used in ATLAS.

I think any company should pay for equipment for their employees. GitLab does this, we will do this.

Desk, monitor, computer, chair, etc. Alternatively, offer a budget for a coworking space.

These kind of expenses are nothing compared to a monthly salary.

When you're working remotely, you have to actively, consciously make an effort to bond, connect with your colleagues. Think regular hangouts where you just have casual chats, casual 1:1 conversations and -if possible- semi-regular meetups in real life where the point is not to work.

That'll feel very unnatural at first, but over time just become part of working remotely.

Thanks - goal is not to build a job board. Goal is to move remote working forward. A job board is an obvious start if done well (note: we have a long way to go, right now).

Hiring from anywhere is amazing, but there are many challenges in paying and employing people from different countries. We hope to make some dent in that, but I'm aware that's going to be very hard.

Thanks - good idea. My plan is to make that kind of content available on Remote.com and not just in a book.

We should be much more transparent about this, you're right.

We're going to split this up between your profile and your contacts, and make it explicit what happens.

This looks cool. Looking forward to give it a try.

For years I've been using Deckset[0] for all my presentations. Being able to just edit a text file to write and update slides is a massive advantage. I usually export them as pdf, which 99% of conferences are happy with.

A big bonus is that you can now version control your slides, allow them to get forked, etc.

If you're curious to see what those slides look like, check any of my previous talks [1].

[0]: https://www.deckset.com/

[1]: http://jobv.gitlab.io/talks/

Most people speak English, but are uncomfortable / inexperienced in doing so. Everyone in tech speaks English just fine.

For day-to-day, it does make your life much easier. Surprisingly, banks are a pain to deal with, without speaking Portuguese. I learned because my parents in law didn't speak English very well.

Portuguese is a rich language, and Portuguese people are typically familiar with the countries famous writers and poets. That makes it a valuable language to learn.

Live in Braga, Portugal.

My wife is Portuguese, but has no ties to our current location, nor do I. We moved here, because we found a great house, in a great location that we could buy for reasonable money.

Portugal is an affordable country (if not in Lisbon or Porto), with great people, great food and great weather. Education is great, and the startup ecosystem is ambitious and growing rapidly.

Let me know if anyone would like to meet up, if you're here; or any tips on moving here.

Yeah, we were all working remotely from the start. We never had an office.

We moved in together for a few months during YC.

Nope, there's only Sids house in SF that has a few desks for when people want to visit _something_.

To be more precise, we support any static site generator, as we will serve any static content that you make available. So you can even use GitLab pages to e.g. display and easily share test output, documentation, or anything else.

See: https://about.gitlab.com/2016/06/17/ssg-overview-gitlab-page...

Thanks gorset for the great response and the new insight you gave me into this. I now understand what you mean and see how the changes have negatively affect patch-series style MRs.

I created an issue on this and I encourage you to contribute there as well: https://gitlab.com/gitlab-org/gitlab-ce/issues/48334

We're not fans of adding additional configuration, but I can imagine we store e.g. what the last state was that you left commit message in, as to not have to unfold it every time. I'm sure you have further thoughts on improvements that can be made.