Sr Mobile Expert

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like EEO, legal, application instructions, etc. We need to parse the posting. Content: - Opening: "At T-Mobile, we invest in YOU! Our Total Rewards Package ensures that employees get the same big love we give our customers. All team members receive a competitive base salary and compensation package - this is Total Rewards. Employees enjoy multiple wealth-building opportunities through our annual stock grant, employee stock purchase plan, 401(k), and access to free, year-round money coaches. That’s how we’re UNSTOPPABLE for our employees!" - Job Overview: paragraph about Sr Mobile Expert. - Job Responsibilities: list bullet points (Sells appropriate products..., Resolves..., Completes..., Consistently..., Works...) - Education and Work Experience: lines: High School Diploma/GED (Required) Retail: 12+ mos. Neighborhood Mobile Expert (Preferred) Care: Elite Expert, Account Care (Preferred) Care: Elite Expert, Technical Care (Preferred) - Knowledge, Skills and Abilities: list of items: Communication (Required)Critical Thinking (Required)Customer Service (Required)Multitasking (Required)Product Knowledge (Required)Sales (Required)Task Management (Required)Teamwork Orientation (Required)Troubleshooting (Required)At least 18 years of ageLegally authorized to work in the United States Travel: Travel Required (Yes/No): No DOT Regulated: DOT Regulated Position (Yes/No): No Safety Sensitive Position (Yes/No): No - Hourly Base Pay: $34.00 Annualized Incentive Target: $7,200 Successful candidate’s actual incentive earnings vary based on performance and full-time status. All employees at T-Mobile, are guaranteed to earn $20/hour inclusive of base pay and incentives. And since we are ALL owners, EVERY employee at T-Mobile is eligible for an Annual Stock Grant. - Benefits paragraph: "At T-Mobile, our benefits exemplify the spirit of One Team, Together! ..." includes many benefits. - Additional: "Never stop growing! As part of the T-Mobile team, you know the Un-carrier doesn’t have a corporate ladder–it’s more like a jungle gym of possibilities! ..." This is about growth/career development; could be part of About the role or maybe a separate section like "Development". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "About the role" to include job overview and growth statements. "Responsibilities" to the list. "Requirements" maybe education and work experience? "Qualifications" maybe knowledge, skills and abilities? "Skills" maybe the list of KSAs? But we need to avoid duplication. The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only when posting has real specific content for it. We need to decide mapping. We have content for: - About the role: job overview paragraph + maybe the opening about Total Rewards? The opening is about total rewards, but that could be Benefits? Actually Benefits section is separate. The opening about total rewards could be part of About the role or Benefits. But we have a Benefits section later with detailed benefits. The opening mentions wealth-building opportunities etc. Could be part of Benefits. But we can include in Benefits. - Responsibilities: the list under "Job Responsibilities:" (5 bullet points). - Requirements: Education and Work Experience (High School Diploma/GED required, retail experience etc). Could be Requirements. - Qualifications: maybe the "Knowledge, Skills and Abilities" list (communication etc) plus age, work authorization, travel etc. Could be Qualifications. - Skills: maybe we could separate out the KSAs as Skills, but we already used Qualifications for that. Could combine. But we need to avoid thin sections. Perhaps we can put KSAs under Skills, and Requirements under Education/Experience. Qualifications could be something else like "At least 18 years of age, legally authorized to work..." but that's also a requirement. Hmm. We have to decide a sensible mapping that uses the headings but not create empty sections. We have content for: - About the role: job overview paragraph (maybe also the opening about total rewards? but that's benefits). We'll keep About the role = job overview paragraph. - Responsibilities: bullet list. - Requirements: Education and Work Experience (High School Diploma/GED required, retail experience etc). Could also include "At least 18 years of age" and "Legally authorized to work in the United States" as requirements. But those are also in KSAs. We'll include them in Requirements. - Qualifications: maybe the "Knowledge, Skills and Abilities" list (communication etc). Could also include "Travel: Travel Required (Yes/No): No" etc but those are more like job details. Could be Qualifications. - Skills: maybe we could separate out the list of KSAs into Skills, but then Qualifications would be empty. Better to put KSAs under Skills, and Qualifications could be something like "At least 18 years of age, legally authorized to work..." but that's also a requirement. Hmm. Alternatively, we could combine Requirements and Qualifications into one section, but we need to follow headings. We could make Requirements include education/experience and age/work auth, and Qualifications include the KSAs list. Skills could be omitted if we don't have distinct content beyond KSAs. But we need to decide if we should include Skills section. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills if we already covered KSAs under Qualifications. But we need to include Skills only if posting has real specific content for it. The posting does have a list of KSAs, which could be considered Skills. But we already used Qualifications for that. Could we treat Qualifications as the list of KSAs and Skills as something else? There's no other skill list. So maybe we put KSAs under Skills, and Qualifications could be something like "At least 18 years of age, legally authorized to work..." but that's also a requirement. However, we could treat Qualifications as the combination of KSAs and eligibility requirements, and Skills as something else? Not ideal. Better approach: Use headings as follows: - About the role: job overview paragraph. - Responsibilities: bullet list. - Requirements: Education and Work Experience (HS Diploma/GED, retail experience etc). - Qualifications: Knowledge, Skills and Abilities list (communication etc) plus age, work authorization, travel etc. - Benefits: detailed benefits paragraph. - Pay: Hourly Base Pay, Annualized Incentive Target, guarantee $20/hour, annual stock grant. - Schedule: Not mentioned explicitly; there is no schedule info. So we should NOT include Schedule section because posting does not state it. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must not include Schedule. Now we need to format: - Use

for each section heading. - Use

• for any list of duties/requirements/benefits. - Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we must cut out the EEO statement at the end, the accommodation contact, etc. Also remove the "At T-Mobile, we invest in YOU!"? That's substantive? It's part of total rewards intro; we can keep it as part of About the role or Benefits. It's not boilerplate. Keep. We must also remove duplicated lines: there may be repeated phrases like "All employees at T-Mobile, are guaranteed to earn $20/hour inclusive of base pay and incentives." and "And since we are ALL owners, EVERY employee at T-Mobile is eligible for an Annual Stock Grant." Keep. We need to ensure we keep all substantive info: job overview paragraph, responsibilities list, education/work experience, KSAs list, benefits list, pay details. We need to format lists properly. Let's extract each piece. **About the role** (job overview paragraph): "Sr Mobile Expert are our most capable experts with a passion for delivering best-in-class customer service experience while also leveraging their retail expertise. Our company-owned Experience stores will be a destination for attracting new customers as well as providing the highest level of service to our existing customers. Sr Mobile Expert will have new systems and tools for solving all customer needs from research to resolution, as well as new products and a product roadmap built specifically for these locations. This store uniquely brings Team of Experts to life, where Experts and Leaders are working directly with peers in Customer Service and Engineering to create a one-stop to resolution for solving customer pain points. Sr Mobile Expert will receive one of a kind curated training and curriculum designed to enhance their expertise as well as provide ongoing development, resulting in an environment where they can best perform and grow. With a team-based culture that rewards and recognizes contribution to experience as well as store results, Sr Mobile Expert will be uniquely set up for success to deliver the BEST sales and service experiences in a customer's lifetime." Also maybe include the opening "At T-Mobile, we invest in YOU! Our Total Rewards Package ensures that employees get the same big love we give our customers. All team members receive a competitive base salary and compensation package - this is Total Rewards. Employees enjoy multiple wealth-building opportunities through our annual stock grant, employee stock purchase plan, 401(k), and access to free, year-round money coaches. That’s how we’re UNSTOPPABLE for our employees!" This is about total rewards, could be part of About the role or Benefits. Since we have a Benefits section, we could put this intro in About the role as well, but it's about rewards. However, we already have Benefits section for detailed benefits. The opening mentions wealth-building opportunities etc. Might be appropriate to include in About the role as a brief overview. But we must not duplicate content. The Benefits section already lists many benefits; the opening mentions annual stock grant, employee stock purchase plan, 401(k), free money coaches. That's a subset. To avoid duplication, we could keep the opening in About the role as a summary, and Benefits section list the full details. That's okay; not duplicate exactly same sentences but overlapping concepts. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the opening sentences exactly as they appear. If we put them in About the role, we keep them. Then Benefits section will also list those same items again (annual stock grant, employee stock purchase plan, 401(k), etc.) That would be duplication of substantive information. The instruction says remove duplicated lines. So we should avoid duplicating the same exact lines. The opening lines are not exactly same as the Benefits paragraph but they mention same benefits. However, they are not identical lines; they are different phrasing. The instruction about duplicated lines likely refers to identical repeated lines in the posting (like repeated bullet points). The opening and Benefits paragraph are not identical lines, but they convey similar info. It's okay to keep both as they are not exact duplicates. We'll keep both. Thus About the role will include the opening paragraph plus the job overview paragraph. Could combine into one

  with both paragraphs? Could be two

  elements. We'll just put them in one

  separated by space? Better to keep as separate

  for readability but still valid. We'll output multiple

  inside the section. **Responsibilities**: list: - Sells appropriate products, features, and services based on customer needs. - Resolves customer pain points in one interaction utilizing in-store