Engineering Systems Business Analyst

We need to output HTML fragment with sections: About the role? Actually the posting includes "Why Work at Banner?" then "Position Summary", "What You’ll Be Doing" with subheadings "Key Responsibilities" etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only if posting has real specific content. We have content for: About the role? Could be "Why Work at Banner?" maybe treat as About the role? The posting includes "Why Work at Banner?" describing company. That could be About the role? Actually "About the role" is typical heading for role description; but we have "Position Summary". Could map that to About the role. We'll include

About the role

with paragraph(s) from "Why Work at Banner?" and "Position Summary". Then Responsibilities: from "What You’ll Be Doing" and sub-bullets. Use

• . Then Requirements: from "What You Bring To The Table" includes Required and Preferred. We'll separate maybe Requirements (required) and Qualifications (preferred) or Skills. The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with content. We have Requirements (required). Qualifications (preferred). Skills maybe from preferred list? Could combine. Benefits: we have list of benefits. Pay: we have base pay range. Schedule: not mentioned (no schedule info). So omit Schedule. We must not include boilerplate like EEO, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Physical Demands", "Working Environment", "Core Values", "If you excel..." etc? Those are not required headings but could be considered extra info. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't say to remove physical demands or working environment; they are substantive. But we don't have headings for them; we could include them as paragraphs under maybe About the role? But we must only use allowed headings? Not required; we can have other headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those for sections. Probably we should stick to those headings and embed other info under appropriate sections. Physical demands and working environment could go under maybe "Requirements" or "Qualifications"? Not ideal. Could create a separate section but not in list; maybe we can omit them? But instruction says preserve ALL substantive information. So we need to include them somewhere. Could add a

  Working Conditions

  but not in list; but they said e.g., not exclusive. Might be okay. However to be safe, we could add a

  Working Conditions

  with paragraphs for Physical Demands and Working Environment. The instruction didn't forbid other headings; just gave examples. So we can add. Also need to include "Core Values" maybe as part of About the role? Could be separate. We'll produce HTML fragment:

  About the role

  Why Work at Banner? For over 50 years, Banner Engineering has been at the forefront of industrial automation...

  Position Summary The Engineering Systems Business Analyst is responsible for the ownership, improvement, and ongoing effectiveness of Banner’s Engineering Systems portfolio....

  Then Responsibilities:

  Responsibilities

  ... list items from key responsibilities bullet points. We need to capture each bullet under Key Responsibilities: there are subheadings: Engineering Systems Management, Business Analysis & Discovery, Systems Process Improvement, Engineering Data Governance, Documentation, Planning & Communication. Each has multiple bullet-like sentences. We'll turn each sentence into
  • . Might be many. Then Requirements:

    Requirements

    from Required bullet points. Qualifications:

    Qualifications

    from Preferred bullet points. Skills: maybe we can extract skills from preferred list: experience gathering requirements, documenting etc. Could put under Skills. Benefits:

    Benefits

    list benefits. Pay:

    Pay

    Base Pay Range: $74,470.00 - $105,064.00

    Working Conditions:

    Working Conditions

    Physical Demands...

    Working Environment...

    We must not include duplicated lines. Ensure no markdown. Let's craft. We need to be careful to preserve all substantive info from the posting. Let's extract sections. First, "Why Work at Banner?" paragraph: "Why Work at Banner? For over 50 years, Banner Engineering has been at the forefront of industrial automation. We offer products and solutions including award-winning sensors, wireless solutions, machine safety, indication and LED lighting. From Fortune 500 leaders to innovative startups, Banner's award-winning products and solutions are helping companies around the world increase efficiency, reduce costs, safeguard equipment, and protect personnel. Our commitment to innovation shows through a continuous, market-driven evolution of products and technology. With engineers employed in nearly every major department, engineering is in our DNA. Banner is a rapidly growing company that offers many personal development opportunities, an excellent benefits package, and a collaborative team of employees who are passionate about what they do." Second, Position Summary paragraph: "Position Summary The Engineering Systems Business Analyst is responsible for the ownership, improvement, and ongoing effectiveness of Banner’s Engineering Systems portfolio. The role combines systems management with business analysis to understand user needs, identify process and system improvement opportunities, define requirements, coordinate solutions, and support implementation. This position works closely with Engineering, DSS, IT, Operations, and other business stakeholders to improve the systems, data, and processes that support product development and the flow of engineering information across the organization. A key expectation of the role is to maintain clear written documentation of systems, projects, requirements, decisions, plans, and outcomes so that work is visible, repeatable, and sustainable. This position reports to the Director of Engineering Systems & Processes" Third, "What You’ll Be Doing" intro: "This is a great opportunity for someone who enjoys working both individually and collaboratively, staying on top of tasks, and making a meaningful impact across teams and projects. Below are some key responsibilities of the role." Then subheadings with bullet-like content. We'll extract each bullet as list items. Engineering Systems Management: - Own and maintain the portfolio of systems, applications, and tools used by Engineering. - Develop and maintain Engineering Systems priorities, roadmaps, lifecycle plans, and system documentation. - Coordinate system upgrades, integrations, configuration changes, support issues, and improvement activities with users, IT, and vendors. - Manage engineering software licensing, access, utilization, renewals, purchasing, and vendor relationships. - Proactively identify system risks, gaps, and opportunities for improvement. Business Analysis & Discovery: - Work with stakeholders to identify business problems, user needs, pain points, and improvement opportunities. - Document current-state processes, systems, data flows, business rules, and requirements. - Analyze problems and alternatives and develop clear recommendations for future-state processes and system solutions. - Facilitate discovery sessions, working meetings, and requirements reviews with cross-functional stakeholders. Systems Process Improvement: - Lead and support Engineering Systems and process-improvement initiatives from discovery through implementation. - Translate business requirements into actionable system, process, data, and integration requirements. - Coordinate testing, issue resolution, implementation, rollout, and stabilization of new or changed solutions. - Identify opportunities to simplify, standardize, automate, and improve business processes, including appropriate application of AI. Engineering Data Governance: - Improve the management and flow of engineering information across design tools, PDM, Oracle, DSS processes, and related systems. - Establish and maintain appropriate standards, business rules, ownership, and Single Source of Truth principles. - Support effective management of engineering design files, product data, documentation, and supporting information throughout their lifecycle. Documentation, Planning & Communication: - Maintain clear, current written documentation of systems, projects, processes, requirements, decisions, issues, plans, milestones, and outcomes. - Develop and maintain project goals, work plans, milestones, target dates, status, risks, and action items for assigned initiatives. - Communicate progress, issues, recommendations, and decisions clearly to stakeholders and leadership. - Ensure completed work leaves behind sufficient documentation for ongoing operation, support, and continuous improvement. Now Requirements (Required): - Bachelor’s degree in Engineering, Information Systems, Business, or a related field, or equivalent relevant experience. - Experience supporting, managing, analyzing, or improving business or engineering systems and processes. - Experience with engineering systems such as PDM/PLM, ERP, CAD/design tools, product data management, or similar enterprise applications preferred. Note: The last line says "preferred" but it's under Required? Actually it's under Required list but says preferred. We'll keep as required bullet. Preferred (Qualifications): - Demonstrated experience gathering requirements, documenting processes, analyzing problems, and implementing system or process improvements. - Experience leading or coordinating projects involving multiple stakeholders and functional areas. - Experience creating and maintaining clear project, process, system, and requirements documentation. - Experience working in a product development or manufacturing environment preferred. - Experience with AI, automation, data analysis, or emerging business technologies is a plus. We could also treat some as Skills. Skills: maybe combine the preferred items that are skill-based: gathering requirements, documenting processes, analyzing problems, implementing improvements, leading projects, creating documentation, working in product development, AI automation data analysis. We'll put under Skills. Benefits list: - 401(k) with match - Student Loan 401(k) match program - Medical, Dental, and Vision Insurance Plans - HSA (Health Savings Account) with company contribution - Paid Time Off (PTO) - Sales and Profit Sharing Eligibility - Flexible work hours - Life Insurance - Paid Parental Leave - Pet Insurance Pay: Base Pay Range: $74,470.00 - $105,064.00 Working Conditions: Physical Demands: - Sit for up to 8 hours per day. - Exposed to a computer screen for extended periods - May require repetitive motions such as utilize a computer mouse, keyboard, computer, and other standard office equipment. - Communicate with others frequently. - Occasionally lift and/or move objects up to 25 pounds. Working Environment: - Corporate office environment – indoor and climate-controlled - Frequent interaction with internal departments, cross-functional teams, or external partners, as well as employees across all levels of the organization—including entry-level staff, senior leadership, clients, or vendors. We also have Core Values and EEO statements etc which we should remove as boilerplate. Also remove "If you excel..." and "Banner Engineering is a premier employer..." maybe considered boilerplate? It's somewhat promotional but still substantive? Might be considered boilerplate but it's about company. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Core Values maybe not boilerplate but could be considered promotional; but we might keep? It's not explicitly listed to remove. However to be safe, we could keep it under About the role? But it's after Pay and Benefits. Might be considered extra. I'd keep it as a separate section maybe "Company Culture". But not in allowed headings. Could omit? The instruction says preserve ALL substantive information. Core Values is substantive. So we should include. Could add a

    Company Culture

    with paragraph. But we already have About the role covering company description; we could append