Lead Solutions Analyst

We need to produce HTML fragment with sections: About the role? The description includes "YOUR TEAM." and "WHY COHNREZNICK?" and "YOUR ROLE." and "Your Experience." Also there is mention of compensation: "Actual compensation within the range will be dependent upon the individual's skills, experience, qualifications and location, and applicable employment laws." That's not a specific salary range, just generic. According to rules: do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It mentions "Total Rewards package" with generous PTO, flexible work environment, expanded parental leave, extensive learning & development, paid time off for volunteering. That's benefits info. So we can include a Benefits section with those specifics. Also mention "generous PTO, a flexible work environment, expanded parental leave, extensive learning & development, and even paid time off for employees to volunteer." That's benefits. Also "discretionary performance bonus" mentioned later. So we can include Benefits. Schedule? Not mentioned. So no Schedule section. Pay? Not specific numbers, just statement about compensation dependent etc. Not a concrete range, so we should not create Pay section because it's not specific. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have specifics, so we can include Benefits. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We have content for About the role? The "YOUR TEAM." paragraph describes role. Could map to About the role. Responsibilities: "YOUR ROLE. Responsibilities Include But Not Limited To" list. Requirements: maybe "Your Experience." includes qualifications. Could split into Requirements and Qualifications? The instruction says use those headings if content exists. We have experience, education, skills. Could put Requirements for education and years experience, Qualifications for specific skills? But better to follow typical: Responsibilities, Requirements (education + experience), Qualifications (skills), Benefits. However we must not create thin sections. Let's see content: - About the role: description of team, role purpose. We have that in "YOUR TEAM." paragraph. - Responsibilities: bullet list after "YOUR ROLE. Responsibilities Include But Not Limited To". Many bullet points. - Requirements: education (Bachelor's degree) and years experience (7-10+). Also maybe "This is not a software development position." but that's more note. - Qualifications: maybe the list of skills/experience: understanding of business process analysis, ability to create TDDs, experience with Power Platform, etc. That's a lot. - Benefits: details about total rewards: generous PTO, flexible work environment, expanded parental leave, extensive learning & development, paid time off for volunteering, discretionary performance bonus. We should not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, accommodation, etc. Also remove "Universal Job Standards" etc. Also remove "In addition, please take a moment to review our Universal Job Standards." That's boilerplate. Also remove "Studies have shown that we are less likely to apply..." etc. Also remove "Actual compensation within the range..." maybe keep as part of Benefits? It's about compensation but not specific; we decided not to include Pay section. Could we include a short paragraph about compensation being based on skills etc? The rule says do not create Pay section unless posting actually states them. It does state compensation is dependent on skills etc, but not a range. Might be considered stating compensation but not specific. Safer to omit Pay section entirely. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about compensation, but not a specific range or number. Might be considered stating them. However they also say "Prefer a few substantive sections over many thin ones." If we include Pay with vague statement, it's thin. Better to omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Now we need to format:

for each heading. Use

• for lists. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the sections. Let's extract content. About the role: from "YOUR TEAM." paragraph: "This is a senior-level individual contributor role responsible for bridging business needs and technology solutions. You will work closely with Product Owners, business stakeholders, developers, and project teams to analyze requirements, define solution approaches, and support the successful delivery of business applications and technology initiatives. Business requirements may be provided through BRDs, stakeholder discussions, existing processes, or strategic initiatives; however, those inputs are often incomplete, ambiguous, or lack the level of detail required for implementation. Success in this role requires the ability to identify gaps, ask thoughtful questions, gather additional information, and transform business needs into well-defined functional and technical requirements. The ideal candidate possesses strong analytical and communication skills, with the ability to facilitate discussions, clarify requirements, document solution approaches, communicate risks and dependencies, and provide recommendations to support informed decision-making. This role requires a strong technical foundation and solution analysis mindset. The successful candidate will analyze business workflows, data flows, integrations, APIs, application functionality, and system interactions across multiple platforms. While technical depth is required, this is not a hands-on software development role. Instead, you will collaborate with developers, QA teams, and business stakeholders to create solution documentation and support successful project delivery." That's the whole paragraph. Responsibilities: list after "YOUR ROLE. Responsibilities Include But Not Limited To". Let's capture each bullet: - Analyze business requirements and contribute to the design and delivery planning of business and technology solutions. - Review, validate, and refine business requirements, identifying gaps, dependencies, assumptions, and risks. - Collaborate with stakeholders to understand business objectives and translate them into functional and technical requirements. - Facilitate workshops, discovery sessions, and requirements-gathering meetings with business and technology teams. - Evaluate proposed solutions and provide recommendations aligned with business needs, technical capabilities, and established standards. - Communicate project impacts, dependencies, risks, assumptions, and implementation considerations. - Create and maintain Technical Design Documents (TDDs), API specifications, workflow diagrams, process maps, integration documentation, and data flow diagrams. - Break down complex business processes into workflows, functional requirements, integrations, data requirements, and system interactions. - Contribute to solution design activities involving Power Platform, Power Apps, Power Automate, Azure services, React applications, SharePoint, Dataverse, SQL Server, APIs, and enterprise platforms. - Partner with architects, developers, QA teams, project managers, and business stakeholders throughout the solution lifecycle. - Create user stories, acceptance criteria, functional specifications, wireframes, and supporting solution documentation. - Communicate technical concepts to business users and business requirements to technical teams. - Support stakeholder alignment by documenting decisions, requirements, assumptions, and solution approaches. - Identify technical, functional, and operational risks and document recommendations for mitigation. - Promote documentation standards, solution analysis best practices, and knowledge sharing across project teams. That's the list. Requirements: education and experience. From "Your Experience. The successful candidate will have:" then list: - Bachelor's degree in Information Systems, Computer Science, Engineering, Business, or a related field. - 7-10+ years of experience in technical analysis, business systems analysis, solution analysis, technology consulting, or related roles. - Experience collaborating with Product Owners, business stakeholders, project teams, and technology resources. - Demonstrated ability to identify incomplete requirements, ask clarifying questions, and work collaboratively to define solutions. - Strong understanding of business process analysis, workflow design, data flows, integrations, and enterprise applications. - Experience creating Technical Design Documents (TDDs), API specifications, process maps, workflow diagrams, data flow documentation, and functional specifications. - Experience contributing to solutions involving Power Platform, Power Apps, Power Automate, Dataverse, SharePoint, Azure services, React applications, SQL Server, and enterprise integrations. - Understanding of APIs, authentication methods, system integrations, relational databases, and enterprise application concepts. - Ability to review, understand, and communicate technical designs without requiring hands-on software development responsibilities. - Working knowledge of SDLC methodologies, Agile delivery practices, Azure DevOps, and solution governance processes. - Experience facilitating workshops, discovery sessions, requirements reviews, and solution discussions. - Strong analytical, problem-solving, facilitation, communication, and collaboration skills. - Excellent written and verbal communication skills with the ability to tailor messaging for technical and non-technical audiences. - Ability to manage competing priorities and support multiple initiatives in a fast-paced environment. - This is not a software development position. The ideal candidate is a solution-oriented professional who combines business analysis expertise, technical understanding, and strong documentation skills to transform business needs into clear, actionable requirements and solution designs that support successful technology delivery. We could treat the bullet list as Requirements (education + experience) and Qualifications (skills). But the list includes many skill items. Perhaps we split: Requirements: education and years experience. Qualifications: the rest of the skill/experience items. Thus Requirements section: Bachelor's degree... and 7-10+ years experience. Qualifications section: all the other bullet points (starting from Experience collaborating...). Also include the final paragraph about not a software development position and ideal candidate description. Benefits: from "WHY COHNREZNICK?" and later compensation paragraph. WHY COHNREZNICK? paragraph: "At CohnReznick, we’re united by a common mission to create opportunity, value, and trust for our clients, our people, and our communities. Whether it’s working alongside your peers to solve a client challenge, or volunteering together at the local food bank, there are so many ways to find your “why” at the firm. We believe it’s important to balance work with everyday life – and make time for enjoyment and fun. We invest in a robust Total Rewards package that includes everything from generous PTO, a flexible work environment, expanded parental leave, extensive learning & development, and even paid time off for employees to volunteer." Later compensation paragraph: "Actual compensation within the range will be dependent upon the individual's skills, experience, qualifications and location, and applicable employment laws. Salary is one component of the CohnReznick total rewards package, which includes a discretionary performance bonus, generous paid time off, expanded and inclusive parental benefits, and access to best-in-class learning and development platforms, to name a few." We can combine benefits: generous PTO, flexible work environment, expanded parental leave, extensive learning & development, paid time off for volunteering, discretionary performance bonus, generous paid time off (already), expanded and inclusive parental benefits, access to best-in-class learning and development platforms. We should not duplicate. Let's craft a Benefits section with bullet list of those items. Now we need to output only HTML fragment, no markdown fences. Let's construct:

  About the role

  ... (the paragraph)

  Responsibilities

  • ... each bullet

  Requirements

  • Bachelor's degree in Information Systems, Computer Science, Engineering, Business, or a related field.
  • 7-10+ years of experience in technical analysis, business systems analysis, solution analysis, technology consulting, or related roles.

  Qualifications

  • Experience collaborating with Product Owners, business stakeholders, project teams, and technology resources.
  • Demonstrated ability to identify incomplete requirements, ask clarifying questions, and work collaboratively to define solutions.
  • Strong understanding of business process analysis, workflow design, data flows, integrations, and enterprise applications.
  • Experience creating Technical Design Documents (TDDs), API specifications, process maps, workflow diagrams, data flow documentation, and functional specifications.
  • Experience contributing to solutions involving Power Platform, Power Apps, Power Automate, Dataverse, SharePoint, Azure