111–120 of 192 posts
Earlier quoted context omitted.
How much is your/the "Bay Area Rate"? Thinking about internationalization of my consultancy and have no real insight into hourly rates for devs in the US. Don't want to leave too much money on the table because I haven't done my research.
EDIT: This comment was incorrect and I do not wish for more down votes. ORIGINAL: I believe it should be about 100 USD/hour for skilled consultant, but maybe someone with more experience can correct that.
Earlier quoted context omitted.
have you thought about a career in software development ?
My response may sound stupid, but the question asked how much the increase in percentage was... So I just answered the question.
Well done. Personally, as a remote developer, I always make a point of billing at my "Bay Area Rate", even though I've never lived there. There was a point, early in my guy-on-the-beach-with-a-laptop era where I would cut my bill rate in half while working from the beach with a laptop. Clients were happy about that, and it more than paid for beers and thatch huts. Then one time I tried not cutting my bill rate in hal…
Basecamp is selling all over the world. What should their salary level be like? Bay Area because that’s where a lot of the larger tech companies are situated? Washington State (Microsoft, Amazon)? Copenhagen (where one founder, DHH is from)? Sudney where one major competitor, Jira, is from? I’d say whatever the market is that they hire in. If you wanna pay above market rate, by all means do that. If you can attract e…
Did anyone suggest they should?
Earlier quoted context omitted.
No, it's a market-clearing rate like everything else. It is for the work and only for the work. Otherwise you get the bad old days where unmarried employees were paid less than married ones, and so on.
But a married programmer might only be willing to work for a higher salary, so you need to pay them more to hire them.
Earlier quoted context omitted.
No way on this earth, $150,000 is anywhere near normal in the Bay Area, let alone in other less expensive metros. Most people are absolutely not making that much money writing code. People have serious tunnel vision on HN.
May want to browse the countless compensation discussions in the app Blind. Lots of Bay Area offer info there. Note that salary is a misnomer. The term now is "total compensation" which has a significant RSU portion.
Every time I see a post from the Basecamp guys and how well they treat their team, it's more depressing than uplifting - just because I know I'll never be good enough to work there, and that they're so unique that no other employer will ever do the same.
Earlier quoted context omitted.
I’m not implying everyone is the best talent and making 150k, quite the opposite. But I definitely don’t agreee the peak is below 150k...
I mean ryandrake above just stated glassdoor and salary.com showing $110,000 as the medium. So below $150k.
Earlier quoted context omitted.
I’m not implying everyone is the best talent and making 150k, quite the opposite. But I definitely don’t agreee the peak is below 150k...
I mean ryandrake above just stated glassdoor and salary.com showing $110,000 as the medium. So below $150k.
Well done. Personally, as a remote developer, I always make a point of billing at my "Bay Area Rate", even though I've never lived there. There was a point, early in my guy-on-the-beach-with-a-laptop era where I would cut my bill rate in half while working from the beach with a laptop. Clients were happy about that, and it more than paid for beers and thatch huts. Then one time I tried not cutting my bill rate in hal…
> As the article so nicely points put, the work you're doing is exactly the same regardless of where you do it from. Charge accordingly.
First of all, a remote employee is not worth the same as one in the office. For 2 engineers of the same capacity, any employer or coworker would rather have the engineer physically near than physically afar. How much that discount is extremely hard to guess, but there should be one in the general case.
Also, being hired as a remote engineer from the get go is not the same commitment as being hired to be in the office. There is no personal or professional relationship yet. This means that being hired as a remote worker, you will generally be assigned remote work, and if they want collaborative, product and team roles, will hire someone to be in the office. The processes of hiring and working relationship are different.
Now, to my personal experiences: I worked remotely my first few years, and then as an in-office employee for a couple of years to a SF startup. After that, I left the US and worked remotely for the same company for 2 years. There was a minimal adjustment to salary: and then I had the incentive to study the finances of what was going on.
The company paid less payroll taxes, and I did not receive any benefits: no 401k matching, no free food, no snacking, no coffee expenditures, etc. The benefits lost my have compensated a chunk of the remote-ness productivity loss in the long run. But there was a cost to productivty and I could compare it solidly between my two periods: it took longer cycles to get some projects finished, and issues of importance sometimes had time-zone differences that made them more inconvenient to resolve.
But then I also saw why talk about cost of living. Working in the same company, I had seldom talked about salary with co-workers (and my personal policy is to disclose mine immediately, even if they dont disclose theirs). But after turning remote I got asked about my salary by a considerable amount of people, even from ex-coworkers! I dont think people have a right to be upset about it, but they do feel upset about such a thing. They perceive it unfair, because the costs are there for them, and maybe their job or their manager wont allow them to be remote.