I generally agree with all the points (minus the obvious caveats), but I'd prefer if we'd push back against the whole "happy work family" mantra. Some of us don't mind being seen as "just that guy doing the job from a distance", but do mind other people trying to make us more than that. For me, part of remote work is to get away from continuous pushing towards more socialization. Whenever someone says 'encourage', it often seems to loop around to a negative if you don't want to participate.
I'm the complete opposite to you. I respect your opinion, so I think the question is even more important to ask. I'm not interested in working for a company where everyone is antisocial and the only interaction is through code reviews.
The problem is that so much of the work-sponsored open socialization feels fake.
Fake smiles and say fake things. Everyone has to type the same "kudos" message for every accomplishment or they're not showing teamwork. The team I was on where everyone had to snap audibly in applause for anyone else "sharing." The pressure to drink together because that's what shows friendship in a frat. Etc. So much garbage!
I don’t consider myself anti social a single bit. My wife describes me as extremely social and I talk to everyone around me.
But I subscribe to what OP said. I don’t want to be forced to socialize at some work event. I’m happy to socialize with everyone during work in that context. We can chit chat. We can have a water cooler conversation. We can talk about personal lives and families. And I’ll happily and genuinely engage.
But I don’t want any forced activities, get togethers or Xmas parties.
Exactly. No one is "wrong." But if your position is that you never want to travel period, that's something you should discuss in the first phone screen if it's a hard condition.
(And of course the converse is true as well. If the company is remote-first and doesn't believe in employees getting together physically that will be a showstopper for some.)
I have similar feelings and thoughts about remote work, I've been working remote in some capacity for over a decade, but I'm careful to ensure that remote doesn't turn into isolated. I've seen that happen before, both to myself and to others, and it's a dangerous place to be in a team environment.
Physical get togethers in a remote-first company means I have to travel for that get together. I live in a rural area with no direct flights to anywhere other then major airline hubs, so now I have a layover somewhere and it’s basically an entire day of traveling to go anywhere. That’s 2 days travel for the round trip.
Since it’s so much work to get everyone together, might as well make a week out of it. So that’s 3 working days plus the 2 travel days. It’s not unlikely one of those working days is going to be a ‘fun’ event day to make it all ‘worth it’ for people to travel- meaning just 2 productive working days.
So a week of working 24 hour days (if I’m not at home with my family then it’s work), for perhaps 2 or 3 productive days. Considering I’m not traveling an entire day, I’m looking at at 96 hour week for maybe 16-24 hours worth of productive time.
I get that we are not robots and being on a team is a very social activity- but I am entirely against traveling. We’ve had some really fun remote game-days during work hours and setting aside time to chat with team members is fun too. Please don’t make me travel and waste all the time away from my family and loved ones.
And you should work for a company that is a match for you. I've worked on mostly remote teams but, pre-COVID, occasional off-sites were really not optional. Which seems reasonable barring exceptional circumstances. The lack of same has really been something of an issue the past couple of years. Of course, people should choose their own circumstances as well as they can.
> push back against the whole "happy work family" mantra
I agree wholeheartedly. The company is not my family. It must pay me to be there.
I also think "team-building" is ridiculous. If people need to interact more, to socialize, that should be built into the work. Engineering is a group activity. Treating social aspects of it as side-effects is just broken.
> Offering equal pay for equal work [...] Pay people for their contribution and treat all humans with equal respect.
Does any company actually do this? I don’t feel like this is economically feasible. What rate do you pay? The California rate or the Romania rate? If pay the Romania rate then no one from California will work for you. If you pay the California rate then you will be putting way more money into salaries then needed, which could drown your company in hard times. Splitting the difference doesn’t actually solve anything.
I can see in the long run equal pay becoming a reality, especially within a country (same pay for California or Nebraska) because movement is so easy. But it will be long time before cost of living between the poorest matches that of the richest.
Other issues folks frequently skip over are legal complications and benefit differences between countries.
If the salary is the same, but an employee in one country has 5 weeks vacation (legally required), but another has 2 weeks, is that equal pay for equal work?
What about when one country says that, if an employee quits (not terminated), the employer must continue paying them for another 3 months anyways? Is this the same carrying cost as employment in a state with at-will employment?
Another somewhat related topic is that if you employ a single employee in some states, your company may have to pay additional taxes because you now have a “presence” in that state. Do you pay them the same, even though their “carrying cost” could be prohibitive for the business?
This is not an endorsement of any particular approach, just surfacing that things are not as cut-and-dry as they are presented.
At the very least, it's an easier case to make that salaries should be equalized across states within the US. There are a lot of complications to making it worldwide and, yes, it probably means at a minimum that total comp including benefits is equalized, not salary.
To be sure, that means you probably don't pay especially competitively in the highest cost of living states--but frankly, that's probably already the case with many companies that don't have significant offices there.
Well you said 'If the salary is the same, but an employee in one country has 5 weeks vacation (legally required), but another has 2 weeks, is that equal pay for equal work?' like it was a blocker?
If you offer everyone 5 weeks, then hire someone in a country that offers 6 weeks, do you go back and readjust an entire workforce to have 6 weeks? Can every business actually financially support that?
The point is merely that “it’s complicated” (as I comment at the end), not “this is a blocker”.
> If you pay the California rate then you will be putting way more money into salaries then needed, which could drown your company in hard times.
This doesn't follow. You can still be profitable by hiring people who add value, and paying them a consistent percentage for that value, regardless of location. Assuming of course that everyone is working remotely regardless of location, and time zones are a non-issue. (remote vs. local could have legitimate salary impacts, as well as time zone availability, due to potential increased burden on the business).
If your business's profit is based on the ability to exploit reduced living costs, then your business is at least partially focused on trading in salary differences (arbitrage?). That has it's own problems (like splitting your focus), but is probably OK as long as the margin you're making from it is lucrative. As this margin decreases you're spending more and more time trading in salaries and less time focus on your product. That's perfectly fine business wise as long as you're still making a profit, although at some point you may turn into an agency / recruiter (pivot?!?).
If however, your business's profit is based purely on providing a valuable product, you still benefit from a much wider pool of talent (thus reducing overall salaries due to supply) even without exploiting living costs. You can ignore location (assuming again time zone isn't an issue) and pay based on percentage of value. Plus you can still focus primarily on your product, instead of becoming a salary trader!
> paying them a consistent percentage for that value
Except... there's a market. People want to be paid based on a market clearing rate, not on your appraisal of value. And what is value anyway? If a company is in build mode and not generating any value is nobody paid anything?
If your value percentage does't cover market rate, then you might need to rethink your business. Market rate is derived from value percentage across all companies that seek the same talent (and also negotiating strength etc.).
If a company is in build mode, there are other creative ways to compensate (stock, etc.) or you convince investors of future value so you can afford to build it (investors) by paying market rate. An investor who just gave you millions of dollars to build something, probably doesn't want to hear about how you're going to cut costs by hiring overseas talent.
If the only way you can succeed is by exploiting location based salaries, then your business isn't just competing in it's product market, but also competing with every other business that is trying to exploit location based salaries (and there's a lot).
I'm saying is that focusing your energies on trying to get location based cheap labour might not be the best use of your time. How am I arguing that people should starve?
If you're building, and paying people in stock, then people can't trade that stock, and they can't buy food with it. So they'll go elsewhere where they get compensation they can buy food with.
Why is that a problem though? Businesses fail every day. Are you saying that paying less for 3rd world talent is going to make or break this business?
What I'm hearing is a bit contrived:
1. You only have enough cashflow to pay exploitative location based salaries.
2. You need talent (can't do it yourself).
3. You can't convince anyone to invest in it.
4. You can't attract talent with a low pay + ownership / stock deal.
If you pay "Romania rate" for Romanians then those people can easily be hired by companies which are willing to pay a few dollars extra.
I think we have begun to see this with people hired in India: if you pay "Indian rate" then you get the bottom of the barrel. If you want very good developers in India you need to pay above "Indian rate".
The market for very good developers is no longer local.
What you just said applies to SV too. Pay average you get an average SV engineer that likely isn’t particularly more effective than engineers abroad, the only advantage being physical locality.
On the other hand, companies are quite terrible at determining and utilizing actual value. So I do think there’s a lot of really good developers that aren’t making “above average” rates for whatever reason. heck, see all the engineers that go off and start companies that they then sell back to the behemoths for several multiples more - they take a pay cut in the short term because they believe they’re being undervalued wherever they are.
Very good developers in India generally don’t make $500k+ USD/year, which is the going rate for very good developers in the Bay Area. Salaries are heterogeneous within areas, but they’re still also heterogeneous across areas even when you hold talent level constant.
> ...especially within a country (same pay for California or Nebraska) because movement is so easy.
I can't entirely agree with this.
Yes, it's easier to move if your job is completely remote.
But for many people, the most significant barriers are not financial problems but mental ones.
Even though I'm single, I have few friends near my house and am satisfied with my current living environment.
It's a bit scary to move to somewhere I don't know.
And if I lived with a family, it would be much harder.
That's why the house prices are skyrocketing even though more people have started working entirely remotely.
The majority of remote workers are still living in a big town and don't plan to move to the countryside in the near future.
A lot of the more desirable countryside or smaller city prices have gone up as well.
Not that I really disagree. Especially if you're settled in there are a lot of frictions to moving--more or less depending on circumstances. Absent a need to move for a job or whatever, you're talking at least a lot of time and at least some amount of money. So if you're "OK" where you are, the default is certainly to stay put.
>That's why the house prices are skyrocketing even though more people have started working entirely remotely.
I don't disagree with the premise prior to this, but I do think a lot of people overestimate how many permanent remote workers there are, and by extension, how big their influence on the housing market is.
I don’t understand that either. Even on-site jobs don’t pay the same whether you’re in the US or Europe working for the same company - IT salaries in Europe are, even in countries like Ireland and Germany, lower than their US counterparts even though the taxes and cost of living can be higher.
Even in the US salaries are different based upon where you live - SFO or NYC vs. Kansas.
If citizenship, or lack thereof, prevents someone from moving to another location in order to work from there, then equal pay across those borders doesn't make sense. But California vs Idaho (states in the US)... they should have equal pay.
> Offering equal pay for equal work [...] Pay people for their contribution and treat all humans with equal respect.
That demand reads like a double-standard to me: people from the western world are happy to buy clothes, hardware, or food from foreign countries with low labour cost. They do that to cut down their own expenses, because the same goods would be much more expensive when produced domestically. This is the exact same mechanism at play, just with reversed roles. In one case it’s considered okay, in the other unfair. It only depends on which side of the table you sit at.
That's because it is a double standard. However, people in low labour cost countries have usually preferred to get something rather than nothing, and they held virtually no power. People in low labour cost countries would need to collectively unionise/strike/fight for their rights, in countries that don't always have the best human rights laws, much less political will to defend their citizens. And if they win? Well, they might get those big companies to leave, because some other country makes it cheaper, or if they have to pay the same as back home, why not move the business back home?
People who are capable of working remotely from low CoL areas/countries are, in contrast, more empowered. Generally better educated, often English-speaking, sometimes fairly well-connected. And it's just as easy to work for <CoL-Adjusting company #1> as it is to work for <CoL-uncaring company #1>.
We're seeing a lot of people who thoroughly enjoyed full-remote work during COVID make it a dealbreaker to work remotely now. Those people often don't even consider on-site positions. This whole CoL-adjusted thing will depend on whether a good % of those people will consider CoL-adjustments a dealbreaker or not. I suspect some might, but not enough that it'll change the balance sheet, and so we'll see larger companies who can "afford" the bureaucracy of CoL-adjustment do it, whereas other companies will use CoL-neutrality as (one of the) carrots to attract talent from CoL-adjusters.
What do you think when someone with 3 years experience gets paid more than someone with 12 years experience simply because they live in California, when the 12 year lives in Alabama?
People frequently demand equal pay for equal performance when it comes to receiving the cheque themselves, while taking advantage of unequal pay for equal performance when it comes to giving the cheque to others. The only two options I see are 1) you accept that markets are different across the globe, and sometimes you win, sometimes you lose, or 2) you want equal treatment regardless of location, but then you also have to live up to your own standards.
And just to make that clear: I don’t know or assume how the author goes about that, I’m just pointing that out as a general pattern.
This happened notably for example where the creator of Redux Dan Abramov, who is also one of the main maintainers of React and Create React App was employed by Facebook in London. Discussing salary it appeared that he was making less than your average React developer in San Francisco:
On the face of it, if they're doing the same work, it seems like there's another problem there - either the 12-year has been coasting for 9+ years or the company doesn't offer interesting opportunities for advancement to senior employees.
Of course, it's hard to generalise about situations where specifics are key.
You would never default to thinking that a surgeon, plumber, athlete, etc, with 12 years of experience may demonstrate these problems, so why would you with software engineering?
Maybe you are are just ignorant to the fact that so many companies default to actually paying remote employees double, and even more, if their location is in the right spot in the USA... for the SAME years of experience, job, and work. I personally know people who pay rent in a 1:1 in New York just for the salary, but actually live and work from South America.
> You would never default to thinking that a surgeon, plumber, athlete, etc, with 12 years of experience may demonstrate these problems, so why would you with software engineering?
Thanks for telling me what I would think, but honestly it would be no different for any of those professions. If you're still doing exactly the same job 9 years later, the real problem is elsewhere.
And CoL-adjusted salaries kind of make sense and have always seemed fair to me when I've been offered one. If people are scamming the system, that would be something for the company to worry about, no?
I guess a better question would be: what would be fairer?
Sorry, I should have said "I presume you would never...". Honestly didn't mean it to come off that way.
> it would be no different for any of those professions
Do you want a surgeon with 12 years of experience or 3?
The issue at hand, unequal pay, has nothing to with experience in the first place, so making up an imaginary scenario where the experienced employee is a slacker is a strawman fallacy anyway. The point is that if someone from a low pay area moves 50 miles in one direction they could suddenly be worth 2-3x as much to the company?
Additionally, most tech companies don't actually pay based on cost of living, they pay based off of cost of the local competition. There are generally* 3 pay tiers in the United States; Hawaii is a Tier 3 state (lowest pay) despite being one of the most expensive places to live. The most expensive zip code in the USA is in Florida, but again: it's a Tier 3.
Anything above the cost of living is money the employee can choose to spend on quality-of-life improvements that are generally the same price no matter where in the USA you live (think investments, tuition, cars, boats, shopping, etc). The Tier 1 employee gets more money for those fixed-price items than the Tier 3.
I'm just saying it doesn't make sense; it's an artificial constraint made even worse when companies exploit the timezones of an employee because they desire a globally diverse workforce.
* Note: I only have experience with two businesses that collect salaries from mid to large (100+ employees) business subscribers in exchange for information about what others in their sector pay their own employees on average. It's a legal form of wage fixing.
I would want the surgeon of 12 years, on the proviso that I imagine (having no idea) that a surgeon by then would be some sort of senior surgeon. If they are still a surgeon-under-supervision (or whatever the surgeon's equivalent is) I would take my chances with the 3 year rookie. There's obviously something going on that the veteran still has 3 year status despite being 12 years on the tools.
I'm sorry you think this is a strawman, but I'm just addressing the scenario you originally posed.
I still can't see what you think would be fairer - the labour market is always going to be subject to demand and supply dynamics. I believe a fair minimum wage should be established (and seriously enforced) for every job, but if employers want to pay above that to attract what they perceive is a better quality of applicant I don't have a problem.
Where it gets admittedly weird is comparing two otherwise equal employees, fully remote - why the company cares where they live is a mystery for them to answer, but considering that wages aren't really a zero sum game, isn't this a case of some employees earning more as much as it is of some earning less (being that all these jobs are above minimum wage, so the question of what a SWE, for example is "worth" is even more at the mercy of the market)?
Not OP, but isn’t that the reality of labour markets? The alternative is that everyone in non-SF areas of the world is competing for SF salary remote positions.
It’s even worse at established tech giants like FAANG, where everyone working at anywhere other than SF would optimally declare fully remote for the free salary increase
>everyone in non-SF areas of the world is competing for SF salary remote positions
They're mostly not. It's really not a race to the top. If you can get a job with FB and get a Bay Area salary from them, most companies will effectively tell you to go for it. (So they are competing in a sense. But many are opting out.)
It’s not even about lying, you can think you’ve done amazing things and just not be in sync with what the interviewer’s expectations. “Led a project” can mean anything from actually being critical to the project’s success to pushing some papers around so other people could do the work.
Sure, but for sake of conversation here it's a decent metric. Another way to frame it: one was recently promoted to senior, the other is an engineering lead who has been managing teams of seniors for 7 tears.
Absolutely agree! What I've seen as a good compromise for startups is to pay generously (~30-40%) above the best local rates but of course below US/SV rates. You can be confident that you're earning more than you could in basically any local job around you, and the company is still better off than hiring only SV (or US) folks.
What I see in my experience is that most fully remote companies only want to pay you the local rate - which doesn't make a lot of sense. Some are willing to pay more, and only a few advertise paying equally regardless of location.
It's understandable because it just doesn't make much economical sense.
Obviously, I'd switch jobs any day for another 30-40% pay increase, and I'm curious how the last approach is going to get adopted by fully remote companies.
As (fully) remote jobs become more prevalent, that also pushes up local rates, though, and local jobs usually offer some better benefits because you're not a contractor. It's an interesting market!
I'm really torn on this issue. On the hand, it seems to make sense to pay people based on the value they deliver for the company, not where they live while delivering it. On the other hand, the reality is that some regions have higher costs of living than others. Somehow, the salary needs to take that into account.
Imagine if all tech companies went fully remote and kept paying about the same salary level as they do now. Employees moving to lower income regions would no doubt upheaval the local economy (e.g., housing).
But then again, this would probably regulate itself in the longer run.
Finally, why would only remote companies be upheld to this standard?
As someone that lives in a HCOL area (and generally likes it) I think I agree.
If I reduced my “quality of life” by eating out less and saving money, my company’s not going to pay me any less. Why should they start paying me less if I reduce my QoL by moving to somewhere I’d enjoy living in less that’s cheaper.
Sure. But if you're working for a non-remote company, you need to live in the area where the company offices are. In that case, your expenses naturally go up.
There is potentially also some premium companies should be willing to pay to employ people who live in locations that have reliable infrastructure, strong legal institutions, and stable government.
The benefits/vacation point is a poor one. So much of that aspect of compensation is driven by local laws so as to be pointless. In fact, it’s a major reason why even remote friendly companies won’t hire internationally.
Heck imagine a company founded in the UK committing to this. How would they deal with providing health insurance to their first employee in the US? Not offer it to US based employees?
> Let’s say you can both afford to save 30% of your salary and you go on to invest it in, say, the S&P500. Then after your career you’ll go and retire in Spain. Guess who’ll afford a better lifestyle? That’s right, the US citizen. Location based pay simply exploits employees of weaker economic regions. It’s common in our world but that doesn’t make it right.
I’m working at Google and moving back to Spain where I’m from where I will see my salary reduced by 50%. I love my team and my work but this is precisely the reason that will make me quit in favor of an American company that doesn’t adjust salary to region.
Plenty of non-FAANG American companies that would pay what I was being paid while based in Germany.
There isn’t an engineering office in Spain. Just a small one for a very specific product acquired by Google.
Truth be told if Google started a proper office in Spain they’d be able to find plenty of good candidates at the reduced 50% salary. Google is still paying way above local market rate.
In my case the reason why I wouldn’t stay is the psychological factor of seeing my salary cut in half and feeling the need to optimize what I earn. I already have a friend here working remotely for what I saw described here on HN once as a second tier American tech company and with less experience he’s making more than I will make once I move. I have researched what other companies pay and I could definitely get my German salary back.
I’m not saying I deserve those salaries or that Google is not being fair. But just as a multi-billion dollar company is optimizing their bottom line with the salaries they pay, I’m also obliged to do the same.
They could; and Google could then close down their offices in Spain and save that money. Maybe it'd be worth it, maybe it wouldn't; I don't know Google's financials to make the decision.
I'm an Engineering Manager at Stacker (YC S20) and heavily involved in hiring (which, yes, we are by the way :-). We're fully remote and I think we do pretty well on this test as written, which is nice to see.
I was just discussing with someone the other day how exciting it is to be involved in this (historically) brand new model of organising around work, discovering and navigating all the advantages and challenges it presents.
Like perhaps the actual Joel test I think this list is broadly directionally right, if I would say a little naive (or more generously, low in nuance) in the extremes where the interesting details and subtleties always are - but I love that the author has had a good run at making this, a decent list, and the first person I've seen attempt to do so. I look forward to us as an industry iterating forwards from here on what the best practices are and seeing how the fully remote model evolves over the next decade or so. Exciting times!
Reasonable list but I do take issue with #5. Synchronous communication is incredibly important in any working environment. Else you end up waiting an inordinate amount of time getting simple answers to simple questions. Not to mention the social aspect of simply having a conversation with a co worker.
we have tools that easily enable this in a remote work environment. I’d suggest that this be re-tooled to be something more like “does the company optimize for focus time/flow time during the workday”
That's not universally true, and by subscribing to it you limit the flexibility possible for remote work to similar 9-5 constraints regular work has. In many businesses, remote work doesn't have to be regular work but at home, and for many of us who have been doing it since before the pandemic that is actually the big draw.
Asynchronous by default means everyone is free to work when they are most productive and capable, and it really doesn't matter so long as the work gets done on time.
Funnily enough, remote work for everyone has meant some remote positions have actually gotten worse, as the line between remote lifestyle worker and regulr employee working from home has been blurred.
You're probably right, at this point the Joel Test should really be the bare minimum if a company is serious about a good software development experience, whereas being asynchronous is a bit extra, and a huge shift for most businesses.
I don't read the screed as being against synchronous communication; just against synchronous communication being the default.
> Else you end up waiting an inordinate amount of time getting simple answers to simple questions
Well, this is the problem. Expecting an immediate response kills deep focus. You should have to wait for a response, for anything that isn't an emergency. Then the question becomes, what's an appropriate amount of time to wait for a response? And how can you a) measure the number of async conversations where ping pong resulted in conversations taking much more time than expected, and b) come up with blameless / systematic responses (e.g. internal wiki maintenance) to reduce that measure over time?
> Well, this is the problem. Expecting an immediate response kills deep focus. You should have to wait for a response, for anything that isn't an emergency.
This is a ridiculous assertion.
"Hey, I think we should change feature Y to do X instead, but this will have an affect on your feature. Can you absorb this into your workstream? Btw I'm writing this code right now and want to push a PR today"
... wait 5 hours because asynchronous ...
"Mmm, maybe. Could we make this slight tweak that will still get you what you want but be easier on me?"
... wait 24 hours because now it's sleeping time ..
etc.
Real-time conversations are extremely valuable. Let's not pretend like they're not.
Yes, waiting five hours to then have a synchronous conversation is one way to handle this. Another way is to not assign feature work asynchronously, but to have a synchronous meeting where the feature is assigned, to try and ensure that people are aligned before they go off and work on their own.
> Real-time conversations are extremely valuable.
Of course they are. It's the ability to have a real-time conversation on demand, with no consideration for the counter-party's focus, that is ruinous.
> “does the company optimize for focus time/flow time during the workday”
I like this rephrase too.
I've recently joined a new team, and having several synced meetings helped me onboard quickly.
I hate if we need to have meetings or synced work often in the future.
I don't want to be interrupted when I focus, so I like communication should be asynchronous by default.
Still, depending on the situation of team members and the project phase, synchronous communication is sometimes much more productive than completely asynchronous work.
Functional teams should be able to choose better communication each time. (I know some people like synced communication too much, and it's often more problem, though...)
I think #8 (weekly syncs) illustrates that even the author doesn't believe in a 100% asynchronous world either. I value a good synchronous discussion when its possible. But between time zone differences and being flexible with people's varying home situations during a pandemic it's an exception rather than the rule.
Isn’t it kinda weird to attribute Joel’s name to this even though he has nothing to do with it?
I mean sure, they are both lists of ten questions for assessing a job’s suitability, but is “Joel test” common enough (first I’ve heard of it but :shrug:) that’s it’s more a noun for the list than being seen as having to do with Joel?
For point #1, perhaps neither scenario is "equitable". "Equal pay" may sound equitable given the horribly biased example given, but look at the converse case:
> You have two people doing the same job but if you live in Romania and your colleague lives in the US at
a company that pays both equally
> Then after your career you’ll go and retire in Spain. Guess who’ll afford a better lifestyle?
That's right - You, the Romanian citizen.
Since your cost of living is 42.4% cheaper than your US colleague, you'll have much more disposable income to invest over the course of your career.
Let's say you both make an after-tax income of $60,000 USD. If your colleague pays $40,000 a year for rent/food/transportation/clothing/staples and another $5,000 for (optional) non-essentials, then they'll have $15,000 to invest.
You will spend roughly $23,000 on the same essentials and another $3,000 on non-essentials, leaving you $34,000 to invest annually.
If you both invest in the S&P500, and it continues to return around 10% annually, then you both move to Spain to retire after 30 number of years, you'll have just over $5.5 million USD compared to your US colleague's ~ $2.5million.
> You have two people doing the same job but if you live in Romania and your colleague lives in the US at Gitlab you could earn a lot less.
> But that’s treating you, a human being, like an asset.
Funny how that objectifies people if you approach it from the market side, but if you start from the human being side, it turns out equal payment doesn't always make sense.
How? Take a human being. One with abilities and needs - family, health, freedom, etc. They offer their abilities to you, the employer, because they need the ability to fulfill their needs. But the amount of resources to get there depend on their physical location: more expensive countries demand more money to fulfill the same needs. Therefore, paying the same would favor the needs of some over others.
If you consider that most humans have some need for fairness and justice, you can't pay equal rates for the same effort. Best you can do is equitable.
It's not the same as paying local market rates, but it precludes paying equally as a solution to objectification.
Hum... Fully, total remote, hiring included is a bit utopia IMO, it can be done practically of course but demand a society that's not there and is in contrast with "being together"...
IMVHO remote work, where possible (around 30% of jobs in the western world probably), should still be inside country borders in the same way multi-national company subdivide themselves by country because local laws can be too incompatible to manage a unique entity. Similarly for salary: in theory we must get paid for what we do so regardless of where we are in, but in practice cost of living must be taken into account because the same amount of money in math terms have not the same value everywhere and taking cost of living into account is simply too complex to be solved. The world is not a global world where anywhere we are things are equal, there are of course similarities, in the end humans are similar, but definitely not enough.
"local" remote work is perfectly doable with little travel and common profit, world-scale remote work is potentially doable but not in the present world, also fully remote work is hardly possible IMO/IME...
My honest opinion is that there is no "test" possible anyway, just negotiation not really different than any "non remote" job.
In regards to the first point, equal pay for equal work, last week I had a place drop the base salary from 260 to 135 because I'm in Arkansas. The whole state apparently has the same cost of living, and it's a fraction of the stated range for NY/CA. Ridiculous.
Seems like all major companies are offering location adjusted pay. Is there anyway to find companies who don't? Also I'm in Canada yet getting like 50% after currency conversion edit I should say Vancouver Canada so property prices are higher than most of the US
These are good questions. But I would replace the 3 pillars with: Reciprocity/Fairness, Empathy and Communication, whereby the first two are known as the pillars of good moral. Effective communication enable and keep all the three coherent.
I would like to add more criteria for the effective communication, though. Most of the time you can do with asynchronous communication but sometimes synchronous communication is the only effective way to solve a problem. The composition of the teams and their time zones should take that into account.
I also don't mind an in-person interview if it's the final round for selected candidates.
> How do you balance the difference in national labour right laws and public holidays? The easiest is to simply give all employees enough vacation to decide themselves which holidays they want to celebrate and for how long. Everything else is an HR policy nightmare and an interference of the company in your personal life.
This is probably illegal in many countries. I assume in many places you can't just give extra vacation and use that instead of giving holidays.
Given that most businesses survive on the margin between business value vs employee pay, the notion of equal pay for equal work certainly sounds good, but will inevitably result either in more selectivity or a race to the bottom.
This is what a union is for. People who think companies can't afford this are
1. Unaware of how much they skim at the top
2. Unaware of how many companies exist that don't deserve to.
> Is the company communication designed to be asynchronous?
No. There will always be some boomer who refuses to use Slack messages and needs handholding on Zoom video for the most minor discussions. Character traits include emotional manipulation, not invented here syndrome, poor time management.
They've been struggling to deploy a simple microservice for multiple financial quarters but will snap and call you slow when their code review process stalls.
It's not easy to teach the concept of decoupling as a problem solving strategy. They've suffered the yoke of enterprise programming for so long, that they feel naked without iron chafing at the neck.
I'll agree with you here; I've got plenty of anecdata of the "younger" people choosing synchronous methods (calls, meetings, one-on-ones, etc.) vs "older" people (perhaps with families or other time-taking things) prefer asynchronicity.
I don't think it's necessarily an age thing, more of a work methodology thing. Same as how some people cannot work remotely at all and will be miserable and unproductive doing so, where others thrive on remote and can't see themselves at the office. We should control for all of that in companies, and try to match people of the same persuasion. It may lead to far less attrition.
I generally agree with all the points (minus the obvious caveats), but I'd prefer if we'd push back against the whole "happy work family" mantra. Some of us don't mind being seen as "just that guy doing the job from a distance", but do mind other people trying to make us more than that. For me, part of remote work is to get away from continuous pushing towards more socialization. Whenever someone says 'encourage', it often seems to loop around to a negative if you don't want to participate.