IT Business Analyst
Leaf Home · Toledo, OH · 3 wk ago
Information TechnologyFull-time
We need to output HTML fragment with sections: About the role? The posting includes "About Leaf Home" and "Why Leaf Home" etc. But we must use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. The posting includes "Position Summary" (which is about the role). It includes "Essential Duties And Responsibilities". It includes "Experience And Minimum Qualifications". It includes "Preferred Knowledge, Skills, Abilities Or Certifications". It includes "Travel Requirements", "Overtime/Additional Hours Requirements", "Physical Requirements". It includes "What We Offer" (benefits). It includes "Additional Perks". It includes "Awards and Recognition". It includes "Diversity and Equal Opportunity" etc. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections to include based on content.
- About the role: Could use Position Summary. So heading
About the role
with paragraph(s) from Position Summary. - Responsibilities: Use Essential Duties And Responsibilities. So headingResponsibilities
with list of duties. - Requirements: Could combine Experience And Minimum Qualifications (experience, education). So headingRequirements
with list. - Qualifications: Could be Preferred Knowledge, Skills, Abilities Or Certifications. Or maybe separate Qualifications vs Skills. The instruction says we can use Qualifications and Skills headings. We need to decide. The posting includes "Experience And Minimum Qualifications" (that's qualifications). Also "Preferred Knowledge, Skills, Abilities Or Certifications" (skills). So we can have Requirements for mandatory qualifications, and Skills for preferred skills. Or we could combine. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications? But we have both headings allowed. We could include Requirements (mandatory) and Skills (preferred). That seems reasonable. - Benefits: Use What We Offer (benefits). Also Additional Perks. So headingBenefits
with list. - Pay: Not mentioned. So we should NOT include Pay section. - Schedule: Not mentioned (no schedule details). So omit. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should exclude sections like "Diversity and Equal Opportunity", "Americans With Disabilities Act Statement", "Are We Your Company?" maybe not needed. Also "Why Leaf Home" maybe not needed as it's fluff. But we could include some of that under About the role? The instruction: "Prefer a few substantive sections over many thin ones." So we might keep only core sections: About the role (Position Summary), Responsibilities, Requirements (Experience And Minimum Qualifications), Skills (Preferred Knowledge...), Benefits (What We Offer + Additional Perks). Possibly also include "Awards and Recognition" maybe not needed as it's fluff. We'll exclude. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep the details from those sections, but we can format as lists. We must not include filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About Leaf Home description: Might be considered fluff but could be part of About the role? The instruction says we should not repeat job title as heading, but we can include About Leaf Home as part of About the role? The heading "About the role" expects description of role, not company. However we could still include some company overview under About the role? Might be considered not specific to role. Safer to stick to Position Summary for About the role. Thus About the role paragraph: "The IT Business Analyst works with business leaders, cross-functional teams, subject matter experts, and technical resources to identify business needs and define technology solutions that support organizational goals. In partnership with the IT Product Owner, the IT Business Analyst gathers, analyzes, and documents business and system requirements, translating them into clear functional and technical specifications for development teams. The role serves as a liaison between stakeholders, internal application teams, and vendors to ensure enterprise systems, such as CRM, ERP/Accounting, HCM, and data platforms, deliver solutions that meet business needs and achieve intended outcomes." Now Responsibilities: list each bullet under Essential Duties And Responsibilities. We need to preserve all details. Let's extract each duty: - Gathering & Analysis: * Partner with business stakeholders to understand business needs, pain points, and operational goals. * Elicit, analyze, and document business, functional, and system requirements. * Translate business needs into clear, actionable requirements for technical teams. - Collaboration With Product Owner: * Work closely with the Product Owner to refine product backlog items and ensure requirements support product priorities and business outcomes. * Assist in breaking down features into detailed user stories and acceptance criteria. * Provide input on scope, dependencies, and implementation considerations during backlog refinement. - Documentation & Requirements Management: * Develop and maintain clear documentation, including user stories, functional specifications, process flows, and business rules. * Ensure requirements are complete, accurate, and aligned with stakeholder expectations. * Maintain traceability between business requirements, technical solutions, and delivered functionality. - Development Support: * Serve as a point of clarification for development teams during implementation. * Participate in backlog refinement, sprint planning, and other agile ceremonies. * Help ensure that delivered solutions align with documented requirements. - Testing & Validation: * Support quality assurance and user acceptance testing (UAT) by validating that those solutions meet business and functional requirements. * Assist in developing test scenarios and validating system functionality. * Coordinate with stakeholders to confirm successful delivery of solutions. - Stakeholder Communication: * Act as a liaison between business teams, product owners, technical teams, and external vendors. * Communicate project updates, requirement changes, and potential impacts to stakeholders. * Facilitate workshops, requirement sessions, and stakeholder reviews when needed. - Enterprise Systems Support: * Contribute to the successful delivery and enhancement of enterprise applications such as CRM, ERP/Accounting, HCM, and data platforms. * Support system improvements that drive operational efficiency and business value. We need to output as- for each duty. Could group under subheadings? Not allowed; only headings are h3. So we can just list all duties as flat list. But we might lose grouping. However we must preserve ALL substantive information; grouping is not required. So we can list each duty as separate
- . Ensure we keep the text exactly.
Now Requirements: Experience And Minimum Qualifications.
Extract:
- Bachelor’s Degree preferred, or equivalent combination of education, training, and experience.
- 2+ years of experience as a Business Analyst working on multiple projects at an intermediate level.
- Experience working on large scale projects as well as handling day-to-day operational requests from the business.
- Project management, ability to successfully manage multiple tasks at any given point, strong relationship building skills & communication skills.
- Excellent communication and interpersonal skills including the ability to build consensus and to present complex presentations.
- Ability to communicate effectively, to recognize, understand, and manage one’s own emotions as well as others, and foster positive working relationships across all levels of the organization.
- Holding oneself responsible and being self-driven in accomplishing business goals, adhering to policies and being responsible for one’s own actions, performance, and decisions.
- Proficiency using Microsoft Office Suite (Outlook, Word, Excel, PowerPoint, Project, and/or Access).
- Must be legally authorized to work in country of employment without sponsorship for employment visa status (e.g., H1B status).
We need to output as list.
Now Skills: Preferred Knowledge, Skills, Abilities Or Certifications.
Extract:
- Certification in Business Analysis (ECBA).
- Certification as a Salesforce Administrator.
Also maybe "Travel Requirements No travel required." That's not skill. Overtime/Additional Hours Requirements: Additional Hours May Be Required (Exempt Positions). Physical Requirements: Normal Office Environment... That's not skill. Could be included under Skills? But they are not skills. Might be better to include under Requirements? However they are not qualifications. The instruction says we can include Skills heading for skills. Travel, overtime, physical are not skills. Could we include them under Requirements? They are not exactly requirements but could be considered job details. However we have no specific heading for those. We could omit them as they are not under allowed headings? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use those headings. It doesn't forbid other headings? It says use those for section headings. Likely we should only use those headings. So we need to fit all content into those sections. Travel, overtime, physical could be placed under Requirements or Skills? Might be considered Requirements (like travel requirement). But they'd be weird. However we could include them under Requirements as additional notes. But we must not invent headings. So we can add them as list items under Requirements. Similarly, "Travel Requirements No travel required." is a statement; we can include as a list item. "Overtime/Additional Hours Requirements Additional Hours May Be Required (Exempt Positions)" as list item. "Physical Requirements Normal Office Environment..." as list item. Now Benefits: What We Offer and Additional Perks. Extract What We Offer: - Industry-leading compensation package - Competitive medical, dental, and vision benefits after 60 days - Retirement savings plan with company match - Paid parental leave and generous paid time off programs - On-campus fitness programs and meal delivery services - Comprehensive health, wellbeing, financial wellness, and childcare benefits - Opportunities for growth and advancement Additional Perks: - Employee assistance program with 24/7 legal, financial, and counseling support - Employee discount marketplace with thousands of savings options - Flexible Gym membership - Employee resource groups, including VetConnect and the Women’s Committee Also Awards and Recognition maybe not needed. We should not include fluff like "Awards and Recognition". So we omit. Now we need to ensure we don't include any boilerplate like "Are We Your Company?" etc. Now produce HTML:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- Certification in Business Analysis (ECBA).
- Certification as a Salesforce Administrator.
- Travel Requirements: No travel required.
- Overtime/Additional Hours Requirements: Additional Hours May Be Required (Exempt Positions).
- Physical Requirements: Normal Office Environment—Indoor work in a climate-controlled environment. Sedentary work. Exerting up to 10 pounds of force occasionally and/or negligible amount of force frequently or constantly to lift, carry, push, pull or otherwise move objects, including the human body. Sedentary work involves sitting most of the time.
Benefits
- Industry-leading compensation package
- Competitive medical, dental, and vision benefits after 60 days
- Retirement savings plan with company match
- Paid parental leave and generous paid time off programs
- On-campus fitness programs and meal delivery services
- Comprehensive health, wellbeing, financial wellness, and childcare benefits
- Op