AI Solution Software Engineer (Staff/Principal)

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 if posting has real specific content. We need to parse the job description. First, there is an introductory paragraph about CohnReznick, then "We currently have an exciting career opportunity for an AI Solution Software Engineer (Staff/Principal) to join our Strategic AI team." Then description of hybrid firm, remote. Then "YOUR TEAM." with description of Strategic AI team. Then "What We Mean By AI-Native" with bullet points. Then "WHY COHNREZNICK?" with description. Then "YOUR ROLE." with responsibilities list. Then "Your Experience." with required qualifications. Then "Preferred Qualifications" list. Then there is a paragraph about Universal Job Standards encouraging apply. Then legal boilerplate about brand name, alternative practice structure, etc. Then EEO statement, accommodation contact, note about unsolicited resumes. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove the Universal Job Standards paragraph? That is more like encouragement to apply; might be considered boilerplate? It's not exactly legal but it's a generic statement encouraging apply; might be considered application instructions? It says "please take a moment to review our Universal Job Standards... we encourage you to apply." That's somewhat application encouragement; might be considered boilerplate. The instruction says remove application instructions. So we should remove that paragraph. Also remove the brand name explanation, alternative practice structure, EEO statement, accommodation contact, note about unsolicited resumes. All that is legal boilerplate. We need to preserve substantive information: about the firm, role, team, AI-native definition, why CohnReznick, responsibilities, required experience, preferred qualifications. We need to decide sections. Potential sections: - About the role (maybe summary of role and firm) - Responsibilities (list) - Requirements (maybe required qualifications) - Qualifications (maybe preferred qualifications) - Skills (maybe list of skills like Python, TypeScript, C#, Azure AI, etc.) - Benefits (maybe from WHY COHNREZNICK? includes PTO, flexible work environment, parental leave, learning & development, volunteer time off) - Pay (not specified) - Schedule (maybe hybrid/remote info) We should only include sections if posting has real specific content. We have info about hybrid/remote: "CohnReznick is a hybrid firm and most of our professionals are located within a commutable distance to one of our offices. This position is considered remote which means it does not require job duties be performed within proximity of a CohnReznick office location. However, as a remote employee, you may be required to be present at a CohnReznick office with scheduled notice for client work, team meetings, or trainings". That's schedule/location info. So we could have a Schedule section. Benefits: WHY COHNREZNICK? includes robust Total Rewards package: generous PTO, flexible work environment, expanded parental leave, extensive learning & development, paid time off for employees to volunteer. That's benefits. Pay: not specified, so we should NOT include Pay section. Now About the role: we can summarize the role description: AI Solution Software Engineer (Staff/Principal) joining Strategic AI team, focusing on AI-enhanced solutions, AI-native team, etc. That's substantive. Responsibilities: list from "Responsibilities Include But Not Limited To" bullet points. Requirements: maybe the "Your Experience." list of required qualifications (10+ years, 5 years applied AI, Azure AI platform, proficiency in Python/TypeScript/C#, GitHub, VS Code, CI/CD, enterprise data security, foundational knowledge of LLM AI models, MCP, RAG, Bachelor/Master's degree). That's required. Qualifications: maybe "Preferred Qualifications" list. Skills: could be extracted from required and preferred but we might combine into Skills section? However we already have Requirements and Qualifications sections; Skills could be redundant. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine required and preferred into Requirements and Qualifications? Or we could have Requirements (required) and Qualifications (preferred). Skills maybe not needed. But we need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. That seems reasonable. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities, Requirements, Qualifications, Benefits we need lists. For About the role and Schedule we can use

  prose. Now we need to preserve all substantive information, not invent or summarize away detail. Must not lose details. Let's extract details. About the role: Should include that it's AI Solution Software Engineer (Staff/Principal) joining Strategic AI team, firm description maybe? But we should not repeat job title as heading (the page already shows it). So About the role section should contain prose about the role and firm. We can include: CohnReznick is a top professional services firm providing advisory, assurance, tax; Strategic AI team under COO, AI-native team delivering AI-enhanced solutions across firm; role is remote/hybrid; etc. But we must not invent. Let's pull from text: - "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 an AI Solution Software Engineer (Staff/Principal) to join our Strategic AI team." - "CohnReznick is a hybrid firm and most of our professionals are located within a commutable distance to one of our offices. This position is considered remote which means it does not require job duties be performed within proximity of a CohnReznick office location. However, as a remote employee, you may be required to be present at a CohnReznick office with scheduled notice for client work, team meetings, or trainings" - "YOUR TEAM. Strategic AI is a newly formed team under the COO’s organization, focused on delivering high-impact, AI-enhanced solutions across the firm. We are an AI-native team, meaning that everything we do—from planning and ideation to execution—leverages AI tools by default. Our mission is to solve complex business problems through applied AI, integrating capabilities into workflows, applications, and business processes." - "What We Mean By AI-Native An AI-native individual instinctively uses AI tools to plan, ideate, research, and execute tasks. AI is not an add‑on—it’s the default. This mindset includes: Starting every initiative with AI in mind Continuously learning and experimenting with the latest AI tools, models, and capabilities Treating AI as a core collaborator in problem-solving and execution" We could incorporate AI-native definition into About the role or maybe as part of Responsibilities? But we have a separate section for Responsibilities; we could include AI-native mindset as part of About the role or maybe as a separate section? But we only have headings list; we could add a section "AI-Native Mindset" but not in allowed headings list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we can use those headings. It doesn't forbid other headings, but says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should stick to those. Thus we need to fit AI-native definition somewhere, maybe in About the role or Responsibilities. Responsibilities list includes: Architect and develop AI-enabled applications leveraging LLMs, ML models, GenAI, RAG/GraphRAG, and NLP/NLM techniques; Build and maintain full-stack web applications, ensuring production readiness: Secure, scalable, and resilient solutions, in conjunction with cyber security, risk, and IAM teams; Design, implement secure and managed data connectors and integrations for AI use; Document architecture, workflows, and practices; contribute to internal learning and knowledge sharing. We can also include AI-native mindset as part of Responsibilities maybe as a bullet? But it's not a responsibility; it's a mindset. Could be part of About the role. Now Requirements: list from "Your Experience." bullet points (though they are numbered). We need to preserve all details. Let's extract required qualifications: - 10+ years in software engineering, with at least 5 years in applied AI solution delivery - Experience with Azure AI platform (OpenAI, AI Studio/Foundry, Cognitive Search), Azure Functions, and one of the coding harnesses (Claude, Copilot, Codex, Windsurf, or others) - Strong proficiency in Python, TypeScript, and C#; experience with full-stack frameworks and HTTP-based API middleware - Expertise with GitHub, VS Code, and CI/CD pipelines - Deep understanding of enterprise data security, governance, and compliance - Foundational knowledge of LLM AI models, MCP, and RAG - Demonstrated self-learning and continuous upskilling in AI tools, models, and capabilities - Bachelor’s or Master’s degree in Computer Science or related field (or equivalent experience) We should keep each as

  . Now Preferred Qualifications list: - Experience in knowledge-engineering and working with domain experts to build software that transforms and legacy processes - Experience with written specifications and/or product management - Experience working in high-compliance, legally-regulated environments such as healthcare or finance (“FinTech”) - Familiarity with security processes and requirements - Experience leading a team, working with outsourced engineers, providing feedback to stakeholders, and influencing technical and product roadmaps - Experience with Dataverse, Fabric, and other similar technologies We should keep each as

  . Benefits: from WHY COHNREZNICK? paragraph: "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." We can list benefits: generous PTO, flexible work environment, expanded parental leave, extensive learning & development, paid time off for employees to volunteer. Schedule: from hybrid/remote description: "CohnReznick is a hybrid firm and most of our professionals are located within a commutable distance to one of our offices. This position is considered remote which means it does not require job duties be performed within proximity of a CohnReznick office location. However, as a remote employee, you may be required to be present at a CohnReznick office with scheduled notice for client work, team meetings, or trainings" We can summarize as: Hybrid firm with remote option; occasional office presence required for client work, team meetings, trainings with scheduled notice. Now About the role: we need to combine firm description and role description. Let's craft a paragraph: "CohnReznick is a top national professional services firm offering advisory, assurance, and tax services through CohnReznick LLP and CohnReznick Advisory LLC, serving clients worldwide as an independent member of Nexia. The firm is launching an AI Solution Software Engineer (Staff/Principal) role within its newly formed Strategic AI team,