BI Developer

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are", "Why Join our Team", "What You Will Do", "Who You Are Required Qualifications", "Requirements", "Living Our Values", "Competencies", "Working Conditions". We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections where there is real specific content. We have content: Who We Are (company overview) maybe not needed as heading? Could be "About the role"? Not exactly. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. We have: - About the role: maybe combine Who We Are and Why Join our Team? But "About the role" is about the role itself, not company. However we can still use it for overview of role and company? Might be okay. - Responsibilities: from "What You Will Do" (list of duties). Use

• . - Requirements: from "Who You Are Required Qualifications" (list of qualifications). Could be Requirements or Qualifications. We'll use Requirements for mandatory qualifications, and Qualifications for preferred? But we have both required and maybe "Experience with SSAS is a plus." Could be Qualifications. - Skills: maybe list of skills like SQL, Tableau, etc. - Benefits: from "Why Join our Team" bullet list of benefits. - Pay: we have compensation range $95,000 - $105,000 plus incentive. So include Pay. - Schedule: we have remote work flexibility, working conditions (home, etc). Not exactly schedule but we could include Working Conditions as Schedule? But schedule heading is for schedule info like full-time, part-time, shift. Not present. We might omit Schedule if no specific schedule info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and Benefits, so include those. No explicit schedule (like hours). So omit Schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, etc. There's none. We must preserve all substantive info. We need to output only HTML fragment, no /, no markdown. We'll produce sections in logical order: About the role (company overview + why join), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Let's extract details. About the role: combine Who We Are and Why Join our Team (mission, impact, etc). We'll write a paragraph. Responsibilities: list from "What You Will Do". Let's extract bullet points: - Aggregating data from multiple data sources and designing, building, and supporting enterprise level BI and analytics solutions that will enable business users to make informed business decisions. - Work closely with business stakeholders to gather requirements, design and develop reports, dashboards, and ad-hoc queries against Lucet’s data warehouse and operational systems. - Collaborate with the larger Reporting and Analytics and Data Engineering teams to provide advice and requirements for data modeling, predictive analytics, data visualization, and data governance. - Data Analysis & BI Solution Development: * Perform analysis of data sources, business processes and data mining to understand the nuances, integrity, completeness, and accuracy of the data. * Utilize tools such as Tableau, SQL, SSIS, and SSRS to architect business intelligence and reporting solutions. * Design and implement best-practice BI solutions and reports that will support business decisions. - Stakeholder Collaboration & Support: * Consult with all levels of users to help them solve problems regarding the use and management of data as well as work on design, maintenance, and completion of highly visible organizational projects. * Establish and maintain cooperative and supportive relationships with customers and stakeholders. * Create and maintain of data domain specific documentation including reporting requirements and data maps. - Project Management & Continuous Improvement: * Manage multiple tasks/projects to timely completion with attention to detail and responsiveness. * Demonstrate independent thought, critical thinking, and a proactive approach to problem-solving. * Support data governance initiatives, including metadata management and data stewardship. * Adhere to Lucet’s Mission Statement, Core Values, Behaviors, Code of Ethical Business Conduct, and Compliance Program. * Comply with all Federal and applicable State and local laws and Lucet Policies and Procedures regarding privacy, confidentiality, and security of health information, and other designated information. We'll turn each bullet into
• . Requirements: from "Who You Are Required Qualifications". Let's list: - BS/BA degree plus with demonstrated experience in BI, with experience in Healthcare Industry strongly preferred - Strong knowledge of SQL queries, SQL Server Reporting Services (SSRS) and SQL Server Integration Services (SSIS). - Experience with SSAS is a plus. - Proficiency in analytic tools such as SQL, SAS, R or Python - Strong experience with Tableau and familiarity with other data visualization tools - In-depth understanding of database management systems and data modeling (relational and dimensional) - Experience in data warehousing, particularly within the healthcare industry - Experience building scalable BI applications - Experience working with end-users and translating their business needs into technical solutions - Good working knowledge skills with Microsoft Office products. - Good working knowledge of gathering requirements and agile processes. - Analytical mindset with a problem-solving aptitude - Willingness to work occasionally outside of normal business hours. Also from "Requirements" section (the background check etc.) That's also requirements but more about eligibility. Could be included under Requirements as well. But we might separate? The instruction: we can have Requirements section for qualifications; we could also include the background check details there. But we might create a separate section? Not allowed headings besides those. Could incorporate into Requirements as additional items. Let's include: - Ability to pass background check upon hire and throughout employment (list of checks) - Ability to undergo a Public Trust background investigation and receive a favorable adjudication. - US Citizenship for at least 5 years. We'll incorporate as bullet points. Qualifications: maybe preferred qualifications? Could be "Experience with SSAS is a plus." but we already included as plus. Could separate Qualifications for preferred: maybe "Experience with SSAS is a plus." Also "Experience in healthcare industry strongly preferred" is already in Requirements. Might not need separate Qualifications. But we can still have Qualifications section for "Experience with SSAS is a plus." and maybe "Experience with other data visualization tools". However we already have strong experience with Tableau and familiarity with other data visualization tools under Requirements. Might be redundant. Better to treat Requirements as mandatory qualifications, Qualifications as preferred/pluss. We'll list: - Experience with SSAS is a plus. - Familiarity with other data visualization tools (beyond Tableau) (though we already have). - Experience in healthcare industry strongly preferred (maybe move to Qualifications). But we already have strongly preferred; could be Qualifications. Let's decide: We'll put Requirements as the list of mandatory (BS/BA, SQL, SSRS, SSIS, Tableau, etc). Qualifications as preferred: SSAS, healthcare industry experience, etc. Skills: list of technical skills: SQL, SSRS, SSIS, Tableau, SAS, R, Python, Microsoft Office, data modeling, data warehousing, etc. Benefits: from "Why Join our Team" bullet list: - Annual compensation between $95,000 - $105,000, PLUS an annual performance-based, discretionary incentive. (but that's Pay, not Benefits) - Comprehensive health benefit options: Medical, dental, and vision coverage - 401(k) with competitive employer match - Company-paid life and disability insurance - Paid parental leave and wellbeing incentives - Generous paid time off, including volunteer time - Flexible spending accounts for healthcare and dependent care - Professional development opportunities and tuition reimbursement - Remote work flexibility (role-dependent) - Opportunity for meaningful growth, both personally and professionally, where your unique background and experience is welcomed and valued. Pay: Annual compensation between $95,000 - $105,000, PLUS an annual performance-based, discretionary incentive. Also note compensation dependent on factors. Schedule: Not present. Working Conditions: maybe we could include under Schedule? But we shouldn't create Schedule unless present. Could we put Working Conditions under "About the role"? Not ideal. The instruction says only create Pay/Schedule/Benefits sections if posting actually states them. It doesn't forbid other sections like "Working Conditions". But allowed headings list only those eight. So we must stick to those headings. So we cannot add a Working Conditions heading. We could incorporate working conditions details into About the role or Responsibilities? Probably better to omit them, as they are not covered by allowed headings. However we must preserve ALL substantive information. If we omit, we violate. But we could fold them into existing sections like About the role (company overview) or Responsibilities? The instruction: "Prefer a few substantive sections over many thin ones." It didn't forbid adding extra headings beyond the list? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive? But likely they want only those headings. Safer to stick to those. We can incorporate working conditions details into About the role or Responsibilities as a paragraph. Eg mention remote work flexibility, home office requirements, etc. That is substantive. Thus About the role can include company overview, mission, remote work flexibility, working conditions. Now we need to ensure we don't repeat content. Let's craft HTML. We'll start with

  About the role

  then

  containing combined overview: Who we are, mission, impact, remote work flexibility, etc. Then

  Responsibilities

  with li items. Then

  Requirements

  with mandatory qualifications. Then

  Qualifications

  with preferred/pluss. Then

  Skills

  with technical skills. Then

  Benefits

  with benefits list. Then

  Pay

  with compensation range and incentive note. We must not include Schedule. Check for any duplicated lines: ensure we don't repeat. Now extract precise text. About the role paragraph: "At Lucet, we are industry leaders in behavioral health, dedicated to helping people live healthy, balanced lives. Our purpose is to advocate for and improve the overall well-being of those we serve, through balanced treatment of the mind and body. When you join Lucet, you become a valued member of our team, serving more than 15 million people across the U.S. Our employees have a passion for helping others - and it shows. From entry-level employees to senior leaders, we are inspired by our members, putting them first in everything we do. From day one, you'll see firsthand the impact you have on our members, knowing you can make a true difference in their lives. We’re committed to creating a workplace where top talent thrives both personally and professionally. We offer a dynamic, mission-driven environment where your work has real impact, your unique background and experience are valued, and no two days are alike. If you’re passionate about meaningful work and delivering impactful results, we encourage you to apply. This role is performed from home with company-provided equipment, requiring a quiet workspace, high-speed internet (minimum 20 Mbps download, 5 Mbps upload, max latency 100 ms), and the ability to remain in a stationary sitting position for extended periods." We need to include remote work flexibility and working conditions details. Now Responsibilities list: we need to capture all duties. Let's list them concisely but preserve all detail. I'll create li items: - Aggregate data from multiple data sources and design, build, and support enterprise