Power BI Developer

We need to output HTML fragment with sections: About the role (maybe from introductory paragraph), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: EEO, contact info, application instructions, etc. Also remove duplicated lines. We need to preserve all substantive information. Let's parse the posting. Title: Power BI Developer Employment Type: Full-Time, Mid-level Department: Information Technology CGS is seeking a Power BI Developer to join our team in supporting a wide-ranging technical support initiative for a large Federal agency. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities. Then "Skills and attributes for success:" bullet list: - Build Data Analytics enterprise models using Microsoft’s Power BI - Develop tabular, multidimensional models compatible with warehouse standards - Develop self-service models, and data analytics using Power BI service - Experience with Microsoft Azure platform and service (Power BI, Flow, Cortana, etc.) - Experience working with data gateway, data integration, self-service data preparation - Develop, publish, and schedule reports and dashboards to meet business requirements - Assist business users with functional and data requirements to enhance data models - Experience in requirement analysis, design, and prototyping - Strong understanding of Data Analytics application security layer models - Experience with ESRI or similar geographical mapping systems and tools is desired - Experience working with Government personnel at the CTO or SES level. Then "Qualifications:" bullet list: - Bachelor's degree or equivalent in Computer Science or related field. - 2-4 years of development experience in Data Analytic technologies - Knowledge in Microsoft enterprise cloud technologies such as Dynamics 365 CRM, Office 365, Microsoft Azure - Strong experience in SQL and RDBMS technologies - Experience working in Agile project deliveries and delivering to tight timescales - Web API Experience - Knowledge of Azure DevOps (VSTS) - ETL, SSAS, and SSIS experience - SSRS Reporting knowledge Then "Ideally, you will also have:" bullet list: - Experience with Government software development policies and procedures - Client-facing communication experience - Federal Agency issued security clearance Then "Our Commitment:" paragraph about CGS. Then "Contact Government Services (CGS) strives to simplify and enhance government bureaucracy..." etc. Then "We are committed to solving the most challenging and dynamic problems. For the past seven years, we’ve been growing our government-contracting portfolio, and along the way, we’ve created valuable partnerships by demonstrating a commitment to honesty, professionalism, and quality work. Here at CGS we value honesty through hard work and self-awareness, professionalism in all we do, and to deliver the best quality to our consumers mending those relations for years to come. We care about our employees. Therefore, we offer a comprehensive benefits package.- Health, Dental, and Vision- Life Insurance- 401k- Flexible Spending Account (Health, Dependent Care, and Commuter)- Paid Time Off and Observance of State/Federal Holidays" Then "Contact Government Services, LLC is an Equal Opportunity Employer..." (remove) Then "Join our team and become part of government innovation!Explore additional job opportunities with CGS on our Job Board: https://cgsfederal.com/join-our-team/For more information about CGS please visit: https://www.cgsfederal.com or contact:Email: [email protected] #CJ$104,832 - $142,272 a yearWe may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses and identifying potential inconsistencies or verification signals in application materials based on available information. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us." We need to extract Pay: "$104,832 - $142,272 a year". That's present near "#CJ$104,832 - $142,272 a year". So we have pay info. Schedule: Not explicitly given. Only employment type Full-Time. Could infer schedule? Not given specific schedule like "Monday-Friday 9-5". Not present. So we should not create Schedule section. Benefits: we have list: Health, Dental, and Vision; Life Insurance; 401k; Flexible Spending Account (Health, Dependent Care, and Commuter); Paid Time Off and Observance of State/Federal Holidays. Thus Benefits section. Now sections: About the role (intro paragraph). Responsibilities: maybe the "Skills and attributes for success" list could be considered responsibilities. Also "Develop, publish, and schedule reports and dashboards to meet business requirements" etc. Could treat as Responsibilities. Requirements: maybe the "Qualifications" and "Ideally, you will also have" could be Requirements? But we have separate Qualifications section. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content goes where. We have content that could map: - About the role: introductory paragraph describing role, mission, etc. - Responsibilities: the bullet list under "Skills and attributes for success:" (these are duties/responsibilities). Also maybe "Assist business users with functional and data requirements to enhance data models" etc. - Requirements: maybe the "Qualifications:" list (education, years experience) plus "Ideally, you will also have:" could be considered preferred qualifications. But we have a separate Qualifications heading; maybe we put the mandatory qualifications under Qualifications, and the "Ideally, you will also have:" under Skills? Actually Skills heading could be for technical skills list. But we already have Skills and attributes for success list which includes both responsibilities and skills. Could split: Skills heading for technical skills (e.g., Power BI, Azure, SQL, etc.) and Responsibilities for duties. However the instruction says prefer a few substantive sections over many thin ones. So we could combine. We need to avoid filler. Let's think: We have: - Intro paragraph (About the role) - Skills and attributes for success (list of duties/skills) - Qualifications (education, experience, knowledge) - Ideally, you will also have (preferred) - Benefits - Pay We could map: About the role: intro paragraph. Responsibilities: the "Skills and attributes for success:" list (since they describe what you will do). Qualifications: the "Qualifications:" list (mandatory) plus maybe the "Ideally, you will also have:" as part of Qualifications (preferred). But we could also have a Skills section for technical skills like Power BI, Azure, SQL, etc. However the "Skills and attributes for success" already includes many skill items. Could treat that as Skills section. But then Responsibilities would be empty. Better to treat that list as Responsibilities (what you will do). Then we could have a Skills section for technical proficiencies like Power BI, Azure, SQL, etc. But we don't have a separate list of just skills; the list includes both responsibilities and skills. Could split: Responsibilities: items that are actions (build models, develop, develop self-service models, develop/publish/schedule reports, assist business users, experience in requirement analysis, etc.) Skills: items that are knowledge/experience (Experience with Microsoft Azure platform, Experience working with data gateway, Strong understanding of Data Analytics application security layer models, Experience with ESRI, Experience working with Government personnel). But that seems arbitrary and may create thin sections. Given instruction to prefer few substantive sections, we could combine Responsibilities and Skills into one section called Responsibilities (or Skills). But we have both headings available; we need to decide which to use. We have Qualifications section definitely. We have Benefits. We have Pay. We could also have About the role. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to ensure we don't create empty sections. Now we need to extract content precisely, preserving all substantive information, not inventing or summarizing away detail. We must not include boilerplate like EEO, contact info, application instructions, AI statement, etc. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must not include duplicated lines. We need to format using

for section headings,

• for lists,

  for prose. We need to preserve all substantive information: that includes the introductory paragraph(s), the bullet lists, the benefits list, the pay line. We need to be careful to not include the "Contact Government Services (CGS) strives to simplify..." paragraph that is part of "Our Commitment:" which is somewhat fluff but still substantive? It's about company mission. Might be considered boilerplate but it's not EEO/legal. It's describing CGS's commitment. Could be considered part of About the role? Actually the intro already includes CGS description. The "Our Commitment:" paragraph is similar to earlier description. Might be considered duplicate. We could include it as part of About the role if not duplicate. But to avoid duplication, we could keep only the first intro paragraph and skip the later "Our Commitment:" as it repeats similar content. However we need to preserve ALL substantive information; if it's duplicate, we might still need to include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicate lines: we should remove duplicated lines. So if the later paragraph is substantially same as earlier, we can drop it as duplicate. Let's compare: First paragraph: "CGS is seeking a Power BI Developer to join our team in supporting a wide-ranging technical support initiative for a large Federal agency. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities." Later "Our Commitment:" paragraph: "Contact Government Services (CGS) strives to simplify and enhance government bureaucracy through the optimization of human, technical, and financial resources. We combine cutting-edge technology with world-class personnel to deliver customized solutions that fit our client’s specific needs. We are committed to solving the most challenging and dynamic problems. For the past seven years, we’ve been growing our government-contracting portfolio, and along the way, we’ve created valuable partnerships by demonstrating a commitment to honesty, professionalism, and quality work. Here at CGS we value honesty through hard work and self-awareness, professionalism in all we do, and to deliver the best quality to our consumers mending those relations for years to come. We care about our employees. Therefore, we offer a comprehensive benefits package.- Health, Dental, and Vision- Life Insurance- 401k- Flexible Spending Account (Health, Dependent Care, and Commuter)- Paid Time Off and Observance of State/Federal Holidays" This later paragraph includes benefits list (which we already captured). The earlier part about mission is somewhat similar but not identical. However we already have benefits captured separately. The mission description could be considered substantive and not duplicate of earlier intro. But we already have an intro describing CGS's mission. The later paragraph adds more detail about simplifying bureaucracy, optimizing resources, delivering customized solutions, past seven years, partnerships, honesty, professionalism, quality, caring about employees, benefits. Some of that is new (e.g