Why Remote Work Should Change Startup Culture
1–10 of 130 posts
Re: Why Remote Work Should Change Startup Culture
#2Re: Why Remote Work Should Change Startup Culture
#3Then again, neither should resistance to remote developers in general or the myriad of other, more bullshit things that go on in sourcing talent. Makes me wonder how self-imposed the "talent shortage" is.
Re: Why Remote Work Should Change Startup Culture
#4Re: Why Remote Work Should Change Startup Culture
#5With startups it's quite difficult - remote law, pay and equity. Law for contracts and equity in different countries vary. Buying power is inconsistent. Stock options in particular are strongly biased against holders with lower pay, since they will have to take greater risk to buy their stake at cost of many more years worth of salary. You got to make sure so many things add up in multiple places, otherwise it's just…
Re: Why Remote Work Should Change Startup Culture
#6With startups it's quite difficult - remote law, pay and equity. Law for contracts and equity in different countries vary. Buying power is inconsistent. Stock options in particular are strongly biased against holders with lower pay, since they will have to take greater risk to buy their stake at cost of many more years worth of salary. You got to make sure so many things add up in multiple places, otherwise it's just…
Re: Why Remote Work Should Change Startup Culture
#7Re: Why Remote Work Should Change Startup Culture
#8After I did well on all of that, I was flown up to NYC for a 'culture-fit' interview. Which I failed, apparently. As a mid-30s guy who was raised in the mid-west, I felt like I had very little in common with the 20-something urbanites with whom I was interviewing.
They didn't seem like bad people at all, and I didn't foresee any issues working with them (esp. remotely), but apparently I gave off a strong enough 'not-like-us' vibe to cause them to pass on a demonstrated technically-solid candidate (because if there truly is a shortage of good developers, this would be an incredibly silly thing to do).
Re: Why Remote Work Should Change Startup Culture
#9One frustrating thing I have found about companies willing to hire remotely is that many refuse to be your first remote gig; i.e. they only hire people who already have years of experience working remote. I understand the hesitation, but if good people really are so hard to find it should be a hesitation that can't stand up in the face of being unable to get things done. Then again, neither should resistance to remot…
We had a team of three co-located with the customer and then we arranged for everyone to work remotely one day a week, barring Monday or Friday (for appearances). Tuesday was my day. After a few successful months of that, we expanded it out to 2 days each. We would have gone to three but the contract wrapped.
But it gave us a small space to experiment and see what would work and slowly convince the customer that it would be okay.
Re: Why Remote Work Should Change Startup Culture
#10If more startups allowed remote workers, would the salaries of developers fall in the bay area?
There are a variety of remote work arrangements: 1) local employees who have employers with liberal work-from-home policies (they're "remote" when they don't commute in), 2) employees who are always remote, but still in-state (located in the same state as the employer), 3) employees who are always remote but still domestic (located in the US), 4) employees who are always remote and located internationally.
The first two kinds of remote employee don't incur (much) additional cost to the employer. The third kind can incur non-trivial additional costs in the management of payroll (state income taxes, labor/unemployment fund requirements, etc.), especially if done at any scale. Larger companies can do this because they are already established in multiple states, but smaller ones tend to impose restrictions on where remote workers can live and even whether they're permitted to move to a new state and still remain employed. The last kind is a whole other ball of wax--it has the same tax and payroll management problems of the third kind, but additional complexity I'm sure.
Then there is the additional overhead of managing remote teams. Having experienced being an "individual contributor" and coordinating with project management to manage remote teams I can assure you this is not a trivial thing and involves its own costs.
So all these factors influence how much lower the salaries have to dip before they are worth it. Personally, I doubt remote work will impact salaries in this area much anytime soon.