Hacker Newsnew | past | comments | ask | show | jobs | submit | clmntrg's commentslogin

It's not about leveraging the lower cost of poorer countries that we do that, as we actually have most of our team living in high cost of life ones. Part of the explanation why we do it this way can be found here, https://slite.com/blog/lets-pay-our-remote-employees-fairly-..., happy to continue the discussion if you want to!


I read the article your justification to pay people leaving in poorer countries less if because it raises costs?

> I'm personally afraid we're going to replicate the San Francisco phenomenon over and over, to cities elsewhere in the world.

What do you mean by this? Your company paying 10 guys US market rates won't raise any city's rent prices. Rent prices are impacted by supply and demand. So you are afraid if you pay your employees San Francisco rates, their city will become San Fransisco? I don't understand the fear of some engineer in Argentina making 200k USD, wouldn't that make your company very desirable to work for over there?

All the reasons you give in the article seems like excuses to no pay people certain rate. And about paying everyone SF rates, it does raises costs, duh, but it also raises the amount and quality of talent you can reach internationally. It feels you are seeking validation on a compensation scheme that's at least equal that most corporations and bring nothing new to plate, nor is any more fair than what everyone else is doing. That's why anyone can see why Basecamp holds the moral high ground on this topic.


>It feels you are seeking validation on a compensation scheme that's at least equal that most corporations and bring nothing new to plate, nor is any more fair than what everyone else is doing.

I think this is a great point, because exec's are not included in this pricing calculator. I think they totally should be.

From the article and some other links I think the company is doing a great marketing campaign during a time where salaries and pay is a hot topic.

I do not think salaries should be paid based on location, especially if the team is remote. Everyone is in the room (zoom room) and they should be paid on their skillset and value they bring to the team. Using location allows the company to focus on cost. This points to the fact they will be located in LOW cost of living locations, using fair calculator is the justification for lower salaries. Which links back to

> If we start giving crazy high US salaries by default in remote, I'm personally afraid we're going to replicate the San Francisco phenomenon over and over, to cities elsewhere in the world.

We should be giving employees higher salary based on the value they bring to the company. If the engineer from Argentina is more productive and bringing more value to the team but they are paid much lower than a team member in the US, this will cause internal conflict but the only person gaining is the company from the margin they will make from that employees contribution to their overall cost.


Yeah, OP seems to not understand why San Fransisco(and tech hubs in general) real state is hot. I'm line with you, this is just a marketing piece, with low effort, made up excuses for why not paying people in 3rd world countries fairly.


I read this, and it is a good argument but should this also apply to founders?

If you make $50m say in an exit will you take $50m minus what you sacrificed in salary terms for being a founder and give it away. Lets say $49m you give away.

Then it would be fair because you have then earned the same as the location based earnings the employees get.

Also, it makes sense that in a company that rewards employees financially for living in high COL locations, that Goodharts law applies and you get most employees living in high COL where possibly they make money through real estate acquisition made possible by the higher salaries etc. as well as nice disposable income for investment / 401k etc.


That's a good point, I'm glad you're raising it.

Indeed, we have a fair salary model but not a fair pricing (by country). But we have a fair billing policy (https://help.slite.com/en/articles/2008029-what-is-slite-s-f...) and most of our customers are global actors that earn money from high cost of living countries.


Hey, thanks for commenting--

> I think that's wrong, and just a way for the company to save as much money as possible. A fair salary should be a % of the $ value you create minus local taxes and expenses needed for your position(equipment, software, training...). TBH with you, 95% of our employees are paid on an index that above France (our HQ). So I'm not sure we pay less in the end.

> For example personally I don't plan in staying long in my current city/country. But if I accepted local salaries I would never be able to save enough to move comfortably. We aim at the 75th percentile of each market (based on an engineer role). I'm sure this would give you enough to move comfortably

> Also local purchasing power usually doesn't apply to objects(electronics, cars...) We index purchasing power on the monthly rent, which accounts for 30-60% of wage (depending on countries/cities).

I understand your opinions, and I don't really want to change that-- but I deeply appreciate you took the time to read and comment. Have a great day!


Please read again, it doesn't work for everyone. The TLDR from our own experience is that it's hard to make it work for juniors.


Remote workers looking for a job, or managers in a remote company.

While working at a company that builds an alternative to meetings, calls and office-friendly practices, I had lots of questions about "would this work for me?". Or people were saying "async seems promising, but I'm sure it's only for developers". This is untrue.

I take the design is not your taste, I'll pass this feedback to the team. Thanks Dimgl


Hey, thanks for taking the time to leave feedback on the post – harsh but I'll take it. I wanted to figure out a way to TLDR a blog piece we wrote about what profiles fit best in async environments, from our won experience. Seems like the format doesn't work well, I'll pass that to the team. Have a great day


The product is so early-stage that's a big commitment to be a user. But you're right. I'll try 1:1 outreach for users, definitely. Thanks!


If anyone is interested in the Beta → slite.typeform.com/discussions


Thanks for taking the time to reply!

Teams we want to recruit: - 10+ employees - ideally software/service companies - early adopters with tech profiles - Geography doesn't really matter since they should be remote/async-first

On 1:1 outreach I thought about it, but I don't feel comfortable with that. That's a good call still. Have you ever had success with that?


> On 1:1 outreach I thought about it, but I don't feel comfortable with that.

To be fair— recruiting users is a sales/marketing process. There may be someone on your team more naturally disposed to this task.

Still — it’s solid advice to go out and talk to your customers.

Good food for thought from PG >

http://paulgraham.com/ds.html?viewfullsite=1


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: