Product Owner, Agile - Core Credit

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: application instructions, EEO, etc. Must not include sections with placeholder like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes benefits description: "General Description of Available Benefits for Eligible Employees of Truist Financial Corporation:" includes medical, dental, vision, life insurance, disability, accidental death and dismemberment, tax-preferred savings accounts, 401k, vacation, sick days, paid holidays, possibly pension, RSU, deferred compensation. So we can include Benefits section. Pay: Not mentioned. So no Pay section. Schedule: The posting includes "Work Shift: 1st shift (United States of America)" and "Regular or Temporary: Regular". Also "NOTE: Candidate must be able to come into the office Monday-Friday in either our Charlotte, NC or Atlanta, GA offices." That's schedule info: work shift, days. So we can include Schedule section with that info. Also "Language Fluency: English (Required)" maybe part of Requirements or Qualifications. Could be under Requirements. We need sections: About the role (maybe from description paragraph after "Please review the following job description:"), Responsibilities (Essential Duties And Responsibilities), Qualifications (Required Qualifications and Preferred Qualifications), Skills (maybe from qualifications list? Could combine but we can have Skills section if there is specific skill content. The qualifications include many skills; we could put them under Qualifications. The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications? Might be overlapping. Better to follow typical: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. But we can decide to include Requirements and Qualifications separate if content distinct. The posting has "Required Qualifications:" and "Preferred Qualifications:" plus earlier language fluency etc. Could treat Required Qualifications as Requirements, and Preferred Qualifications as Qualifications? Or combine. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include those headings as appropriate. We'll include About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Possibly Skills not needed if covered elsewhere. We must not invent or summarize away detail. Must preserve all substantive info. So we need to include all details from the posting, except boilerplate. Let's extract substantive content: - About the role: "This role is a Product Owner in the Scaled Agile Framework who partners with product managers to balance business, technology and design priorities to deliver brand-defining product and service experiences. The position requires the ability to understand strategic impacts but concentrates on the day-to-day details to ensure tactical execution. The Product Owner should possess working knowledge of commercial credit risk rating frameworks and methodologies, including: Probability of Default (PD) concepts. Loss Given Default (LGD) considerations. Internal risk rating scorecards and models. Financial spreading methodologies and workflows. The Product Owner works with Product Managers to translate the product vision into stories that can be actioned by the delivery teams. The work will span the IRIS delivery process; from assisting with identification of areas for improvement, to more detailed work in authoring user stories, working closely with technical leads/scrum teams to ensure the solution effectively addresses experience priorities while maintaining technical integrity, and overseeing tactical execution of efforts." That's the role description. - Responsibilities: list of essential duties (the bullet points after "Essential Duties And Responsibilities"). Need to capture each duty as list items. Let's list them: 1. Lead their delivery team’s priorities in PI planning, sprint planning, and other agile ceremonies; aligned to larger experience platform priorities and vision defined by product management. 2. Align with product managers to clearly articulate product strategy to the delivery team. 3. Deliver new experiences by working directly with delivery, experience design, business, and operations partners to design new products and improvements to existing capabilities. 4. Author and maintain the team’s backlog of user stories and serve as a subject matter expert on features, user stories, and product capabilities. 5. Perform triage on critical issues and communicate consistently and clearly with all concerned parties. 6. Serve as key resource to development team to answer questions, provide clarifications, and conduct and coordinate business validation, focusing on fitness for use. 7. Update leadership on the epic and feature delivery schedule, including dependencies impacting deliverables, along with recommended solutions. 8. Partner with solution architects and other technical leads to ensure their solutions effectively address program priorities while balancing client experience and technical integrity. 9. Facilitate sprint planning with stakeholder groups to drive alignment and visibility for which features will be built when, and to ensure overall adherence to the product roadmap and enterprise strategic themes. 10. Facilitate sprint demos and provide final acceptance for completed user stories in sprint demos; ensuring that the story meets acceptance criteria and otherwise meets its definition of done. 11. Co-ordinate the creation of release-specific business documents, such as support model definitions, go/no-go approvals, internal release notes, and release-related living documents. 12. Risk management: Ensure all Product Management Lifecycle (PML) process & procedures are followed, supporting security, risk, audit, and more, and ensure action items and deadlines are met. 13. Partner with product manager on evidence to support recommendations. That's all. - Requirements: Could include language fluency, work shift, regular/temporary, office location, maybe education? Actually education is under qualifications. Requirements might be things like "Regular or Temporary: Regular", "Language Fluency: English (Required)", "Work Shift: 1st shift (United States of America)", "NOTE: Candidate must be able to come into the office Monday-Friday in either our Charlotte, NC or Atlanta, GA offices." Also maybe "Sitting Constantly..." etc are under Other Job Requirements / Working Conditions. Those could be Requirements as well. But we have a separate Qualifications section for education/experience. We could treat Requirements as the mandatory conditions: language, shift, regular, office location, maybe physical requirements? But the instruction says we can have Requirements and Qualifications sections. We'll put language fluency, work shift, regular/temporary, office location under Requirements. Also maybe "Travel Minimal and up to 10%" could be under Requirements or Schedule? It's travel requirement. Could be under Requirements. We'll include Requirements as a

list. - Qualifications: includes Required Qualifications and Preferred Qualifications. We'll list both as sub-sections? But we need to output only HTML fragment; we can have

Qualifications

then maybe

Required Qualifications:

then
list, then

Preferred Qualifications:

then
. That preserves detail. - Benefits: from "General Description of Available Benefits for Eligible Employees of Truist Financial Corporation:" includes medical, dental, vision, life insurance, disability, accidental death and dismemberment, tax-preferred savings accounts, 401k, vacation (10 days prorated), sick days (10 days prorated), paid holidays, possibly defined benefit pension plan, restricted stock units, deferred compensation. We'll list them. - Schedule: includes Work Shift: 1st shift, Regular, Monday-Friday office in Charlotte or Atlanta. Also maybe "Travel Minimal and up to 10%" could be schedule? But we already put travel under Requirements. We'll include schedule: Work Shift: 1st shift (United States of America); Regular position; Expected to work Monday-Friday in Charlotte, NC or Atlanta, GA offices. We must not include boilerplate: application instructions, EEO, disability accommodation request, etc. Also remove "Regular or Temporary: Regular Language Fluency: English (Required) Work Shift: 1st shift (United States of America)" from the raw text but we already used that info. We must not repeat job title. Not include "Please review the following job description:" as heading; we already used that content. We must not include duplicated lines. Now produce HTML fragment:

About the role

...

Responsibilities

• ...
...

Requirements

• Regular position
• English language fluency required
• 1st shift work schedule (United States)
• Must be able to work Monday‑Friday in either the Charlotte, NC or Atlanta, GA office
• Travel required: minimal, up to 10%
Maybe also include physical requirements? Those are under Other Job Requirements / Working Conditions: Sitting Constantly, Standing Frequently, Walking Frequently, Visual/Audio/Speaking, Manual Dexterity/Keyboarding, Availability (able to work all hours scheduled, including overtime). Those could be considered Requirements as well. But we already have Requirements; we could add them. However they are more about working conditions; but we can include them under Requirements to preserve all substantive info. The instruction says preserve ALL substantive information. So we should include those details. Let's add them under Requirements as list items. Thus Requirements list will be longer. Now Qualifications: We'll have

Qualifications

then

Required Qualifications:

list of required qualifications. Then

Preferred Qualifications:

list. We must not include "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That's boilerplate? It's part of qualifications but it's a standard statement; maybe we should keep? It's not boilerplate exactly but it's a generic statement about accommodations. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is about reasonable accommodations; could be considered EEO-related. Safer to remove it. Also remove "NOTE: Candidate must be able to come into the office Monday-Friday in either our Charlotte, NC or Atlanta, GA offices." we already used that. Now Benefits: list. Now Schedule: we already included shift etc under Requirements? Actually we placed schedule info under Requirements. But we also have a Schedule section. To avoid duplication, we could put schedule info under Schedule section and not under Requirements. Let's decide: We have both Requirements and Schedule sections; we can put language fluency, regular/temporary, travel under Requirements, and shift/office location under Schedule. Or we can put all under Requirements and not have Schedule. The instruction says include a section ONLY when the posting has real, specific content for it. The posting does have schedule info (Work Shift, regular/temporary, office location). So we can have Schedule section with that info. Then Requirements can be things like language fluency, regular/temporary? Actually regular/temporary is also schedule. But we can keep regular/temporary under Requirements as employment type. Let's allocate: Requirements: Language fluency (English required), Regular position, Travel (minimal up to 10%), Physical requirements (sitting, standing, walking, visual/audio, manual dexterity, availability to work all hours including overtime). Also maybe "Ability to work all hours scheduled, including overtime as directed by manager/supervisor and required by business need." That's availability. Schedule: Work Shift: 1st shift (United States of America); Expected to work Monday‑Friday in Charlotte, NC or Atlanta, GA offices. That seems good. Now Benefits section. Now ensure we don't include any placeholder like "commensurate with experience". Not present. Now produce HTML. Let's craft the About the role paragraph exactly as in posting, preserving details. About the role paragraph: "This role is a Product Owner