Senior Functional Analyst - II

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content. Job posting details: - Company: Syms Strategic Group (SSG) - Position: Senior Functional Analyst - II - Location: Remote - Department: Veterans Affairs - Type: Full Time - Min. Experience: Experienced - Security Clearance Level: Public Trust (MBI) - Salary Range: $78,167 - $103,855 - If previously applied, no need to reapply. - Applications still under review. - Military Veterans highly encouraged. - Essential Duties and Responsibilities: long list. - Required Skills and Experience: list. - Professional Certifications: None required. - Years of Professional Experience: 10 years (additional 10 years may be substituted for education) - Desired experience: list. - Formal Education: Master’s degree in Engineering or related scientific or technical discipline. - Citizenship Requirement: U.S. Citizenship required. - Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI) - Critical notes: SSG will not make assumptions... etc. - Recruiters or third parties not considered. - This is a 100% U.S. based remote position. However, candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered. - U.S Citizenship required. - Applicants selected will be subject to government security investigation... - Background investigation... - Equal Opportunity Employer statement. - Powered by JazzHR. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "If you have previously applied..." etc? That's application instruction? Possibly remove. Also "Applications are still under review." maybe keep? It's not instruction but meta. Might keep as part of About the role? Probably not needed. The instruction says: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove lines about previously applied, applications still under review, maybe also "Military Veterans are highly encouraged to apply!" That's encouragement but not boilerplate? Might be okay to keep as part of About the role? It's not a duty. Could be considered a note but not required. Safer to keep substantive info: duties, responsibilities, required skills, qualifications, etc. Also include salary range (Pay). Also location remote (maybe in About the role). Also department Veterans Affairs. Also type Full Time. Also security clearance. Also citizenship requirement. Also note about state restrictions (CA etc) maybe considered location restriction; could be included in About the role or Requirements? It's a restriction; maybe include in About the role or Requirements. But we should not invent sections; we can include in About the role as a note. We need sections: About the role (maybe include location, department, type, clearance, citizenship, salary? Actually salary goes to Pay section if present. We have salary range, so we should create a Pay section. Benefits: not mentioned, so omit. Schedule: not mentioned (full time is type but schedule not given). Could we treat Full Time as schedule? The instruction: include Schedule section only if posting actually states them. It states Type: Full Time, which is schedule type. Could be considered schedule. Might include Schedule section with "Full Time". But they said prefer few substantive sections over many thin ones. Might combine type into About the role. Safer to not create Schedule unless explicit schedule like "Monday-Friday, 9-5". So omit Schedule. Thus sections: About the role (location remote, department Veterans Affairs, type Full Time, security clearance Public Trust MBI, citizenship US, salary? Actually salary goes to Pay). Responsibilities (essential duties). Requirements (maybe combine required skills and experience, professional certifications, years of experience, desired experience, formal education). Qualifications maybe similar to Requirements; but we can have Requirements section covering required skills and experience, and Qualifications for certifications/education? But we have both Required Skills and Experience and Professional Certifications None required, Years of Professional Experience, Desired experience, Formal Education. Could split: Requirements (required skills/experience), Qualifications (education, certifications, years experience). However we have limited content; maybe better to have one Requirements section covering all. But we need to follow headings list; we can choose which to include. The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (covering skills, experience, education, certifications), Pay (salary). That's four sections. We must not repeat job title as heading. So no

Senior Functional Analyst - II. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all duties list verbatim? We can keep as

• each duty. Must not omit any duty. The duties list is long; we need to include each bullet. Ensure we capture all. Let's extract duties from "Essential Duties and Responsibilities" paragraph. It's a long sentence with many items separated by line breaks? Actually it's a paragraph with many items separated by line breaks? In the text, after "Essential Duties and Responsibilities" there is a line break then a list of items each starting with a verb. We need to parse them. Let's copy the duties text: "Lead the capture of business requirements for software development teams Collaborate with business users, Information Technology (IT), and leadership to elaborate and document requirements in an Application Lifecycle Management (ALM) tool Manage requirements in an ALM tool Perform Agile requirement management activities for a product team Perform the analysis of user needs to determine functional, cross-functional, and technical requirements Conduct user interviews, lead and facilitate sessions, and develop business process models and formal specifications Work with customers, team members, stakeholder users, and other contractors to gather and document business, functional, technical, and non-technical requirements Perform elaboration of user stories and decomposition of stories into backlog items and determine acceptance criteria Use an ALM tool (JIRA) for Requirements Management, Testing, and Defect Management to create and manage requirements, epics, sub-epics, and user stories Perform the collection, tracking, and monitoring of system and business requirements Validate requirements and integration Conduct backlog refinement sessions Coordinate with Systems Engineers to assess impact on technical solutions Manage and coordinate requirements for various projects Write and deliver project documents to the client Identify and manage risks and issues impacting the progress and outcome of the project Develop and maintain the scheduled project/product backlog(s) Own and manage requirements change control Develop Change Requests per established policies and procedures Facilitate accurate configuration management for project-related artifacts Identify, document, verify, and track traceability amongst requirements, test cases, and potential risks and impediments Collect, analyze, manage, and report key Program and Product Team execution status and metrics across all aspects of the Agile product development lifecycle using SAFe Perform analysis to identify required tasks and their interrelationships to establish well-documented stories Become a product functional Subject Matter Expert (SME) Lead and mentor junior analysts in accordance with strategy and direction established by the Team Lead Establish strong relationships with product and business owners Support development team as needed to help everyone understand the requirements’ details Follow Agile methodology (Scrum) and deliver requirements/specifications for Sprint teams Remove impediments from team members to achieve successful completion of Sprints Provide clear qualitative and quantitative information to teams and stakeholders Support change control processes established to monitor and control project scope" We need to ensure each is a
• . Now Required Skills and Experience list: "Must possess a strong background in software development and Agile/Scaled Agile Framework (SAFe) methodologies Must possess excellent oral and written communication skills with the demonstrated ability to communicate complex technical topics to the customer, management, and non-technical audiences Must possess excellent attention to detail, customer service skills, and problem-solving abilities Past experience conducting independent research to support the resolution of complex questions Must possess advanced experience with Microsoft (MS) Office, including Excel Must possess excellent analytical skills, including integrating information from several sources Expertise with JIRA tools Experience in large, Agile software development or data integration projects" Then Professional Certifications: None required. Years of Professional Experience: 10 years of professional (an additional 10 years of experience may be substituted for education) Desired experience list: "Experience working in an Agile environment Working knowledge of VA’s Veterans Independence Program (VIP) VA SQA Testing experience Certified Scrum Master (CSM) or Professional Scrum Master (PSM) Experience working for a Federal Health Agency (VA, DHA, HHS, etc.) Healthcare billing and claims processing application knowledge" Formal Education: Master’s degree in Engineering or a related scientific or technical discipline Citizenship Requirement: U.S. Citizenship required for this specific opportunity. Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI) Critical notes: many lines about SSG will not make assumptions, recruiters, etc. Also location restriction: candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered. Also statement about 100% U.S. based remote position. Also background investigation etc. Also EEO statement. We need to remove boilerplate: EEO/equal-opportunity/scam-warning boilerplate. The EEO statement is boilerplate; remove. Also "Powered by JazzHR" remove. Also "CRITICAL NOTES:" maybe partly boilerplate but contains substantive restrictions (state restrictions, citizenship, security investigation). We should keep substantive info: citizenship requirement already captured; security clearance captured; location restriction (state exclusions) is substantive; also "This is a 100% U.S. based remote position." is substantive about location; also "Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information and be able to obtain a government-granted security clearance." is substantive but overlaps with security clearance. Might keep as note. Also "Individuals may also be subject to a background investigation including, but not limited to criminal history, employment and education verification, drug testing, and creditworthiness." is substantive. We need to decide where to put these notes. Could be in About the role or Requirements. Probably About the role can include location, remote, citizenship, clearance, state restrictions, background investigation. But we must not duplicate. Let's structure:

  About the role

  Remote position supporting the Veterans Affairs department. Full‑time. Requires U.S. citizenship and eligibility for a Public Trust (MBI) security clearance. Candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered. Selected applicants will undergo a government security investigation and background check (criminal history, employment/education verification, drug testing, creditworthiness).

  That captures location, type, citizenship, clearance, restrictions, background. Now Responsibilities:

  Responsibilities

  • ... each duty ...
  Now Requirements: combine required skills, experience, certifications, years, desired experience, education. We need to preserve all details, not summarize away. So we need to list each bullet as
• . For items like "Must possess a strong background..." etc. Also "Professional Certifications: None required." Should we include as a bullet? It's a statement; we can include as
• None required.
but that might be weird. Could include as a sentence in

. But we need to use

• for any list of duties/requirements/benefits. This is a list of requirements; we can include each requirement as a li. For "None required" we can include as li.