Lead Solutions Analyst
CohnReznick · Boca Raton, FL · 3 wk ago
RemoteRemoteInformation TechnologyFull-time
We need to output only HTML fragment, with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate, EEO, legal, etc. Must preserve all substantive info.
We need to parse the job description.
Key sections:
- Intro about company: "As CohnReznick grows..." etc. That's about the firm, could be "About the role"? Actually "About the role" maybe includes description of role and team. We'll decide.
- "YOUR TEAM." paragraph describing role responsibilities.
- "WHY COHNREZNICK?" paragraph about mission, benefits, total rewards.
- "YOUR ROLE. Responsibilities Include But Not Limited To" then bullet list of responsibilities.
- "Your Experience." bullet list of qualifications/experience.
- Then after that: "In addition, please take a moment to review our Universal Job Standards." That's boilerplate? Might be encouraging to apply; but it's not a qualification. Might be considered generic. We'll likely drop as it's not specific substantive content? It's encouraging to apply if not meet all qualifications. Could be considered part of "Requirements"? Might be considered generic. Safer to drop as it's not a concrete requirement.
- Then "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." This gives info about compensation and benefits. So we can have a Benefits section (maybe also Pay). Since they mention salary range not given, but they say compensation dependent on skills etc. No specific numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state benefits: discretionary performance bonus, generous PTO, expanded parental benefits, learning & development. So we can include Benefits section. Pay: they do not give specific numbers or range, just say dependent. That's not specific; we should not create Pay section because it's not stating actual pay. So omit Pay.
- Schedule: not mentioned. So omit.
- Then further boilerplate about brand name, equal opportunity, etc. Remove.
Thus sections:
- About the role (maybe combine intro and team description). Could have heading About the role with paragraphs describing the role, team, mission? Actually "WHY COHNREZNICK?" is about firm culture and benefits; could be Benefits section. But we already have Benefits separate. Could put "About the role" containing description of role and team (YOUR TEAM). Then "Responsibilities" with bullet list. Then "Requirements" maybe combine qualifications and experience? Actually we have "Your Experience." which includes qualifications. Could be Requirements or Qualifications. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content. We have experience/qualifications list; we could put under Requirements (or Qualifications). Also we have skills list within that. Could separate Skills? But we have many skill items; maybe better to put under Requirements. Since we want few substantive sections over many thin ones. So we can have: About the role, Responsibilities, Requirements, Benefits.
Let's extract content.
About the role: Should include description of team and role purpose. 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."
Also maybe include intro about firm? Could be part of About the role but not necessary. We'll keep that as About the role.
Responsibilities: bullet list from "YOUR ROLE. Responsibilities Include But Not Limited To" then each line.
Let's list them:
- 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/Qualifications: from "Your Experience." bullet list.
Let's extract each:
- 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 last sentence as part of description, not a requirement. Might include in About the role. But we can keep as part of Requirements.
Benefits: from "WHY COHNREZNICK?" and 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."
Then 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 to volunteer, discretionary performance bonus, generous paid time off (duplicate), expanded and inclusive parental benefits, access to best-in-class learning and development platforms. Also mention mission, work-life balance, enjoyment/fun. But those are more culture; still could be part of Benefits or About the role. Since Benefits section should contain tangible benefits. We'll list them.
We should not repeat items; we can consolidate.
Benefits list:
- Generous PTO (paid time off)
- Flexible work environment
- Expanded parental leave (expanded and inclusive parental benefits)
- Extensive learning & development (access to best-in-class learning and development platforms)
- Paid time off for employees to volunteer
- Discretionary performance bonus
We could also mention mission/value but that's not a benefit; could be part of About the role? But we already have About the role focusing on role. Could add a short paragraph about mission in About the role or separate section "About the firm"? Not allowed headings except those listed. Could include mission in About the role as part of description. But we already have About the role focusing on role; we could incorporate mission there.
Better: About the role includes description of role and also mention of firm's mission? Might be okay.
But we need to avoid duplication. We'll keep About the role as role/team description. Benefits as list.
Now produce HTML:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate, EEO, legal, etc. Must preserve all substantive info.
We need to parse the job description.
Key sections:
- Intro about company: "As CohnReznick grows..." etc. That's about the firm, could be "About the role"? Actually "About the role" maybe includes description of role and team. We'll decide.
- "YOUR TEAM." paragraph describing role responsibilities.
- "WHY COHNREZNICK?" paragraph about mission, benefits, total rewards.
- "YOUR ROLE. Responsibilities Include But Not Limited To" then bullet list of responsibilities.
- "Your Experience." bullet list of qualifications/experience.
- Then after that: "In addition, please take a moment to review our Universal Job Standards." That's boilerplate? Might be encouraging to apply; but it's not a qualification. Might be considered generic. We'll likely drop as it's not specific substantive content? It's encouraging to apply if not meet all qualifications. Could be considered part of "Requirements"? Might be considered generic. Safer to drop as it's not a concrete requirement.
- Then "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." This gives info about compensation and benefits. So we can have a Benefits section (maybe also Pay). Since they mention salary range not given, but they say compensation dependent on skills etc. No specific numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state benefits: discretionary performance bonus, generous PTO, expanded parental benefits, learning & development. So we can include Benefits section. Pay: they do not give specific numbers or range, just say dependent. That's not specific; we should not create Pay section because it's not stating actual pay. So omit Pay.
- Schedule: not mentioned. So omit.
- Then further boilerplate about brand name, equal opportunity, etc. Remove.
Thus sections:
- About the role (maybe combine intro and team description). Could have heading About the role with paragraphs describing the role, team, mission? Actually "WHY COHNREZNICK?" is about firm culture and benefits; could be Benefits section. But we already have Benefits separate. Could put "About the role" containing description of role and team (YOUR TEAM). Then "Responsibilities" with bullet list. Then "Requirements" maybe combine qualifications and experience? Actually we have "Your Experience." which includes qualifications. Could be Requirements or Qualifications. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content. We have experience/qualifications list; we could put under Requirements (or Qualifications). Also we have skills list within that. Could separate Skills? But we have many skill items; maybe better to put under Requirements. Since we want few substantive sections over many thin ones. So we can have: About the role, Responsibilities, Requirements, Benefits.
Let's extract content.
About the role: Should include description of team and role purpose. 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."
Also maybe include intro about firm? Could be part of About the role but not necessary. We'll keep that as About the role.
Responsibilities: bullet list from "YOUR ROLE. Responsibilities Include But Not Limited To" then each line.
Let's list them:
- 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/Qualifications: from "Your Experience." bullet list.
Let's extract each:
- 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 last sentence as part of description, not a requirement. Might include in About the role. But we can keep as part of Requirements.
Benefits: from "WHY COHNREZNICK?" and 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."
Then 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 to volunteer, discretionary performance bonus, generous paid time off (duplicate), expanded and inclusive parental benefits, access to best-in-class learning and development platforms. Also mention mission, work-life balance, enjoyment/fun. But those are more culture; still could be part of Benefits or About the role. Since Benefits section should contain tangible benefits. We'll list them.
We should not repeat items; we can consolidate.
Benefits list:
- Generous PTO (paid time off)
- Flexible work environment
- Expanded parental leave (expanded and inclusive parental benefits)
- Extensive learning & development (access to best-in-class learning and development platforms)
- Paid time off for employees to volunteer
- Discretionary performance bonus
We could also mention mission/value but that's not a benefit; could be part of About the role? But we already have About the role focusing on role. Could add a short paragraph about mission in About the role or separate section "About the firm"? Not allowed headings except those listed. Could include mission in About the role as part of description. But we already have About the role focusing on role; we could incorporate mission there.
Better: About the role includes description of role and also mention of firm's mission? Might be okay.
But we need to avoid duplication. We'll keep About the role as role/team description. Benefits as list.
Now produce HTML:
About the role
... paragraphs ...
Responsibilities
- ... each ...
Requirements
- ... each ...
Benefits
- ... each ...