Competitive Data Scientist（远程职位）

这条招聘信息来自 micro1，岗位是 Competitive Data Scientist。职位属于「数据与分析」类别，完全远程。公司不限制候选人的居住地，在任何地方都可以申请。

招聘信息里列出的主要工具是：Python、Machine Learning。简历上最好能给出正是这几项能力的具体例子。

公司没有公布具体数字，这一项会在面试时谈定。对工作时间，招聘信息没有提出任何条件。

这个职位通过了自动核查：凡是要求外国工作许可、签证担保、特定国籍，或者必须居住在指定国家的招聘信息，都不会进入列表。

Role Title: Competitive Data Scientist Pay: $60-$120/hour Location: Global, fully remote Job Type: Contractor (~15 hours per week) Schedule: Flexible-you choose the hours and days you work, including weekends if desired We're looking for data scientists, machine learning practitioners, and applied mathematics experts with competitve Data Science experience. (Kaggle, DrivenData, etc.) You’ll draw on your competition experience, mathematical reasoning, and programming skills to create tasks that require more than a plausible answer. Each task should have a reproducible environment, a verified reference solution, and reliable checks for successful completion. What You’ll Do

* Build reproducible environments, prepare relevant data and dependencies, and implement reference solutions.

* Develop tests and evaluation criteria that reliably distinguish correct solutions from incomplete or flawed approaches.

* Run coding agents against tasks, investigate their failures, and refine the tasks based on observed behavior.

* Identify implementation errors, flawed assumptions, data leakage, and other issues that affect correctness.

* Document task requirements, solution reasoning, and verification steps clearly.

What We’re Looking For

* Demonstrated experience in data science, ML, quantitative modeling, or relevant research competitions. (Kaggle, DrivenData, etc.)

* Strong problem-solving ability and a clear understanding of the methods you use.

* Practical programming ability sufficient to implement and verify your own solutions.

Relevant competition platforms include Kaggle, DrivenData, Zindi, AIcrowd, Numerai, DataSource.ai, and CodaLab/Codabench. Huge Pluses

* Strong coding experience, particularly in Python, including testing, debugging, and working with unfamiliar code Originally posted on Himalayas