Ask HN: What are the biggest challenges preventing startups from hiring remote?
We're starting a new company focused on solving the problem of talent war by helping late-stage startups have successful remote collaborations with tech talent. However, we're still trying to figure out which vertical to focus on. Which of these verticals is most pressing?
1. Sourcing & vetting candidates? 2. Managing international payroll? 3. Bootcamps? 4. Infrastructure & working space?
Let me know your thoughts!
136 comments
[ 2.6 ms ] story [ 205 ms ] threadProblems 1-4 only become real problems after the management team feels comfortable with:
5) How are we going to integrate them into our workflow and team?
"Hire remote workers" has become an extended and rebranded form of "offshoring". Folks learned some hard lessons from the offshoring days that you can't just hire remote. Your organizational thinking and processes need to be ready.
My take is, if you're solving 1-4, you're selling to companies who already have some remote workers. If you're focused on companies with few to 0 remote folks, you'll need something to help them solve 5.
The US has 300 some million people. India has a billion some.
If you can't find an employee in those two countries, it seems you have other problems? (or add 1 or 2 more if you want to spread it around).
Not that there are not great people in all countries. But opening your resume pool from say 1.5 billion people to 3 billion people is unlikely to have a huge benefit to hiring.
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.
I can recall several times where clearly (or so we thought) laid out plans were given over to have them come back a week later with some measure of misunderstanding. The 2 solutions to this have either been micromanaging the remote team, which is painful or time consuming -- or giving the team enough autonomy to work independently, which is risky.
In practice what this means is if you're based in the US, you can either focus on having teams in Europe or Asia, but not both.
Instead of just a requirements document, give them a requirements document but also define a set of red/green tests to show whether the requirements were met. It's hard to do this with front end, where feel is often very important, but in my experience, it works well provided that the remote team's manager is qualified to make the types of architectural decisions necessary to pull this off.
You can even start tying compensation into passing red/green tests!
None of these are big problems. The biggest problem we have is communicating effectively with people in various time zones, and making them feel apart of the team. Video conferencing is still an area that is lacking in this area. I've yet to find a service that meets all our needs. Right now we are using LifeSize because it's the best we've found, and still fairly annoying.
The problem really isn't on the "hiring" end. It's how to work as effectively with remote people as you would with people in the same office. When you introduce friction with remote, it causes problems. That being said, I think it's a worthwhile problem to solve.
Not sure this helps, but this is our biggest struggle right now.
I think it's even harder for companies that have open open offices or are doing Agile. Those two things usually mean the companies are explicitly stressing in-person collaboration. In-person communication isn't a bad thing by itself, but I think that explicitly valuing in-person communication ends up making remote work harder.
It is really hard for established companies, full of many different humans with their habits, to shift from shouting across the room to some sort of distributed, async, communication.
Arguably, one of Ubuntu / Canonical's failings.
The Debian - Canonical distinction is milder, though the latter has at least some centralisation. Nowhere near as much RH's.
Some people feel really insecure without an office, deep inside they think it isn't a "serious business" unless you own real estate in a "serious" postcode. I don't know if it's just an European thing but it's definitely an attitude I've encountered.
In IT, tbh, I think we should just own it. There are more productive and creative ways to send out that sort of signal.
But, then the marketing/sales part of my experience chimes in and I think of all the various times in my career that having physical space added to my credibility. I think of the sectors (government tech and financial tech instantly come to mind) where decisions makers are heavily moved by AAA office space. And, I think of how many times I've seen spending an obscene amount on rent actually convert into paying customers.
My inner developer is saying "right on" but my inner marketer/sales type is thinking of all these times when physical space has a positive ROI from a sales/marketing point of view.
If the person in charge doesn't know what he's doing the rest doesn't matter.
Regarding your options:
1. Hardly any different than on site. 2. Not an issue at all. 3. Huh? 4. For some.
My recent experience left me a bit scarred.
Trying to figure it out on your own is irresponsible at best, so it boils down to hiring a local CPA or tax attorney in each state/city you hire in to go over the implications of bringing someone on in that city.
If the person is right, it's worth the cost, but it's a large, unexpected time-suck.
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.
Hiring is hard to begin with, and hiring remotely has additional pitfalls. A company like Triplebyte that would perform additional vetting to prove a candidate's ability to work remotely would be quite welcome.
Re 4. VC systems are still awful and both companies and employees aren't willing to invest to the right level, and commit to workflow changes, in order to make it seamless to work remotely. In particular, latency and packet loss is what just kills VC and makes it very apparent that we're not actually in the same room together. The way to solve that is gigabit home-office Internet connections, but $10k to run lines and an additional $500/month, as well as the hassle of using a wired connection at home to take advantage of it, and then a dedicated VC system, is a total non-starter for many, on both sides, employer, and employee.
Throw in a timezone difference, and the wrong remote employees can take more time to manage than they're worth. (That's not to say there aren't some really really good, really solid remote employees, just that there are also the wrong hires - same as goes for in-person.)
Re. 2. On top of payroll, there are also plain cultural differences between countries that make it more challenging than when there is no difference - holiday schedules, vacation policies, etc, and until you've lived it, it's hard to know what to look for in advance.
For example, bots like http://tatsu.io or http://standuply.com help running standup meetings.
I think remote work will become more and more popular in the future despite its challenges.
Timezone is a tough one. For us, finding a scrum time that works for everyone (in a small team it's doable), and sticking to it daily helped to get the team to communicate more openly with each other, and stay in sync.
Finding the right set of tools to manage remote teams is one the biggest challenge when a team is distributed across the world. Traditional task management tools didn't lets us easily ideate, organize, and share task lists together, hence we were inspired to build Taskade (Disclaimer: I'm the co-founder of https://taskade.com). The idea of having the freedom to work together on task lists in real-time, see each other's progress, and collaborate without any distractions.
Startups and fast growing companies grow quickly and changes happen rapidly. If priorities are constantly changing and communication/the planning process isn't really robust you won't have remote people who are successful.
These are two areas where good solutions may exist at reasonable price-points, but if so that information isn't widely known.
Not sure if it fits with your business model, but it would be extremely helpful for someone to carefully evaluate the effectiveness of various technologies / products / services for those areas, and provide recipes for known-good setups.
I.e., if one of your clients can tell you their current and upcoming team sizes, network connectivities, etc., you can tell them what products and services give them good video / whiteboard quality at various price points.
IME companies with remote workers tend to be "penny wise, pound foolish" regarding these things.
EDIT: To be more specific: For call quality, having good data on what setups result in good call quality in Skype vs. Slack vs. Google Hangouts etc. And for shared whiteboards, having good information on how effective / sufficient teams find various approaches such as (some website + iPads), (some website + a particular Wacom tablet), (everyone on the team having a particular model of interactive whiteboard such as this one [0]), etc.
[0] https://www.cdwg.com/product/SMART-Board-6075-75in-LED-displ...
But no software can fix variances in bandwidth or latency. I wish there was a way to test a remote hire's internet connection quality. Lack of access to a good internet connection would be a deal breaker for a remote hire for us.
I suspect the reality is that, amongst the best-performing services, which one works best depends on network QoS details, network topology, particular client hardware / OS, etc.
For example: some conferencing software seems to have a real problem with echo cancelation, so either (a) everyone needs mic/speaker hardware that sidesteps the issue, or (b) you accept that everyone will go insane.
Similarly, difference conferencing software has different solutions to people talking over each other accidentally due to latency. One product (Cisco's maybe?) has an icon for metaphorically raising one's hand to request a turn speaking.
One of the most useful parts of it was timing http requests and tracking response times. We solved some very complicated technical support issues using this tool. Do you think it would be useful to adapt something like this to remote workers? It's weird because I've struggled with internet connections when I've worked with remote workers, but never thought of actually testing it until I read this comment...
Doing it more seriously you might even want to use a separate older machine as a skype drone (ie only runs skype) and feed your audio out from your main machines sound card into that.
I had an initial phone call with a firm and it was obvious that they where clustered round a mac laptop - inaudible and very low quality sound.
Don't be discouraged. I checked out your site (and github) Looks nice. I'll use the tool next time I need remote collaboration
Keep up the good work.
Amen to that. I recently was interviewed remotely, and the voice call quality was unacceptably low- I could barely even understand the questions being asked!
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.
We ultimately went with a company[4] that had a different model where they connect you with a local PEO in each market and present a common UI on top of all the disparate local PEOs so that you get a company that specializes in just that country, but a common UX no matter how many countries you work with.
I liked the model, and more importantly, it was a fixed fee and much less expensive, and they published pricing. Disclosure: We made the decision to go with them, but haven't started working with them yet.
[1] https://gruntwork.io
[2] https://www.globalization-partners.com
[3] http://globalpeoservices.com
[4] https://papayaglobal.com
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 employee...
Can you elaborate on what is keeping you from offering options to contractors? Sure, incentive stock options can only be given to employees but what about nonqualified stock options? They can be given to anyone.
Whilst you can offer on approved schemes - you might have to offer people in the uk more options to cover this which might make local (US employees) jealous
We're a remote team but much smaller and certainly unable to pay a full time employee to create companies.
Do you have, or know where to find, a list of countries that can work without setting up a legal entity? We've lost a lot of time trying to recruit candidates where we've not been to find a workable solution due to local laws and our limited resources (e.g. in France!)
Learning about this stuff basically requires a huge time sink per country in reading local laws, as well as a cost of paying a lawyer to verify your assumptions. It is unfortunate. A "tldrlegal" site for entity creation and employment laws would be amazing.
Also re: France... yeah, that is a tough one. We're just about ready to hire there. The whole process was very difficult, on the harder end of the spectrum that we've experienced so far. :)
I don't know for the specific case you've posed, but we've had similar things happen. If an employee moves into a state/country we can't employ them in, it causes a bit of a panic. We either have to 1.) establish the correct legal/financial entities to employ them or 2.) let them go. In theory, you can convert the employee into a contractor, but this has ramifications on options vesting and benefits and so on and is a huge mess. I'm sure there are a lot more caveats to this that are under consideration (again, I'm now a lawyer) that may affect this, so I wouldn't generalize this too far.
I don't think we've ever let someone go for this though, we have once to memory panicked and rushed to establish the entity (potentially paying fines along the way). I may be mistaken, I just don't recall exactly. In any case, we kindly ask our employees to notify us of any change of location, since it almost certainly changes payroll tax even if you are moving to a location we CAN employ in (i.e. even between US states). Also, the panicking is not fun for anyone (including the employee, whose job status is suddenly uncertain).
(If the spouse is working for the US military there are NATO agreements which might make German employment law inapplicable but I know almost nothing about that.)
Would you be able to share the actual countries in question? In which country was it required to open a bank account in the local currency? Which one has taken 10 months to complete opening an entity in?
Tax avoidance is perfectly legal and encouraged to maximize shareholder value. Tax evasion is illegal.
> First, we can't offer options/stock to contractors
Can you elaborate why?
Think about it: the benefits of remote work go mainly to the employee, but the drawbacks (harder to communicate, harder to evaluate productivity) fall disproportionately on the manager. Since the manager is the one making the hiring decision, they don't hire remotes.
So to give a really broad answer, my suggestion would be "change the incentives so managers will hire more remote workers". That could mean internalizing costs of on-site workers, better communication tools, etc.
- Which payroll companies, if any, will be the best solution for handling international (or even just inter-state within the U.S.) payroll / tax issues?
- What communications technologies and practices work best for various team geographies / network-connection-quality / local-hardware setups?
- What's the optimal frequency, duration, structure, etc. of whole-team face-to-face meetings for teams that are typically distributed?
- What management training is most helpful for managers of all-remote teams, or of teams where only some members are remote?
For example: At ($10k initially + $3k/year) per employee, you're likely to avoid problems A, B, and C, but still run into D and E occasionally, depending on team size, using recipe $FOO.
At ($20k initially + $10k/year) per employee, you avoid problems A-D, using recipe $BAR.
PS. We are hiring
Personally, I find the toughest part to be actually managing the people. You really need to trust your team to be self-motivating which can be tough for a manager to do, especially new ones, because you need to give up some control.
But even though you trust them you need to have a way to measure results. That means being more disciplined and mature in your project planning than you might be if everyone is co-located.
For a startup that is key. Startups often skimp on disciplined project management.
I also find it tougher to do things like say, identify when someone is having a rough time (personal or professional) and take steps to correct or accommodate for that. If a co-located employee starts underperforming but I can see they are clearly checked out (like their head is somewhere else) I might suspect there is something going on at home and adjust my management style with that person. If they are remote it is harder to tell those things. Communication becomes extremely important when body language / behavioral clues are lacking.
So to pile on a lot of the other answers here... communication, communication, communication.