Senior Functional Analyst - II

We need to produce HTML fragment with sections: About the role? Not present. Responsibilities (Essential Duties and Responsibilities). Requirements (Required Skills and Experience). Possibly Qualifications? Could combine. Also Pay (Salary Range). Benefits? Not given. Schedule? Not given (Full Time). Could include Schedule if present: "Full Time". That's schedule info. Should we include Schedule section? The rule: include a section ONLY when posting has real, specific content for it. It says "Full Time" under Type. That's schedule info. So we can include Schedule section with

Full Time

. Pay section: Salary Range given. Include Pay section with that range. Benefits: none given, so omit. About the role: maybe not explicit; we could skip. Could include a brief intro paragraph about the role? The instruction: Use

for prose. We could include a short paragraph summarizing the role from the first sentences: "Syms Strategic Group (SSG) is seeking a talented 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". But we should not repeat job title as heading. We can include a paragraph with that info. However we already have Pay and Schedule sections; we could put location, department, type, clearance in a short paragraph under About the role or similar. But we need to avoid filler. Let's create sections: Responsibilities, Requirements, Pay, Schedule. Possibly also Qualifications? The Required Skills and Experience could be Requirements. Could also include Qualifications (certifications, education). But we can combine. We must preserve all substantive information. So we need to include all duties, responsibilities, required skills, experience, certifications desired, education, citizenship, security clearance, location remote, department Veterans Affairs, full time, salary range, etc. We must not include boilerplate like EEO, etc. Remove duplicated lines. We need to output only HTML fragment. Let's structure:

Responsibilities

• ... each duty as li

We have many duties; we need to list them as separate li items. Ensure we preserve all. Then

Requirements

• ... each requirement

We need to include: Must possess strong background in software development and Agile/SAFe methodologies; excellent oral/written communication; attention to detail, customer service, problem-solving; past experience conducting independent research; advanced experience with MS Office including Excel; excellent analytical skills; expertise with JIRA tools; experience in large Agile software development or data integration projects; professional certifications none required; years of professional experience 10 years (additional 10 years may be substituted for education); desired experience: working in Agile environment; working knowledge of VA’s Veterans Independence Program (VIP); VA SQA Testing experience; CSM or PSM; experience working for a Federal Health Agency; healthcare billing and claims processing application knowledge; formal education Master’s degree in Engineering or related scientific/technical discipline; citizenship requirement U.S. Citizenship required; security clearance Public Trust (MBI); location remote; department Veterans Affairs; full time; etc. We also have notes about CRITICAL NOTES etc. Those are not requirements but maybe include as a note? Could be omitted as boilerplate? It's about screening questions etc. Might be considered substantive? It says "CRITICAL NOTSS: SSG will not make assumptions regarding your qualifications..." This is important for applicants. Should we include? It's not exactly a requirement but a note. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include that note as a paragraph maybe under a section like "Important Notes". But we don't have a heading for that; we could create a section "Important Notes" but rule says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we could still use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. But we could embed the note in a

under Requirements or maybe under a generic section like "Notes". However to be safe, we could include it as a paragraph under Requirements or maybe under a separate

Important Notes

but that deviates from examples. Might be okay but risk. Better to incorporate into Requirements as a note. Also we have "If you have previously applied to Syms Strategic Group (SSG), there is no need to reapply. Applications are still under review. Military Veterans are highly encouraged to apply!" That's substantive; we could include as a paragraph under a section like "Application Info" but not in allowed headings. Could embed in a

after responsibilities maybe. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The lines about previously applied, military veterans encouraged are not boilerplate; they are specific to the posting. So we should keep them. Thus we need to include a paragraph with that info. Let's craft:

Syms Strategic Group (SSG) is seeking a talented Senior Functional Analyst - II. This is a remote position within the Veterans Affairs department, full‑time, requiring a Public Trust (MBI) clearance. Salary range: $78,167 – $103,855.

Then Responsibilities section. Then Requirements section. Then Pay section: maybe we already included salary in intro; but we should still have Pay section per rule: include only when posting has real content. We have salary range, so we can have Pay section with that. Schedule section: Full Time. We could also include Location and Department maybe in intro. Let's produce:

Responsibilities

• 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

Requirements

• 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
• Must possess 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
• Professional certifications: none required
• Years of professional experience: 10 years (an additional 10 years of experience may be substituted for education)
• Desired experience: working in an Agile environment
• Desired experience: working knowledge of VA’s Veterans Independence Program (VIP)
• Desired experience: VA SQA Testing experience
• Desired experience: Certified Scrum Master (CSM) or Professional Scrum Master (PSM)
• Desired experience: experience working for a Federal Health Agency (VA, DHA, HHS, etc.)
• Desired experience: 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: Must possess or qualify for a Public Trust (MBI)
• Note: SSG will not make assumptions regarding your qualifications; answers to mandatory screening questions must be supported by your resume. Applications with inconsistencies will not be considered. Recruiters or third parties will not be considered.
• Military veterans are highly encouraged to apply!
• If you have previously applied to Syms Strategic Group (SSG), there is no need to reapply; applications are still under review.

Pay

Salary range: $78,167 – $103,855

Schedule

Full Time

We also need to include location remote and department Veterans Affairs maybe in intro paragraph. Already we have intro paragraph? We didn't include yet. Let's add a leading paragraph before sections.

Syms Strategic Group (SSG) is seeking a talented Senior Functional Analyst – II. This is a remote position within the Veterans Affairs department, full‑time, requiring a Public Trust (MBI) clearance.

But we already have Pay and Schedule sections; we could keep that intro. Make sure not to repeat job title as heading; we didn't. Check for any duplicated lines: we have "Military veterans are highly encouraged to apply!" and "If you have