Learning Experience Leader - RAD/Fleet Response (T2)

We need to output HTML fragment with sections: About the role? Actually the job description includes "About TaskUs" and "What We Offer", "Salary Range", "Benefits", "Application Window", "Job Description" (duties), "Requirements", "Nice To Have", "About Us", "How We Partner To Protect You", "DEI", "EEO". We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop EEO, DEI, How We Partner To Protect You (maybe considered boilerplate?), but the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove EEO and DEI sections. Also "How We Partner To Protect You" might be considered legal/scam-warning? It's about not soliciting money; could be considered scam-warning boilerplate. Probably remove it. Also "Application Window" includes date and recommendation to apply within 7 days – that's application instructions, should be removed. Also "Req Id" and "Posted At" metadata should be folded into short

or dropped. We can include a short paragraph with metadata like "Req Id: R_2607_9884 | Posted: Thu Jul 30 2026". But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a

with that info. We need to preserve all substantive information. So we need sections: About the role? Actually we have "Job Description" which includes duties. We'll make a section with heading

Responsibilities

(or maybe "Job Description" but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have: - About TaskUs (company overview) could be "About the role"? Actually "About the role" is about the job, not company. But we have "About TaskUs" describing company. Could be placed under a heading like "About the company" but not in list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where appropriate. We can also add other headings if needed, but better to stick to those. So we need to map content: - About the role: maybe a brief summary of what the role does. We have "Job Description: What does a Learning Experience Leader really do?" That's a good fit for About the role. - Responsibilities: the bullet list of duties (the colon list after "As a Learning Experience Leader, you will:"). - Requirements: the list under "Requirements:" (including travel, age, education, etc.) - Qualifications: maybe "Nice To Have" could be qualifications? But they have separate "Nice To Have". Could treat as "Qualifications" or "Skills". We have skills listed in Requirements (proficient in Microsoft and Google applications, problem solver, etc.) and also Nice To Have (experience, leadership). We could put skills under "Skills". But we have a separate "Skills" heading in the list. So we could put the skill-based items under Skills, and the experience/education under Requirements/Qualifications. Better: Use Requirements for mandatory items (education, age, travel, etc.). Use Skills for abilities (problem solver, critical thinker, interpersonal, etc.). Use Qualifications maybe for preferred education (Four-year college degree preferred) and Nice To Have (experience, leadership). But we need to avoid thin sections. Let's think. We have: Requirements list: - Up to 25% travel required - Must be 18 years of age or older - High School Diploma or GED required. - Four-year college degree (preferred) in a related field like industrial or applied sciences; - Proficient in Microsoft and Google applications - A problem solver and critical thinker - Follow well-defined methods, procedures, reports, forms, and competent aspects of the job - Can present and facilitate a class discussion - Energetic, enthusiastic, and creative-can think outside the box with different ways to motivate and engage an audience - With strong interpersonal, conflict management, mentoring, organizational, project management, and influencing skills - Has excellent oral and written communication skills - Can work in a flexible schedule including weekends, holidays, and longer hours Nice To Have: - At least 1 to 2 years of working experience in a related field (training or teaching experience - Has strong leadership skills, with proficiency in handling groups We could treat "Nice To Have" as "Qualifications" (preferred qualifications). Or we could add a "Preferred Qualifications" heading but not in list. Since they only gave examples, we can still use other headings if needed but better to stick to given ones. We could put the Nice To Have under "Qualifications". And the Four-year college degree (preferred) also under Qualifications. Thus: - About the role: summary paragraph from "Job Description: What does a Learning Experience Leader really do?" plus maybe the first sentence about creating learning environment. - Responsibilities: the bullet list of duties. - Requirements: mandatory items: travel, age, HS diploma/GED, proficient in MS/Google, problem solver/critical thinker, follow methods, present/facilitate discussion, energetic/enthusiastic/creative, strong interpersonal etc., excellent oral/written communication, flexible schedule. - Qualifications: preferred college degree, 1-2 years experience, strong leadership skills. - Skills: maybe we could separate some skill items but they'd overlap with Requirements. Could also put the skill-based items under Skills and keep Requirements more about education/experience. But we already used Requirements for many skill items. Might be okay. - Benefits: we have benefits listed. - Pay: Salary Range. - Schedule: maybe not explicitly stated; we have flexible schedule including weekends, holidays, longer hours under Requirements. Could put that under Schedule? But they said only create Schedule section if posting actually states them. It does mention flexible schedule including weekends, holidays, longer hours. That's schedule info. So we can create a Schedule section with that detail. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to ensure we don't create empty sections. All have content. Now we need to strip boilerplate: remove "About TaskUs" company overview? That's not about the role but could be considered "About the company". Not in list; maybe we can omit it because it's not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the company overview. Where to put it? Could be a heading like "About the company" but not in list. However they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can add other headings as needed, but better to keep to those. However we need to preserve the company overview; we could put it under "About the role" as a brief intro? But that would mix company info with role info, maybe okay. But the "About the role" heading is supposed to be about the role, not company. However we could still include company overview as a paragraph before the role description under same heading. That might be acceptable. Alternatively we could add a heading "About the company" as an

. Since they didn't forbid other headings, it's okay. But to be safe, we could include it as a

without heading? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but they gave examples. I'd stick to those headings and incorporate company overview into a paragraph under "About the role" or maybe as a separate

before any heading. But they said output ONLY the HTML fragment. It's okay to have a leading

before any heading? Probably fine. Let's structure:

TaskUs is a provider of outsourced digital services and next-generation customer experience to fast-growing technology companies, helping its clients represent, protect and grow their brands. Leveraging a cloud-based infrastructure, TaskUs serves clients in the fastest-growing sectors, including social media, e-commerce, gaming, streaming media, food delivery, ride-sharing, HiTech, FinTech, and HealthTech. The People First culture at TaskUs has enabled the company to expand its workforce to approximately 60,000 employees globally. Presently, we have a presence in twenty-three locations across twelve countries, which include the Philippines, India, and the United States. It started with one ridiculously good idea to create a different breed of Business Processing Outsourcing (BPO)! We at TaskUs understand that achieving growth for our partners requires a culture of constant motion, exploring new technologies, being ready to handle any challenge at a moment's notice, and mastering consistency in an ever-changing world.

Then

About the role

with paragraph: "What does a Learning Experience Leader really do? Think of yourself as someone who will create and maintain a positive and professional learning environment in the organization. Imagine yourself going to work with one thing on your mind: you will design and expand training and development programs. These programs should be aligned with product-specific training methodologies and initiatives. As a Learning Experience Leader, you will: ..." Actually the colon list is responsibilities; we could keep the intro sentence then list responsibilities under

Responsibilities

. So About the role could be just the first two sentences before the colon list. Thus:

About the role

What does a Learning Experience Leader really do? Think of yourself as someone who will create and maintain a positive and professional learning environment in the organization. Imagine yourself going to work with one thing on your mind: you will design and expand training and development programs. These programs should be aligned with product-specific training methodologies and initiatives.

Then

Responsibilities

with

of the duties. Then

Requirements

with
of mandatory items. Then

Qualifications

with
of preferred items (college degree preferred, 1-2 years experience, strong leadership skills). Then

Skills

maybe we could list some skill items not already covered? But many skill items are in Requirements. To avoid duplication, we could move some skill-oriented items to Skills and keep Requirements more about baseline (education, age, travel). Let's split: Requirements (baseline): - Up to 25% travel required - Must be 18 years of age or older - High School Diploma or GED required. - Proficient in Microsoft and Google applications - Can work in a flexible schedule including weekends, holidays, and longer hours Skills (competencies): - A problem solver and critical thinker - Follow well-defined methods, procedures, reports, forms, and competent aspects of the job - Can present and facilitate a class discussion - Energetic, enthusiastic, and creative—can think outside the box with different ways to motivate and engage an audience - Strong interpersonal, conflict management, mentoring, organizational, project management, and influencing skills - Excellent oral and written communication skills Qualifications (preferred): - Four-year college degree (preferred) in a related field like industrial or applied sciences - At least 1 to 2 years of