TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

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

176 点作者 hichamin大约 7 年前
We&#x27;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&#x27;re still trying to figure out which vertical to focus on. Which of these verticals is most pressing?<p>1. Sourcing &amp; vetting candidates? 2. Managing international payroll? 3. Bootcamps? 4. Infrastructure &amp; working space?<p>Let me know your thoughts!

43 条评论

ecwilson大约 7 年前
Others have mentioned this to some extent, but what I&#x27;ve found the most challenging is when a company tries to do both local and remote, but was not <i>remote-first</i>. People who are remote are de-facto second-class citizens by virtue of the fact that they aren&#x27;t included in hallway conversations or casual meetings. It&#x27;s incredibly hard to overcome that. Teams that started remote-first are already well-practiced in inclusion and remote rapport-building, so it&#x27;s less of an issue for them. But people who have the <i>opportunity</i> to meet locally and build rapport locally tend to get lazy and their remote muscles atrophy over time, unless they are making a very conscious effort, or the habits have already been deeply ingrained in them over time.<p>I&#x27;d add that this culture-setting rolls down from management -- if they aren&#x27;t setting a good example, others will falter and the remote-supporting culture will fall apart.<p>Things like payroll, taxes, infrastructure are all solvable today, IMO, with the right resources or tools.
评论 #17023019 未加载
评论 #17024164 未加载
评论 #17022843 未加载
评论 #17022906 未加载
评论 #17025830 未加载
allday大约 7 年前
The biggest challenge to making remote workers successful is the existing company culture. If the organization has not been built with a conscious &quot;remote-first&quot; 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.
评论 #17022661 未加载
评论 #17022408 未加载
评论 #17022522 未加载
评论 #17022414 未加载
评论 #17026576 未加载
评论 #17022557 未加载
DoofusOfDeath大约 7 年前
IMO one of the least-solved problems is communication. Two areas in particular: (1) lack of a shared real whiteboard, and (2) video-call quality.<p>These are two areas where good solutions may exist at reasonable price-points, but if so that information isn&#x27;t widely known.<p>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 &#x2F; products &#x2F; services for those areas, and provide recipes for known-good setups.<p>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 &#x2F; whiteboard quality at various price points.<p>IME companies with remote workers tend to be &quot;penny wise, pound foolish&quot; regarding these things.<p>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 &#x2F; 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.<p>[0] <a href="https:&#x2F;&#x2F;www.cdwg.com&#x2F;product&#x2F;SMART-Board-6075-75in-LED-display&#x2F;4477254?RecommendedForEDC=4527545&amp;RecoType=RP&amp;cm_sp=Product-_-Session&amp;ProgramIdentifier=3" rel="nofollow">https:&#x2F;&#x2F;www.cdwg.com&#x2F;product&#x2F;SMART-Board-6075-75in-LED-displ...</a>
评论 #17022573 未加载
评论 #17022836 未加载
评论 #17023677 未加载
评论 #17023304 未加载
throwaway2016a大约 7 年前
5. Managing people<p>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.<p>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.<p>For a startup that is key. Startups often skimp on disciplined project management.<p>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 &#x2F; behavioral clues are lacking.<p>So to pile on a lot of the other answers here... communication, communication, communication.
评论 #17036766 未加载
jvalencia大约 7 年前
The biggest challenge with remote is coordination. I&#x27;ve now managed 4 remote teams. The turn-around time between communication cycles with people on the other side of the globe can drastically increase the time it takes to get consensus on issues that locally might take 10 minutes.<p>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.
评论 #17022969 未加载
评论 #17023526 未加载
DisruptiveDave大约 7 年前
Young founders with zero or near-zero management experience in person, never mind remote. To a lesser degree - and strictly for small team, early stage startups - part of the journey is living it together. The whole vibe loses something when you&#x27;re staying late and eating ramen together over Skype.
mitchellh大约 7 年前
I&#x27;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&#x27;re a US-founded company (this comes along later).<p>I&#x27;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.<p>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. &quot;Not real remote&quot; &quot;first world remote only&quot; &quot;remote != 8 countries&quot; etc. are common criticisms.<p>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.<p>When hiring remote, there are a few things to keep in mind:<p>1.) You have to adhere to employment laws within the country you&#x27;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&#x2F;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&#x27;s a challenge because &quot;in work hours&quot; for one country may be &quot;out of work hours&quot; for another country.<p>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.<p>In the past 12 months, we&#x27;ve had at least one member (more now) on our HR&#x2F;finance teams establishing legal entities _full time_. I&#x27;ve had my signature on at least 8 incorporation documents in the past 6 months. By the way, most incorporation documents require a &quot;wet&quot; signature so if you&#x27;re remote like we are, be prepared to be FedExing a lot of sensitive legal documents around.<p>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 &quot;not working&quot; can be problematic depending what stage you&#x27;re at.<p>In one country we&#x27;re establishing an entity in, the process just takes a LONG time. We&#x27;ve been responding to any inquiries and sending paperwork immediately and we&#x27;re 8 months in and still probably 2 months away from completing the process. Meanwhile, we still can&#x27;t legally hire there.<p>A lot of legal paperwork is understandable in the local language of where you&#x27;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.<p>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.<p>3.) Hiring contractors DOES work around some issues, but has its own downsides. First, we can&#x27;t offer options&#x2F;stock to contractors and we&#x27;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&#x27;t want to create second class citizens.<p>Legally, some countries have legal limits on the hours a contractor can work or length of time they can be contracted before they&#x27;re considered an &quot;employee&quot; 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.<p>So we certainly DO hire contractors but our point of view is that we intend to hire those people full time over time. We&#x27;ll often hire contractors if we know that we&#x27;ll have a legal entity established to hire them within X months, and we&#x27;re up front with the new hire about this. We&#x27;ll also pro-rate option&#x2F;stock vesting for their contractor period when they are hired.<p>4.) We prioritize countries where we have the most interest. We get asked a lot &quot;please hire in X&quot; but if the number of times we&#x27;ve heard X is much lower than Y, then we&#x27;ll prioritize Y first.<p>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.<p>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&#x27;ll probably be able to hire the most roles while we continue to expand our entities.<p>5.) We are also open to relocating employees into countries where we do have entities. We&#x27;ve done this multiple times, we pay a relocation fee, and its a great way to hire someone from a country where we can&#x27;t [yet]. Also note they&#x27;re &quot;relocating&quot; but are still working remote.<p>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!<p>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&#x27;ll restrict some job postings to certain countries so we can have that overlap.<p>EDIT, some additions:<p>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.<p>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&#x2F;against whether that makes sense, but for a startup this can be VERY expensive.<p>Our corporate tax obligation would be hundreds of thousands of dollars [less] if we didn&#x27;t employ people in New York state. We&#x27;ve had to weigh this in cases because the tax obligation from hiring _one_ individual could suddenly be that you can&#x27;t afford to hire _multiple_ other individuals.<p>Note we don&#x27;t want to avoid taxes, that&#x27;s not what we&#x27;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.<p>----------------------------------------------------<p>Finally, I want to note that we&#x27;re 100% dedicated at HashiCorp to remaining fully remote. We WANT to hire from everywhere. We&#x27;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&#x27;ll continue from there.<p>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&#x27;ll keep it to this. Maybe in the future I&#x27;ll write more about &quot;chat literacy&quot;, the importance of decision inclusion, things that definitely don&#x27;t work, keeping people motivated&#x2F;happy, managing people you can&#x27;t physically see, the lack of body language for signaling, and a lot more.<p>I hope this helps someone!
评论 #17028849 未加载
评论 #17023497 未加载
评论 #17022774 未加载
评论 #17089185 未加载
评论 #17026919 未加载
评论 #17027873 未加载
评论 #17023010 未加载
评论 #17029173 未加载
评论 #17025983 未加载
评论 #17027683 未加载
评论 #17026241 未加载
评论 #17027703 未加载
评论 #17022780 未加载
评论 #17028027 未加载
评论 #17028598 未加载
poulsbohemian大约 7 年前
It’s been my experience that many first-time entrepreneurs and in many cases first-time managers &#x2F; executives, operate from a place of fear. They are scared about their burn rate, about whether the team is working, whether they have the right team, about countless administrative details, and on top of that the good ones are hopefully out there actually talking to prospects and seeking customer feedback. What this means is that many are scared of remote because they <i>feel</i> like they need you there present next to them in order to <i>feel</i> like there is forward momentum in the business. It’s a trust problem and a management problem; maybe not even a legitimate problem so much as an emotional burden. Is there a technical solution to that? Some might say the solution revolves around time trackers and project management tools, but I’ve seen those just become a further burden to the team without actually relieving anyone’s general overbearing need to micromanage the team (something they can control) over engaging with prospects &#x2F; trying to grow the business (something harder to control).
johnxie大约 7 年前
Infrastructure &amp; working space is a big challenge depending on where your remote team member is based, but overall that has seen a big improvement with more affordable UPS options and wireless connectivity for backup.<p>Timezone is a tough one. For us, finding a scrum time that works for everyone (in a small team it&#x27;s doable), and sticking to it daily helped to get the team to communicate more openly with each other, and stay in sync.<p>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&#x27;t lets us easily ideate, organize, and share task lists together, hence we were inspired to build Taskade (Disclaimer: I&#x27;m the co-founder of <a href="https:&#x2F;&#x2F;taskade.com" rel="nofollow">https:&#x2F;&#x2F;taskade.com</a>). The idea of having the freedom to work together on task lists in real-time, see each other&#x27;s progress, and collaborate without any distractions.
joss82大约 7 年前
Communication.<p>Communication! Communication! Communication!<p>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.
评论 #17022547 未加载
fragmede大约 7 年前
Personally I&#x27;d say 1 and 4 are the most pressing, though 2 raises some other issues. Personally I&#x27;d not hire anyone junior for remote work at all (sorry), so 3 is an anti-issue to me.<p>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&#x27;s ability to work remotely would be quite welcome.<p>Re 4. VC systems are still awful and both companies and employees aren&#x27;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 <i>kills</i> VC and makes it very apparent that we&#x27;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&#x2F;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.<p>Throw in a timezone difference, and the <i>wrong</i> remote employees can take more time to manage than they&#x27;re worth. (That&#x27;s not to say there aren&#x27;t some really really good, really solid remote employees, just that there are also the wrong hires - same as goes for in-person.)<p>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&#x27;ve lived it, it&#x27;s hard to know what to look for in advance.
BrandiATMuhkuh大约 7 年前
We are a pure remote company but Tax&#x2F;employment-law is for us the biggest issue. Or to be more precise, it&#x27;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.
评论 #17022491 未加载
评论 #17023283 未加载
评论 #17022335 未加载
评论 #17024716 未加载
codegeek大约 7 年前
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&#x2F;freelancer for tax purposes <i>unless</i> they open a local office in that country which is a major PITA.<p>I have a US company and trying to build a remote team as &quot;employees&quot;. Going crazy trying to figure out how to set this up other than the usual option of &quot;pay them as freelancers and let them do their own taxes&quot;. Not everyone is cut out for that and not able to attract good talent.
评论 #17022645 未加载
DoofusOfDeath大约 7 年前
From the comments so far, I&#x27;m hearing that your prospective clients would benefit from knowledgable consulting to help them navigate <i>multiple</i> issues:<p>- Which payroll companies, if any, will be the best solution for handling international (or even just inter-state within the U.S.) payroll &#x2F; tax issues?<p>- What communications technologies and practices work best for various team geographies &#x2F; network-connection-quality &#x2F; local-hardware setups?<p>- What&#x27;s the optimal frequency, duration, structure, etc. of whole-team face-to-face meetings for teams that are typically distributed?<p>- What management training is most helpful for managers of all-remote teams, or of teams where only some members are remote?
评论 #17022670 未加载
sontek大约 7 年前
Payroll is the biggest issue. You have to pay taxes in any state your employee is working. This gets expensive and time intensive as you start filing annual reports and paying taxes in 4 or 5 states.
评论 #17022324 未加载
Fire-Dragon-DoL大约 7 年前
I&#x27;m confused by people saying they have problems communicating across the internet due to conference software. Gamers have been running 40-people fully-coordinated real time raids and a company can&#x27;t manage to run a meeting online?<p>How people have problems every day with the conference software? If you do, buy a dumb hardware that you use only for conferences (I think a raspberry could work too?). Or join 2 minutes earlier than your meeting and run a sanity check.<p>Connection will drop once every 10 meetings, but so people will get distracted, or sick.
j45大约 7 年前
Startups often don&#x27;t know how to hire let alone hire and manage remote, and quite often, remote workers aren&#x27;t always the best at it too.<p>What could work quite well often is more challenging... Some things that have made it easier for me:<p>- Dedicated PeopleOps person - this person&#x27;s job is only to make all the tools work together better for everyone. Jira, Slack, integrations, notifications. People should be able to open requests to remove remote friction of using multiple tools, etc.<p>- Start with real-time remote (everyone who works is awake at the same time) has gone a long way. Plus or minus 2-3 time zones, no more. That way, especially in the beginning, everyone is available to work at the same time.<p>- International payments, in the beginning, is easier to start as a contractor via a service that takes care of it like Upwork. Once you know you have a winning candidate, it&#x27;s worth figuring out that new jurisdiction.<p>- Onboarding - should be collaborative, hanging out on slack. Make candidates join your infrastructure during the trial period to confirm that in fact, they can use your tools.<p>- Read - there are lots of companies building healthy online cultures. STudy and follow them.<p>- Weekly WOS video call - 1&#x2F;2 hour every week for everyone to have 1-2 to minutes to share what they&#x27;re working on.<p>- Run all meetings as if they were remote. Everything gets scheduled on hangout, etc, in case someone needs to hop on.<p>There&#x27;s some good handbooks out there for remote working too that have been a treasure trove. If I can find a link I&#x27;ll update this post.
jlisam13大约 7 年前
I have been working at GitHub for almost a year, which is a remote first company. I would say challenges include:<p>- Solitude (at first it&#x27;s not an issue) - Asynchronous communication. Learning to read and write effectively. - Team collaboration work (designing&#x2F;brainstorming). It&#x27;s very difficult to explain ideas through &lt;insert name of video conference product&gt;. To solve for this, GitHub allows employees to meet each other as long as there is a business need. On top of this, we hold summits very often, where the team gets to meet each other in a location for a week. - Internet and great conferencing hardware (GitHub provides a great budget for both Internet costs and hardware).<p>But I would say the most challenging part is <i></i>Trust<i></i>. Trust in your manager, trust in your organization, trust in your company, and trust in your peers. Without Trust, there is no way to build a remote friendly company. How are you going to micro manage someone who is working in EU while you are sleeping in the US? Obviously GitHub is not a perfect place, but I would say that there is a mutual understanding among employees to trust each other and to communicate effectively.
评论 #17028039 未加载
ethanjdiamond大约 7 年前
Can I ask a question? I personally have never been in a relationship with remote workers that has been more than 70-80% as effective as having everyone co-located.<p>What are some examples of companies that have been successful using primarily remote workers? I don&#x27;t mean companies that Hacker News considers do remote work &quot;correctly&quot;. I mean companies who have grown to around the nine figure mark without a co-located team?
评论 #17024821 未加载
评论 #17024715 未加载
评论 #17024047 未加载
cimmanom大约 7 年前
None of the above. Few engineers (or other individual contributors) have the operational maturity to work effectively remotely. Few managers have the skills to manage remote employees. Few employees have the insight and communication skills needs to work as effectively with remote colleagues as with those who are present. These issues magnify the larger and organization gets.
celestialcheese大约 7 年前
Payroll 100%. When we started hiring people remote it was the biggest surprise, and most headache.<p>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&#x2F;city you hire in to go over the implications of bringing someone on in that city.<p>If the person is right, it&#x27;s worth the cost, but it&#x27;s a large, unexpected time-suck.
评论 #17022367 未加载
randycupertino大约 7 年前
Remote tech is unreliable. Our company spends tons of money on conference software, and we still all sat around for 20 minutes of a wasted meeting today while they couldn&#x27;t get a weird echo out of the dial-in. There&#x27;s always something- we can hear you but we can&#x27;t see you. We can see you but we can&#x27;t hear you. The slides are showing but the video isn&#x27;t working. The video is working but the sound has a weird echo. Everything is working, but someone forgot to put themselves on mute and you can hear the driving noise.<p>Even when everything works perfectly, there is always a lag or a missed connection due to miscommunication or timezones.<p>In short, it always kinda sucks, is a drag to deal with even with the best tech and we just get more done with our in-house teams.<p>Remote workers don&#x27;t build up any social capital and so are always the first to be laid off.
doozy大约 7 年前
After working remotely for over a decade for multiple companies my conclusion is the biggest issue is finding managers who grok remote working.<p>If the person in charge doesn&#x27;t know what he&#x27;s doing the rest doesn&#x27;t matter.<p>Regarding your options:<p>1. Hardly any different than on site. 2. Not an issue at all. 3. Huh? 4. For some.
评论 #17022757 未加载
jiveturkey大约 7 年前
0. bandwidth<p>There’s no solution as good as yelling across the room or walking past the desk. chat is a poor substitute for all the reasons everyone in this boat knows.<p>The best way to get this to work is like that one company did (saw it here on HN): have everyone in the company work remote for a week.
jasonlotito大约 7 年前
We hire remote.<p>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&#x27;ve yet to find a service that meets all our needs. Right now we are using LifeSize because it&#x27;s the best we&#x27;ve found, and still fairly annoying.<p>The problem really isn&#x27;t on the &quot;hiring&quot; end. It&#x27;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&#x27;s a worthwhile problem to solve.<p>Not sure this helps, but this is our biggest struggle right now.
评论 #17022423 未加载
Analemma_大约 7 年前
I can&#x27;t remember if I read it here or somewhere else, but someone once made a really good point: that the incentives are strongly skewed against hiring remotely.<p>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&#x27;t hire remotes.<p>So to give a really broad answer, my suggestion would be &quot;change the incentives so managers will hire more remote workers&quot;. That could mean internalizing costs of on-site workers, better communication tools, etc.
BasHamer大约 7 年前
Pay late stage startup employees &amp; new-hires to keep a time diary, and see where they spend time with coworkers. Then do the same w&#x2F; people not working at startups. I guess that startups have more &quot;non-work&quot; time spend together.<p>Joining a startup is different than a 9-5 commitment, it means joining a tribe&#x2F;family. So if the office people leave for a 2-hour lunch before spending a late night in the office, how does a remote person &quot;join&quot; that? Being part of the family means you are there for the leisure as well as the work.
poulsbohemian大约 7 年前
I work frequently with startups &#x2F; early-stage companies and have not found remote to be a legitimate problem or any different than the experiences encountered by established companies with regard to working remotely. Managing international payroll, or frankly even dealing with tax and regulatory differences among the 50 states is likely something many startups would be willing to outsource. Just dealing with several states was a burden, plus the administrative costs of a payroll service felt like a lot for the service received.
souprock大约 7 年前
Security is the big problem, even if not international. You essentially have to connect computers with trade secrets (source code, CAD files, etc.) to the internet, which is a big no-no.<p>If you go international, then you are probably dealing with a legal system that is stacked against you. The government probably even intends to divert your trade secrets to fully domestic (relative to them) companies, and will apply pressure to &quot;your&quot; employees (who may even be government agents) to make it so.
jedberg大约 7 年前
#4 is the most pressing. I have a fully remote team, and we try to make sure as much communication is asynchronous as possible. But sometimes, you just need a few people to work together in real time.<p>And right now that means dealing with a terrible video conferencing experience and not having a good shared whiteboard solution.<p>If you could figure out a way to realistically replicate &quot;a bunch of people around a whiteboard&quot;, then I will pay you money for your product.
ellyot大约 7 年前
We have been working remotely from day one. It was difficult at the beginning and can feel harder sometimes, but once you get used to it it works. The team meets also every few months in beautiful places like Italy or Spain and spends a few days together. This is how we get over problems like &quot;isolation&quot;.<p>Our set up has partly brought us to create ellyot.com that allows you to find inspiring workspaces globally and network with like minded people.
macinjosh大约 7 年前
I&#x27;d say #4. I am remote and my company has a hard time providing, tracking, maintaining, and upgrading the gear employees need to do their job. It currently involves a lot of manual data entry, trips to the UPS store by both HQ staff and remote employees. Especially an issue when the person who is ordering gear doesn&#x27;t understand the gear or the needs of the employee.
评论 #17028786 未加载
purplezooey大约 7 年前
They must be big, because it seems like every startup has to put their HQ in the most miserable places like Mountain View or Menlo Park.
评论 #17025918 未加载
iamcasen大约 7 年前
Biggest challenge has to be timezones. Just due to the delays in communication, and the difficulty of having meetings late at night or super early in the morning.<p>I&#x27;ve found the most difficult type of remote work is highly collaborative. Iterating on designs, on software, or ideas in general.<p>Anything that can aid in that type of remote work would be a boon
ejcx大约 7 年前
I think the hardest part is the planning process and communicating rapid change.<p>Startups and fast growing companies grow quickly and changes happen rapidly. If priorities are constantly changing and communication&#x2F;the planning process isn&#x27;t really robust you won&#x27;t have remote people who are successful.
daurnimator大约 7 年前
<p><pre><code> - International payroll: often impacts tax situation - Adjusting to remote collaboration. e.g. no more walls of sticky notes; can no longer rely on water cooler conversations or &quot;quick meetings&quot; - Timezones</code></pre>
评论 #17022364 未加载
legohorizons大约 7 年前
What exactly is the pain with international payrolls? I don’t quite understand..
评论 #17022542 未加载
评论 #17024502 未加载
评论 #17022276 未加载
评论 #17022480 未加载
评论 #17022471 未加载
hkmurakami大约 7 年前
Trust building&#x2F;erosion and buyin&#x2F;retention.
JamesLeonis大约 7 年前
Co-located work is synchronous programming.<p>Remote work is asynchronous programming.<p>The great part of co-located work is that so much communication happens organically. If you need something, or have a question, the answer is a desk or two away. Processes can be ad-hoc and decided in the hallway or around the water cooler.<p>At the same time, that organic nature turns on a company once it gets bigger. The organic transfer of information takes time. In small organizations or teams that time is small, but as the organization or team grows, the more repetition is needed to propagate the same information in the system. Where you used to answer a question once, it&#x27;s now once a week.<p>The reason is because the ease of organic communication prevented the organization from writing down it&#x27;s tribal information. It took too much effort! But as the organization grew, that slow organic information transfer simply could not propagate tribal knowledge fast enough or redundant enough like writing it down. Remote work is essentially permanent async work, but you are also temporarily async at 3am and your servers are down. I hope your coworkers wrote the production debug steps down, or you are relying on your own memory. It also affects your new hires because they will have to enculture themselves to the information and organization.<p>Remote-first policies see that, eventually, all companies require async access to it&#x27;s tribal knowledge. That&#x27;s READMEs, Wikis, tickets, helper programs, the accounting department, etc. Realizing that all corporations are eventually remote (if only because you <i>will</i> spread to another city, office, or different floors), you spend the extra energy to build those tools so you can look up your tribal information at 3am on a Saturday morning after drinking. Those Wikis really help, yo!<p>It also adds a tremendous amount of visibility and accountability into what you do. You have visible documentation and visible communication. Tickets are filed for bugs, and others in a completely different office can check the status. My drunk self can read the production FAQ at 4am before the hangover sets in. The best part is you can hire remote workers, because your entire process supports that asynchronous access to information.<p>In many ways these asynchronous processes add a tremendous amount of value to your business, as well as offer the perk of hiring fully remote employees.<p>Why, given all of these benefits, would companies bother with co-location at all? Well, to borrow from Behavioral Economics, I&#x27;d say they are making an economically irrational choice to value <i>the show of productivity</i> over <i>actual productivity</i>. Management by visibility. I <i>do</i> think management types are incentivized to continue the <i>show</i>, rather than the <i>substance</i>, because their boss judges based on visibility rather than metrics. At the same time, the fixes are spelled out above since they add that visibility into processes (to an extent), but it takes a management that holds itself accountable.<p>For another stupid geeky metaphor, businesses are highly parallelized processes. A synchronous co-located organization has highly mutable information sources, it&#x27;s employees. To get information in such a system, that it must acquire a mutex lock (interrupt the employee) to read information but it&#x27;s faster for both people. A asynchronous organization, through it&#x27;s explicit processes and documentation, allows for lock-free reads of information but requires more overhead on the individual processes as well as embracing some Eventual Consistency. In a small organization with few employees&#x2F;threads and few interruptions&#x2F;locks, co-location probably is fine. But as your employee&#x2F;thread count increases, those locks and interruptions exponentially explode and your whole organization can grind to a halt in endless Slack questions and status updates: The Deadlock of Corporations.<p>If you are thinking about remote, consider tools that embrace asynchronous access. IMHO this means any software that requires both parties to participate at the same time is bad. I&#x27;m including Phone Calls, Slack, IRC, AIM, Email, Hangouts, and others like them. You should never have to ask &quot;Did you see&#x2F;read&#x2F;notice my X?&quot; as these tools encourage synchronous behaviors. These processes are the Interfaces of your Organization. They increase overhead but they pay dividends when your organization grows in headcount. The ability to hire remote is a perk at this point.
Kiro大约 7 年前
How does 2 normally work? Apart from invoicing as a contractor, can the company actually hire someone located in another country?
rhspeer大约 7 年前
Skill qualification and the more formal communication requirements.
fairpx大约 7 年前
For us (<a href="http:&#x2F;&#x2F;fairpixels.pro" rel="nofollow">http:&#x2F;&#x2F;fairpixels.pro</a>) it’s actually the off-work connectivity. Slack, email, todo lists and all of the other tools make us pretty effecient and productive. But I’d love to see how I can boost social connectivity outside of ‘work’.<p>PS. We are hiring
评论 #17023510 未加载
alexxtomsk大约 7 年前
Everybody speaks here about communication. With the rise of enterprise messengers like Slack it&#x27;s becoming easier.<p>For example, bots like <a href="http:&#x2F;&#x2F;tatsu.io" rel="nofollow">http:&#x2F;&#x2F;tatsu.io</a> or <a href="http:&#x2F;&#x2F;standuply.com" rel="nofollow">http:&#x2F;&#x2F;standuply.com</a> help running standup meetings.<p>I think remote work will become more and more popular in the future despite its challenges.