Business Analyst
Metas Solutions · Atlanta, GA · 3 wk ago
AnalystFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us" and "Job Description". We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to extract content.
Let's parse the posting:
- About Us: description of company. Could map to "About the role"? Actually "About Us" is about company, not role. The instruction says use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to extract content.
Let's parse the posting:
- About Us: description of company. Could map to "About the role"? Actually "About Us" is about company, not role. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings if content exists. "About the role" could be derived from Job Description paragraph: "Metas Solutions has an 'immediate opening' for a talented Business Analyst to support public health analytic initiatives for government health agencies within an Agile delivery framework. Serve as the bridge between business stakeholders and technical teams, translating business needs into well-structured, testable requirements while ensuring alignment with Agile principles and practices. Formulate and define systems scope and objectives through research, fact-finding, and a comprehension of applicable business systems and industry requirements. Conduct qualitative analysis of existing implementations and provide thoughtful, strategic improvement recommendations. Identify gaps in processes and opportunities for improvement and automation."
That's a description of the role. So we can put that under About the role
as
About the role
as. Then Responsibilities: list bullet points: "Translate business needs into clear testable technical requirements", "Lead Agile-based requirements and backlog management activities", "Analyze business processes and identify improvement opportunities", "Support User Acceptance Testing and cross-team alignment". Use
- .
Then Qualifications: The posting has a "Qualifications" section with bullet points (actually a list of qualifications). It includes many bullet-like sentences. We need to decide if we treat them as Qualifications or Requirements. The instruction includes both Requirements and Qualifications headings. We need to split content appropriately. The posting has "Qualifications" heading then a list of items. Also there is "Additional Qualifications". Also "Security Requirements". Also "Must be US Citizen and with the ability to obtain a US Government security clearance (Public Trust 5) within a reasonable period". Also "Market competitive salary, commensurate with experience and education" (Pay). Also "Comprehensive benefits package available, Medical, Dental, Vision and Life Insurance, Paid Time Off (PTO), 401K with company match, growth, and promotion opportunities" (Benefits). Also "Notice on Candidate AI Usage" and EEO etc which we should remove (boilerplate). Also "See www.metassolutions.com for further details about us and careers with Metas." That's maybe not needed.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the "Notice on Candidate AI Usage", "We are an Equal Opportunity Employer/Veterans/Disabled". Also maybe remove "See www.metassolutions.com for further details about us and careers with Metas." That's not boilerplate but maybe considered navigation? It's a link to careers; could be considered extra but it's substantive? It's just a pointer; maybe we can keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to careers might be considered navigation; but it's not a boilerplate. However it's not essential to the job description; but it's not duplicated. I'd consider it navigation and remove. Safer to remove.
Now we need to map content to headings:
- About the role: we have the paragraph after "Job Description". Use that.
- Responsibilities: the bullet list under "Responsibilities". Use that.
- Requirements: maybe we can treat the core qualifications (the first list under "Qualifications") as Requirements. Then Additional Qualifications as Skills? Or Qualifications? The instruction includes both Requirements and Qualifications headings. We need to decide what goes where. Typically Requirements are mandatory qualifications; Qualifications could be preferred. The posting has "Qualifications" then a list of items (looks like requirements). Then "Additional Qualifications" (preferred). Then "Security Requirements". Then "Market competitive salary..." (Pay). Then "Comprehensive benefits package..." (Benefits). No explicit Schedule.
Thus we can map:
- Requirements: the list under "Qualifications" (the first set). Use
- .
- Qualifications: the list under "Additional Qualifications". Use
- .
- Skills: maybe we could combine some skill items from Additional Qualifications? But we already have Qualifications heading; we could also have Skills heading if we want to separate technical skills. However we should not create thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Additional Qualifications into Qualifications heading (since both are qualifications). But we have already used Qualifications for the first list; we could rename first list as Requirements and second list as Qualifications (preferred). That seems reasonable.
- Benefits: we have benefits description. Use
- for each benefit? The posting says "Comprehensive benefits package available, Medical, Dental, Vision and Life Insurance, Paid Time Off (PTO), 401K with company match, growth, and promotion opportunities". That's a sentence; we could split into list items: Medical, Dental, Vision, Life Insurance, Paid Time Off (PTO), 401K with company match, growth, promotion opportunities. We'll output as
- each.
- Pay: "Market competitive salary, commensurate with experience and education". This is vague but it's actual statement. The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state "Market competitive salary, commensurate with experience and education". That's not a specific number but it's a statement. Is that considered filler? It says "commensurate with experience and education" which is a placeholder-like phrase. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should NOT create a Pay section because the content is just that placeholder phrase. So we omit Pay.
- Schedule: not mentioned, so omit.
- Security Requirements: Could be part of Requirements or Qualifications? It's a requirement: "Must be US Citizen and with the ability to obtain a US Government security clearance (Public Trust 5) within a reasonable period". This is a substantive requirement. We could include it under Requirements list as an item. Or we could create a separate section? But we already have Requirements; we can add it there.
- Also "Must be a U.S. Citizen or Lawful Permanent Resident (Green Card Holder)" is also a requirement. That's also under Qualifications list originally. Actually that appears in the Qualifications list: "Must be a U.S. Citizen or Lawful Permanent Resident (Green Card Holder)". So we already have that.
Thus we need to combine all requirement-like items: the list under Qualifications (including citizenship, experience, Agile, Jira, etc.) plus the Security Requirements item.
Now we need to ensure we don't duplicate lines. Let's extract the Qualifications list exactly:
From posting:
Qualifications
3+ years of experience working directly with business system users to elicit and document complete, accurate, and testable requirements, including capturing solid acceptance criteria from the Product Owner (PO)
Experience working within an Agile delivery framework, with a strong understanding of Agile principles, ceremonies, and artifacts
Experience using Jira for requirements documentation, backlog management, and logging defects, including creating, deleting, and updating stories following PO approval
Ability to conduct requirements gathering sessions with client stakeholders using interviews, document analysis, business process descriptions, use cases, scenarios, and workflow analysis, and to actively listen to stakeholder needs and document all requests
Ability to document business, functional, and non-functional requirements and system touchpoints, including reporting, dashboard, and workflow requirements, and to translate requirements into technical specifications
Ability to help the business break requirements down into small, valuable stories with clear user acceptance criteria and business rules, and to ensure stories, test cases, and business rules are clear and understood by developers during the iteration
Ability to understand and document business processes and develop as-is and to-be process flow diagrams, and to organize requirement artifacts into an accessible centralized repository
Ability to obtain and maintain a Public Trust or Suitability/Fitness determination based on client requirements
Bachelor's degree
Must be a U.S. Citizen or Lawful Permanent Resident (Green Card Holder)
Then after that: Additional Qualifications
Experience writing user stories for health data and analytic systems
Experience serving as Scrum Master
Knowledge of data structures, relational databases, data lineage, and data governance principles
Experience supporting User Acceptance Testing (UAT) by providing the UAT plan and scripts, facilitating UAT sessions, providing results, obtaining Product Owner signatures, and validating solutions during production deployment
Professional certification such as Certified Business Analysis Professional (CBAP), PMI-PBA, or a recognized Agile certification
Security Requirements
Must be US Citizen and with the ability to obtain a US Government security clearance (Public Trust 5) within a reasonable period
Then Pay/Benefits etc.
We need to avoid duplication: The citizenship appears twice: once in Qualifications (Must be a U.S. Citizen or Lawful Permanent Resident (Green Card Holder)) and again in Security Requirements (Must be US Citizen and with the ability to obtain a US Government security clearance (Public Trust 5) within a reasonable period). They are not identical; one is citizenship/green card, the other is citizenship plus ability to obtain clearance. Both are substantive; we should keep both.
Now we need to format as HTML.
We'll produce:
About the role
Metas Solutions has an "immediate opening" for a talented Business Analyst to support public health analytic initiatives for government health agencies within an Agile delivery framework. Serve as the bridge between business stakeholders and technical teams, translating business needs into well-structured, testable requirements while ensuring alignment with Agile principles and practices. Formulate and define systems scope and objectives through research, fact-finding, and a comprehension of applicable business systems and industry requirements. Conduct qualitative analysis of existing implementations and provide thoughtful, strategic improvement recommendations. Identify gaps in processes and opportunities for improvement and automation.
Responsibilities
- Translate business needs into clear testable technical requirements
- Lead Agile-based requirements and backlog management activities
- Analyze business processes and identify improvement opportunities
- Support User Acceptance Testing and cross-team alignment
Requirements
- 3+ years of experience working directly with business system users to elicit and document complete, accurate, and testable requirements, including capturing solid acceptance criteria from the Product Owner (PO)
- Experience working within an Agile delivery framework, with a strong understanding of Agile principles, ceremonies, and artifacts
- Experience using Jira for requirements documentation, backlog management, and logging defects, including creating, deleting, and updating stories following PO approval
- Ability to conduct requirements gathering sessions with client stakeholders using interviews, document analysis, business process descriptions, use cases, scenarios, and workflow analysis, and to actively listen to stakeholder needs and document all requests
- Ability to document business, functional, and non-functional requirements and system touchpoints, including reporting, dashboard, and workflow requirements, and to translate requirements into technical specifications
- Ability to help the business break requirements down into small, valuable stories with clear user
- each.
- Pay: "Market competitive salary, commensurate with experience and education". This is vague but it's actual statement. The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state "Market competitive salary, commensurate with experience and education". That's not a specific number but it's a statement. Is that considered filler? It says "commensurate with experience and education" which is a placeholder-like phrase. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should NOT create a Pay section because the content is just that placeholder phrase. So we omit Pay.
- Schedule: not mentioned, so omit.
- Security Requirements: Could be part of Requirements or Qualifications? It's a requirement: "Must be US Citizen and with the ability to obtain a US Government security clearance (Public Trust 5) within a reasonable period". This is a substantive requirement. We could include it under Requirements list as an item. Or we could create a separate section? But we already have Requirements; we can add it there.
- Also "Must be a U.S. Citizen or Lawful Permanent Resident (Green Card Holder)" is also a requirement. That's also under Qualifications list originally. Actually that appears in the Qualifications list: "Must be a U.S. Citizen or Lawful Permanent Resident (Green Card Holder)". So we already have that.
Thus we need to combine all requirement-like items: the list under Qualifications (including citizenship, experience, Agile, Jira, etc.) plus the Security Requirements item.
Now we need to ensure we don't duplicate lines. Let's extract the Qualifications list exactly:
From posting:
Qualifications
3+ years of experience working directly with business system users to elicit and document complete, accurate, and testable requirements, including capturing solid acceptance criteria from the Product Owner (PO)
Experience working within an Agile delivery framework, with a strong understanding of Agile principles, ceremonies, and artifacts
Experience using Jira for requirements documentation, backlog management, and logging defects, including creating, deleting, and updating stories following PO approval
Ability to conduct requirements gathering sessions with client stakeholders using interviews, document analysis, business process descriptions, use cases, scenarios, and workflow analysis, and to actively listen to stakeholder needs and document all requests
Ability to document business, functional, and non-functional requirements and system touchpoints, including reporting, dashboard, and workflow requirements, and to translate requirements into technical specifications
Ability to help the business break requirements down into small, valuable stories with clear user acceptance criteria and business rules, and to ensure stories, test cases, and business rules are clear and understood by developers during the iteration
Ability to understand and document business processes and develop as-is and to-be process flow diagrams, and to organize requirement artifacts into an accessible centralized repository
Ability to obtain and maintain a Public Trust or Suitability/Fitness determination based on client requirements
Bachelor's degree
Must be a U.S. Citizen or Lawful Permanent Resident (Green Card Holder)
Then after that: Additional Qualifications
Experience writing user stories for health data and analytic systems
Experience serving as Scrum Master
Knowledge of data structures, relational databases, data lineage, and data governance principles
Experience supporting User Acceptance Testing (UAT) by providing the UAT plan and scripts, facilitating UAT sessions, providing results, obtaining Product Owner signatures, and validating solutions during production deployment
Professional certification such as Certified Business Analysis Professional (CBAP), PMI-PBA, or a recognized Agile certification
Security Requirements
Must be US Citizen and with the ability to obtain a US Government security clearance (Public Trust 5) within a reasonable period
Then Pay/Benefits etc.
We need to avoid duplication: The citizenship appears twice: once in Qualifications (Must be a U.S. Citizen or Lawful Permanent Resident (Green Card Holder)) and again in Security Requirements (Must be US Citizen and with the ability to obtain a US Government security clearance (Public Trust 5) within a reasonable period). They are not identical; one is citizenship/green card, the other is citizenship plus ability to obtain clearance. Both are substantive; we should keep both.
Now we need to format as HTML.
We'll produce:
- for each benefit? The posting says "Comprehensive benefits package available, Medical, Dental, Vision and Life Insurance, Paid Time Off (PTO), 401K with company match, growth, and promotion opportunities". That's a sentence; we could split into list items: Medical, Dental, Vision, Life Insurance, Paid Time Off (PTO), 401K with company match, growth, promotion opportunities. We'll output as
- .
- Skills: maybe we could combine some skill items from Additional Qualifications? But we already have Qualifications heading; we could also have Skills heading if we want to separate technical skills. However we should not create thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Additional Qualifications into Qualifications heading (since both are qualifications). But we have already used Qualifications for the first list; we could rename first list as Requirements and second list as Qualifications (preferred). That seems reasonable.
- Benefits: we have benefits description. Use
- .
- Qualifications: the list under "Additional Qualifications". Use