Spanish AI Product Tester
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Key info:
- Location: 100% Remote, located in the U.S.
- Device: Applicants must have a qualifying Google Pixel device for the duration of the project
- 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)
- 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 of bullet points:
- Native or expert-level fluency in Spanish spoken in Mexico (es_mx)
- 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
- The Project: description paragraph.
- Workload: 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.
- Duties: list bullet points:
- 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: confidentiality terms, must use own qualifying Google Pixel device, list of qualifying device examples, note about Pixel 9a and 10a not compatible.
- About Us: description of company.
- Disclaimer: background screening, diversity inclusion.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The disclaimer about background screening maybe considered legal? It's a disclaimer but maybe we keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The disclaimer about background screening is legal; we should remove it. Also "About Us" maybe not a standard heading but could be considered "About the role"? Actually "About Us" is company description; we could treat as "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. We have:
- About the role: could include description of the project (The Project paragraph) and maybe Workload.
- Responsibilities: Duties list.
- Requirements: Project Requirements list.
- Qualifications: maybe overlapping with Requirements; but we can combine? The instruction says prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Pay, Schedule? Pay we have compensation. Schedule we have workload/daily time.
We need to include Pay section only if posting actually states them. Yes compensation stated: USD $250.00 one time payment upon successful completion of 14 qualified submissions. So we can have Pay section.
Schedule: we have expected daily participation time 10-15 minutes per day, duration until 14 qualified submissions (maybe 14-21 days). So we can have Schedule section.
Benefits: not mentioned besides compensation; no other benefits. So we should not create Benefits section.
Skills: maybe language fluency etc. Could be included in Requirements. But we could have Skills section for language fluency and device comfort. However instruction: prefer few substantive sections over many thin ones. So maybe combine language fluency and device comfort into Requirements.
Thus sections: About the role, Responsibilities, Requirements, Pay, Schedule.
We need to output HTML fragment only, no /. Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reorganize into sections.
We must not repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. There's no job title given; we can ignore.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to drop the Disclaimer about background screening and diversity inclusion. Also drop "Active Project Status" maybe? That's not boilerplate but it's about urgency; could be part of About the role? It's substantive: "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." That's about application process; maybe considered application instructions? It says remove application instructions. This is about keeping eye on communication after applying; that's application instruction. So we should drop that. Also "Please note: To ensure eligibility for this project, applicants must be located in the U.S." is a requirement; we can keep that as part of Requirements.
Also "Please note: Google Pixel 9a and Pixel 10a devices are not compatible with project requirements." That's a requirement detail; keep.
Also "Participants Must Use their own qualifying Google Pixel device." That's requirement.
Also "Engagement Requirements 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." That's confidentiality requirement; could be part of Requirements or Responsibilities? It's a requirement; we can include under Requirements.
Also "About Us" description: we could treat as About the role? Actually About the role is about the job/project; About Us is company description. Could be considered "About the role"? Might be better to include as a short paragraph under About the role? But the instruction says use headings like About the role, Responsibilities, etc. So we can put company description under About the role? Might be okay. However we need to preserve all substantive information; we can include About Us as a paragraph under About the role heading.
We must not create sections with filler text like "commensurate with experience". We have real content.
Now let's extract content.
We'll create:
About the role
...
Content for About the role: combine location, device requirement, project description, workload, maybe active project status? But we decided to drop active project status as application instruction. However location and device requirement are requirements; maybe they belong in Requirements. But we can still include location in About the role as context. Let's think.
Better to separate: About the role: description of the project (The Project paragraph) and maybe workload description. Requirements: list of requirements (language fluency, device, Wi-Fi, age, confidentiality, etc.). Responsibilities: duties list. Pay: compensation. Schedule: expected daily time and duration.
Thus About the role 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."
Also maybe include location: "Location: 100% Remote, located in the U.S." Could be in About the role or Requirements. I'd put in About the role as a brief context.
Now Responsibilities: list of duties.
Requirements: list of requirements (language fluency, device comfort, downloading apps, using device as primary phone, participation duration 14-21 days, age 18+, reliable Wi-Fi, able to read English instructions, must use own qualifying Pixel device, qualifying device examples, note about Pixel 9a/10a not compatible, confidentiality terms). Also maybe include "Must be located in the U.S." as requirement.
Pay: "USD $250.00 one time payment upon successful completion of 14 qualified submissions.
"
Schedule: "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.
" Also maybe mention duration 14-21 consecutive days? That's more requirement; but we can include in Schedule: "Participants must be willing to participate daily for 14-21 consecutive days." That's both requirement and schedule. We'll put in Schedule.
Now we need to ensure we don't repeat info. Let's list all requirements bullet points:
- Native or expert-level fluency in Spanish spoken in Mexico (es_mx)
- 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
- Must be located in the U.S.
- Must use own qualifying Google Pixel device
- 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 with project requirements.
- Adherence to 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.
We could combine some.
Now Responsibilities bullet points:
- 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
Now About the role paragraph: include location, project description, maybe also mention that it's remote US.
Let's craft:
Location: 100% Remote, located in the U.S.
We are seeking detail-oriented and motivated speakers to participate in an upcoming notification sorting project.
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reorganize into sections.
We must not repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. There's no job title given; we can ignore.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to drop the Disclaimer about background screening and diversity inclusion. Also drop "Active Project Status" maybe? That's not boilerplate but it's about urgency; could be part of About the role? It's substantive: "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." That's about application process; maybe considered application instructions? It says remove application instructions. This is about keeping eye on communication after applying; that's application instruction. So we should drop that. Also "Please note: To ensure eligibility for this project, applicants must be located in the U.S." is a requirement; we can keep that as part of Requirements.
Also "Please note: Google Pixel 9a and Pixel 10a devices are not compatible with project requirements." That's a requirement detail; keep.
Also "Participants Must Use their own qualifying Google Pixel device." That's requirement.
Also "Engagement Requirements 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." That's confidentiality requirement; could be part of Requirements or Responsibilities? It's a requirement; we can include under Requirements.
Also "About Us" description: we could treat as About the role? Actually About the role is about the job/project; About Us is company description. Could be considered "About the role"? Might be better to include as a short paragraph under About the role? But the instruction says use headings like About the role, Responsibilities, etc. So we can put company description under About the role? Might be okay. However we need to preserve all substantive information; we can include About Us as a paragraph under About the role heading.
We must not create sections with filler text like "commensurate with experience". We have real content.
Now let's extract content.
We'll create:
About the role
...
Content for About the role: combine location, device requirement, project description, workload, maybe active project status? But we decided to drop active project status as application instruction. However location and device requirement are requirements; maybe they belong in Requirements. But we can still include location in About the role as context. Let's think.
Better to separate: About the role: description of the project (The Project paragraph) and maybe workload description. Requirements: list of requirements (language fluency, device, Wi-Fi, age, confidentiality, etc.). Responsibilities: duties list. Pay: compensation. Schedule: expected daily time and duration.
Thus About the role 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."
Also maybe include location: "Location: 100% Remote, located in the U.S." Could be in About the role or Requirements. I'd put in About the role as a brief context.
Now Responsibilities: list of duties.
Requirements: list of requirements (language fluency, device comfort, downloading apps, using device as primary phone, participation duration 14-21 days, age 18+, reliable Wi-Fi, able to read English instructions, must use own qualifying Pixel device, qualifying device examples, note about Pixel 9a/10a not compatible, confidentiality terms). Also maybe include "Must be located in the U.S." as requirement.
Pay: "USD $250.00 one time payment upon successful completion of 14 qualified submissions.
"
Schedule: "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.
" Also maybe mention duration 14-21 consecutive days? That's more requirement; but we can include in Schedule: "Participants must be willing to participate daily for 14-21 consecutive days." That's both requirement and schedule. We'll put in Schedule.
Now we need to ensure we don't repeat info. Let's list all requirements bullet points:
- Native or expert-level fluency in Spanish spoken in Mexico (es_mx)
- 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
- Must be located in the U.S.
- Must use own qualifying Google Pixel device
- 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 with project requirements.
- Adherence to 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.
We could combine some.
Now Responsibilities bullet points:
- 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
Now About the role paragraph: include location, project description, maybe also mention that it's remote US.
Let's craft:
Location: 100% Remote, located in the U.S.
We are seeking detail-oriented and motivated speakers to participate in an upcoming notification sorting project.
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reorganize into sections. We must not repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. There's no job title given; we can ignore. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to drop the Disclaimer about background screening and diversity inclusion. Also drop "Active Project Status" maybe? That's not boilerplate but it's about urgency; could be part of About the role? It's substantive: "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." That's about application process; maybe considered application instructions? It says remove application instructions. This is about keeping eye on communication after applying; that's application instruction. So we should drop that. Also "Please note: To ensure eligibility for this project, applicants must be located in the U.S." is a requirement; we can keep that as part of Requirements. Also "Please note: Google Pixel 9a and Pixel 10a devices are not compatible with project requirements." That's a requirement detail; keep. Also "Participants Must Use their own qualifying Google Pixel device." That's requirement. Also "Engagement Requirements 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." That's confidentiality requirement; could be part of Requirements or Responsibilities? It's a requirement; we can include under Requirements. Also "About Us" description: we could treat as About the role? Actually About the role is about the job/project; About Us is company description. Could be considered "About the role"? Might be better to include as a short paragraph under About the role? But the instruction says use headings like About the role, Responsibilities, etc. So we can put company description under About the role? Might be okay. However we need to preserve all substantive information; we can include About Us as a paragraph under About the role heading. We must not create sections with filler text like "commensurate with experience". We have real content. Now let's extract content. We'll create:
About the role
...
Content for About the role: combine location, device requirement, project description, workload, maybe active project status? But we decided to drop active project status as application instruction. However location and device requirement are requirements; maybe they belong in Requirements. But we can still include location in About the role as context. Let's think. Better to separate: About the role: description of the project (The Project paragraph) and maybe workload description. Requirements: list of requirements (language fluency, device, Wi-Fi, age, confidentiality, etc.). Responsibilities: duties list. Pay: compensation. Schedule: expected daily time and duration. Thus About the role 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." Also maybe include location: "Location: 100% Remote, located in the U.S." Could be in About the role or Requirements. I'd put in About the role as a brief context. Now Responsibilities: list of duties. Requirements: list of requirements (language fluency, device comfort, downloading apps, using device as primary phone, participation duration 14-21 days, age 18+, reliable Wi-Fi, able to read English instructions, must use own qualifying Pixel device, qualifying device examples, note about Pixel 9a/10a not compatible, confidentiality terms). Also maybe include "Must be located in the U.S." as requirement. Pay: "USD $250.00 one time payment upon successful completion of 14 qualified submissions.
" Schedule: "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.
" Also maybe mention duration 14-21 consecutive days? That's more requirement; but we can include in Schedule: "Participants must be willing to participate daily for 14-21 consecutive days." That's both requirement and schedule. We'll put in Schedule. Now we need to ensure we don't repeat info. Let's list all requirements bullet points: - Native or expert-level fluency in Spanish spoken in Mexico (es_mx) - 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 - Must be located in the U.S. - Must use own qualifying Google Pixel device - 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 with project requirements. - Adherence to 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. We could combine some. Now Responsibilities bullet points: - 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 Now About the role paragraph: include location, project description, maybe also mention that it's remote US. Let's craft:Location: 100% Remote, located in the U.S.
We are seeking detail-oriented and motivated speakers to participate in an upcoming notification sorting project.