Enterprise Business Analyst

We need to output HTML fragment with sections: About the role? Actually we have Overview, You Will, You Have, Compensation Details, BerryDunn Benefits & Culture, About BerryDunn. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. We have content for responsibilities (You Will), requirements/qualifications (You Have), compensation (Pay), benefits (BerryDunn Benefits & Culture). Also maybe About the role (Overview). We should map headings accordingly. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, accommodation, equal opportunity, etc. Also remove navigation, cookie, legal, scam-warning, duplicated lines. Also remove "Visit our website for a complete list of benefits and a look into our culture: Experience BerryDunn ." That's maybe part of benefits but it's a link; we can keep benefits description but maybe drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Visit our website..." is not exactly those but could be considered navigation? It's a promotional link; maybe we keep benefits description but we can keep the sentence about benefits but maybe drop the link? Safer to keep the benefits description but remove the link text? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The link is substantive? It's a pointer to website; maybe we can keep it as plain text without hyperlink. Since we cannot output markdown, just plain text. We'll keep the sentence but maybe remove the link markup (there is none). It's just text: "Visit our website for a complete list of benefits and a look into our culture: Experience BerryDunn ." That's okay. We also have "About BerryDunn" section which is descriptive about the company. Should we include as a section? The allowed headings list does not include About the company, but we could use "About BerryDunn" as a heading? Not in list. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should likely stick to those headings. However we have content about BerryDunn that is not exactly responsibilities etc. Could we treat it as "About the role"? No. Could we treat as "About BerryDunn" but not in list; maybe we should omit it because it's not required? The instruction: "Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid adding other headings beyond the examples, but the examples are given. Safer to stick to the given headings. So we may omit About BerryDunn section, or we could incorporate its content into Benefits or Overview? But it's about the firm, not role. Might be considered boilerplate? It's descriptive about the firm; maybe we can keep as a section titled "About BerryDunn" but not in the list; risk of violating instruction. Better to omit it, as it's not required for the role. However we must preserve ALL substantive information; omitting that would lose info about the company. But maybe it's considered boilerplate? It's not EEO etc. It's about the firm; could be considered relevant. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we should keep it. But we need a heading; we could use

About BerryDunn

even if not in examples; 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, just gives examples. So we can use About BerryDunn as heading. Thus sections: Overview (maybe About the role), Responsibilities (You Will), Requirements (You Have), Qualifications (maybe combine with Requirements?), Skills (maybe separate), Benefits, Pay. We have content for responsibilities, requirements/qualifications, benefits, pay. We also have overview (first paragraph). We'll map: - About the role: Overview paragraph(s) (first two paragraphs maybe). We'll combine the overview paragraphs: "We are seeking an Enterprise Business Analyst..." and "This role partners closely..." and "This role will ideally be based..." That's substantive. - Responsibilities: You Will bullet list. - Requirements: You Have bullet list (education, experience). Could also include Qualifications: maybe separate but we can combine. - Skills: maybe list of tools and proficiencies from You Have (proficiency with BA tools, etc.) Could separate but we can embed in Requirements. Better to follow typical sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We'll extract: About the role: first two paragraphs (Overview and role partnership). Could also include location statement. Responsibilities: list of items under "You Will". Each sentence starting with a verb. Requirements: Bachelor’s degree or equivalent experience. 5+ years of business analysis experience in both agile and waterfall environments, with 2+ years working on enterprise-level or cross-functional initiatives. Experience with software selection processes and enterprise software implementations (ERP, CRM, HCM, workflow platforms, or similar). Strong understanding of business process mapping, optimization, requirements gathering, and data analysis techniques. Experience in backlog refinement, user story creation and acceptance criteria, iterative requirements development, and agile ceremonies. Proficiency with BA tools (e.g., Visio, Lucidchart, Jira, Confluence, Azure DevOps, MS Office/365, Smartsheet). Preferred: Experience in a PMO, enterprise technology environment, or large-scale transformation program. Experience in Professional Services delivery, Consulting, or Assurance, Tax, Audit, and Advisory environment. Knowledge of Lean/Six Sigma, ITIL, BABOK, Agile Extension to the BABOK, or related frameworks. Professional certifications (e.g., CBAP, CCBA, PBA, AAC, CSPO, ICP, ACP, SAFE POPM) are a plus. Experience supporting change management and organizational readiness activities. Experience operating in highly regulated and secure environments, ensuring compliance with industry standards and regulations. Qualifications: maybe we could separate preferred qualifications? But we can keep as Requirements. Skills: maybe list of tools and methodologies: Visio, Lucidchart, Jira, Confluence, Azure DevOps, MS Office/365, Smartsheet; business process mapping, optimization, requirements gathering, data analysis; backlog refinement, user story creation, acceptance criteria; agile ceremonies; change management; etc. But we already have many. We could avoid duplication by putting skills as a separate section listing tools and methodologies. Benefits: paragraph about benefits and culture. Pay: compensation details. We must not include filler like "commensurate with experience". Not present. We must not include duplicated lines. We must not include application instructions (like "Please contact careers@berrydunn.com to request an accommodation.") That's accommodation request; maybe considered application instruction? It's about accommodation; could be considered part of EEO? Might be considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The accommodation request is likely an application instruction. So we should remove that line. Also remove EEO statement lines. Also remove "We will ensure that individuals are provided reasonable accommodation..." and the following equal opportunity paragraph. Also remove "We are proud to be an equal opportunity workplace." Also remove "About BerryDunn" maybe not needed but we decided to keep. We also need to remove "Visit our website for a complete list of benefits and a look into our culture: Experience BerryDunn ." That's not application instruction; it's okay. Now produce HTML fragment. Structure:

About the role

We are seeking an Enterprise Business Analyst to join our Enterprise Project Management Office to contribute to organization-wide initiatives that improve efficiency, strengthen operational alignment, and support strategic growth. This role partners closely with business units, project managers, technical teams, and executive leadership to lead business analysis functions across major enterprise projects—including software selection and implementation, process improvement initiatives, and other cross-functional programs. This role will ideally be based in our Portland, Maine headquarters, or one of our other New England regional offices.

Responsibilities

• Lead business analysis activities across large, cross-functional initiatives and enterprise transformation programs.
• Facilitate stakeholder interviews, workshops, and discovery sessions to define business needs and gather detailed requirements.
• Document business, functional, and technical requirements using the appropriate methodology (user stories, acceptance criteria, business requirements documents, functional requirements documents, traceability matrices, etc.).
• Analyze current-state processes, workflows, and data structures; develop future-state designs that improve efficiency, clarity, and standardization.
• Support software selection efforts including RFP/RFI development, vendor evaluations, scoring, and fit-gap analysis.
• Support backlog refinement, sprint planning, design reviews, and solution delivery.
• Participate in agile ceremonies (standups, reviews, retrospectives) and waterfall stage-gate activities (requirements signoff, design walkthroughs, test planning).
• Develop and maintain process maps, data flows, decision models, and documentation that align with enterprise standards.
• Support testing activities including UAT planning, test case development, defect triage, and validation of requirements.
• Assist with change management deliverables including training content, communications, SOPs, and go-live readiness activities.
• Collaborate with cross-functional teams to ensure alignment, manage risks, and provide clear, concise communication throughout the project lifecycle.

Requirements

• Bachelor’s degree or equivalent experience.
• 5+ years of business analysis experience in both agile and waterfall environments, with 2+ years working on enterprise-level or cross-functional initiatives.
• Experience with software selection processes and enterprise software implementations (ERP, CRM, HCM, workflow platforms, or similar).
• Strong understanding of business process mapping, optimization, requirements gathering, and data analysis techniques.
• Experience in backlog refinement, user story creation and acceptance criteria, iterative requirements development, and agile ceremonies.
• Proficiency with BA tools (e.g., Visio, Lucidchart, Jira, Confluence, Azure DevOps, MS Office/365, Smartsheet).
• Experience supporting change management and organizational readiness activities.
• Experience operating in highly regulated and secure environments, ensuring compliance with industry standards and regulations.

Qualifications

• Preferred: Experience in a PMO, enterprise technology environment, or large-scale transformation program.
• Preferred: Experience in Professional Services delivery, Consulting, or Assurance, Tax, Audit, and Advisory environment.
• Preferred: Knowledge of Lean/Six Sigma, ITIL, BABOK, Agile Extension to the BABOK, or related frameworks.
• Preferred: Professional certifications (e.g., CBAP, CCBA, PBA, AAC, CSPO, ICP, ACP, SAFE POPM) are a plus.

Skills

• Business process mapping and optimization.
• Requirements gathering and documentation (user stories, acceptance criteria, BRD, FRD, traceability matrices).
• Data analysis techniques.
• Backlog refinement, user story creation, acceptance criteria.
• Agile