Sr Analyst - IT Business Applications
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. Likely "About Your Future With QXO" corresponds to "About the role". We'll put that paragraph(s) under About the role
.
- Job Description: includes "As a Senior Business Analyst...". That's responsibilities. So we can put under Responsibilities
the bullet list of duties.
- "What You’ll Do" includes bullet points: Build Strong Business Partnerships, Deliver Business Value. Those are responsibilities.
- "What You’ll Bring" includes partnership, collaboration, drive for results, critical thinking, priority management, technical knowledge. Those could be under Requirements or Qualifications? The instruction: Use sections for Requirements, Qualifications, Skills. We need to decide where each piece goes. Typically "What You’ll Bring" are competencies/skills. Could be Skills. Also "Education And Experience" is Qualifications. "Skills for Success" is Skills. There's also "Physical Requirements" maybe under Requirements? But physical requirements maybe not needed as a separate section; could be under Requirements? But we only create sections if there is real specific content. Physical Requirements is specific: "Work is performed in a typical office environment...". Could be under Requirements or maybe a separate section but not in list. Since not in allowed headings, we could incorporate into Requirements or Qualifications? Probably under Requirements (since it's about job demands). But we have to decide.
- Compensation Range: $86,700.00 - $130,000.00 plus note about variable compensation. That's Pay section.
- Benefits: Not explicitly listed. There's no benefits description. So we should NOT create Benefits section.
- Schedule: Not mentioned. So no Schedule.
- Qualifications: Education And Experience (Bachelor's degree, 5+ years experience, etc.) plus maybe Construction industry experience preferred, Must be at least 18 years old. That's qualifications.
- Skills: "What You’ll Bring" (partnership, collaboration, drive for results, critical thinking, priority management, technical knowledge) plus "Skills for Success" (analytical, problem-solving, consensus-building, leadership, communication, troubleshooting, understanding SDLC, ability to work independently, growth mindset). Also Technical Knowledge mentioned earlier. So combine into Skills.
- Responsibilities: The "What You’ll Do" bullet points plus the earlier Job Description paragraph (partner closely..., help solve complex challenges...). Also maybe the bullet list under Build Strong Business Partnerships and Deliver Business Value.
We need to output HTML with headings and - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading. No markdown fences.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, except boilerplate (EEO, legal, navigation, cookie, etc). Also remove duplicated lines.
Let's extract substantive content.
Full text:
"About Your Future With QXO Are you looking for a career with an industry leader that drives the future of energy-efficient insulation and building material products? Look no further! At QXO, you will be part of a team that reflects our values of integrity and innovation by delivering solutions that make a difference in the communities we serve. Here, you are part of a company that rewards your contributions and encourages you to take ownership of your career."
That's prose.
"Job Description As a Senior Business Analyst, Business Applications at QXO, you will partner closely with TruTeam, Specialty Distribution, QXO business partners, and IT teams to translate strategic objectives into effective technology solutions. You will help solve complex challenges across QXO’s enterprise business applications, including Oracle E-Business Suite (EBS) and Oracle Fusion, while ensuring solutions are reliable, secure, scalable, and aligned with enterprise technology standards. This role is ideal for a collaborative, solutions-focused professional who combines strong business analysis skills with hands-on experience implementing and supporting Oracle enterprise applications."
That's prose (could be part of responsibilities).
"What You’ll Do Build Strong Business Partnerships Develop a strong understanding of core business processes, priorities, and desired outcomes.Serve as a primary liaison between business partners and IT, leading regular discussions and helping prioritize requests.Stay current on relevant technologies and business processes, recommending improvements that enhance efficiency and performance.Use data and application knowledge to measure results, identify opportunities, and support continuous improvement.Maintain a working understanding of connected applications and how data moves across the technology environment. Deliver Business Value Lead projects in accordance with IT standards and coordinate with Audit during compliance reviews.Partner with business stakeholders to gather requirements, translate them into functional specifications, and lead user testing to support high-quality delivery.Collaborate with IT developers and business analysts to implement solutions consistent with QXO’s solution delivery processes.Manage a product backlog spanning support, enhancements, and project work, confirming priorities with business partners.Help ensure applications and business processes meet security and compliance requirements through appropriate controls and documentation.Clearly communicate ideas, requirements, and technical concepts to business stakeholders and development teams.Monitor incidents and outages, communicate status, analyze trends and root causes, and drive issues through resolution.Support third-party applications, maintain vendor relationships, and periodically review supporting documentation.Analyze feature and capability usage to help drive successful product adoption."
That's a list of duties; we can break into bullet points.
"What You’ll Bring Partnership: A customer-focused approach and the ability to build productive, trusted relationships.Collaboration: The ability to strengthen connections across teams and functions to accomplish shared goals.Drive for Results: A proactive approach to moving work forward and delivering meaningful outcomes.Critical Thinking: Sound judgment and the ability to use data to understand issues, evaluate options, and recommend solutions.Priority Management: The ability to organize time and resources effectively in a changing environment.Technical Knowledge: Current, practical knowledge of relevant technologies, applications, and industry trends."
That's a list of skills/competencies.
"Education And Experience Bachelor’s degree in Computer Science, Information Technology, Engineering, Accounting, or a related field, or equivalent practical experience.Five or more years of experience supporting or implementing enterprise business applications, including Oracle EBS and/or Oracle Fusion.Experience partnering with development teams to build custom applications and integrate connected or satellite applications.Experience with agile development methodologies.Construction industry experience is preferred.Must be at least 18 years old."
That's qualifications.
"Skills for Success Strong analytical, problem-solving, consensus-building, and leadership skills.Clear verbal and written communication skills, including the ability to explain complex information in a concise, audience-appropriate way.Ability to troubleshoot high-level application and business process issues.Understanding of software development life cycles.Ability to work independently while contributing effectively as part of a team.A growth mindset and willingness to learn new skills, technologies, and frameworks."
That's skills.
"Ready to make an impact? Join QXO and help shape reliable, secure business solutions that support teams across the organization."
That's a call to action; could be considered prose but maybe not needed? It's substantive; we could include under About the role or maybe as a closing paragraph. We'll include as a paragraph under About the role maybe.
"Physical Requirements Work is performed in a typical office environment and may require standing, bending, lifting boxes or packages under 10 lbs., and sitting for long periods of time. Work requires regularly inputting/retrieving words or data into or from an automated/computer system."
That's physical requirements; we could put under Requirements (maybe as a sublist). But we have no specific heading for Physical Requirements; we could include under Requirements as a list.
"Compensation Range $86,700.00 - $130,000.00 To comply with Pay Transparency laws, employers must disclose an annual salary range. Actual offers depend on factors such as location, experience, skills, and market data. This position may also offer variable compensation."
That's Pay.
Then company description: "QXO is North America’s largest distributor and installer of insulation; second-largest distributor of roofing products; second-largest publicly traded distributor of lumber and building materials; and largest distributor of waterproofing products. QXO is the fastest growing company in the $800 billion building products distribution industry and plans to become the tech-enabled leader by delivering best-in-class customer satisfaction and outsized returns for its shareholders. The company is targeting $50 billion in annual revenue within the next decade through accretive acquisitions and organic growth. Visit QXO.com for more information."
That's about the company; could be part of About the role.
Then EEO boilerplate: "QXO is an Equal Opportunity Employer. We value diversity and do not discriminate on the basis of race, color, religion, gender or sexual orientation, national origin, age, disability, or any other protected status." This is boilerplate; we must remove.
Thus we need to produce HTML with sections:
- About the role: include the "About Your Future With QXO" paragraph, plus maybe the company description, plus the "Ready to make an impact?" line. Could combine into prose paragraphs.
- Responsibilities: include the Job Description paragraph plus the "What You’ll Do" bullet points.
- Qualifications: include Education And Experience bullet points (maybe also Physical Requirements? but physical requirements could be under Requirements). However we have a Requirements section; we could put Physical Requirements there. But we also have Qualifications section for education/experience. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where.
Typically:
- Responsibilities: duties.
- Requirements: maybe mandatory requirements (like experience, education, physical). But we also have Qualifications separate. Might be overlapping. But we can follow typical pattern: Requirements = mandatory (like experience, education, physical). Qualifications = preferred (like construction industry experience, etc). However the posting lumps education/experience as "Education And Experience". Then "Construction industry experience is preferred." and "Must be at least 18 years old." Could be considered requirements.
We need to avoid thin sections; prefer few substantive sections. So we could combine Education And Experience and Construction industry experience and age into Qualifications. Physical Requirements could be under Requirements (maybe as a list). But we could also put Physical Requirements under Requirements as a list.
Skills: combine What You’ll Bring and Skills for Success.
Pay: compensation range.
We should not create Benefits or Schedule sections.
Thus sections: About the role, Responsibilities, Qualifications, Skills, Pay, Requirements (if we have physical requirements). But we need to check if we have enough content for Requirements besides physical requirements. If we only have physical requirements, that's thin but still substantive. Could we incorporate physical requirements into Qualifications? It's not exactly qualification but could be under Requirements. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can omit Requirements section and put physical requirements into Qualifications as a bullet? But physical requirements are not qualifications; they are job demands. However we could still include them under Qualifications as a bullet point; it's still substantive. But better to follow the headings list: we have Requirements as an option; we could include it if we have content. Physical requirements is content. So we can have a Requirements section with that content.
Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Pay, Requirements.
Check if any content duplicated: we must not repeat.
- for any list of duties/requirements/benefits, and
for prose. We must not repeat job title as heading. No markdown fences. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, except boilerplate (EEO, legal, navigation, cookie, etc). Also remove duplicated lines. Let's extract substantive content. Full text: "About Your Future With QXO Are you looking for a career with an industry leader that drives the future of energy-efficient insulation and building material products? Look no further! At QXO, you will be part of a team that reflects our values of integrity and innovation by delivering solutions that make a difference in the communities we serve. Here, you are part of a company that rewards your contributions and encourages you to take ownership of your career." That's prose. "Job Description As a Senior Business Analyst, Business Applications at QXO, you will partner closely with TruTeam, Specialty Distribution, QXO business partners, and IT teams to translate strategic objectives into effective technology solutions. You will help solve complex challenges across QXO’s enterprise business applications, including Oracle E-Business Suite (EBS) and Oracle Fusion, while ensuring solutions are reliable, secure, scalable, and aligned with enterprise technology standards. This role is ideal for a collaborative, solutions-focused professional who combines strong business analysis skills with hands-on experience implementing and supporting Oracle enterprise applications." That's prose (could be part of responsibilities). "What You’ll Do Build Strong Business Partnerships Develop a strong understanding of core business processes, priorities, and desired outcomes.Serve as a primary liaison between business partners and IT, leading regular discussions and helping prioritize requests.Stay current on relevant technologies and business processes, recommending improvements that enhance efficiency and performance.Use data and application knowledge to measure results, identify opportunities, and support continuous improvement.Maintain a working understanding of connected applications and how data moves across the technology environment. Deliver Business Value Lead projects in accordance with IT standards and coordinate with Audit during compliance reviews.Partner with business stakeholders to gather requirements, translate them into functional specifications, and lead user testing to support high-quality delivery.Collaborate with IT developers and business analysts to implement solutions consistent with QXO’s solution delivery processes.Manage a product backlog spanning support, enhancements, and project work, confirming priorities with business partners.Help ensure applications and business processes meet security and compliance requirements through appropriate controls and documentation.Clearly communicate ideas, requirements, and technical concepts to business stakeholders and development teams.Monitor incidents and outages, communicate status, analyze trends and root causes, and drive issues through resolution.Support third-party applications, maintain vendor relationships, and periodically review supporting documentation.Analyze feature and capability usage to help drive successful product adoption." That's a list of duties; we can break into bullet points. "What You’ll Bring Partnership: A customer-focused approach and the ability to build productive, trusted relationships.Collaboration: The ability to strengthen connections across teams and functions to accomplish shared goals.Drive for Results: A proactive approach to moving work forward and delivering meaningful outcomes.Critical Thinking: Sound judgment and the ability to use data to understand issues, evaluate options, and recommend solutions.Priority Management: The ability to organize time and resources effectively in a changing environment.Technical Knowledge: Current, practical knowledge of relevant technologies, applications, and industry trends." That's a list of skills/competencies. "Education And Experience Bachelor’s degree in Computer Science, Information Technology, Engineering, Accounting, or a related field, or equivalent practical experience.Five or more years of experience supporting or implementing enterprise business applications, including Oracle EBS and/or Oracle Fusion.Experience partnering with development teams to build custom applications and integrate connected or satellite applications.Experience with agile development methodologies.Construction industry experience is preferred.Must be at least 18 years old." That's qualifications. "Skills for Success Strong analytical, problem-solving, consensus-building, and leadership skills.Clear verbal and written communication skills, including the ability to explain complex information in a concise, audience-appropriate way.Ability to troubleshoot high-level application and business process issues.Understanding of software development life cycles.Ability to work independently while contributing effectively as part of a team.A growth mindset and willingness to learn new skills, technologies, and frameworks." That's skills. "Ready to make an impact? Join QXO and help shape reliable, secure business solutions that support teams across the organization." That's a call to action; could be considered prose but maybe not needed? It's substantive; we could include under About the role or maybe as a closing paragraph. We'll include as a paragraph under About the role maybe. "Physical Requirements Work is performed in a typical office environment and may require standing, bending, lifting boxes or packages under 10 lbs., and sitting for long periods of time. Work requires regularly inputting/retrieving words or data into or from an automated/computer system." That's physical requirements; we could put under Requirements (maybe as a sublist). But we have no specific heading for Physical Requirements; we could include under Requirements as a list. "Compensation Range $86,700.00 - $130,000.00 To comply with Pay Transparency laws, employers must disclose an annual salary range. Actual offers depend on factors such as location, experience, skills, and market data. This position may also offer variable compensation." That's Pay. Then company description: "QXO is North America’s largest distributor and installer of insulation; second-largest distributor of roofing products; second-largest publicly traded distributor of lumber and building materials; and largest distributor of waterproofing products. QXO is the fastest growing company in the $800 billion building products distribution industry and plans to become the tech-enabled leader by delivering best-in-class customer satisfaction and outsized returns for its shareholders. The company is targeting $50 billion in annual revenue within the next decade through accretive acquisitions and organic growth. Visit QXO.com for more information." That's about the company; could be part of About the role. Then EEO boilerplate: "QXO is an Equal Opportunity Employer. We value diversity and do not discriminate on the basis of race, color, religion, gender or sexual orientation, national origin, age, disability, or any other protected status." This is boilerplate; we must remove. Thus we need to produce HTML with sections: - About the role: include the "About Your Future With QXO" paragraph, plus maybe the company description, plus the "Ready to make an impact?" line. Could combine into prose paragraphs. - Responsibilities: include the Job Description paragraph plus the "What You’ll Do" bullet points. - Qualifications: include Education And Experience bullet points (maybe also Physical Requirements? but physical requirements could be under Requirements). However we have a Requirements section; we could put Physical Requirements there. But we also have Qualifications section for education/experience. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. Typically: - Responsibilities: duties. - Requirements: maybe mandatory requirements (like experience, education, physical). But we also have Qualifications separate. Might be overlapping. But we can follow typical pattern: Requirements = mandatory (like experience, education, physical). Qualifications = preferred (like construction industry experience, etc). However the posting lumps education/experience as "Education And Experience". Then "Construction industry experience is preferred." and "Must be at least 18 years old." Could be considered requirements. We need to avoid thin sections; prefer few substantive sections. So we could combine Education And Experience and Construction industry experience and age into Qualifications. Physical Requirements could be under Requirements (maybe as a list). But we could also put Physical Requirements under Requirements as a list. Skills: combine What You’ll Bring and Skills for Success. Pay: compensation range. We should not create Benefits or Schedule sections. Thus sections: About the role, Responsibilities, Qualifications, Skills, Pay, Requirements (if we have physical requirements). But we need to check if we have enough content for Requirements besides physical requirements. If we only have physical requirements, that's thin but still substantive. Could we incorporate physical requirements into Qualifications? It's not exactly qualification but could be under Requirements. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can omit Requirements section and put physical requirements into Qualifications as a bullet? But physical requirements are not qualifications; they are job demands. However we could still include them under Qualifications as a bullet point; it's still substantive. But better to follow the headings list: we have Requirements as an option; we could include it if we have content. Physical requirements is content. So we can have a Requirements section with that content. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Pay, Requirements. Check if any content duplicated: we must not repeat.