Italian AI Product Tester
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to preserve all substantive info.
Let's parse the posting:
- Intro: "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." This is about device lending.
- Location: "100% Remote, located in the U.S."
- Device: "Applicants must use a qualifying Google Pixel device for the duration of the project"
- Compensation: "USD $250.00 upon successful completion of the 14-day participation period (10–15 minutes of activity per day)"
- Note: "Please note: To ensure eligibility for this project, applicants must be located in the U.S."
- Active Project Status: "This project is now live, and we are urgently onboarding participants to begin immediately. Because we are moving quickly, we kindly ask that you keep a close eye on your communication (email and messages) after applying. It is essential that you respond promptly so we can get you cleared and ready to start without delay."
- Project Requirements list: bullet points.
- The Project description: paragraphs.
- Workload: description.
- Duties: bullet list.
- Engagement Requirements: confidentiality.
- Participants Must Use their own qualifying Google Pixel device. Qualifying Device Examples list.
- About Us: description.
- Disclaimer: background screening, diversity inclusion.
We need to decide sections: Likely we have sections: About the role (maybe The Project description), Responsibilities (Duties), Requirements (Project Requirements), Qualifications (maybe device requirements, language fluency, age, location), Skills (maybe fluency, comfort with apps), Benefits (Compensation, device lending), Pay (maybe separate but we can combine? The rule: include a section ONLY when posting has real specific content. We have compensation info, so we can have Pay section. Benefits maybe device lending. Schedule maybe workload (10-15 min per day, 14 days). We should not create sections with filler like "commensurate with experience". We have actual specifics.
We must not repeat job title. No headings for Job ID.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
...
Schedule
...
We need to ensure we don't include sections with no content. All sections we include must have content. Let's extract content for each. About the role: Could be "The Project" paragraph: "We are seeking detail-oriented and motivated speakers to participate in an upcoming notification sorting project. Participants will use a Google Pixel 9 or newer device throughout the project period while interacting naturally with apps that generate notifications. Participants will complete daily project tasks involving notification organization/sorting workflows and provide related feedback/documentation as instructed. Participants will also complete a short daily feedback/check-in form throughout the duration of the pilot to assist with participation tracking and troubleshooting support. This project is part of an ongoing effort to improve emerging mobile AI and notification-management technologies for international users." That seems appropriate. Responsibilities: Duties list: "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". Also maybe Engagement Requirements confidentiality? Could be part of Responsibilities or separate but we can include under Responsibilities. Requirements: Project Requirements list: "Native or expert-level fluency in Italian", "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 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". Also location: "100% Remote, located in the U.S." and "Applicants must be located in the U.S." Could be part of Requirements. Qualifications: Could be device specifics: "Qualifying Device Examples: Google Pixel 9, Google Pixel 9 Pro, Google Pixel 10, Google Pixel Fold (newer generation)". Also note that Pixel 9a and Pixel 10a not compatible. Also maybe "Applicants must use a qualifying Google Pixel device for the duration of the project". Also "Participants Must Use their own qualifying Google Pixel device." Also "We will happily lend and ship the required phone directly to your home for the duration of the project." That's a benefit. Skills: maybe "Native or expert-level fluency in Italian", "Comfortable using Google Pixel device", "Comfortable downloading and using common mobile apps", "Ability to read and understand English instructions". But these overlap with Requirements. Could separate: Skills: language fluency, technical comfort, attention to detail, communication promptness. But we need to avoid duplication? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. It's okay to have overlapping content if it's present in multiple places? Might be duplication but we can keep as is. However we should not invent. We'll try to allocate distinct sections. Benefits: "We will happily lend and ship the required phone directly to your home for the duration of the project." Also maybe "Compensation: USD $250.00 upon successful completion". But compensation is Pay. Benefits could be device lending. Pay: "USD $250.00 upon successful completion of the 14-day participation period (10–15 minutes of activity per day)". Also maybe note about no guarantee of additional work beyond pilot, but that's not pay. Schedule: "Participants will engage with the project daily for 14 consecutive days. 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." Also "This is project-based work, and there is no guarantee of additional work beyond the pilot period." Could be schedule. We also have "Active Project Status: This project is now live, and we are urgently onboarding participants to begin immediately. Because we are moving quickly, we kindly ask that you keep a close eye on your communication (email and messages) after applying. It is essential that you respond promptly so we can get you cleared and ready to start without delay." This could be part of About the role or maybe a separate section like "How to apply"? But we must not include application instructions. This is about responsiveness after applying; it's not exactly application instruction but could be considered part of process. Might be okay to include under About the role or a separate "Important notes". But we only have predefined headings list; we could put under About the role. Also "Disclaimer All engagements are contingent upon successful completion of a background screening. Productive Playhouse is committed to diversity and inclusion across our global contractor network. We welcome applicants of all backgrounds and abilities." This is boilerplate EEO/diversity; we should remove per instruction: remove EEO/equal-opportunity/scam-warning boilerplate. So we should drop that disclaimer. Also "About Us" section: description of company. Could be included under About the role? Or maybe a separate "About Us" but not in headings list. The headings list does not include About Us; we could incorporate into About the role or maybe omit? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should stick to those headings. Probably we should only use those headings. So we can put company description under About the role as well.
Thus About the role will contain: project description, company info, active status note.
Now we need to ensure we don't include any boilerplate like "Please note: To ensure eligibility for this project, applicants must be located in the U.S." That's not boilerplate; it's a requirement. Keep.
Now produce HTML.
Let's craft:
About the role
We are seeking detail-oriented and motivated speakers to participate in an upcoming notification sorting project. Participants will use a Google Pixel 9 or newer device throughout the project period while interacting naturally with apps that generate notifications. Participants will complete daily project tasks involving notification organization/sorting workflows and provide related feedback/documentation as instructed. Participants will also complete a short daily feedback/check-in form throughout the duration of the pilot to assist with participation tracking and troubleshooting support. This project is part of an ongoing effort to improve emerging mobile AI and notification-management technologies for international users. As a global data company, Productive Playhouse “PPH”, is pioneering our approach to language and data services, while incorporating their roots as a production company. Originally creating content to support children's language acquisition, our commitment to excellence, forward-thinking strategies, and world-wide cultural experience has proven key for delivering exceptional service. Originally founded as an educational production company, Productive Playhouse made a mark with our award winning children’s series, which taught fundamental subjects through engaging and effective programming. This early success paved the way for our evolution into a comprehensive data services provider. Since 2011, Productive Playhouse has expanded rapidly to offer an extensive suite of data services. Our current offerings include transcription, translation, linguistic analysis, rating, systems testing, localization, field and studio recording, language skill verification, and specialized data handling with a focus on sensitivity and diversity. Our commitment to innovation means we continually enhance our service portfolio to meet the evolving needs of our clients. At Productive Playhouse, we are proud of our reputation for addressing complex challenges with agility and delivering premium, secure data solutions across diverse environments. Our dynamic team is dedicated to maintaining the highest standards and ensuring exceptional service every time. The project is now live, and we are urgently onboarding participants to begin immediately. Because we are moving quickly, we kindly ask that you keep a close eye on your communication (email and messages) after applying. It is essential that you respond promptly so we can get you cleared and ready to start without delay.
Responsibilities
- 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 outlined in the User Agreement; any information accessed or received related to this project is confidential and may not be shared or disclosed to third parties
Requirements
- Native or expert-level fluency in Italian
- Must be comfortable using a Google Pixel 9 or newer device