French AI Product Tester

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key info: - No Google Pixel device? They will lend and ship required phone directly to home for duration of project. - Location: 100% Remote, located in the U.S. - Device: Participants must use a qualifying Google Pixel device for duration. - Compensation: USD $250.00 one time payment upon successful completion of 14 qualified submissions (each submission should take 10–15 minutes of activity per day) - Must be located in the U.S. - Project Requirements: - Native or expert-level fluency in French spoken in France (ISO; fr-FR) - Must be comfortable using a Google Pixel 9 or newer device - Must be comfortable downloading and using common mobile applications that generate notifications (messaging apps, email apps, social media apps, etc.) - Must be comfortable using the Google Pixel device as their primary phone for the duration of the project - Must be willing to participate daily for 14-21 consecutive days - Must be 18 or older to meet project eligibility requirements - Must have access to reliable Wi-Fi/internet - Participants must be able to read and understand instructions and company communications in English - What You'll Do: - Participants will engage with the project daily until 14 qualified submissions have been submitted. - Expected daily participation time may vary slightly depending on notification volume and project tasks, but participants should expect approximately 10–15 minutes of activity per day. - This is project-based work, and there is no guarantee of additional work beyond the pilot period. However, participants who perform well may be considered for future related projects. - Use a Google Pixel 9 or newer device throughout the project duration - Interact naturally with apps that generate notifications - Complete assigned notification sorting / organization tasks - Submit required daily feedback and documentation - Follow all provided project instructions carefully - Communicate promptly regarding technical issues or project blockers - Perform all work with attention to quality, completeness, and detail - Engagement Requirements: - This project is part of an ongoing effort to improve emerging mobile AI and notification-management technologies for international users. - While participating in this project, adherence to the confidentiality terms outlined in the User Agreement is required. Any information accessed or received related to this project is confidential and may not be shared or disclosed to third parties. - Qualifying Device Examples: - Google Pixel 9 - Google Pixel 9 Pro - Google Pixel 10 - Google Pixel Fold (newer generation) - Note: Google Pixel 9a and Pixel 10a devices are not compatible. - About Us: description of Productive Playhouse. - Disclaimer: background screening, diversity etc. Probably boilerplate? It's not EEO but still maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Disclaimer about background screening maybe legal? Might be considered boilerplate. Safer to drop it. Also "Powered by JazzHR" is boilerplate. We need sections: maybe About the role (description), Responsibilities (What You'll Do), Requirements (Project Requirements + maybe device lending info?), Qualifications (maybe language fluency, age, etc.), Skills (maybe comfort with device, apps), Benefits (Compensation, device lending), Pay (maybe separate), Schedule (duration 14-21 days, daily 10-15 min). But we should only include sections if there is real specific content. We can combine some. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation (Pay) and schedule (duration, daily time). Also benefits: device lending, remote work. So we can include those sections. We need to avoid filler like "commensurate with experience". Not present. We'll produce HTML with headings

and content in

or

• . We need to preserve all substantive info. Let's extract. Substantive info: - Device lending: "No Google Pixel device? No problem at all! We will happily lend and ship the required phone directly to your home for the duration of the project." - Location: "Location: 100% Remote, located in the U.S." - Device requirement: "Participants must use a qualifying Google Pixel device for the duration of the project" - Compensation: "Compensation: USD $250.00 one time payment upon successful completion of 14 qualified submissions.(each submission should take 10–15 minutes of activity per day)" - Must be located in the U.S. (again) - Project Requirements list (bulleted) - What You'll Do list (bulleted) - Engagement Requirements (confidentiality) - Qualifying Device Examples list - About Us paragraph(s) - Possibly also note about enrollment process: "Ready to earn? Let's make it happen! We're currently enrolling participants and moving fast! After you apply, watch your email and messages closely. Responding promptly will help us get you through the enrollment process and into the project as quickly as possible." This is application instructions? It's about enrollment process; maybe considered boilerplate? It's not exactly application instructions but could be considered promotional. The instruction says remove application instructions. This is about enrollment process after applying. Might be considered application instructions. Safer to drop. Also "Please note: To ensure eligibility for this project, applicants must be located in the U.S." Already covered. Also "Please note: Google Pixel 9a and Pixel 10a devices are not compatible with project requirements." Keep. Now structure sections: We could have:

  About the role

  - maybe a brief description: remote, device lending, compensation, etc. But we already have separate sections for Pay, Benefits, Schedule. Could combine. Better to follow typical headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. About the role: general overview: 100% remote, device lending, project description (improve mobile AI notification-management), compensation, duration. Responsibilities: What You'll Do list. Requirements: maybe the eligibility requirements: location, age, language fluency, device comfort, Wi-Fi, etc. Qualifications: maybe language fluency, expert-level French, ability to read English instructions, etc. But could overlap. Skills: comfort with Google Pixel, downloading apps, using as primary phone, notification sorting tasks, etc. Benefits: device lending, remote work, compensation? Actually compensation is Pay. Pay: compensation $250 one-time. Schedule: duration 14-21 consecutive days, daily 10-15 minutes activity. We must not create sections with filler. Ensure each section has substantive content. Let's craft. About the role: include remote, device lending, project purpose, compensation maybe? But compensation separate. We'll keep About the role short: remote, device lending, purpose. Responsibilities: bullet list from What You'll Do. Requirements: bullet list from Project Requirements (including location, age, language, device comfort, Wi-Fi, English comprehension). Also maybe include willingness to participate daily 14-21 days? That's schedule though. Qualifications: maybe language fluency (native/expert French), ability to read English instructions, etc. Could be minimal. Skills: comfort with Google Pixel 9+, downloading apps, using as primary phone, notification sorting, etc. Benefits: device lending, remote work. Pay: compensation. Schedule: duration and daily time. We also have Qualifying Device Examples and note about incompatible devices. Could be part of Requirements or Skills. Maybe include under Requirements as bullet list. Engagement Requirements confidentiality: could be part of Responsibilities or a separate section like "Engagement". But we don't have a heading for that; we could include under Responsibilities as a bullet. About Us: maybe not needed as a section; could be omitted? The instruction says preserve ALL substantive information. About Us is substantive. Could be a section "About the company". But we don't have that heading in allowed list. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. About Us not listed. Should we omit? The instruction says use those headings for section headings. It doesn't forbid other headings, but says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. About Us could be omitted or we could put under About the role? Might be okay to include as a paragraph under About the role? But About the role is about the role, not company. However we could include a brief About the company paragraph under About the role? Might be stretching. Better to follow instruction: only use those headings. So we need to fit About Us content somewhere else, maybe under About the role? Could be considered part of role description. We'll include a short paragraph about company under About the role. Now produce HTML. We must not include markdown fences. Let's draft:

  About the role

  This is a 100% remote project based in the United States. Productive Playhouse will lend and ship a qualifying Google Pixel device to your home for the duration of the project. The project aims to improve emerging mobile AI and notification‑management technologies for international users.

  Responsibilities

  • Engage with the project daily until 14 qualified submissions have been submitted.
  • Expect approximately 10–15 minutes of activity per day (time may vary with notification volume).
  • Use a Google Pixel 9 or newer device throughout the project duration.
  • Interact naturally with apps that generate notifications.
  • Complete assigned notification sorting / organization tasks.
  • Submit required daily feedback and documentation.
  • Follow all provided project instructions carefully.
  • Communicate promptly regarding technical issues or project blockers.
  • Perform all work with attention to quality, completeness, and detail.
  • Adhere to confidentiality terms; project‑related information must not be shared or disclosed to third parties.

  Requirements

  • Located in the United States (100% remote).
  • Must be 18 years of age or older.
  • Native or expert‑level fluency in French spoken in France (ISO; fr‑FR).
  • Ability to read and understand instructions and company communications in English.
  • Comfortable using a Google Pixel 9 or newer device as the primary phone for the project duration.
  • Comfortable downloading and using common mobile applications that generate notifications (messaging, email, social media, etc.).
  • Willing to participate daily for 14‑21 consecutive days.
  • Have access to reliable Wi‑Fi/internet.
  • Qualifying device examples: Google Pixel 9, Pixel 9 Pro, Pixel 10, Pixel Fold (newer generation). Note: Pixel 9a and Pixel 10a are not compatible.

  Skills

  • Proficiency with Google Pixel 9+ devices.
  • Comfort downloading and using notification‑generating mobile apps.
  • Ability to sort and organize notifications as instructed.
  • Strong attention to detail and quality in completing tasks.
  • Prompt communication regarding any technical issues.

  Benefits

  • Device loan: