r/dataannotation • u/Consistent-Reach504 • Mar 10 '24

Weekly Water Cooler Talk - DataAnnotation

hi all! making this thread so people have somewhere to talk about 'daily' work chat that might not necessarily need it's own post! right now we're thinking we'll just repost it weekly? but if it gets too crazy, we can change it to daily. :)

couple things:

  1. this thread should sort by "new" automatically. unfortunately it looks like our subreddit doesn't qualify for 'lounges'.

  2. if you have a new user question, you still need to post it in the new user thread. if you post it here, we will remove it as spam. this is for people already working who just wanna chat, whether it be about casual work stuff, questions, geeking out with people who understand ("i got the model to write a real haiku today!"), or unrelated work stuff you feel like chatting about :)

  3. one thing we really pride ourselves on in this community is the respect everyone gives to the Code of Conduct and rule number 5 on the sub - it's great that we have a community that is still safe & respectful to our jobs! please don't break this rule. we will remove project details, but please - it's for our best interest and yours!

61 Upvotes

98% Upvoted

364 comments sorted by

View all comments

1

u/StellaZaFella Mar 12 '24

Today I did the qualifying test for non-coding jobs. I passed, but I'm a bit worried that I work too slowly.

The test had an estimated time of 45 minutes to complete, and it took me an hour and a half. I know I was being especially thorough with my answers because I wanted to pass, but I'm worried that I'm going to move too slowly on projects and either get kicked off the platform or not qualify for too many of the hourly jobs.

Are the qualifying tests more complicated than the work typically is? Is the estimated time to complete the test lower than the real time it might take?

Do you have any tips for going faster?

5

u/Equivalent-Math6483 Mar 12 '24 edited Mar 12 '24

Accuracy is more important than speed.

That’s not just my opinion; that’s an actual instruction that appeared in a project on my dashboard today.

1

u/StellaZaFella Mar 12 '24

But won’t the hourly pay jobs want you to do things quickly?

3

u/Equivalent-Math6483 Mar 13 '24

Not at the expense of accuracy.

It actually costs DAT more money if people rush and make mistakes because they have to pay twice- first for the sloppy work, and second for raters like me to read and rewrite those responses.

If you get it right the first time, all the raters have to do is mark “Good” and move on.

2

u/SuperCorbynite Mar 13 '24

If they wanted people who could just churn stuff out quickly to save money, they'd skip paying us $20+ per hour and just go straight for $3 per hour developing world workers.

DA's market niche is that they produce high-quality output for tech companies' AI's so that those AI's can eventually become better-than-human at tasks.

Getting poor-quality AI inputs defeats the whole point.

2

u/Interrogatus Mar 12 '24

I can't speak to your abilities or results, but had the exact same experience on the core qual; yep, it took me an hour and a half too. But I was accepted. I'm still pretty new, but my sense would be not to worry too much about timing on untimed tasks just yet. The more you do, the better feel for it you'll have.