Sr Content Specialist

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. No job title heading. No Job ID. Remove boilerplate. Keep substantive info. We need to parse content. Content: Title: Content Strategist Paragraph: "The Content Strategist role is responsible for helping to shape and craft simple, approachable, and straightforward language, hierarchy, and voice & tone for our digital experiences for our clients and participants. In partnership with designers, product owners, and technologists, this position plays a critical role in shaping our end to end experiences to guide, inform and educate our clients to make the best choices for their future financial security, supporting our participants to and through their retirement." Then "Key Responsibilities And Duties" list bullet-like sentences separated by periods? Actually they are sentences separated by periods but we can treat as list items. List: - Collaborate with design, product, development, and marketing teams to develop clear and concise content to reach business goals and TIAA’s internal and external audiences. - Conduct content audits and content gap analyses to ensure that user experiences consistent and in line with industry best practices and enterprise needs. - Collaborate with UX design and writing teams to build consistency and clarity across experiences. - Research and analyze audience need, preferences, objectives, and methods. Study and understand how participants and B2B audiences consume content to plan for retirement. - Plan, write and present content for existing and emerging mobile and web experiences. - Identify and help solve problems in new and existing user experiences to ensure ease of use in a complex, fast-paced, deadline-driven financial environment. - Create consistent, on-brand messaging that clearly articulates the benefits of TIAA products and services, while streamlining operational tasks for internal and external audiences. Then "Educational Requirements University (Degree) Preferred". So Education: University degree preferred. "Work Experience 5+ Years Required; 7+ Years Preferred". So experience. "Career Level 8IC". Probably not needed. "Required Skills: 5+ Years of UX Writing Experience Preferred Skills: Experience in financial services UX content Writing Related Skills Accountability, Adaptability, Collaboration, Communication, Consultative Communication, Continuous Improvement Mindset, Creative Thinking, Critical Thinking, Innovation, Prototyping, Relationship Management, Test & Learn Mentality, User Experience Design" So we have required skills: 5+ Years of UX Writing Experience. Preferred skills: Experience in financial services UX content Writing. Also list of related skills. "Anticipated Posting End Date: 2026-09-29" - metadata, can be minor. "Base Pay Range: $126,000/yr - $177,000/yr Actual base salary may vary based upon, but not limited to, relevant experience, time in role, base salary of internal peers, prior performance, business sector, and geographic location. In addition to base salary, the competitive compensation package may include, depending on the role, participation in an incentive program linked to performance (for example, annual discretionary incentive programs, non-annual sales incentive plans, or other non-annual incentive plans)." So Pay section: base pay range and mention of incentive. "Benefits And Total Rewards" paragraph: talk about comprehensive Total Rewards package, superior retirement program, health, wellness, work life offerings, etc. Also mention "To learn more about your benefits, please review our Benefits Summary." That's substantive. We also have Company Overview etc. That could be "About the role"? Actually About the role could be the initial paragraph describing role. Could also include company overview? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (the initial description). Responsibilities (list). Requirements (education, experience). Qualifications maybe combine? But we can have Requirements and Qualifications separate if content. However we have "Educational Requirements" and "Work Experience". Could put under Requirements. Qualifications maybe not separate; we could omit if no distinct content. Skills section: required and preferred skills and related skills. Benefits: we have Benefits And Total Rewards paragraph. Pay: base pay range and incentive. Schedule: not mentioned, so omit. We must not include sections with filler like "commensurate with experience". We have actual pay range, so include Pay. We must not repeat job title as heading. We must not include boilerplate like EEO, accessibility, drug policy, privacy notices, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details: e.g., "University (Degree) Preferred", "5+ Years Required; 7+ Years Preferred", "Career Level 8IC" maybe not needed but could be included under Requirements? It's a metadata but maybe not essential. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Career Level 8IC is minor metadata; we could fold into a short p under Requirements or drop. Probably drop to keep concise. We need to keep "Anticipated Posting End Date: 2026-09-29" maybe minor metadata; could drop or fold into a short p under About the role? Probably drop as not essential. We need to keep the list of related skills. We need to keep the benefits description. We need to keep the company overview? The instruction: sections like About the role could include the initial paragraph describing role. The company overview is separate but could be considered "About the role"? Actually "About the role" is about the role, not company. The company overview is about TIAA. Could we include it under About the role? Might be considered extra but it's substantive about the company. The instruction: "Prefer a few substantive sections over many thin ones." We could include an "About the company" section but not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. Company overview could be placed under About the role? Might be a stretch but we could incorporate a brief sentence about TIAA's mission within About the role? However the initial paragraph already mentions TIAA's mission indirectly. The company overview is separate but we could drop it as not required for the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep company overview info. But we don't have a heading for it. Could we include it as a

under About the role? That would be adding content not originally under that heading but still preserving info. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It doesn't say we cannot have other headings, but we should follow the pattern. Safer to include company overview as a

under About the role? Might be considered not accurate but still preserves info. However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine company overview into About the role as a paragraph. Alternatively, we could add an "About the company" heading but not in the list; risk of deviating. Better to keep within allowed headings. Thus About the role will contain the initial paragraph plus company overview paragraph. Now Responsibilities: list. Requirements: education and experience (maybe also career level). We'll put education and experience as

• . Qualifications: maybe we could include "Career Level 8IC" as a qualification? But it's not really qualification. Could omit Qualifications section if no specific content besides what's already in Requirements. The instruction: include a section ONLY when the posting has real, specific content for it. If we don't have distinct qualifications beyond requirements, we could omit Qualifications. But we have "Required Skills" and "Preferred Skills" etc. Those go under Skills. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Check if we need Qualifications: maybe we could put "Career Level 8IC" under Qualifications. But it's minor. Could drop. Now format:

  About the role

  The Content Strategist role is responsible for helping to shape and craft simple, approachable, and straightforward language, hierarchy, and voice & tone for our digital experiences for our clients and participants. In partnership with designers, product owners, and technologists, this position plays a critical role in shaping our end to end experiences to guide, inform and educate our clients to make the best choices for their future financial security, supporting our participants to and through their retirement.

  TIAA is a market-leading retirement company with over 100 years of history, dedicated to helping educators and millions of Americans achieve a secure retirement. Guided by values such as Champion Our People, Be Client Obsessed, Lead with Integrity, Own It, and Win As One, TIAA fosters a collaborative in‑office environment where teams work across boundaries to drive innovation and deliver meaningful results.

  But we need to ensure we don't invent details. The company overview paragraph we wrote includes specifics from the text: "Every worker deserves a secure retirement. For more than 100 years, TIAA has delivered it for millions of people. Founded to help educators retire with dignity, today weʼre a market-leading retirement company fueled by world-class asset management. But weʼre not just another legacy financial services firm. Weʼre fighting harder than ever before for our clients and the many Americans who need us. Our Culture of Impact At TIAA, we're on a mission to build on our 100+ year legacy of delivering for our clients while evolving to meet tomorrow's challenges. We equip our associates with future-focused skills and AI tools that enable us to advance our mission. Together, we are fighting to ensure a more secure financial future for all and for generations to come. We are guided by our values: Champion Our People, Be Client Obsessed, Lead with Integrity, Own It, and Win As One. They influence every decision we make and how we work together to serve our clients every day. We thrive in a collaborative in-office environment where teams work across organizational boundaries with shared purpose, accelerating innovation and delivering meaningful results. Our workplace brings together TIAA and Nuveen's entrepreneurial spirit, where we work hard and work together to create lasting impact. Here, every associate can grow through meaningful learning experiences and development pathways—because when our people succeed, our impact on clients' lives grows stronger." We need to include that exactly or paraphrase? We must preserve ALL substantive information; do NOT invent or summarize away detail. Paraphrasing may be considered summarizing away detail? Safer to copy the text verbatim (or close) but we can keep the essential info. However the instruction says do NOT summarize away detail; we can keep the same meaning but not omit details. Paraphrasing could be okay if we keep all details. But better to quote directly. Thus we can include the company overview as a blockquote? But we just need

  . We'll copy the company overview text exactly as given (with proper punctuation). Ensure we don't include boilerplate like EEO etc. Now Responsibilities: list each duty as

• . We need to capture all duties from "Key Responsibilities And Duties". Let's extract them precisely: - Collaborate with design, product, development, and marketing teams to develop clear and concise content to reach business goals and TIAA’s internal and external audiences. - Conduct content audits and content gap analyses to ensure that user experiences consistent and in line with industry best practices and enterprise needs. - Collaborate with UX design and writing teams to build consistency and clarity across experiences. - Research and analyze audience need, preferences, objectives, and methods. Study and understand how participants and B2B audiences consume content to plan for retirement. - Plan, write and present content for