Senior Python Data Scraping Engineer (Freelance)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include boilerplate. Must preserve all substantive info. We need to parse the posting. Let's extract content: - Intro: "Mindrift is looking for highly skilled Vibecode specialists to join the Tendem project (https://tendem.ai/) and drive specialized data scraping workflows for real-world use cases. Mindrift is looking for highly skilled Senior Python Data Scraping Engineers to join the Tendem project and drive specialized data scraping workflows for real-world applications. In this role, you'll apply your expertise in web scraping, data extraction, and data processing to deliver accurate, reliable, and high-quality results. This part-time remote opportunity is ideal for technical professionals with hands-on experience in web scraping, data extraction and processing." - "What We Do" paragraph: "The Mindrift platform connects specialists with innovative technology projects. Our mission is to help develop high-quality AI technologies by combining real-world expertise from professionals across the globe with advanced AI development efforts." - "About The Role": "This is a freelance role for a Tendem project. As a Senior Python Data Scraping Engineer, you'll handle data scraping tasks requiring technical precision for web extraction and processing, utilizing tools such as Apify, OpenRouter, and other technologies, alongside your own technical expertise and approaches." - "Key Responsibilities": list bullet points (they are sentences separated by line breaks). We'll need to extract each bullet. Responsibilities text: "Own end-to-end data extraction workflows across complex websites, ensuring complete coverage, accuracy, and reliable delivery of structured datasets" "Leverage available tools and custom workflows to accelerate data collection, validation, and task execution while meeting defined requirement" "Ensure reliable extraction from dynamic and interactive web sources, adapting approaches as needed to handle JavaScript-rendered content and changing site behavior" "Enforce data quality standards through validation checks, cross-source consistency controls, adherence to formatting specifications, and systematic verification prior to delivery" "Scale scraping operations for large datasets using efficient batching or parallelization, monitor failures, and maintain stability against minor site structure changes" Note: second bullet has typo "requirement". We'll keep as is. - "Educational Qualifications": bullet points: "At least 5+ years of relevant experience in data engineering, web scraping, automation, or software development (required)" "Bachelor's or Master's Degree in Engineering, Applied Mathematics, Computer Science, or related technical fields is a plus" - "Academic and/or Professional Experience": paragraph: "Candidates should have a strong technical foundation and practical experience with scripting, automation, and data extraction workflows. We are looking for specialists who can solve non-trivial problems, work confidently with modern development tools and technologies, and systematically collect, structure, and validate data from diverse sources. A methodical, detail-oriented approach and the ability to work independently are essential." - "Technical Skills (Essential)": bullet points: "Strong experience in Python web scraping (BeautifulSoup, Selenium or similar), including dynamic content (JS, AJAX, infinite scroll) and APIs via proxies" "Proven ability to extract data from complex structures (hierarchies, archived pages, inconsistent HTML)" "Solid background in data cleaning, normalization, and validation, delivering structured datasets (CSV, JSON, Google Sheets)" - "Additional Requirements": bullet points: "Demonstrated experience handling anti-bot mechanisms and dynamic site structures at scale" "Experience with cloud infrastructure (AWS or equivalent) and containerization (Docker) as part of real workflows" "Hands-on experience with LLM frameworks (LangChain, OpenRouter, or similar) applied to automation tasks" "Strong attention to detail and commitment to data accuracy" "Self-directed work ethic with ability to troubleshoot independently" "A link to GitHub is a plus" "English proficiency: Upper-intermediate (B2) or above (required)" - "Project time expectations": paragraph: "For this project, tasks are estimated to require around 10-20 hours per week during active phases, based on project requirements. This is an estimate, not a guaranteed workload, and applies only while the project is active." - "Compensation": paragraph: "On this project, contributors can earn up to $45 per hour equivalent, depending on their level and pace of contribution. Compensation varies across projects depending on scope, complexity, and required expertise. Please note that other projects on the platform may offer different earning levels based on their requirements." We need to decide sections: About the role (we have content), Responsibilities (list), Requirements (maybe combine Educational Qualifications + Academic/Professional Experience + Additional Requirements?), Qualifications (maybe Educational Qualifications?), Skills (Technical Skills), Benefits (none explicit), Pay (Compensation), Schedule (Project time expectations). The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some. We must not create sections with placeholder/filler. So we need to ensure each section has real content. We have content for: - About the role: we have paragraph(s). Could combine "What We Do" and "About The Role"? But "What We Do" is about company, not role. Might be okay as part of About the role? Probably better to have About the role section containing the description of role and maybe what we do? But we can keep separate sections: About the role (includes "About The Role" paragraph). Could also include "What We Do" as part of About the role? Might be okay. - Responsibilities: we have list. - Requirements: we could combine Educational Qualifications, Academic/Professional Experience, Additional Requirements into a single Requirements section (list). But we need to decide if we want separate Qualifications and Skills sections. The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have multiple sections if they have content. We have content for Qualifications (Educational Qualifications). We have content for Skills (Technical Skills). We have content for Requirements (maybe Additional Requirements? Actually Additional Requirements could be part of Requirements). But we also have Academic/Professional Experience which could be part of Requirements or Qualifications. Let's think. We could structure: - About the role (includes What We Do and About The Role paragraphs) - Responsibilities (list) - Qualifications (Educational Qualifications bullet list) - Skills (Technical Skills bullet list) - Requirements (Additional Requirements bullet list) maybe also include Academic/Professional Experience? Could merge Academic/Professional Experience into Requirements or Qualifications. But we already have Qualifications for education; Academic/Professional Experience is more about experience, could be part of Requirements. However we also have "Project time expectations" (Schedule) and "Compensation" (Pay). So we need Schedule and Pay sections. We must not create Benefits section if no content. There's no explicit benefits mentioned. So omit Benefits. We must not repeat job title as heading. We must not include Job ID etc. We must output only HTML fragment. Let's craft:

About the role

... combine What We Do and About The Role paragraphs.

Responsibilities

• Own end-to-end data extraction workflows across complex websites, ensuring complete coverage, accuracy, and reliable delivery of structured datasets
• Leverage available tools and custom workflows to accelerate data collection, validation, and task execution while meeting defined requirement
• Ensure reliable extraction from dynamic and interactive web sources, adapting approaches as needed to handle JavaScript-rendered content and changing site behavior
• Enforce data quality standards through validation checks, cross-source consistency controls, adherence to formatting specifications, and systematic verification prior to delivery
• Scale scraping operations for large datasets using efficient batching or parallelization, monitor failures, and maintain stability against minor site structure changes

Qualifications

• At least 5+ years of relevant experience in data engineering, web scraping, automation, or software development (required)
• Bachelor's or Master's Degree in Engineering, Applied Mathematics, Computer Science, or related technical fields is a plus

Skills

• Strong experience in Python web scraping (BeautifulSoup, Selenium or similar), including dynamic content (JS, AJAX, infinite scroll) and APIs via proxies
• Proven ability to extract data from complex structures (hierarchies, archived pages, inconsistent HTML)
• Solid background in data cleaning, normalization, and validation, delivering structured datasets (CSV, JSON, Google Sheets)

Requirements

• Demonstrated experience handling anti-bot mechanisms and dynamic site structures at scale
• Experience with cloud infrastructure (AWS or equivalent) and containerization (Docker) as part of real workflows
• Hands-on experience with LLM frameworks (LangChain, OpenRouter, or similar) applied to automation tasks
• Strong attention to detail and commitment to data accuracy
• Self-directed work ethic with ability to troubleshoot independently
• A link to GitHub is a plus
• English proficiency: Upper-intermediate (B2) or above (required)

We also have Academic and/or Professional Experience paragraph. Could we incorporate into Requirements or Qualifications? It's about experience, maybe better to add to Requirements as a paragraph before list? But we already have Requirements list. Could add a

before list: "Candidates should have a strong technical foundation and practical experience with scripting, automation, and data extraction workflows. We are looking for specialists who can solve non-trivial problems, work confidently with modern development tools and technologies, and systematically collect, structure, and validate data from diverse sources. A methodical, detail-oriented approach and the ability to work independently are essential." That is substantive. So we should include that as part of Requirements section (maybe before the list). Let's add a

after the heading. Similarly, we have Project time expectations (Schedule) and Compensation (Pay). We'll add those sections. Schedule:

Schedule

For this project, tasks are estimated to require around 10-20 hours per week during active phases, based on project requirements. This is an estimate, not a guaranteed workload, and applies only while the project is active.

Pay:

Pay

On this project, contributors can earn up to $45 per hour equivalent, depending on their level and pace of contribution. Compensation varies across projects depending on scope, complexity, and required expertise. Please note that other projects on the platform may offer different earning levels based on their requirements.

We must not include Benefits section. Now check for any repeated content: We used "What We Do" and "About The Role" combined. Let's craft About the role paragraph: We have two paragraphs: "What We Do" and "About The Role". Combine them maybe as two

under same heading? Could be multiple

. We'll output:

About the role

The Mindrift platform connects specialists with innovative technology projects. Our mission is to help develop high-quality AI technologies by combining real-world expertise from professionals across the globe with advanced AI development efforts.

This is a freelance role for a Tendem project. As a Senior Python Data Scraping Engineer, you'll handle data scraping tasks requiring technical precision for web extraction and processing, utilizing tools such as Apify, OpenRouter, and other technologies, alongside your own technical expertise and approaches.

We also have earlier introductory sentences about Mindrift looking for specialists etc. That content is somewhat repetitive; we might incorporate into About the role as well. The initial paragraphs: "Mindrift is looking for highly skilled Vibecode specialists to join the Tendem project (https://tendem.ai/) and drive specialized