Financial Data Products Developer

We need to output only HTML fragment, no markdown fences, no html/body tags. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Content: - Intro paragraph about team, mission, etc. That's "About the role" maybe. - "WHAT WE CAN OFFER YOU:" includes estimated salary range, 401(k) plan details, work-life balance with vacation, personal time and paid holidays, see benefits page. So we have Pay (salary), Benefits (401k, vacation, personal time, paid holidays). Also maybe schedule? Not given. - "WHAT YOU'LL DO:" list of duties. That's Responsibilities. - "WHAT YOU'LL BRING:" list of qualifications/skills. That's Requirements/Qualifications/Skills. We need to decide which sections to use. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple of those as appropriate. We should not repeat job title as heading. We should not include Job ID etc. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to cut out the "Applicants for this position must not now, nor at any point in the future, require sponsorship for employment." That's a requirement? It's a condition; maybe it's a requirement but it's not boilerplate? It's a specific requirement about sponsorship. It's not EEO etc. It's a legitimate requirement. Should we keep? It's not boilerplate; it's a specific eligibility requirement. We'll keep it under Requirements. Also "For individuals residing within 50 miles of the office location, onsite attendance is currently expected one day per week and is expected to increase to three days per week when the new office opens in 2027. Local Finance Operations Division employees are expected to be in the office for key business activities and critical in-person events, as determined by their manager." That's schedule info. So we can include a Schedule section. Also "PREFERRED:" list of preferred experience. That's qualifications/skills. We need to avoid duplicative lines. Ensure we don't repeat same content. We'll structure:

About the role

... intro paragraph(s) ...

Responsibilities

• ... each duty ...

Requirements

• ... each requirement ...

Maybe also

Skills

but we can combine Requirements and Skills? The instruction says prefer a few substantive sections over many thin ones. We could have Requirements covering technical foundation, communication, organization, sponsorship requirement, etc. Skills could be separate for preferred? But we could also have Qualifications for required and Skills for preferred? However we need to avoid thin sections. Perhaps we combine Requirements and Skills into one section called Requirements (or Qualifications). But we have headings list; we can choose to include Requirements and Skills if both have substantive content. Let's see. Required: Strong technical foundation in SQL and data analysis, experience using programming or scripting languages such as Python, R, or similar tools to support data transformation, automation, validation, and reporting. Demonstrated ability to learn new technologies, troubleshoot data issues, and support process improvements that increase reliability, efficiency, and business value. Strong communication and collaboration skills, including ability to understand business needs, document requirements, and explain technical concepts clearly to both technical and non-technical audiences. Highly organized and analytical, with a structured approach to problem-solving, documentation, validation, stakeholder follow-up, and managing priorities. Promotes a culture of diversity and inclusion, values different ideas and opinions, and listens courageously while remaining curious in all that you do. For individuals residing within 50 miles of the office location, onsite attendance is currently expected one day per week and is expected to increase to three days per week when the new office opens in 2027. Local Finance Operations Division employees are expected to be in the office for key business activities and critical in-person events, as determined by their manager. Applicants for this position must not now, nor at any point in the future, require sponsorship for employment. Preferred: Experience developing or supporting data products, including data discovery, curation, validation, controls, reporting, and user adoption. Experience with semantic modeling and business intelligence tools such as Power BI, SSAS, Power Pivot, Excel connected reports, and related platforms used to build, deploy, and support analytical solutions. Experience with Python or similar automation tools for data manipulation, testing, documentation support, refresh processes, or repeatable workflow automation. Experience using AI-enabled tools to support development, documentation, testing, data analysis, or productivity improvements. Background in data architecture, dimensional modeling, Snowflake, GitHub, deployment pipelines, governance, or production support practices that contribute to scalable and well-controlled analytical solutions. We value unique experience, skills, and passion for innovation. Thus we could have: - Requirements (mandatory) - Preferred Qualifications (or Skills) as separate section. But the instruction says we can use headings like Requirements, Qualifications, Skills. We could have Requirements for mandatory, Skills for preferred. Or Qualifications for mandatory and Skills for preferred. Let's decide: Use Requirements for mandatory, Skills for preferred. That gives two substantive sections. Also Benefits: 401(k) plan with a 2% company contribution and 6% company match. Work-life balance with vacation, personal time and paid holidays. See our benefits and perks page for details. That's substantive. Pay: Estimated Salary: Financial Data Products Developer (Internal Title: Business Intelligence Developer): $75,500-$97,000, plus annual bonus opportunity. Schedule: Onsite attendance expectation (one day per week currently, increasing to three days per week when new office opens in 2027). Also note local Finance Ops division employees expected in office for key activities. We should not include "See our benefits and perks page for details" as it's a reference; but we can keep the benefits description. We need to avoid repeating info. Ensure we don't duplicate the schedule info in both Requirements and Schedule. We'll put schedule info only in Schedule section. We need to remove boilerplate: "Stay Safe from Job Scams Mutual of Omaha only accepts applications from mutualofomaha.com/careers. Legitimate communications will come from '@mutualofomaha.com.' We never request sensitive information or extend job offers without conducting interviews. For more details, check our Hiring FAQs. Stay alert for scams and apply securely! Hiring Policies and Legal Notices". Remove that. Also remove "Please allow at least one week from time of applying if you are checking on the status." and "If you have questions about your application or the hiring process, email our Talent Acquisition area at careers@mutualofomaha.com." That's application instructions; remove. Also remove "We value unique experience, skills, and passion for innovation. If your experience aligns with the listed requirements, please apply!" That's also application encouragement; remove. Now craft HTML. We'll output:

About the role

Come join the Financial Analytics & Data Strategy (FADS) team at Mutual of Omaha! This dynamic team is responsible for activating the vision that empowers internal financial data consumers throughout the enterprise with easy access to trusted data. By curating data and enabling contemporary data consumption tools our business partners have accelerated the time to action, decision-making and analysis to help achieve our company mission: help our customers protect what they care about and achieve their financial goals. The impact of this team to date has been so powerful that there is now a critical need for an experienced Data Products Developer to further evolve our data landscape by expanding the development of holistic and consumable data products. Be a part of a fun, collaborative team committed to transformation at a stable Fortune 500 company!

Responsibilities

• Supports the development and ongoing maintenance of financial data products, including data discovery, data curation, semantic model updates, testing, deployment support, and post-deployment troubleshooting.
• Works with stakeholders, Finance and Actuarial users, IS partners, and team members to understand requirements, validate results, document decisions, and ensure solutions meet business needs.
• Contributes to modernization efforts by helping improve model performance, strengthen data controls, organize repeatable logic, and support users as they adopt modern analytics tools and processes.
• Follows established team standards for documentation, version control, validation, access/security practices, automation, deployment readiness, and backup coverage.
• Contributes to organizational goals by supporting reliable, scalable, and consumable data solutions; continuing to learn; and aligning with the company’s mission, vision, and values.

Requirements

• Strong technical foundation in SQL and data analysis, with experience using programming or scripting languages such as Python, R, or similar tools to support data transformation, automation, validation, and reporting.
• Demonstrated ability to learn new technologies, troubleshoot data issues, and support process improvements that increase reliability, efficiency, and business value.
• Strong communication and collaboration skills, including the ability to understand business needs, document requirements, and explain technical concepts clearly to both technical and non-technical audiences.
• Highly organized and analytical, with a structured approach to problem-solving, documentation, validation, stakeholder follow-up, and managing priorities.
• Promotes a culture of diversity and inclusion, values different ideas and opinions, and listens courageously while remaining curious in all that you do.
• Applicants for this position must not now, nor at any point in the future, require sponsorship for employment.

Skills

• Experience developing or supporting data products, including data discovery, curation, validation, controls, reporting, and user adoption.
• Experience with semantic modeling and business intelligence tools such as Power BI, SSAS, Power Pivot, Excel connected reports, and related platforms used to build, deploy, and support analytical solutions.
• Experience with Python or similar automation tools for data manipulation, testing, documentation support, refresh processes, or repeatable workflow automation.
• Experience using AI-enabled tools to support development, documentation, testing, data analysis, or productivity improvements.
• Background in data architecture, dimensional modeling, Snowflake, GitHub, deployment pipelines, governance, or production support practices that contribute to scalable and well-controlled analytical solutions.

Benefits

• 401(k) plan with a 2% company contribution and 6% company match.
• Work-life balance with vacation, personal time and paid holidays.

Pay

Estimated Salary: Financial Data Products Developer (Internal Title: Business Intelligence Developer): $75,500-$97,000, plus annual bonus opportunity.

Schedule

For individuals residing within 50 miles of the office location, onsite attendance is currently expected one day per week and is expected to increase to three days per week when the new office opens in 2027. Local Finance Operations Division employees are expected to be in the office for key business activities and critical in-person events, as determined by their manager.

Check for any duplicated content: The schedule appears also in Requirements? We removed it from Requirements. Good. Check that we didn't include any boilerplate: removed sponsorship line? Actually we kept sponsorship line under Requirements as it's a requirement. That's fine. Check that we didn't include any "See our benefits and perks page for details".