Lead Solutions Analyst
CohnReznick · Miami, FL · 3 wk ago
RemoteRemoteInformation TechnologyFull-time
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. The posting includes: About the role (intro paragraph), Responsibilities (list), Your Experience (qualifications/requirements), maybe Skills (some bullet points). Benefits: mention "Why CohnReznick?" includes robust Total Rewards package: generous PTO, flexible work environment, expanded parental leave, extensive learning & development, paid time off for volunteers. That's benefits. Pay: they mention "Actual compensation within the range will be dependent upon the individual's skills, experience, qualifications and location, and applicable employment laws." That's vague, not a specific range; they say salary is one component. This is not a specific pay figure, but they mention compensation dependent on skills etc. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. For Benefits, they do state specifics: generous PTO, flexible work environment, expanded parental leave, extensive learning & development, paid time off for employees to volunteer. So Benefits section is valid. Pay: they do not give a specific number or range; they say actual compensation within the range will be dependent... That's not a specific pay figure; it's vague. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since they didn't state a specific pay range or amount, we should not include Pay section. Schedule: not mentioned. So we omit Pay and Schedule.
We need sections: About the role (maybe heading "About the role"), Responsibilities, Requirements (or Qualifications), Skills, Benefits. The posting includes "Your Experience." which is qualifications/experience. Also there are skill-like bullet points: strong analytical, problem-solving, facilitation, communication, collaboration skills; excellent written and verbal communication; ability to manage competing priorities; etc. Could be Skills section.
We must not repeat job title as heading. No Job ID etc.
We need to preserve all substantive information, not invent or summarize away detail. Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the role (intro paragraph), Responsibilities (list), Your Experience (qualifications/requirements), maybe Skills (some bullet points). Benefits: mention "Why CohnReznick?" includes robust Total Rewards package: generous PTO, flexible work environment, expanded parental leave, extensive learning & development, paid time off for volunteers. That's benefits. Pay: they mention "Actual compensation within the range will be dependent upon the individual's skills, experience, qualifications and location, and applicable employment laws." That's vague, not a specific range; they say salary is one component. This is not a specific pay figure, but they mention compensation dependent on skills etc. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. For Benefits, they do state specifics: generous PTO, flexible work environment, expanded parental leave, extensive learning & development, paid time off for employees to volunteer. So Benefits section is valid. Pay: they do not give a specific number or range; they say actual compensation within the range will be dependent... That's not a specific pay figure; it's vague. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since they didn't state a specific pay range or amount, we should not include Pay section. Schedule: not mentioned. So we omit Pay and Schedule.
We need sections: About the role (maybe heading "About the role"), Responsibilities, Requirements (or Qualifications), Skills, Benefits. The posting includes "Your Experience." which is qualifications/experience. Also there are skill-like bullet points: strong analytical, problem-solving, facilitation, communication, collaboration skills; excellent written and verbal communication; ability to manage competing priorities; etc. Could be Skills section.
We must not repeat job title as heading. No Job ID etc.
We need to preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits, and
for prose.
We need to extract lists.
Let's parse:
Intro paragraph: "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. We currently have an exciting career opportunity for a Lead Solutions Analyst to join the Global Digital & CyberSecurity team."
That's prose for About the role.
Then "YOUR TEAM." paragraph: description of role. Could be part of About the role or separate? Probably part of About the role. We'll keep as prose.
Then "WHY COHNREZNICK?" paragraph: benefits description. We'll put under Benefits.
Then "YOUR ROLE. Responsibilities Include But Not Limited To" then a long list of responsibilities each ending with period. We'll make a
- list.
Then "Your Experience." then bullet list of qualifications (each line ends with period). We'll make a
- list under Requirements or Qualifications.
Then after that there is a paragraph about "This is not a software development position..." etc. That's more qualifications/skills. Could be part of Requirements.
Then "In addition, please take a moment to review our Universal Job Standards..." etc. That's boilerplate encouraging diversity; we should remove boilerplate? It's not cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate? It's about encouraging to apply even if not meet all qualifications; that's somewhat EEO-ish but maybe considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This paragraph is encouraging to apply; might be considered EEO boilerplate? It's about diversity and inclusion; likely considered EEO boilerplate. So we should remove it.
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 is about compensation and benefits; we already have Benefits section; we could incorporate some of this into Benefits (discretionary performance bonus, generous PTO, expanded parental benefits, learning & development). However we already captured benefits from Why CohnReznick section; we can add more details.
Then "To learn more about life at CohnReznick, v i sit Life at CohnReznick "CohnReznick" is the brand name..." That's boilerplate about firm structure; likely legal boilerplate; remove.
Then "CohnReznick LLP and CohnReznick Advisory LLC (and their respective subsidiaries) practice in an alternative practice structure..." etc. That's legal boilerplate; remove.
Then "CohnReznick is an equal opportunity employer..." etc. That's EEO boilerplate; remove.
Then "If you are an individual with a disability..." etc. That's accommodation info; maybe considered legal; remove.
Then "Please note: This email address is reserved..." etc. That's application instruction? Actually it's about accommodation; could be considered legal; remove.
Then "CohnReznick does not accept unsolicited resumes from third-party recruiters..." etc. That's legal; remove.
Then "#GD #IND123" maybe internal tags; remove.
Thus we keep: About the role (intro + YOUR TEAM), Responsibilities list, Requirements/Qualifications list (Your Experience + maybe the "This is not a software development position" paragraph), Benefits list (Why CohnReznick + compensation benefits paragraph), maybe Skills section (some of the skills mentioned in Your Experience could be split). But we can combine Requirements and Skills? The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications (which includes experience and skills), Benefits. That's four sections.
We need to use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
Thus:
About the role
... (combined intro and YOUR TEAM paragraph)
Responsibilities
- ... each responsibility
Qualifications
- ... each qualification/experience/skill
Benefits
- ... each benefit
.
We need to ensure we preserve all substantive information. Let's extract.
About the role prose:
Combine:
"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. We currently have an exciting career opportunity for a Lead Solutions Analyst to join the Global Digital & CyberSecurity team.
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."
That's the prose.
Now Responsibilities list: The bullet points after "YOUR ROLE. Responsibilities Include But Not Limited To". Let's extract each line (they are sentences ending with period). We'll 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 15 items.
Now Qualifications list: From "Your Experience." bullet list plus maybe the "This is not a software development position..." paragraph.
Your Experience bullet 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,
for prose. We need to extract lists. Let's parse: Intro paragraph: "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. We currently have an exciting career opportunity for a Lead Solutions Analyst to join the Global Digital & CyberSecurity team." That's prose for About the role. Then "YOUR TEAM." paragraph: description of role. Could be part of About the role or separate? Probably part of About the role. We'll keep as prose. Then "WHY COHNREZNICK?" paragraph: benefits description. We'll put under Benefits. Then "YOUR ROLE. Responsibilities Include But Not Limited To" then a long list of responsibilities each ending with period. We'll make a
- list.
Then "Your Experience." then bullet list of qualifications (each line ends with period). We'll make a
- list under Requirements or Qualifications.
Then after that there is a paragraph about "This is not a software development position..." etc. That's more qualifications/skills. Could be part of Requirements.
Then "In addition, please take a moment to review our Universal Job Standards..." etc. That's boilerplate encouraging diversity; we should remove boilerplate? It's not cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate? It's about encouraging to apply even if not meet all qualifications; that's somewhat EEO-ish but maybe considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This paragraph is encouraging to apply; might be considered EEO boilerplate? It's about diversity and inclusion; likely considered EEO boilerplate. So we should remove it.
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 is about compensation and benefits; we already have Benefits section; we could incorporate some of this into Benefits (discretionary performance bonus, generous PTO, expanded parental benefits, learning & development). However we already captured benefits from Why CohnReznick section; we can add more details.
Then "To learn more about life at CohnReznick, v i sit Life at CohnReznick "CohnReznick" is the brand name..." That's boilerplate about firm structure; likely legal boilerplate; remove.
Then "CohnReznick LLP and CohnReznick Advisory LLC (and their respective subsidiaries) practice in an alternative practice structure..." etc. That's legal boilerplate; remove.
Then "CohnReznick is an equal opportunity employer..." etc. That's EEO boilerplate; remove.
Then "If you are an individual with a disability..." etc. That's accommodation info; maybe considered legal; remove.
Then "Please note: This email address is reserved..." etc. That's application instruction? Actually it's about accommodation; could be considered legal; remove.
Then "CohnReznick does not accept unsolicited resumes from third-party recruiters..." etc. That's legal; remove.
Then "#GD #IND123" maybe internal tags; remove.
Thus we keep: About the role (intro + YOUR TEAM), Responsibilities list, Requirements/Qualifications list (Your Experience + maybe the "This is not a software development position" paragraph), Benefits list (Why CohnReznick + compensation benefits paragraph), maybe Skills section (some of the skills mentioned in Your Experience could be split). But we can combine Requirements and Skills? The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications (which includes experience and skills), Benefits. That's four sections.
We need to use
for section headings. Use
- for any list of duties/requirements/benefits, and
for prose. Thus:
About the role
... (combined intro and YOUR TEAM paragraph)
Responsibilities
- ... each responsibility
Qualifications
- ... each qualification/experience/skill
Benefits
- ... each benefit . We need to ensure we preserve all substantive information. Let's extract. About the role prose: Combine: "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. We currently have an exciting career opportunity for a Lead Solutions Analyst to join the Global Digital & CyberSecurity team. 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." That's the prose. Now Responsibilities list: The bullet points after "YOUR ROLE. Responsibilities Include But Not Limited To". Let's extract each line (they are sentences ending with period). We'll 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 15 items. Now Qualifications list: From "Your Experience." bullet list plus maybe the "This is not a software development position..." paragraph. Your Experience bullet 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,
- for any list of duties/requirements/benefits, and
- list under Requirements or Qualifications.
Then after that there is a paragraph about "This is not a software development position..." etc. That's more qualifications/skills. Could be part of Requirements.
Then "In addition, please take a moment to review our Universal Job Standards..." etc. That's boilerplate encouraging diversity; we should remove boilerplate? It's not cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate? It's about encouraging to apply even if not meet all qualifications; that's somewhat EEO-ish but maybe considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This paragraph is encouraging to apply; might be considered EEO boilerplate? It's about diversity and inclusion; likely considered EEO boilerplate. So we should remove it.
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 is about compensation and benefits; we already have Benefits section; we could incorporate some of this into Benefits (discretionary performance bonus, generous PTO, expanded parental benefits, learning & development). However we already captured benefits from Why CohnReznick section; we can add more details.
Then "To learn more about life at CohnReznick, v i sit Life at CohnReznick "CohnReznick" is the brand name..." That's boilerplate about firm structure; likely legal boilerplate; remove.
Then "CohnReznick LLP and CohnReznick Advisory LLC (and their respective subsidiaries) practice in an alternative practice structure..." etc. That's legal boilerplate; remove.
Then "CohnReznick is an equal opportunity employer..." etc. That's EEO boilerplate; remove.
Then "If you are an individual with a disability..." etc. That's accommodation info; maybe considered legal; remove.
Then "Please note: This email address is reserved..." etc. That's application instruction? Actually it's about accommodation; could be considered legal; remove.
Then "CohnReznick does not accept unsolicited resumes from third-party recruiters..." etc. That's legal; remove.
Then "#GD #IND123" maybe internal tags; remove.
Thus we keep: About the role (intro + YOUR TEAM), Responsibilities list, Requirements/Qualifications list (Your Experience + maybe the "This is not a software development position" paragraph), Benefits list (Why CohnReznick + compensation benefits paragraph), maybe Skills section (some of the skills mentioned in Your Experience could be split). But we can combine Requirements and Skills? The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications (which includes experience and skills), Benefits. That's four sections.
We need to use