Freelance data projects and remote data jobs
This page covers analytics, reporting, data science and data engineering. Read the responsibilities carefully: data entry and analytical work call for different skills.
See live data work →What lands here
Nabbly reads data briefs and roles from job boards and hiring communities. Arrival times vary by source. A gig reaches this page when it talks about work like this:
- data engineer
- analytics
- data scientist
- data analyst
- machine learning
- business intelligence
- data analytics
- data science
Recent gigs
Board snapshot: 2 November 2026. Open one, or open the board. It carries far more and changes through the day, so some of these will already have been filled.
- Data Science Manager
- Chief Analytics Officer (CAO)
- Software Engineering – Data Engineer (Python & Cloud Databases)
- Senior/Staff/Principal Data Scientist (HHS)
- Digital Data Analyst
- Data Engineer
- Senior Business Intelligence Professional
- Machine Learning Scientist, Multimodal AI — Natera
- Data Scientist — Doximity
- Pricing and Data Analyst
- Public Health Data Analyst
- Data Scientist 5, Media Science
- Customer Architect (Marketing Analytics & Experimentation)
- Data Analyst (12 months contract) — Binance
- Senior ML Data Scientist - Women’s Health — ŌURA
- Data Scientist - Music Promotion — Spotify
Snapshot: 2 November 2026
- 1,829 English-language gigs in the snapshot of 2 November 2026.
- Posts using urgent wording, such as ASAP or today: 22 of 1,829 gigs (1%).
- Stating a budget in the posting, in the snapshot: 268 of 1,829 gigs (15%).
- Budget bands in the snapshot, of the 268 that state one: Under $100 154 (57%); $100-500 58 (22%); $500-2k 46 (17%); $2k+ 10 (4%).
- 69 further gigs name an amount above $20,000 and are left out of the bands.
- Freelancer.com offers clients a dropdown of budget ranges, so many of its posts share the same range; the midpoint is what is counted.
- Work type recorded in these listings: project 187 (10%); contract 46 (3%); other 104 (6%); not stated 1,492 (82%).
- Listings labeled remote: 1,779 of 1,829 gigs (97%); on-site 27 (1%); not stated 23 (1%).
- Listings by source: Himalayas 1,463, 80% of the snapshot; Freelancer.com 182, 10% of the snapshot; Jobicy 117, 6% of the snapshot; Arbeitnow 27; Jobspresso 22; We Work Remotely 12; PeoplePerHour 5; Realworkfromanywhere 1.
- Common words in listing titles: data engineer (227 gigs); analytics (202 gigs); data scientist (146 gigs).
- Posting dates in this snapshot: 23 Oct 2026–2 Nov 2026 (10 days; dates read for 1,829 of 1,829 gigs).
How to read this snapshot. Sample size: 1,829 English-language gigs as of 2 November 2026. Unknown: budget not stated or not parseable in 1,492; work type not stated in 1,492; remote/on-site not stated in 23. Budgets are parsed from posting text (currencies not converted, hourly and project figures not separated); field membership is the board's own classifier, which is not perfect. Budgets are amounts stated in postings.
Look for the question behind the data work
Data work can involve repairing a spreadsheet, preparing a reporting pipeline, investigating a business question or building a model. Start with the decision the client wants to make. A request for a dashboard is incomplete until you know who will use it and what they need to see. A request for analysis needs a question that the available records can actually answer.
The supplied sample includes business intelligence, sales analytics, spreadsheet development and data-platform support. Those titles describe different responsibilities. Some involve a defined output; others belong to an ongoing team role. Check the duties and engagement terms before treating a remote listing as a freelance project. Data entry, reporting and statistical analysis also require different evidence of suitability.
Inspect the inputs before estimating the task
Ask where the records come from, how they are stored and whether the client can provide an approved sample. A workbook assembled manually may contain inconsistent labels or formulas that need investigation. A database extract may omit the relationships needed to join its tables. Establish whether cleaning and validation belong in the engagement instead of assuming the input is ready to analyse.
Check the meaning of the measures. Revenue might refer to orders, invoices or received payments; active customers might exclude people who have recently cancelled. Ask who can resolve these definitions. Without that agreement, a technically correct chart can still answer the wrong question. Document the definition alongside the calculation so the client can understand and reuse the output.
Access should match the task. You may need a redacted extract rather than access to an entire customer database. Establish where work can be stored and who may receive the results. Do not request private records in an opening reply when a description of the structure would be enough to discuss scope.
Agree how the result will be checked
For a dashboard, clarify the reporting period, refresh process and intended users. For a cleaned dataset, define which corrections are allowed and which ambiguous records should be returned for review. For a model, establish how its performance will be evaluated and what happens when its assumptions do not hold. A file that opens successfully is not a sufficient acceptance check for these different outputs.
Handover can include a data dictionary, a record of transformations and instructions for running the work again. Ask whether the client needs an editable workbook, a reproducible script or an update within an existing tool. The maintenance burden matters: a manually refreshed report and an automated pipeline can look similar while requiring different work after delivery.
Use your reply to demonstrate analytical judgement
Connect a relevant example to the client's question. Explain what you investigated, which limitations affected the result and what part you handled. If you show a chart, describe the decision it supported rather than relying on its appearance. Keep confidential datasets out of your portfolio and label illustrative material clearly.
A useful opening question might ask how the client currently reconciles the proposed measure with their existing report. That can reveal missing definitions or records before you promise an answer. Name tools you can use, but explain why they suit the task. A software list does not establish that you understand the problem.
Interpret the listing's payment terms
Confirm whether the amount covers investigation, implementation or continuing report maintenance. Read its currency and payment unit before estimating the engagement. The snapshot combines unlike amounts and leaves some work types unresolved; it cannot establish a fee for your analysis. Clarify data preparation and review time when those responsibilities are absent from the posting.
Use the reply guide to organise your evidence and scope question.
Start with the brief
Separate analysis assignments from data entry before choosing an example. For analysis, ask about the dataset and the decision it should support; for entry, clarify volume, format and accuracy checks. Keep private client data out of your reply. Use an editable Free template or a Pro draft informed by the posting, then check that it describes work you can deliver.
Replying to data briefs: the data guide → · what to put in the first two lines →