4 ms·

How much money can one make in an hour as a Turk? Has anyone tried it? I used to click links and made a few dollars back in the day...

by cevn 7y ago

bookofjoe 7y ago
97 cents/hour: https://www.nytimes.com/interactive/2019/11/15/nyregion/amazon-mechanical-turk.html?action=click&module=Top%20Stories&pgtype=Homepage https://www.nytimes.com/interactive/2019/11/15/nyregion/amaz...
- psychstudio 7y ago
  That article is a bit off the mark. Here's a rebuttal: https://blog.turkerview.com/writer-who-never-learned-to-drive-works-for-uber/ https://blog.turkerview.com/writer-who-never-learned-to-driv...
- galfarragem 7y ago
  That value is accurate. Ocasionally there are some jobs that pay $2 for 10 minutes but they are the exception. Most jobs pay from 5 to 10 cents for 5 minutes (when done properly). Unless you live in a country with extremely low living costs, mturk is completely worthless as a job.
seangrogg 7y ago
As someone that was building a platform that took advantage of MTurk (among other things) this varies wildly. The platform project I worked on was structured in such a way that, if you were able to receive sufficient tasks from it, you should hypothetically make ~$9 per hour (USD for clarification). There are a lot of assumptions even there, though: 1) The $9/hour figure is based on making ~$0.15 per minute. This means if a survey on the platform took 5 minutes it should pay out ~$0.75. But then there's the question of who sets that time, and it's ultimately the requester. If they aim too low (or, conversely, high) this skews the accuracy. And given they're the ones paying it's in their interest to assume low. We were fond of using calibration-like surveys that would inform roughly how long a survey took before launching more to reduce this bias. 2) Even if you got (1) right, the $9/h figure assumes you're able to do those back-to-back with zero delay. That's damn near impossible without smart tools. There's often a multi-second (if not multi-minute) delay between surveys and all of those add up. Although we did generate some surveys long enough to meet the $9/h figure (and Turkers did get paid for them accordingly) most of the time we saw many small surveys where the cost of latency adds up. Ultimately, I don't think this was a problem of our approach so much as it was just a reality for any HIT or similar "microtask". 3) Even if you could have a perfect (1) and (2), another reality is that there is a finite volume of tasks being requested. Assuming an average of 5 minute HITs we'd need to be producing 12 units of work for an individual Turker per hour. That's a lot of outgoing work and really depends on what you're looking to attain. As a platform we couldn't really force more work to come out of it, so there was a natural limit. 4) Lastly, even if you managed (1) (2) and (3), it assumes everyone was actually getting all of their work from us. Fact of the matter is that there are a lot of companies that pay differently. Perhaps more, perhaps less, perhaps keyed on other more meaningful metrics than $/hour. But that all changes the calculus. 5) Lastly, even if you somehow managed everything, there's still the effect of locale. The value of $9USD/h varies wildly depending on the context. For this reason, it wasn't uncommon to see many requests coming from regions in the world where the dollar is comparatively strong. Ultimately, it's really hard to say how much you could make in an hour as a Turker just because of the inherently volatile nature of the work. In instances where you do make an outsized amount of money it's more likely that you were filling an urgent need at that time. If I were to guess, chances are you'd see more work closer to the middle/end of business accounting periods as that's when large-n research would likely answer important questions, with higher pay likely towards the end to fulfill any last-minute research gaps.
bluedays 7y ago
Hourly is a pretty narrow view of it. It depends on a lot of things. Often there's no point in working on the tasks as they are underpaid. Some projects can be $10 an hour, some can be $20 an hour. Also knowing how to program in javascript can significantly boost your earnings.

How much money can one make in an hour as a Turk? Has anyone tried it? I used to click links and made a few dollars back in the day...

by cevn 7y ago

How much money can one make in an hour as a Turk? Has anyone tried it? I used to click links and made a few dollars back in the day...

bookofjoe 7y ago

97 cents/hour: https://www.nytimes.com/interactive/2019/11/15/nyregion/amazon-mechanical-turk.html?action=click&module=Top%20Stories&pgtype=Homepage https://www.nytimes.com/interactive/2019/11/15/nyregion/amaz...

psychstudio 7y ago
That article is a bit off the mark. Here's a rebuttal: https://blog.turkerview.com/writer-who-never-learned-to-drive-works-for-uber/ https://blog.turkerview.com/writer-who-never-learned-to-driv...
galfarragem 7y ago
That value is accurate. Ocasionally there are some jobs that pay $2 for 10 minutes but they are the exception. Most jobs pay from 5 to 10 cents for 5 minutes (when done properly). Unless you live in a country with extremely low living costs, mturk is completely worthless as a job.

seangrogg 7y ago

As someone that was building a platform that took advantage of MTurk (among other things) this varies wildly. The platform project I worked on was structured in such a way that, if you were able to receive sufficient tasks from it, you should hypothetically make ~$9 per hour (USD for clarification). There are a lot of assumptions even there, though: 1) The $9/hour figure is based on making ~$0.15 per minute. This means if a survey on the platform took 5 minutes it should pay out ~$0.75. But then there's the question of who sets that time, and it's ultimately the requester. If they aim too low (or, conversely, high) this skews the accuracy. And given they're the ones paying it's in their interest to assume low. We were fond of using calibration-like surveys that would inform roughly how long a survey took before launching more to reduce this bias. 2) Even if you got (1) right, the $9/h figure assumes you're able to do those back-to-back with zero delay. That's damn near impossible without smart tools. There's often a multi-second (if not multi-minute) delay between surveys and all of those add up. Although we did generate some surveys long enough to meet the $9/h figure (and Turkers did get paid for them accordingly) most of the time we saw many small surveys where the cost of latency adds up. Ultimately, I don't think this was a problem of our approach so much as it was just a reality for any HIT or similar "microtask". 3) Even if you could have a perfect (1) and (2), another reality is that there is a finite volume of tasks being requested. Assuming an average of 5 minute HITs we'd need to be producing 12 units of work for an individual Turker per hour. That's a lot of outgoing work and really depends on what you're looking to attain. As a platform we couldn't really force more work to come out of it, so there was a natural limit. 4) Lastly, even if you managed (1) (2) and (3), it assumes everyone was actually getting all of their work from us. Fact of the matter is that there are a lot of companies that pay differently. Perhaps more, perhaps less, perhaps keyed on other more meaningful metrics than $/hour. But that all changes the calculus. 5) Lastly, even if you somehow managed everything, there's still the effect of locale. The value of $9USD/h varies wildly depending on the context. For this reason, it wasn't uncommon to see many requests coming from regions in the world where the dollar is comparatively strong. Ultimately, it's really hard to say how much you could make in an hour as a Turker just because of the inherently volatile nature of the work. In instances where you do make an outsized amount of money it's more likely that you were filling an urgent need at that time. If I were to guess, chances are you'd see more work closer to the middle/end of business accounting periods as that's when large-n research would likely answer important questions, with higher pay likely towards the end to fulfill any last-minute research gaps.

bluedays 7y ago

Hourly is a pretty narrow view of it. It depends on a lot of things. Often there's no point in working on the tasks as they are underpaid. Some projects can be $10 an hour, some can be $20 an hour. Also knowing how to program in javascript can significantly boost your earnings.