Consulting Data Architect - Microsoft Fabric

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. No job title heading. No Job ID etc. Remove boilerplate like EEO, navigation, etc. Must preserve all substantive info. We need to parse the posting. Content: Intro paragraph: "The Consulting Data Architect makes innovative contributions ..." That's about the role. Could be "About the role" section. Then "What you will do" list of duties. That's responsibilities. Then "What we expect of you" includes requirements, qualifications, skills. Then "Pay range: $128,000 - $193,200 depending on experience and skill set Annual bonus target of 10% subject to terms and conditions of plan Benefits overview: https://cdw.benefit-info.com/ Salary ranges may be subject to geographic differentials" Then some culture statements: "CDW is committed to being an AI-fluent organization ..." That's maybe about company but not needed? Might be considered "About Us" but not required heading. We can include as a paragraph maybe under "About the role" or separate? The instruction: include a section ONLY when posting has real, specific content for it. The "About Us" is present but not one of the prescribed headings. We could put it under "About the role" or maybe not include separate heading. Probably we can incorporate into "About the role" as prose. Also there is EEO statement at end: remove. Also there is "Additionally, CDW is committed to fostering an equitable..." that's EEO-ish, remove. Also "We’re looking for people who bring curiosity..." that's culture, could be part of "About the role" or maybe a separate "About CDW" but not required heading. Probably incorporate into "About the role". We need to output only HTML fragment, no markdown fences. We'll create sections:

About the role

with paragraphs summarizing the role description and maybe culture.

Responsibilities

with

• for each duty from "What you will do". Need to preserve all specifics. Let's extract duties: - Design and deliver Microsoft Fabric architectures that incorporate OneLake, Power BI, data engineering, real-time analytics, Copilot experiences, Azure AI services, and Generative AI solution patterns. - Lead development of practical AI-enabled solution patterns, including retrieval-augmented generation, vector search, embedding pipelines, prompt orchestration, semantic search, and AI-enabled analytics workflows. - Build and validate proofs of concept, prototypes, reusable accelerators, reference architectures, and implementation templates that help move data and AI solutions from concept to production-ready outcomes. - Lead project teams, directing coworker and client teams in solution design and development. - Provide leadership in creating business cases, financial justification and solution benefit content for customer ready deliverables and presentations. - Aggregate oversight of technical solutions across multiple projects to ensure synergy in our approach and broad visibility to the solutions delivery team - Proactively addresses or escalates any budget issues that are identified during the project. - Quality Assurance for SOW requests that meet triggers for size, cross brand, and complexity. - Perform peer review of deliverables from other team members for technical content to ensure accuracy. - Maintain client relationships as a trusted Technical Advisor. - Serve as focal point for communications between multiple departments and clients, when necessary, using experience and judgment to communicate effectively to all parties. - Recommend solutions supporting client account teams with development of proposals, quotations, and presentations. Also earlier: "Provides technical expertise in analyzing client’s requirements to develop services offerings across multiple technology solutions that provide significant value." That's also a duty but maybe part of responsibilities. Could include. We'll include that as a bullet. Now Requirements/Qualifications/Skills: The "What we expect of you" includes many items. We could split into Requirements (education/experience), Qualifications (specific experience), Skills (technical). But instruction: prefer few substantive sections over many thin ones. Could combine into one section "Requirements and Qualifications" but headings limited to given list: we have Requirements, Qualifications, Skills. We could use all three if they have content. Let's see. Education/experience: Bachelor’s degree and 7+ years of IT Infrastructure experience, including 3 years of experience with large enterprise cross-brand projects OR 11+ years of IT Infrastructure experience, including 3 years of experience with large enterprise cross-brand projects. Experience should include enterprise data platform implementation, analytics, AI-enabled solution delivery, or Microsoft Fabric-focused consulting delivery. That's requirements. Then "Demonstrated hands-on experience designing, building, implementing, troubleshooting, and optimizing Microsoft Fabric solutions, including Data Engineering, Data Factory, OneLake, Direct Lake, semantic models, pipelines, notebooks, and Power BI." That's qualifications/skills. Then "Practical experience with Generative AI capabilities such as Azure OpenAI, Azure AI Search, Copilot, retrieval-augmented generation, embeddings, prompt engineering, grounding patterns, and AI service integration." Then "Strong data engineering and implementation skills, including SQL, Python, Spark or PySpark, modern ELT patterns, CI/CD practices, and the ability to configure, test, and optimize solutions directly in the platform." Then "Ability to define and apply data governance, AI governance, security, and responsible AI controls, including RBAC, data classification, auditability, sensitivity labeling, prompt protection, content safety, and secure handling of sensitive data." Then "The candidate will be expected to maintain client relationships as a trusted Technical Advisor and serve as the focal point for communications between multiple departments and clients when necessary. They should be able to take a lead technical role in reviewing and editing deliverables produced by other Engineering and Consulting teams." Then "Provide technical expertise in analyzing client’s requirements to develop IT services offerings across multiple technology solutions." (duplicate) Then "Should also be able to recommend solutions and support internal account teams with the development of proposals, quotations, and presentations." Then "Excellent written, presentation, and verbal communication skills are required, including demonstrated experience presenting technology recommendations from a business perspective to internal and external clients." Then "Proven ability to research advanced and complex technology solutions, evaluate alternatives, make recommendations, and present materials to clients in a manner that meets clients’ needs." Then "Must be able to act calmly and productively when confronted with change, ambiguity, and risk, and deal constructively with problems that do not have clear solutions or outcomes." Then "Demonstrated experience applying lessons learned to unique problems and a history of reskilling on new technologies with the ability to determine benefits for clients." Then "Should have the ability and willingness to travel as needed to other CDW locations or client sites." Then "A valid U.S. driver’s license is required." Thus we can split: Requirements (education/experience), Qualifications (hands-on experience with Fabric, GenAI, data engineering, governance), Skills (communication, travel, driver's license, etc). But many overlap. Given instruction to prefer few substantive sections, maybe we combine Requirements and Qualifications into one section "Requirements". But we have separate headings allowed; we could still use both if they have content. However we risk thin sections. Let's see if we can make three sections each with decent content. Requirements: education/experience bullet. Qualifications: hands-on experience with Fabric, GenAI, data engineering, governance. Skills: communication, presentation, travel, driver's license, ability to work with change, etc. That seems reasonable. Now Pay and Benefits: we have Pay range and bonus, benefits overview link. Also "Salary ranges may be subject to geographic differentials". That's pay info. Benefits: we have a link to benefits overview. No details of benefits given besides link. Should we include Benefits section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay range and bonus, and mentions Benefits overview link. So we can include Pay and Benefits sections. Schedule not mentioned, so omit. Pay section: include pay range and bonus target. Benefits section: include the link and maybe note "Benefits overview: https://cdw.benefit-info.com/". Could also mention that benefits are described there. We should not include boilerplate like "CDW is committed to being an AI-fluent organization..." but that is substantive culture; could be included under About the role or maybe a separate "About CDW" but not in headings list. Probably incorporate into About the role. Now we need to remove duplicated lines: e.g., "Maintain client relationships as a trusted Technical Advisor." appears both in responsibilities and qualifications; we should keep only once? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate lines: we should keep them? It says remove duplicated lines. So we should deduplicate. So we need to ensure each piece of info appears only once. We'll need to check duplicates. List of responsibilities includes "Maintain client relationships as a trusted Technical Advisor." and "Serve as focal point for communications between multiple departments and clients, when necessary, using experience and judgment to communicate effectively to all parties." and "Recommend solutions supporting client account teams with development of proposals, quotations, and presentations." Qualifications includes similar lines: "The candidate will be expected to maintain client relationships as a trusted Technical Advisor and serve as the focal point for communications between multiple departments and clients when necessary. They should be able to take a lead technical role in reviewing and editing deliverables produced by other Engineering and Consulting teams." Also "Provide technical expertise in analyzing client’s requirements to develop IT services offerings across multiple technology solutions." and "Should also be able to recommend solutions and support internal account teams with the development of proposals, quotations, and presentations." Thus we need to deduplicate: keep each unique statement. We'll compile unique bullets for responsibilities (What you will do) and maybe some of those also appear in qualifications but we can keep them only in responsibilities (since they are duties). For qualifications we keep the unique experiential requirements. Let's extract unique responsibilities bullets: 1. Design and deliver Microsoft Fabric architectures that incorporate OneLake, Power BI, data engineering, real-time analytics, Copilot experiences, Azure AI services, and Generative AI solution patterns. 2. Lead development of practical AI-enabled solution patterns, including retrieval-augmented generation, vector search, embedding pipelines, prompt orchestration, semantic search, and AI-enabled analytics workflows. 3. Build and validate proofs of concept, prototypes, reusable accelerators, reference architectures, and implementation templates that help move data and AI solutions from concept to production-ready outcomes. 4. Lead project teams, directing coworker and client teams in solution design and development. 5. Provide leadership in creating business cases, financial justification and solution benefit content for customer ready deliverables and presentations. 6. Aggregate oversight of technical solutions across multiple projects to ensure synergy in our approach and broad visibility to the solutions delivery team. 7. Proactively addresses or escalates any budget issues that are identified during the project. 8. Quality Assurance for SOW requests that meet triggers for size, cross brand, and complexity. 9. Perform peer review of deliverables from other team members for technical content to ensure accuracy. 10. Maintain client relationships as a trusted Technical Advisor. 11. Serve as focal point for communications between multiple departments and clients, when necessary, using experience and judgment to communicate effectively to all parties. 12. Recommend solutions supporting client account teams with development of proposals, quotations, and presentations. 13. Provides technical expertise in analyzing client’s requirements to develop services offerings across multiple technology solutions that provide significant value. (From intro) Maybe also "Provides technical expertise in analyzing client’s requirements to develop services offerings across multiple technology solutions that provide significant value." is similar to #5? Not exactly; it's about analyzing requirements to develop services offerings. We'll keep as separate. Now qualifications unique: - Bachelor’s degree and 7+ years of IT Infrastructure experience, including 3 years of experience with large enterprise cross-brand projects OR 11+ years of IT Infrastructure experience, including 3 years of experience with large enterprise cross-brand projects. Experience