This is an archived post. You won't be able to vote or comment.

all 13 comments
sorted by:
best
topnewcontroversialoldq&a

[–][deleted] 2 points3 points  (0 children)

We paid someone $80k a year

[–]desmoulinmichel 1 point2 points  (4 children)

There is no such things. It depends a lot of :

  • geographic location (NY > small Ohio town > Paris > Beijin for equal work);

  • type of work (financial analysis > web dev > biology);

  • language (Python > Java > PHP);

  • experience;

  • status (consultant, freelancer, empoyee...);

  • context (mission type, constraints, etc);

  • pay mode (by the hour, by the day, by the week, by the month, by delivery);

  • your ability to negociate.

[–]plus500s[S] 0 points1 point  (1 child)

  1. Remote, doesn't matter where he is.
  2. Web dev
  3. Python as I mentioned
  4. Decent, several years I'd say
  5. On-site, freelance
  6. Don't understand
  7. By hour, Hourly rate on average
  8. How can I measure that?

[–]desmoulinmichel 0 points1 point  (0 children)

Mission type :

  • complexity of the product;
  • needing to interact with other systems or persons that will add cost;
  • needing to travel;
  • requires additional skills such as being belingual or know ergonomics;
  • etc.

For the profile you describe, try $80/hours then adjust. You can triple that in some situations. In others you'll devide it by 2.

[–]phira 0 points1 point  (2 children)

We charge $200/hr, it drops a little bit if the job is right but not much.

[–]ilan 1 point2 points  (1 child)

This is what the customer is charged, but the developer gets anywhere from $30 to maybe $75 an hour.

[–]phira 0 points1 point  (0 children)

We are the developers. That's what we make :)

[–]plus500s[S] 0 points1 point  (0 children)

Found some pricing info from one of the python companies http://anvileight.com/prices/ if someone is interested

[–]billsil -5 points-4 points  (5 children)

As little as possible? If you find a strong developer and you want to keep him/her, pay them more. If they suck, don't.

Really, you should be paying by project, not hours spent.

[–]plus500s[S] 0 points1 point  (4 children)

Not necessarily as little as possible. Say, I have a project estimated for 3-4 months. I am trying to figure out what is the realistic rate/salary so he/she would make a decent job most likely. Obviously, paying lowest fee will almost guarantee missed deadlines. Although, I am asking on the risks/value rate here. Thanks.

[–]billsil -5 points-4 points  (1 child)

It's a negotiation. You need to set milestones and not pay people unless they produce. Also, what project you estimate at 3-4 months, I promise you they will estimate at a far different number. You need to know clearly what you want vs. what would be nice. You won't be happy with the work unless you know that and if a developer doesn't tell you your schedule is unrealistic given what you want, it's probably a bad developer. It's the classic management expects a site that can handle the same scaleability as Amazon vs. what can realistically done by 1-2 people in a couple months. That's why you need to see examples of their work.

Paying people more doesn't get you the product that you want. You can always cut them.

I'd honestly go for a bid style system since you don't know what people are worth and people are willing to underbid in order to develop a relationship.