3 ms·
There are no right or wrong answers to this. It can be pro-rated for the cost of living, pro-rated to the cost of market (GitLab approach) or just a standard ra
by baristaGeek 6y ago
There are no right or wrong answers to this. It can be pro-rated for the cost of living, pro-rated to the cost of market (GitLab approach) or just a standard rate that's below SF market.
You can pay $60k to a senior engineer in an emerging economy and he/she will be super happy about it because that is way above market in his/her country. Regardless of which method you used to get to that number.
- bushido 6y agoThanks for that, led me to discover Gitlab's compensation page! Gitlab's documentation on this topic is fantastic: https://about.gitlab.com/handbook/total-rewards/compensation/ https://about.gitlab.com/handbook/total-rewards/compensation... Admittedly, I hadn't considered the golden handcuff angle which seems very relevant!
- khannavid 6y agoIt's not as well-documented as Gitlab but you can check Buffer too: https://buffer.com/salary/senior-data-architect-2/average/ https://buffer.com/salary/senior-data-architect-2/average/ I think the most thoughtful/fair approach is to use more than one factor: role, years of experience, costs of living (having kids? big or small city? etc.) and loyalty (how many years in our company?) are the most important factors that come to my mind...