Data
Data entry, cleanup, and research micro-jobs on Buxonline, starting at $1.
About data
Data work involves collecting, cleaning, structuring, analysing and interpreting information so that organisations can make informed decisions. This spans everything from building pipelines that move data between systems, to writing SQL queries that extract specific records, to creating statistical models that predict customer behaviour. The work might involve scraping websites, designing database schemas, building dashboards in Tableau or Power BI, running regression analyses in R or Python, or setting up ETL processes that transform raw logs into usable datasets.
What separates competent data work from poor work is rigour around accuracy and reproducibility. A well-executed analysis documents assumptions, handles missing values explicitly, validates results against known benchmarks, and produces outputs that another practitioner could recreate from the same source material. Poorly done data work introduces silent errors—joins that drop records, aggregations that double-count, or visualisations that mislead through inappropriate scales or chart types. The difference often lies in whether someone checks their work against ground truth, writes clear transformation logic, and understands the limitations of their methods.
Good data work also means choosing appropriate techniques for the question at hand. Not every problem needs machine learning; sometimes a pivot table and a clear chart communicate more effectively than a complex model. Understanding when to use median versus mean, whether a sample is representative, or how to handle time-series data with seasonality—these practical judgments determine whether the output actually helps someone make a better decision.
Guides related to data
Data — questions and answers
- What does it mean to normalise a database, and when would you skip it?
- Normalisation structures a database to reduce redundancy by splitting data into related tables. You might denormalise deliberately for read-heavy applications where query speed matters more than storage efficiency, accepting some duplication to avoid expensive joins. Data warehouses often use denormalised star schemas for exactly this reason.
- How do you handle missing data without skewing the analysis?
- It depends on why data is missing. If values are missing completely at random, you might drop those rows or impute using mean or median. If missingness correlates with other variables—say, high earners skip income questions—ignoring it biases results. Sometimes the best approach is analysing only complete cases and stating that limitation clearly.
- What makes a dataset tidy, and why does structure matter before analysis?
- Tidy data has one observation per row, one variable per column, and one value per cell. This structure lets analytical tools work predictably—filtering, grouping and joining behave as expected. Untidy data, like multiple measurements in one column or variables spread across column headers, requires reshaping before most analysis tools can process it properly.
- When does a correlation actually suggest causation might exist?
- Correlation alone never proves causation, but temporal precedence, dose-response relationships, and consistency across different datasets strengthen the case. Randomised controlled trials or natural experiments provide better evidence. In observational data, techniques like propensity score matching or instrumental variables help, but confounding variables can still mislead without careful controls.
- Can machine learning models trained on one dataset work reliably on another?
- Only if the new data comes from the same distribution. Models trained on summer sales data may fail in winter; fraud detection trained on one region may miss patterns elsewhere. Concept drift—where underlying patterns change over time—degrades performance. Regular retraining and monitoring prediction accuracy on fresh holdout data catch these problems.
- What's the practical difference between batch processing and streaming data?
- Batch processing handles data in scheduled chunks—nightly ETL jobs, weekly reports—which suits historical analysis and tolerates some latency. Streaming processes records as they arrive, enabling real-time dashboards or immediate alerts. Streaming requires different infrastructure like Kafka or Kinesis and complicates operations, so it only makes sense when timeliness genuinely matters.
