Lead Solutions Analyst
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones.
We need to extract substantive content: The posting includes:
- Intro paragraph about CohnReznick (maybe "About the role"? Actually it's about the firm). Could be "About the role" or "About the firm". But we have to use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings based on content.
We have sections:
- "YOUR TEAM." describes role responsibilities: bridging business needs and technology solutions, etc. Could map to "Responsibilities".
- "WHY COHNREZNICK?" describes firm culture, total rewards, benefits. Could map to "Benefits" (maybe also "About the role"? but we have Benefits heading). 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. That's definitely responsibilities.
- "Your Experience." lists qualifications: degree, years experience, etc. Could map to "Requirements" or "Qualifications". We have both headings; we need to decide. Probably "Qualifications" for experience/education, and "Skills" for skills list. But we can combine.
We need to avoid filler. No Pay or Schedule sections because not explicitly stated (though they mention compensation range dependent on skills etc but not actual numbers). So we should not create Pay or Schedule.
We need to output only HTML fragment, no /, no markdown fences.
We need to use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details as given, but we can format them into lists.
We need to remove boilerplate: EEO, legal, accommodation, unsolicited resumes, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "In addition, please take a moment to review our Universal Job Standards." etc. Also remove the "Studies have shown..." paragraph encouraging to apply if not perfect qualification. That's maybe not boilerplate but it's more of a encouragement; but it's still part of the posting. Should we keep? It's not a list; it's prose encouraging to apply. Might be considered part of the description but not essential? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Studies have shown..." is not exactly those categories, but it's more of a motivational note. It's not a list; it's prose. I'd keep it as part of the "Your Experience" section maybe.
Also remove the paragraph about Universal Job Standards etc. That's likely boilerplate.
Also remove the paragraph about "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..." That's about compensation but not specific numbers; we should not create Pay section, but we could include that prose in Benefits? It's about compensation but not specific. Since we shouldn't create Pay section unless posting actually states them (they do not state specific pay). So we should not create a Pay heading. However we could include that sentence in Benefits? It's about total rewards; but Benefits heading is for benefits like PTO etc. The sentence about compensation could be considered part of Benefits but it's vague. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state benefits (PTO, flexible work, parental leave, learning & development, volunteer time). So Benefits section is okay. The compensation sentence is not a specific benefit; it's about salary being part of total rewards. Might be okay to include in Benefits as prose, but we risk creating a Pay section inadvertently. Safer to include that sentence in Benefits as prose? It's not a list; it's prose. Could be okay.
But we need to avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive information: So we need to keep the details about responsibilities, experience, qualifications, benefits, etc.
Let's extract sections:
Section 1: About the role? Could be the introductory paragraph about CohnReznick growth and the role. But we already have "YOUR TEAM." which describes role. Maybe we can use "About the role" for the intro paragraph that describes the role and team. However the instructions say use headings like About the role, Responsibilities, etc. We can decide to have:
-
About the role
: containing the introductory paragraph about CohnReznick and the role (the first paragraph up to "YOUR TEAM." maybe). But we need to avoid duplication.
Alternatively we could have:
- Responsibilities
: containing the "YOUR TEAM." description and the bullet list under "YOUR ROLE. Responsibilities Include But Not Limited To". That seems appropriate.
- Qualifications
: containing the "Your Experience." bullet list (education, years experience, etc.) plus maybe the skills list.
- Benefits
: containing the "WHY COHNREZNICK?" paragraph about total rewards.
We could also have Skills
for the skills list (analytical, communication, etc.) but we can incorporate into Qualifications.
We need to avoid thin sections; prefer few substantive sections. So maybe three sections: Responsibilities, Qualifications, Benefits.
We need to ensure we include all substantive info.
Let's parse the content:
Intro: "Job Description 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 about the firm and the role. Could be part of About the role. But we might incorporate into Responsibilities? It's more about the firm. Could be About the role.
But we have to avoid duplication; we can include this as a short paragraph under About the role.
Then "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 responsibilities.
Then "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."
That's benefits.
Then "YOUR ROLE. Responsibilities Include But Not Limited To" followed by a long list of responsibilities (each sentence ends with a period). That's more responsibilities.
Then "Your Experience." followed by bullet list of qualifications (education, years experience, etc.) and then a paragraph about "This is not a software development position..." and then encouragement to apply etc.
We need to capture all substantive info.
Let's structure:
About the role
Intro paragraph about CohnReznick growth and the Lead Solutions Analyst role.
Responsibilities
YOUR TEAM paragraph (maybe combine with the list). Then
list of responsibilities from "YOUR ROLE. Responsibilities Include But Not Limited To". Each bullet as - . Actually we need
- for list. So we can have a
for the YOUR TEAM paragraph, then
for the list.
But we need to ensure we don't lose any details from the YOUR TEAM paragraph that are not in the list. So we keep that paragraph.
Then Qualifications
Your Experience bullet list (education, years experience, etc.) as
- . plus maybe the paragraph about "This is not a software development position..." and the encouragement to apply (the "Studies have shown..." paragraph). That's prose, so
.
Then
Benefits
WHY COHNREZNICK? paragraph.
We should not include the paragraph about compensation (Actual compensation within the range...) because it's not specific pay/benefits; but it's about total rewards. Could be included in Benefits as prose. However the instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state benefits (PTO etc). So Benefits section is okay. Including compensation sentence in Benefits is okay
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to extract substantive content: The posting includes: - Intro paragraph about CohnReznick (maybe "About the role"? Actually it's about the firm). Could be "About the role" or "About the firm". But we have to use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings based on content. We have sections: - "YOUR TEAM." describes role responsibilities: bridging business needs and technology solutions, etc. Could map to "Responsibilities". - "WHY COHNREZNICK?" describes firm culture, total rewards, benefits. Could map to "Benefits" (maybe also "About the role"? but we have Benefits heading). 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. That's definitely responsibilities. - "Your Experience." lists qualifications: degree, years experience, etc. Could map to "Requirements" or "Qualifications". We have both headings; we need to decide. Probably "Qualifications" for experience/education, and "Skills" for skills list. But we can combine. We need to avoid filler. No Pay or Schedule sections because not explicitly stated (though they mention compensation range dependent on skills etc but not actual numbers). So we should not create Pay or Schedule. We need to output only HTML fragment, no /, no markdown fences. We need to use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details as given, but we can format them into lists.
We need to remove boilerplate: EEO, legal, accommodation, unsolicited resumes, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "In addition, please take a moment to review our Universal Job Standards." etc. Also remove the "Studies have shown..." paragraph encouraging to apply if not perfect qualification. That's maybe not boilerplate but it's more of a encouragement; but it's still part of the posting. Should we keep? It's not a list; it's prose encouraging to apply. Might be considered part of the description but not essential? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Studies have shown..." is not exactly those categories, but it's more of a motivational note. It's not a list; it's prose. I'd keep it as part of the "Your Experience" section maybe.
Also remove the paragraph about Universal Job Standards etc. That's likely boilerplate.
Also remove the paragraph about "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..." That's about compensation but not specific numbers; we should not create Pay section, but we could include that prose in Benefits? It's about compensation but not specific. Since we shouldn't create Pay section unless posting actually states them (they do not state specific pay). So we should not create a Pay heading. However we could include that sentence in Benefits? It's about total rewards; but Benefits heading is for benefits like PTO etc. The sentence about compensation could be considered part of Benefits but it's vague. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state benefits (PTO, flexible work, parental leave, learning & development, volunteer time). So Benefits section is okay. The compensation sentence is not a specific benefit; it's about salary being part of total rewards. Might be okay to include in Benefits as prose, but we risk creating a Pay section inadvertently. Safer to include that sentence in Benefits as prose? It's not a list; it's prose. Could be okay.
But we need to avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive information: So we need to keep the details about responsibilities, experience, qualifications, benefits, etc.
Let's extract sections:
Section 1: About the role? Could be the introductory paragraph about CohnReznick growth and the role. But we already have "YOUR TEAM." which describes role. Maybe we can use "About the role" for the intro paragraph that describes the role and team. However the instructions say use headings like About the role, Responsibilities, etc. We can decide to have:
-
About the role
: containing the introductory paragraph about CohnReznick and the role (the first paragraph up to "YOUR TEAM." maybe). But we need to avoid duplication.
Alternatively we could have:
- Responsibilities
: containing the "YOUR TEAM." description and the bullet list under "YOUR ROLE. Responsibilities Include But Not Limited To". That seems appropriate.
- Qualifications
: containing the "Your Experience." bullet list (education, years experience, etc.) plus maybe the skills list.
- Benefits
: containing the "WHY COHNREZNICK?" paragraph about total rewards.
We could also have Skills
for the skills list (analytical, communication, etc.) but we can incorporate into Qualifications.
We need to avoid thin sections; prefer few substantive sections. So maybe three sections: Responsibilities, Qualifications, Benefits.
We need to ensure we include all substantive info.
Let's parse the content:
Intro: "Job Description 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 about the firm and the role. Could be part of About the role. But we might incorporate into Responsibilities? It's more about the firm. Could be About the role.
But we have to avoid duplication; we can include this as a short paragraph under About the role.
Then "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 responsibilities.
Then "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."
That's benefits.
Then "YOUR ROLE. Responsibilities Include But Not Limited To" followed by a long list of responsibilities (each sentence ends with a period). That's more responsibilities.
Then "Your Experience." followed by bullet list of qualifications (education, years experience, etc.) and then a paragraph about "This is not a software development position..." and then encouragement to apply etc.
We need to capture all substantive info.
Let's structure:
About the role
Intro paragraph about CohnReznick growth and the Lead Solutions Analyst role.
Responsibilities
YOUR TEAM paragraph (maybe combine with the list). Then
list of responsibilities from "YOUR ROLE. Responsibilities Include But Not Limited To". Each bullet as - . Actually we need
- for list. So we can have a
for the YOUR TEAM paragraph, then
for the list.
But we need to ensure we don't lose any details from the YOUR TEAM paragraph that are not in the list. So we keep that paragraph.
Then Qualifications
Your Experience bullet list (education, years experience, etc.) as
- . plus maybe the paragraph about "This is not a software development position..." and the encouragement to apply (the "Studies have shown..." paragraph). That's prose, so
.
Then
Benefits
WHY COHNREZNICK? paragraph.
We should not include the paragraph about compensation (Actual compensation within the range...) because it's not specific pay/benefits; but it's about total rewards. Could be included in Benefits as prose. However the instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state benefits (PTO etc). So Benefits section is okay. Including compensation sentence in Benefits is okay
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details as given, but we can format them into lists. We need to remove boilerplate: EEO, legal, accommodation, unsolicited resumes, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "In addition, please take a moment to review our Universal Job Standards." etc. Also remove the "Studies have shown..." paragraph encouraging to apply if not perfect qualification. That's maybe not boilerplate but it's more of a encouragement; but it's still part of the posting. Should we keep? It's not a list; it's prose encouraging to apply. Might be considered part of the description but not essential? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Studies have shown..." is not exactly those categories, but it's more of a motivational note. It's not a list; it's prose. I'd keep it as part of the "Your Experience" section maybe. Also remove the paragraph about Universal Job Standards etc. That's likely boilerplate. Also remove the paragraph about "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..." That's about compensation but not specific numbers; we should not create Pay section, but we could include that prose in Benefits? It's about compensation but not specific. Since we shouldn't create Pay section unless posting actually states them (they do not state specific pay). So we should not create a Pay heading. However we could include that sentence in Benefits? It's about total rewards; but Benefits heading is for benefits like PTO etc. The sentence about compensation could be considered part of Benefits but it's vague. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state benefits (PTO, flexible work, parental leave, learning & development, volunteer time). So Benefits section is okay. The compensation sentence is not a specific benefit; it's about salary being part of total rewards. Might be okay to include in Benefits as prose, but we risk creating a Pay section inadvertently. Safer to include that sentence in Benefits as prose? It's not a list; it's prose. Could be okay. But we need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive information: So we need to keep the details about responsibilities, experience, qualifications, benefits, etc. Let's extract sections: Section 1: About the role? Could be the introductory paragraph about CohnReznick growth and the role. But we already have "YOUR TEAM." which describes role. Maybe we can use "About the role" for the intro paragraph that describes the role and team. However the instructions say use headings like About the role, Responsibilities, etc. We can decide to have: -
About the role
: containing the introductory paragraph about CohnReznick and the role (the first paragraph up to "YOUR TEAM." maybe). But we need to avoid duplication. Alternatively we could have: -Responsibilities
: containing the "YOUR TEAM." description and the bullet list under "YOUR ROLE. Responsibilities Include But Not Limited To". That seems appropriate. -Qualifications
: containing the "Your Experience." bullet list (education, years experience, etc.) plus maybe the skills list. -Benefits
: containing the "WHY COHNREZNICK?" paragraph about total rewards. We could also haveSkills
for the skills list (analytical, communication, etc.) but we can incorporate into Qualifications. We need to avoid thin sections; prefer few substantive sections. So maybe three sections: Responsibilities, Qualifications, Benefits. We need to ensure we include all substantive info. Let's parse the content: Intro: "Job Description 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 about the firm and the role. Could be part of About the role. But we might incorporate into Responsibilities? It's more about the firm. Could be About the role. But we have to avoid duplication; we can include this as a short paragraph under About the role. Then "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 responsibilities. Then "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." That's benefits. Then "YOUR ROLE. Responsibilities Include But Not Limited To" followed by a long list of responsibilities (each sentence ends with a period). That's more responsibilities. Then "Your Experience." followed by bullet list of qualifications (education, years experience, etc.) and then a paragraph about "This is not a software development position..." and then encouragement to apply etc. We need to capture all substantive info. Let's structure:About the role
Intro paragraph about CohnReznick growth and the Lead Solutions Analyst role.
Responsibilities
YOUR TEAM paragraph (maybe combine with the list). Then
- list of responsibilities from "YOUR ROLE. Responsibilities Include But Not Limited To". Each bullet as
- . Actually we need
- for list. So we can have a
for the YOUR TEAM paragraph, then
- for the list.
But we need to ensure we don't lose any details from the YOUR TEAM paragraph that are not in the list. So we keep that paragraph.
Then
- . plus maybe the paragraph about "This is not a software development position..." and the encouragement to apply (the "Studies have shown..." paragraph). That's prose, so
. Then
Benefits
WHY COHNREZNICK? paragraph.
We should not include the paragraph about compensation (Actual compensation within the range...) because it's not specific pay/benefits; but it's about total rewards. Could be included in Benefits as prose. However the instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state benefits (PTO etc). So Benefits section is okay. Including compensation sentence in Benefits is okay
Qualifications
Your Experience bullet list (education, years experience, etc.) as
- . plus maybe the paragraph about "This is not a software development position..." and the encouragement to apply (the "Studies have shown..." paragraph). That's prose, so
- for list. So we can have a