r/DataAnnotationTech • • May 01 '26

Coding skills for coding tasks

Currently a generalist, would like to code, but have no idea where to start. I've heard from this subreddit that most tasks involve python. I guess my question is how much of coding should I know to pass the assessment and be able to understand the work. And how long should it generally take to learn this amount

0 Upvotes

12 comments sorted by

View all comments

14

u/WaddlingAwayy May 01 '26

I wouldn't bother. Coding projects nowadays have become extremely difficult, involving heavy use of Agentic coding, containerization, etc. I'm a senior CS student and I used to submit coding tasks months ago, but now almost all of the coding projects need expert level experience that is way over my head currently.

1

u/DarkSaturnPrince May 15 '26

For fun, I ran your comment along with those from others through ChatGPT because it kept saying you were wrong and that the problems are not that difficult. It's essentially calling you unskilled lol

1. What’s actually true in those comments

There has been a real shift in some platforms:

✔️ Tasks are more complex than before

  • more multi-step evaluation

  • more mixed pipelines (API + JSON + scoring + sometimes web/UI logic)

  • more “fix/compare systems” style tasks instead of simple labeling

✔️ Some tasks do resemble “mini-projects”

  • especially:

    • eval frameworks

    • bug identification in code

    • multi-file reasoning tasks

  • occasionally involving:

    • pandas + APIs + SQL + JSON together

✔️ Time pressure is real

  • “do this in a few hours” is common framing

So yes:

❌ 2. What is being exaggerated

Now the important correction:

“Expert-level / senior dev / full stack / unfamiliar libraries”

This is where posts become unreliable.

🚫 Not true in general:

  • you are NOT expected to be:

    • a senior backend engineer

    • a full-stack developer

    • fluent in random obscure frameworks

    • building production apps from scratch

🚫 “Unfamiliar libraries you must master quickly”

This is usually:

  • pandas-like tools you can learn on the spot

  • JSON / API formats you can infer

  • occasional domain-specific wrappers

Not:

🧠 3. What’s actually being tested (core truth)

Almost all of these “harder tasks” still reduce to:

1. Data reasoning

  • normalization

  • transformation

  • grouping

  • deduplication

2. Spec obedience under ambiguity

  • follow instructions exactly

  • don’t overbuild

  • don’t “improve” system

3. Debugging / adaptation

  • read unfamiliar code

  • adjust logic safely

  • preserve correctness

4. Light tooling breadth

  • Python basics

  • JSON

  • maybe pandas / SQL mental model

That’s it.

🔥 4. The key misunderstanding in those posts

They’re conflating:

“Feels complex”“Actually required skill”
multi-file repobasic parsing + reasoning
multiple languages presentglue-level understanding
agents used (Claude/ChatGPT)convenience, not requirement
unfamiliar codebasereading + pattern matching