Scrum Master (Irvine, CA/Ontario, CA)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, equal opportunity, scam warning, navigation, cookie, legal, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Content: Intro paragraph: "Shaping the Future of Lending With 30 years of fintech leadership, Origence empowers credit unions with innovative SaaS lending solutions that make lending more accessible, efficient, and competitive. We invest in our people and foster a culture of innovation, ownership, and continuous improvement. As we help shape the future of lending, we're leveraging AI to enhance the way we work and create value for our clients, and we're seeking individuals who are excited by emerging technologies and eager to use them responsibly to solve problems and drive impact." Then: "The Scrum Master will work with Agile teams that span across time zones required for operational excellence in product deliveries. Responsible for making sure a Scrum team lives by the values and practices of Scrum. Additionally, provide guidance and provide guidance and help educate the team in Lean, Kanban, and Scaled Agile framework (SAFe). We are in the implementation phase of the SAFe transformation journey. The scrum master will (1) ensure that the Agile process is being followed; (2) help remove blockers and impediments. (3) foster an environment to create high-performing team that generates continuous flow of value, with ongoing innovation and relentless improvement. MUST BE LOCATED IN IRVINE, CA OR ONTARIO, CA (USA)***" Then "The Origence Mindset ..." paragraph. Then "How You'll Contribute" list of duties. Then "Preferred Education What Makes You a Great Fit:" list of qualifications. Then "Your Strengths & Expertise" list of strengths. Then "Bring your ideas..." paragraph. Then "How We Invest In You" list of benefits. Then "Recognizing Your Impact" paragraph with salary range. Then EEO boilerplate to remove. We need sections: About the role (maybe intro), Responsibilities (the How You'll Contribute list), Requirements (maybe Preferred Education?), Qualifications (maybe Your Strengths & Expertise?), Skills (maybe combine?), Benefits (How We Invest In You), Pay (salary range), Schedule (maybe not present; no schedule info, so omit). Must not create empty sections. We need to decide which headings to use. We have content for: - About the role: could be the introductory paragraph describing company and role overview. - Responsibilities: the "How You'll Contribute" bullet list. - Requirements: maybe the "Preferred Education What Makes You a Great Fit:" bullet list (education, certifications, experience). Could also include location requirement (must be located in Irvine, CA or Ontario, CA). That is a requirement. - Qualifications: maybe "Your Strengths & Expertise" bullet list. - Skills: maybe combine some of the strengths? But we could also have Skills as separate if we have specific skill list (e.g., Azure DevOps, JIRA, SAFe, etc.) Those appear in Requirements. Might be better to put technical skills under Skills. However we need to avoid duplication. Let's think. We have: Preferred Education section includes: - BA/BS degree in a technical or related field - PMP and CSM are a plus - Advanced Certified Scrum Master (A-CSM) Certified - Experience with Azure DevOps, and/or JIRA - Experience in SAFe (Scaled Agile Framework), or any scaled environment is required - 3-5 years of experience in a software development environment - 3-5 years working in an Agile team - 3-5 years of experience as a Scrum Master That's more like qualifications/requirements. Your Strengths & Expertise includes: - Demonstrated expert knowledge of agile principles, practices, and methods - Demonstrated use of Agile metrics to track the Team and Release progress - Practical experience of servant-leadership in agile teams - Experience in participating in program events like PI planning etc. - Excellent organizational and facilitation skills during system demo, I&A problem solving etc - Exceptional in oral, written, and presentation communication with team, RTE and others - Self-starting mentality and willingness to take ownership of difficult challenges - Desire to drive change, implement new ways of working and think "out of the box" - Excellent knowledge of PC based computer systems, including MS Word, Project, Excel, PowerPoint, Visio, etc. These are skills/competencies. Thus we could map: - About the role: intro paragraph. - Responsibilities: How You'll Contribute list. - Requirements: Preferred Education list (including location requirement maybe separate). Could also include location as a requirement. - Qualifications: maybe not needed if we used Requirements for qualifications; but we need to follow instruction: use headings only when posting has real specific content. We have content for both Requirements and Qualifications; we can split: Requirements = mandatory items (location, experience, SAFe, etc.) Qualifications = preferred/certifications etc. But the posting lumps them together under "Preferred Education What Makes You a Great Fit:" which includes both required and preferred. However we can still separate: Requirements: location, SAFe experience, 3-5 years experience as Scrum Master, etc. Qualifications: degree, PMP/CSM, A-CSM, Azure DevOps/JIRA, etc. But we need to avoid duplication. Better: Use Requirements for the mandatory items: location (must be located in Irvine, CA or Ontario, CA), SAFe experience required, 3-5 years as Scrum Master, 3-5 years in Agile team, 3-5 years software development. Use Qualifications for the preferred/certifications: BA/BS degree, PMP/CSM plus, A-CSM, Azure DevOps/JIRA experience. Skills: Your Strengths & Expertise list. Benefits: How We Invest In You list. Pay: Recognizing Your Impact salary range. Schedule: none -> omit. We also need to include maybe a short paragraph about location under Requirements. Now we must remove boilerplate: EEO, equal opportunity, etc. Also remove duplicated lines, navigation, cookie/legal, application instructions. There's no explicit application instructions besides maybe "Bring your ideas..." but that's part of content. We'll keep that as part of About the role or maybe a separate paragraph. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as they appear (maybe rephrase slightly? But we should preserve meaning; we can keep them as list items. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

Shaping the Future of Lending With 30 years of fintech leadership, Origence empowers credit unions with innovative SaaS lending solutions that make lending more accessible, efficient, and competitive. We invest in our people and foster a culture of innovation, ownership, and continuous improvement. As we help shape the future of lending, we're leveraging AI to enhance the way we work and create value for our clients, and we're seeking individuals who are excited by emerging technologies and eager to use them responsibly to solve problems and drive impact. The Scrum Master will work with Agile teams that span across time zones required for operational excellence in product deliveries. Responsible for making sure a Scrum team lives by the values and practices of Scrum. Additionally, provide guidance and help educate the team in Lean, Kanban, and Scaled Agile framework (SAFe). We are in the implementation phase of the SAFe transformation journey. The scrum master will (1) ensure that the Agile process is being followed; (2) help remove blockers and impediments. (3) foster an environment to create high-performing team that generates continuous flow of value, with ongoing innovation and relentless improvement. MUST BE LOCATED IN IRVINE, CA OR ONTARIO, CA (USA)

But we need to separate location maybe into Requirements. However we can keep location in About the role but it's a requirement; but we can also move to Requirements. The instruction: do not repeat job title as heading; we can keep location in About the role but it's okay. However we might want to keep location in Requirements for clarity. Let's split: About the role: company overview and role purpose (first two paragraphs up to "The Scrum Master will work with Agile teams..." maybe). Then Responsibilities: How You'll Contribute list. Requirements: location, SAFe experience required, years experience. Qualifications: degree, certifications, Azure DevOps/JIRA. Skills: Strengths & Expertise. Benefits: How We Invest In You list. Pay: salary range. We must not include sections with placeholder/filler text. All sections have real content. Now we need to format lists:

• for any list of duties/requirements/benefits. Thus: Responsibilities:
  • Act as a servant-leader to facilitate and support teams in the day-to-day operation of their agile practices.
  ... etc. We need to capture all bullet points from "How You'll Contribute". Let's extract them: - Act as a servant-leader to facilitate and support teams in the day-to-day operation of their agile practices. - Actively facilitate team events like Daily Stand Up, Sprint Planning, Sprint Review and Sprint Retrospective. - Actively facilitate activities such as backlog refinement, in order to maintain a healthy backlog. - Facilitate/help with program events breakouts during PI planning, system demo, problem solving during I&A. - Support the team in identifying and help the team in addressing impediments that prevent the team from achieving the sprint goals. - Take action where necessary to remove the impediments. - Drive improvements through retrospectives by deriving insights from data and dashboards. - Keeps up to date with sprint board and team deliverables to act as the team representative in the Scum of Scrum. (Note typo "Scum" but keep as is.) - Helps achieve transparency and conflict resolution. - Monitors and tracks the risks while not having the ownership of the risk itself. - Build a trusting, safe environment within the team where problems can be raised without fear of blame, retribution, or being judged. - Assist with internal and external communication, improving transparency and making information visible. - Coaching and mentoring support to teams or individuals to help improve performance and achieve goals. - Provide training to impart or reinforce knowledge of Lean-Agile concepts, tools and practices. - Provide support with risk management, release management, and facilitate release planning activities maintaining and improving the flow of value delivery. We need to preserve exactly as written, but we can correct obvious typos? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Should we keep typos? Probably keep as is, but we could keep the text exactly as given. The typo "Scum of Scrum" is in original; we should keep it. Now Requirements list: - MUST BE LOCATED IN IRVINE, CA OR ONTARIO, CA (USA) (maybe we keep uppercase) - Experience in SAFe (Scaled Agile Framework), or any scaled environment is required - 3-5 years of experience in a software development environment - 3-5 years working in an Agile team - 3-5 years of experience as a Scrum Master We could also include that the Scrum Master will ensure Agile process followed etc but that's more responsibility. Now Qualifications list: - BA/BS degree in a technical or related field - Project Management Professional (PMP) and Certified Scrum Master (CSM) are a plus - Advanced Certified Scrum Master (A-CSM) Certified - Experience with Azure DevOps, and/or JIRA Now Skills list (Your Strengths & Expertise): -