Lead Solutions Analyst

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Keep substantive info. We need to parse the job description. Key parts: - Intro: "As CohnReznick grows..." etc. That's about the firm, maybe "About the role" or "About the company". Could be "About the role" but we have "YOUR TEAM." then description of role. Could treat as "About the role" section. - "YOUR TEAM." then description: senior-level individual contributor role responsible for bridging business needs and technology solutions... etc. That's role description. - "WHY COHNREZNICK?" then description of mission, benefits, total rewards. That could be Benefits section? It includes generous PTO, flexible work environment, expanded parental leave, extensive learning & development, paid time off to volunteer. That's benefits. - "YOUR ROLE. Responsibilities Include But Not Limited To" then a long list of responsibilities (bullet-like sentences). That's Responsibilities. - "Your Experience." then list of qualifications/experience. That's Requirements/Qualifications/Skills. We need to decide sections: maybe "Qualifications" for education and years experience, "Skills" for specific abilities. But we can combine into "Requirements" or "Qualifications". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. We have About the role (intro + team), Responsibilities, Requirements (or Qualifications), Benefits. No explicit Pay or Schedule given (they mention compensation range dependent, but not specific numbers; they say "Actual compensation within the range will be dependent upon the individual's skills, experience, qualifications and location, and applicable employment laws." That's vague; we should not create Pay section because no specific pay. Similarly Schedule not given. Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Benefits. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. 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 description, but we can format them as lists or paragraphs. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, accommodation, etc. Also remove "Universal Job Standards" etc. Also remove "In addition, please take a moment to review our Universal Job Standards." etc. Also remove the paragraph about "Studies have shown that we are less likely to apply..." etc. Also remove the equal opportunity employer statement etc. Also remove the "Please note: This email address is reserved..." etc. Also remove the "#GD #IND123". Also remove the "To learn more about life at CohnReznick, v i sit Life at CohnReznick". Also remove the "Actual compensation within the range will be dependent upon ..."? That's about compensation but vague; we might keep it as part of Benefits? But it's not specific benefit; it's about compensation. Since we are not creating Pay section, we could include that sentence in Benefits or maybe in About the role? It's about compensation; but we have no Pay section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits we have (they list PTO, flexible work, parental leave, learning & development, volunteer time). The compensation sentence is not a specific benefit; it's generic. Might be okay to include in Benefits as a note? But it's not a benefit per se; it's about compensation. Safer to omit it because it's not a concrete benefit and we don't have a Pay section. However we must preserve ALL substantive information; but we can omit boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The compensation sentence is not boilerplate; it's substantive about pay. But we are not allowed to create Pay section unless posting actually states them. It does state that compensation is dependent on skills etc. That's still about pay but not a specific range. Could we include it in Benefits? Might be okay to include a

  under Benefits about compensation being based on skills etc. But the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about compensation, albeit vague. So we could include a Benefits section that includes both the listed benefits and a note about compensation. However the instruction also says "Prefer a few substantive sections over many thin ones." So we could combine compensation note into Benefits. Thus Benefits section will include: generous PTO, flexible work environment, expanded parental leave, extensive learning & development, paid time off for employees to volunteer. Also note that actual compensation depends on skills, experience, qualifications, location, and applicable employment laws, and includes discretionary performance bonus etc. Actually the posting also says: "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." That's more detail about total rewards. So we can include that. Thus Benefits section will have a

  • list of those items. Now Responsibilities: we have a long list of responsibilities each sentence starting with a verb. We'll turn each into
  • . Requirements/Qualifications: we have "Your Experience." then list of items: Bachelor's degree..., 7-10+ years..., Experience collaborating..., Demonstrated ability..., Strong understanding..., Experience creating..., Experience contributing to solutions..., Understanding of APIs..., Ability to review..., Working knowledge..., Experience facilitating..., Strong analytical..., Excellent written..., Ability to manage..., This is not a software development position..., The ideal candidate is a solution-oriented professional..., In addition, please take a moment to review our Universal Job Standards. (remove). Also the paragraph about "Studies have shown that we are less likely to apply..." (remove). Also the equal opportunity etc (remove). So we keep the substantive qualifications. We could split into Requirements (education, years experience) and Skills (specific abilities). But we can just have one section "Requirements" with a
    • list. We need to avoid filler like "commensurate with experience". Not present. Now About the role: we have introductory paragraphs about CohnReznick and the team. Could be two paragraphs: first about firm, second about team. We'll combine into

      elements. We must not repeat job title as heading. So we will not include "Lead Solutions Analyst" as heading. Now produce HTML fragment:

      About the role

      As CohnReznick grows, so do our career opportunities. As one of the nation’s top professional services firms, CohnReznick creates rewarding careers in advisory, assurance, and tax with team members who value innovation and collaboration in everything they do! CohnReznick helps organizations optimize performance, manage risk, and maximize value through CohnReznick LLP (assurance services) and CohnReznick Advisory LLC (advisory and tax services). Together, the firm provides leaders with deep industry knowledge and relationships, solutions to address clients’ unique business goals and risks, and insight on how emerging market forces can drive opportunity. With offices nationwide, the firm serves organizations around the world as an independent member of Nexia.

      YOUR TEAM. 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.

      Responsibilities

      • 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.

      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.
      • 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.