Intermediate Systems Analyst
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate. The posting includes:
- Duration: 12 months to start (maybe minor metadata, can be folded into short
or drop it). Probably we can include as a short paragraph.
- Job Description paragraph: "The Intermediate Systems Analyst will work with the client to support the business teams in monitoring system effectiveness and implementing system changes. This includes performing system analysis, UAT validations for new change requests/ production incidents covering the business requirements, which includes coordination with State vendors and interfaces/ other partners. Coordinating design sessions, gathering and detailing specific application or project requirements. Identifying the business workers and entities required, and defining the responsibilities, operations, attributes, process flows and relationships necessary to realize the business objectives of the project. Producing both functional and process requirements and documentation necessary to design and build the system. This includes assistance with data requests. Performs ad hoc data script validations, notice review in live environment ensuring the quality of changes being made. Performs KPI validations and automate the standard queries using SQL to efficiently verify data points/ internal QC validations. Works closely with the program admin team to support collection of required data for federal agencies. Performs data analysis and prepares documentation, provides demonstrations to federal agencies, when required. Also, responsibilities include working with the operations team on an ad-hoc basis to review the case issues. Monitoring and tracking incident tickets ensuring the resolution from a business standpoint. Coordinating with tier-II team to handle the case issues and suggesting corrections to ensure timely case processing."
- Required Skills: a long list of abilities.
- Supplemental Information: repeats many responsibilities.
We need to decide sections: Possibly "About the role" (could be the job description paragraph). "Responsibilities" could be list of duties from description and supplemental. "Requirements" could be required skills? Actually "Requirements" maybe for education/experience. "Qualifications" maybe for degree. "Skills" for technical skills. But we must not create thin sections; prefer few substantive sections.
We could combine: "About the role" (description), "Responsibilities" (list of duties), "Requirements and Qualifications" (experience, education), "Skills" (technical skills). But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with content.
We have content for About the role (description). Responsibilities (list). Requirements (experience: 5-7 years). Qualifications (Bachelor's degree or higher preferred). Skills (list of abilities). No Benefits, Pay, Schedule.
We must not repeat job title as heading. Also not include Job ID etc.
We need to use
- for any list of duties/requirements/benefits. So for Responsibilities we can list bullet points derived from description. For Skills we can list bullet points. For Requirements maybe bullet points (experience). For Qualifications maybe bullet (degree). Ensure we preserve all substantive information; do not invent or summarize away detail. That means we should not condense too much; we need to keep the details. However we can bullet each responsibility item as separate
- preserving the detail sentences. That's okay.
We must not create placeholder text like "commensurate with experience". Avoid that.
We need to parse the description into responsibility bullets. Let's extract distinct responsibilities:
- Work with client to support business teams in monitoring system effectiveness and implementing system changes.
- Perform system analysis.
- Perform UAT validations for new change requests/production incidents covering business requirements, including coordination with State vendors and interfaces/other partners.
- Coordinate design sessions.
- Gather and detail specific application or project requirements.
- Identify business workers and entities required, and define responsibilities, operations, attributes, process flows and relationships necessary to realize business objectives.
- Produce functional and process requirements and documentation necessary to design and build the system (including assistance with data requests).
- Perform ad hoc data script validations, notice review in live environment ensuring quality of changes.
- Perform KPI validations and automate standard queries using SQL to efficiently verify data points/internal QC validations.
- Work closely with program admin team to support collection of required data for federal agencies.
- Perform data analysis and prepare documentation, provide demonstrations to federal agencies when required.
- Work with operations team on ad-hoc basis to review case issues.
- Monitor and track incident tickets ensuring resolution from business standpoint.
- Coordinate with tier-II team to handle case issues and suggest corrections to ensure timely case processing.
That's a lot; we can keep them as bullet points.
Now Required Skills list: It's a paragraph with many abilities separated by periods. We need to break into bullet points preserving each ability.
Let's extract:
- 5-7 years of experience with: System analysis, UAT, ability to understand the change and handle test design and execution of test cases.
- Identification and generation of data reports from backend data repository.
- Ability to work with Integrated eligibility system, with minimum guidance.
- Self-motivation to upgrade the knowledge related to state policy documents and verify if the data is in line with the policy guidelines.
- Ability to convert the policy or business requirements into a verifiable and reusable data query script to identify and report any issues.
- Ability to validate KPI (key performance Indicators) metrics.
- Ability to support field operations team when required.
- Ability to involve and guide the system design sessions.
- Ability to prepare documentation for demonstration of application changes to the state leadership.
- Ability to work with different vendors and other state agencies to support integration of systems and validation of files, data.
- Good knowledge of SQL to review queries and validate the data script results.
- Ability to guide design for a large health and human service software application suite.
- Problem identification and integration of technical skills to resolve issues.
- Ability to translate and communicate highly technical concepts to both technical personnel and non-IT business users.
- Flexibility/adaptability and ability to develop relationships/partnerships by responding to urgent needs.
- Ability to independently identify and develop solutions/test plans procedures and job aids to support new business processes.
- Experience in business process analysis (Use Cases and/or process flows) and mapping (Gap Analysis) techniques.
- SQL or other query languages.
- Ability to generate ad hoc reports using visualization tools. (Tableau Preferred).
- Health and Human Service programs and associated business processes of a social services organization.
- Ability to establish and maintain effective working relationships.
- Ability to organize, prioritize and follow complex and detailed technical and financial procedures.
- Excellent oral and written communications.
- Bachelor s degree or higher preferred.
But note Bachelor's degree appears also in Supplemental Information; we can treat as qualification.
We need to avoid duplication. The Supplemental Information repeats many responsibilities; we should not duplicate content. We should preserve all substantive information but not duplicate identical sentences. We can combine responsibilities from both sections, but ensure we don't repeat same bullet. We'll just use the description responsibilities; supplemental info is largely same; we can ignore duplicates.
Now we need to output HTML fragment.
Structure:
Duration: 12 months to start.
maybe.
Then About the role
... description paragraph ...
Then Responsibilities
- ... each responsibility ...
Then Requirements
- ... experience bullet ...
Then Qualifications
- ... Bachelor's degree or higher preferred.
Then Skills
- ... each skill bullet ...
We must not include Benefits, Pay, Schedule.
Check that we didn't invent or summarize away detail: we kept each bullet as a sentence from original. Ensure we didn't lose any nuance.
Let's craft bullets precisely.
Responsibilities bullets (from description):
1. Work with the client to support the business teams in monitoring system effectiveness and implementing system changes.
2. Perform system analysis.
3. Perform UAT validations for new change requests/production incidents covering the business requirements, including coordination with State vendors and interfaces/other partners.
4. Coordinate design sessions.
5. Gather and detail specific application or project requirements.
6. Identify the business workers and entities required, and define the responsibilities, operations, attributes, process flows and relationships necessary to realize the business objectives of the project.
7. Produce both functional and process requirements and documentation necessary to design and build the system (including assistance with data requests).
8. Perform ad hoc data script validations, notice review in live environment ensuring the quality of changes being made.
9. Perform KPI validations and automate the standard queries using SQL to efficiently verify data points/internal QC validations.
10. Work closely with the program admin team to support collection of required data for federal agencies.
11. Perform data analysis and prepare documentation, provide demonstrations to federal agencies when required.
12. Work with the operations team on an ad-hoc basis to review the case issues.
13. Monitor and track incident tickets ensuring the resolution from a business standpoint.
14. Coordinate with tier-II team to handle the case issues and suggest corrections to ensure timely case processing.
Now Requirements bullet: "5-7 years of experience with: System analysis, UAT, ability to understand the change and handle test design and execution of test cases." Actually that's a skill but also experience. We could separate experience as requirement: "5-7 years of experience in system analysis, UAT, test design and execution." But we need to preserve detail. Let's keep as: "5-7 years of experience with system analysis, UAT, ability to understand the change and handle test design and execution of test cases."
Qualifications bullet: "Bachelor's degree or higher preferred."
Skills bullets: list each ability from Required Skills (excluding the experience bullet maybe). But we need to avoid duplication with responsibilities. We'll list all distinct skill statements.
Let's extract from Required Skills paragraph after the first sentence (which we used for experience). The paragraph: "5-7 years of experience with: System analysis, UAT, ability to understand the change and handle test design and execution of test cases. Identification and generation of data reports from backend data repository. Ability to work with Integrated eligibility system, with minimum guidance. Self-motivation to upgrade the knowledge related to state policy documents and verify if the data is in line with the policy guidelines. Ability to convert the policy or business requirements into a verifiable and reusable data query script to identify and report any issues. Ability to validate KPI (key performance Indicators) metrics. Ability to support field operations team when required. Ability to involve and guide the system design sessions. Ability to prepare documentation for demonstration of application changes to the state leadership. Ability to work with different vendors and other state agencies to support integration of systems and validation of files, data. Good knowledge of SQL to review queries and validate the data script results. Ability to guide design for a large health and human service software application suite. Problem identification and integration of technical skills to resolve issues. Ability to translate and communicate highly technical concepts to both technical personnel and non-IT business usersFlexibility/adaptability and ability to develop relationships/partnerships by responding to urgent needs. Ability to independently identify and develop solutions/test plans procedures and job aids to support new business processes. Experience in business process analysis (Use Cases and/or process flows) and mapping (Gap Analysis) techniques.SQL or other query languages. Ability to generate ad hoc reports using visualization tools. (Tableau Preferred). Health and Human Service programs and associated business processes of a social services organization. Ability to establish and maintain effective working relationships. Ability to organize, prioritize and follow complex and detailed technical and financial procedures. Excellent oral and written communications. Bachelor s degree or
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate. The posting includes: - Duration: 12 months to start (maybe minor metadata, can be folded into short
or drop it). Probably we can include as a short paragraph. - Job Description paragraph: "The Intermediate Systems Analyst will work with the client to support the business teams in monitoring system effectiveness and implementing system changes. This includes performing system analysis, UAT validations for new change requests/ production incidents covering the business requirements, which includes coordination with State vendors and interfaces/ other partners. Coordinating design sessions, gathering and detailing specific application or project requirements. Identifying the business workers and entities required, and defining the responsibilities, operations, attributes, process flows and relationships necessary to realize the business objectives of the project. Producing both functional and process requirements and documentation necessary to design and build the system. This includes assistance with data requests. Performs ad hoc data script validations, notice review in live environment ensuring the quality of changes being made. Performs KPI validations and automate the standard queries using SQL to efficiently verify data points/ internal QC validations. Works closely with the program admin team to support collection of required data for federal agencies. Performs data analysis and prepares documentation, provides demonstrations to federal agencies, when required. Also, responsibilities include working with the operations team on an ad-hoc basis to review the case issues. Monitoring and tracking incident tickets ensuring the resolution from a business standpoint. Coordinating with tier-II team to handle the case issues and suggesting corrections to ensure timely case processing." - Required Skills: a long list of abilities. - Supplemental Information: repeats many responsibilities. We need to decide sections: Possibly "About the role" (could be the job description paragraph). "Responsibilities" could be list of duties from description and supplemental. "Requirements" could be required skills? Actually "Requirements" maybe for education/experience. "Qualifications" maybe for degree. "Skills" for technical skills. But we must not create thin sections; prefer few substantive sections. We could combine: "About the role" (description), "Responsibilities" (list of duties), "Requirements and Qualifications" (experience, education), "Skills" (technical skills). But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include only those with content. We have content for About the role (description). Responsibilities (list). Requirements (experience: 5-7 years). Qualifications (Bachelor's degree or higher preferred). Skills (list of abilities). No Benefits, Pay, Schedule. We must not repeat job title as heading. Also not include Job ID etc. We need to use
- for any list of duties/requirements/benefits. So for Responsibilities we can list bullet points derived from description. For Skills we can list bullet points. For Requirements maybe bullet points (experience). For Qualifications maybe bullet (degree). Ensure we preserve all substantive information; do not invent or summarize away detail. That means we should not condense too much; we need to keep the details. However we can bullet each responsibility item as separate
- preserving the detail sentences. That's okay.
We must not create placeholder text like "commensurate with experience". Avoid that.
We need to parse the description into responsibility bullets. Let's extract distinct responsibilities:
- Work with client to support business teams in monitoring system effectiveness and implementing system changes.
- Perform system analysis.
- Perform UAT validations for new change requests/production incidents covering business requirements, including coordination with State vendors and interfaces/other partners.
- Coordinate design sessions.
- Gather and detail specific application or project requirements.
- Identify business workers and entities required, and define responsibilities, operations, attributes, process flows and relationships necessary to realize business objectives.
- Produce functional and process requirements and documentation necessary to design and build the system (including assistance with data requests).
- Perform ad hoc data script validations, notice review in live environment ensuring quality of changes.
- Perform KPI validations and automate standard queries using SQL to efficiently verify data points/internal QC validations.
- Work closely with program admin team to support collection of required data for federal agencies.
- Perform data analysis and prepare documentation, provide demonstrations to federal agencies when required.
- Work with operations team on ad-hoc basis to review case issues.
- Monitor and track incident tickets ensuring resolution from business standpoint.
- Coordinate with tier-II team to handle case issues and suggest corrections to ensure timely case processing.
That's a lot; we can keep them as bullet points.
Now Required Skills list: It's a paragraph with many abilities separated by periods. We need to break into bullet points preserving each ability.
Let's extract:
- 5-7 years of experience with: System analysis, UAT, ability to understand the change and handle test design and execution of test cases.
- Identification and generation of data reports from backend data repository.
- Ability to work with Integrated eligibility system, with minimum guidance.
- Self-motivation to upgrade the knowledge related to state policy documents and verify if the data is in line with the policy guidelines.
- Ability to convert the policy or business requirements into a verifiable and reusable data query script to identify and report any issues.
- Ability to validate KPI (key performance Indicators) metrics.
- Ability to support field operations team when required.
- Ability to involve and guide the system design sessions.
- Ability to prepare documentation for demonstration of application changes to the state leadership.
- Ability to work with different vendors and other state agencies to support integration of systems and validation of files, data.
- Good knowledge of SQL to review queries and validate the data script results.
- Ability to guide design for a large health and human service software application suite.
- Problem identification and integration of technical skills to resolve issues.
- Ability to translate and communicate highly technical concepts to both technical personnel and non-IT business users.
- Flexibility/adaptability and ability to develop relationships/partnerships by responding to urgent needs.
- Ability to independently identify and develop solutions/test plans procedures and job aids to support new business processes.
- Experience in business process analysis (Use Cases and/or process flows) and mapping (Gap Analysis) techniques.
- SQL or other query languages.
- Ability to generate ad hoc reports using visualization tools. (Tableau Preferred).
- Health and Human Service programs and associated business processes of a social services organization.
- Ability to establish and maintain effective working relationships.
- Ability to organize, prioritize and follow complex and detailed technical and financial procedures.
- Excellent oral and written communications.
- Bachelor s degree or higher preferred.
But note Bachelor's degree appears also in Supplemental Information; we can treat as qualification.
We need to avoid duplication. The Supplemental Information repeats many responsibilities; we should not duplicate content. We should preserve all substantive information but not duplicate identical sentences. We can combine responsibilities from both sections, but ensure we don't repeat same bullet. We'll just use the description responsibilities; supplemental info is largely same; we can ignore duplicates.
Now we need to output HTML fragment.
Structure:
Duration: 12 months to start.
maybe. ThenAbout the role
... description paragraph ...
ThenResponsibilities
- ... each responsibility ...
Requirements
- ... experience bullet ...
Qualifications
- ... Bachelor's degree or higher preferred.
Skills
- ... each skill bullet ...