Integration Analyst

We need to output HTML fragment only, with sections for headings where there is real content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve substantive info. Must not create sections like Pay/Schedule/Benefits unless posting actually states them. The posting includes benefits overview (Everforth Apex Benefits Overview). So we should include a Benefits section with that content. Also maybe Pay? Not mentioned. Schedule? Not mentioned. So only include sections that have content: About the role (Position Overview), Responsibilities (Key Responsibilities broken into sub-sections? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to decide what content goes where. The posting includes: Position Overview (we can map to About the role). Then Key Responsibilities (multiple bullet points grouped). Then Required Qualifications and Preferred Qualifications (these could go under Requirements and Qualifications? Actually they said Requirements, Qualifications, Skills as possible headings. We have Required Qualifications and Preferred Qualifications; we could combine into Qualifications section. Also there is a list of Common Skills & Technologies which could go under Skills. Also there is "What Success Looks Like" and "Ideal Candidate" maybe could be part of About the role or separate? But we should only create sections when there is real specific content. We could include a section for What Success Looks Like (maybe as part of About the role). But better to follow the given headings list. We can include About the role (Position Overview + What Success Looks Like + Ideal Candidate). Responsibilities (Key Responsibilities). Requirements (maybe Required Qualifications). Qualifications (maybe Preferred Qualifications). Skills (Common Skills & Technologies). Benefits (Benefits overview). Ensure we don't create empty sections. We must use

• for any list of duties/requirements/benefits. So for responsibilities we need a list. For qualifications we need list. For skills we need list. For benefits we need list. We must use

  for prose. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, application instructions, etc. Also remove the "Everforth Apex Benefits Overview:" heading? We'll keep benefits content. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, qualifications, skills, benefits. We must not create sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Job Description text: "Job#: 3052728 Job Description: Business & Integration Analyst Location: St Louis Employment Type:Contract Practice Area: Business Applications / Business Analysis Position Overview We are seeking a Business & Integration Analyst to support complex business and technology initiatives within a large enterprise environment. This position serves as the bridge between business stakeholders, product teams, developers, architects, and integration partners. The analyst will gather and refine requirements, investigate system interactions, document existing and future-state processes, and translate business needs into actionable artifacts for delivery teams. The ideal candidate is comfortable operating across business analysis, systems analysis, API and integration analysis, data investigation, quality validation, and technical documentation. This is not a software development role. It is best suited for an analytical professional who can navigate ambiguity, uncover dependencies, ask thoughtful questions, and produce clear, implementation-ready documentation." Then "Key Responsibilities" with subheadings: Business Analysis & Requirements Management - Lead stakeholder interviews, discovery sessions, workshops, and working sessions. - Gather, document, and validate business and functional requirements. - Analyze current-state processes and define future-state solutions. - Translate business needs into: Functional requirements User stories and acceptance criteria Business rules Process flows Use cases Data requirements Validation rules Exception and error-handling scenarios - Identify gaps, dependencies, risks, and downstream impacts. - Maintain requirements traceability from intake through implementation. Systems & Integration Analysis - Research how data moves across applications, APIs, enterprise services, and downstream systems. - Identify systems of record, integration points, dependencies, endpoints, and supporting data sources. - Assess whether existing services and APIs can support business requirements. - Review API requests, responses, field mappings, logs, and system behaviors. - Analyze RESTful and web-service integrations using JSON and XML. - Trace transactions across multiple systems to identify failures and inconsistencies. - Collaborate with architects, developers, and stakeholders to validate proposed solutions. - Evaluate the impact of changes across interconnected systems. Documentation & Process Design - Produce and maintain documentation throughout the delivery lifecycle. - Create and update: Process maps Data-flow diagrams Sequence diagrams System interaction diagrams Source-to-target mappings Functional specifications Integration documentation Current-state and future-state workflows Decision logs Support documentation - Document data origins, transformations, integrations, and user-facing outputs. - Ensure documentation is sufficiently detailed for development and QA teams. Issue Investigation & Root Cause Analysis - Investigate production issues, operational exceptions, and data discrepancies. - Review logs and transaction records to identify root causes. - Determine whether issues stem from: Requirements Application logic APIs and integrations Data transformations Source-system data Configuration Process execution Third-party dependencies - Document findings, impacts, recommendations, and preventative controls. - Validate corrective actions through resolution. Agile Delivery & Quality Support - Create and maintain epics, features, user stories, and acceptance criteria. - Participate in backlog refinement, sprint planning, testing, and release activities. - Partner with developers and QA teams to clarify requirements throughout delivery. - Support test planning, defect triage, regression analysis, and user acceptance testing. - Validate completed functionality against documented requirements. Stakeholder Collaboration - Serve as a liaison between business and technical teams. - Communicate technical concepts in business-friendly language. - Coordinate efforts across cross-functional and distributed teams. - Support multiple concurrent initiatives while maintaining clear priorities and documentation. Then "Required Qualifications" list: - 5+ years of experience as a Business Analyst, Business Systems Analyst, Systems Analyst, Integration Analyst, or similar role. - Demonstrated experience leading requirements gathering and discovery workshops. - Strong experience converting business requests into functional requirements and user stories. - Experience analyzing system integrations, APIs, workflows, and data flows. - Ability to create process flows, sequence diagrams, data mappings, and technical documentation. - Working knowledge of REST APIs, web services, JSON, XML, and distributed systems. - Experience using SQL for data validation and analysis. - Experience performing root-cause analysis and production issue investigation. - Familiarity with log analysis and monitoring platforms. - Experience using Jira, Confluence, SharePoint, or similar collaboration tools. - Understanding of Agile methodologies and the software development lifecycle. - Strong written and verbal communication skills. - Ability to work independently in fast-paced environments with evolving requirements. Then "Preferred Qualifications" list: - Experience supporting large-scale customer-facing or operational platforms. - Experience with billing, service management, customer support, troubleshooting, or workflow management systems. - Familiarity with Java and Spring-based application environments. - Understanding of enterprise integration patterns, middleware, and API ecosystems. - Experience using API testing and analysis tools such as Postman, SoapUI, or similar platforms. - Experience working with distributed or offshore delivery teams. - Background in software development, integration testing, technical support, or quality assurance. - Experience using AI-assisted tools for requirements development, documentation, and analysis. - Familiarity with user-interface analysis and documenting system behavior. Then "What Success Looks Like" bullet points (6? Actually list): - Develop a strong understanding of supported applications, workflows, data flows, and integrations. - Build trusted relationships with business and technology stakeholders. - Independently lead requirements discovery and solution analysis efforts. - Produce high-quality requirements, user stories, and implementation documentation. - Effectively analyze cross-system workflows and data movement. - Investigate issues, identify root causes, and recommend practical solutions. - Improve documentation quality, traceability, and knowledge management. - Become a trusted subject-matter resource within assigned functional areas. Then "Ideal Candidate" paragraph: description. Then "Common Skills & Technologies" list (comma-separated but we can treat as list): Business Analysis Systems Analysis Requirements Gathering Process Mapping Data Flow Analysis SQL REST APIs JSON / XML Jira Confluence SharePoint Postman SoapUI Agile / Scrum Root Cause Analysis Technical Documentation Integration Analysis User Stories & Acceptance Criteria Enterprise Applications & Services Then benefits overview paragraph: "Everforth Apex Benefits Overview: Everforth Apex offers a range of supplemental benefits, including medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection. We offer an ESPP (employee stock purchase program) and a 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure. Everforth Apex also offers a HSA (Health Savings Account on the HDHP plan), a SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions, a corporate discount savings program and other discounts. In terms of professional development, Everforth Apex hosts an on-demand training program, provides access to certification prep and a library of technical and leadership courses/books/seminars once you have 6+ months of tenure, and certification discounts and other perks to associations that include CompTIA and IIBA. Everforth Apex has a dedicated customer service team for our Consultants that can address questions around benefits and other resources, as well as a certified Career Coach. You can access a full list of our benefits, programs, support teams and resources within our ‘Welcome Packet’ as well, which an Everforth Apex team member can provide." We need to output HTML with sections. We must not include boilerplate like EEO etc. So we stop before that. We'll produce:

  About the role

  Position Overview paragraph + maybe What Success Looks Like and Ideal Candidate? But we could keep them separate? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should stick to those. However we can include additional headings if needed? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections. It doesn't say we cannot use other headings, but better to follow the pattern. We can embed What Success Looks Like and Ideal Candidate within About the role as prose. Thus About the role will contain the Position Overview paragraph, then maybe a paragraph about What Success Looks Like (we could make a

  summarizing but we must not summarize away detail; we need to preserve ALL substantive information. So we need to include the bullet points of What Success Looks Like somewhere. Could we put them under a separate heading like "What Success Looks Like"? That's not in the example list but maybe allowed. 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 it says "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. So we could incorporate What Success Looks Like and Ideal Candidate into About the role as prose paragraphs, but we must preserve the bullet points exactly. We can turn them into a

  • list inside About