Live data from Hacker News

Ask HN: What are the biggest challenges preventing startups from hiring remote?

news.ycombinator.com

31–40 of 137 posts

Re: Ask HN: What are the biggest challenges preventing startups from hiring remote?

#31

We are a pure remote company but Tax/employment-law is for us the biggest issue. Or to be more precise, it's the biggest issue for potential co-workers. We find that people are super interested in us, but when we tell them they have to do their own tax and basically act as freelancers, most say no to us. The majority simply wants a standard legal employment. Which I understand and I would like to have that too.

I keep seeing in remote job posts for US companies that you need a work permit, they don't mention the option to work as a freelancer. In the Netherlands a lot of people work from their own one person company.

Re: Ask HN: What are the biggest challenges preventing startups from hiring remote?

#32
post #28

What exactly is the pain with international payrolls? I don’t quite understand..

So tell me, how do you employ someone who is in Germany if you are based in the US? Germany wants its taxes so you can't just put them as a regular US employee and you don't have any presence in Germany so you can't hire them locally.

Even hiring within the US remote workers can cause issues with the "tax nexus" as a remote worker acts as a physical presence in that state, forcing the company to pay taxes as if they did business in that state.

Re: Ask HN: What are the biggest challenges preventing startups from hiring remote?

#33
post #8

The biggest challenge to making remote workers successful is the existing company culture. If the organization has not been built with a conscious "remote-first" mindset, new remote collaborators will inevitably be excluded from necessary communications and decisions. Making a remote worker a true part of the team requires a massive culture shift if your company does not already (successfully) do distributed work.

I've worked remote for 6 years. This comment echoes my experience.

Re: Ask HN: What are the biggest challenges preventing startups from hiring remote?

#34

What exactly is the pain with international payrolls? I don’t quite understand..

Dealing with taxes and with contracts in different jurisdictions. Sure, some people may be ok with working self-employed and handle all of that themselves, but not everyone will do.

Somebody should build startup which would solve payroll issues with remote employees.

Re: Ask HN: What are the biggest challenges preventing startups from hiring remote?

#35

What exactly is the pain with international payrolls? I don’t quite understand..

Country A requires all employees to receive a default-opt-in pension.

Country B requires employers to register with tax authorities and deduct tax directly from the employee's salary.

Country C allows employees to buy childcare vouchers with their pre-tax salary.

Country D has a similar scheme, except for bicycles and it's a loan.

Country E considers private healthcare a taxable benefit-in-kind.

Country F has three different tax bands for employee stock options, depending on when they can be exercised.

Country G makes it mandatory to provide flexible working for new parents...

Of course in a lot of cases you can save on admin by being less tax-efficient, like by not participating in tax-efficient government incentive schemes.

Re: Ask HN: What are the biggest challenges preventing startups from hiring remote?

#36
post #13

Communication. Communication! Communication! Communication! If any part of your product requires people to communicate with each other, then the team members lying on vastly different time zones will have low efficiency because information round trip time will be larger than those of the local (or time zone near) ones.

Yes, Specifically being able to communicate in front of a whiteboard is crucial. Exploring ideas, creating a shared understanding, etc, all becomes a lot easier if you can support this with some interactive visualization on a whiteboard. I feel disabled if I have to communicate without a whiteboard.

Re: Ask HN: What are the biggest challenges preventing startups from hiring remote?

#37
As a few others have said as well, the biggest challenge personally has been Payroll and Taxes. A lot of good candidates want to feel part of the company which means they need to be hired as employees. But legally, a US company hiring in a different country can at best hire them as a consultant/freelancer for tax purposes unless they open a local office in that country which is a major PITA.

I have a US company and trying to build a remote team as "employees". Going crazy trying to figure out how to set this up other than the usual option of "pay them as freelancers and let them do their own taxes". Not everyone is cut out for that and not able to attract good talent.

Re: Ask HN: What are the biggest challenges preventing startups from hiring remote?

#38
post #8

The biggest challenge to making remote workers successful is the existing company culture. If the organization has not been built with a conscious "remote-first" mindset, new remote collaborators will inevitably be excluded from necessary communications and decisions. Making a remote worker a true part of the team requires a massive culture shift if your company does not already (successfully) do distributed work.

Red Hat v. Debian.

Arguably, one of Ubuntu / Canonical's failings.

Re: Ask HN: What are the biggest challenges preventing startups from hiring remote?

#39
I'm the founder of a company that is ~250 people, remote first, and still fully remote. We do have an office in SF, but ~10% of our employees are present, almost no full teams are centralized, and all our processes revolve around remote work. Important to note that we're a US-founded company (this comes along later).

I'm going to use this comment as a way to talk about remote hiring generally, rather than respond directly to your comments. I want to help others understand some of the challenges it has been being one of the larger (relatively) fully distributed companies.

I think there is a common misconception that the world is mostly flat and that our company can hire from anywhere. I am commonly criticized when tweeting job postings (almost always remote) when the countries we can hire from is limited to a select few. "Not real remote" "first world remote only" "remote != 8 countries" etc. are common criticisms.

Disclaimer for the remainder: I am not a lawyer and my exact details because of that may be wrong. Please consult your own legal team.

When hiring remote, there are a few things to keep in mind:

1.) You have to adhere to employment laws within the country you're hiring from. Employment laws vary widely between countries and getting them wrong can be very expensive. For example: vacation time will vary, holidays will vary, the ability to let someone go will vary, what you can/cannot expect from an employee varies. In one country, emailing an employee outside of work hours is legally considered harassment; when working with multiple timezones that's a challenge because "in work hours" for one country may be "out of work hours" for another country.

2.) To employ someone full time, many countries require you to have a legally entity within that country. Establishing a legal entity takes a lot of time and a lot of money.

In the past 12 months, we've had at least one member (more now) on our HR/finance teams establishing legal entities _full time_. I've had my signature on at least 8 incorporation documents in the past 6 months. By the way, most incorporation documents require a "wet" signature so if you're remote like we are, be prepared to be FedExing a lot of sensitive legal documents around.

Beyond just paperwork, there are often requirements to establish a legal entity: a real, physical, local address is one. In one country, we had to pay out of a local bank account in local currency (which has its own red tape), and this country also required we maintain a minimum balance to pay 3 months salary in the local account in local currency at all times. For a startup, that much cash "not working" can be problematic depending what stage you're at.

In one country we're establishing an entity in, the process just takes a LONG time. We've been responding to any inquiries and sending paperwork immediately and we're 8 months in and still probably 2 months away from completing the process. Meanwhile, we still can't legally hire there.

A lot of legal paperwork is understandable in the local language of where you're creating the entity. This means that you also have to pay lawyers fluent in that language to vet the paperwork. We employ full time lawyers, but primarily in English, so this requires us to go to expensive outside counsel.

Finally, this is all expensive. There are fees to creating entities but also recall that we have multiple full time employees that spend their entire day establishing legal entities. So we have our own full time salary costs plus filing costs plus legal costs.

3.) Hiring contractors DOES work around some issues, but has its own downsides. First, we can't offer options/stock to contractors and we'd like all our employees to benefit from this. Second, we often can extend the same full time benefits we want all our employees to share such as healthcare, 401K, etc. Put another way: we want all HashiCorp employees to be employees, we don't want to create second class citizens.

Legally, some countries have legal limits on the hours a contractor can work or length of time they can be contracted before they're considered an "employee" by default and regardless of what you SAY the relationship is, the country will consider it employment and points 1 and 2 above all take effect immediately.

So we certainly DO hire contractors but our point of view is that we intend to hire those people full time over time. We'll often hire contractors if we know that we'll have a legal entity established to hire them within X months, and we're up front with the new hire about this. We'll also pro-rate option/stock vesting for their contractor period when they are hired.

4.) We prioritize countries where we have the most interest. We get asked a lot "please hire in X" but if the number of times we've heard X is much lower than Y, then we'll prioritize Y first.

This creates somewhat of an imbalance, since more countries with a more established tech ecosystem generally have more qualified candidates and therefore get prioritized higher.

We WANT to hire from everywhere, but as a startup with constrained capital and timelines, we have to be pragmatic about choosing the locations where we'll probably be able to hire the most roles while we continue to expand our entities.

5.) We are also open to relocating employees into countries where we do have entities. We've done this multiple times, we pay a relocation fee, and its a great way to hire someone from a country where we can't [yet]. Also note they're "relocating" but are still working remote.

Of course, this is highly dependent on the individual and it is unfair of us to ask or force someone to do this if they have an established family, friend circle, and generally just a life in their existing country. So this only works some of the time!

6.) Despite building process around remote-first, we try to a keep a healthy timezone overlap in each of our teams (3 to 4 hours out of the working day is best). We find that teams that have a team member with a non-overlapping TZ struggle for multiple reasons. So, even though we can hire in many countries now, we'll restrict some job postings to certain countries so we can have that overlap.

EDIT, some additions:

7.) Each US state ALSO requires a legal entity in addition to adhering to state-local employment laws, taxes, and more. At this point HashiCorp has entities in ~30 US states.

Further, there is a tax consequence to the business outside of employment taxes. If you hire an employee in a state, you also now have to pay sales tax on revenue from there. You may argue for/against whether that makes sense, but for a startup this can be VERY expensive.

Our corporate tax obligation would be hundreds of thousands of dollars [less] if we didn't employ people in New York state. We've had to weigh this in cases because the tax obligation from hiring _one_ individual could suddenly be that you can't afford to hire _multiple_ other individuals.

Note we don't want to avoid taxes, that's not what we're doing. But startups are capital constrained and we have to determine long term how we continue to grow and hundreds of thousands of dollars can make a difference.

----------------------------------------------------

Finally, I want to note that we're 100% dedicated at HashiCorp to remaining fully remote. We WANT to hire from everywhere. We're establishing the entities and process to hire in new countries full time. 18 months ago we could only legally hire in 2 countries, today we can hire in 8. By the end of the year it should be at least 4 more. We'll continue from there.

I could write a LOT more about culture and process within the company. But this comment is already getting very long and I think I'll keep it to this. Maybe in the future I'll write more about "chat literacy", the importance of decision inclusion, things that definitely don't work, keeping people motivated/happy, managing people you can't physically see, the lack of body language for signaling, and a lot more.

I hope this helps someone!

Re: Ask HN: What are the biggest challenges preventing startups from hiring remote?

#40
post #8

The biggest challenge to making remote workers successful is the existing company culture. If the organization has not been built with a conscious "remote-first" mindset, new remote collaborators will inevitably be excluded from necessary communications and decisions. Making a remote worker a true part of the team requires a massive culture shift if your company does not already (successfully) do distributed work.

Red Hat v. Debian. Arguably, one of Ubuntu / Canonical's failings.

Huh? Canonical is excellent for remote work, and I know many people who work at Red Hat who say the same about it.
Post reply on HN