ETL Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: description (about role), responsibilities (list of duties), required qualifications, preferred qualifications, benefits (What's in it for you). No explicit Pay or Schedule. So we should not include Pay or Schedule sections. Also maybe Skills? The posting includes required and preferred qualifications, which could be considered Requirements and Qualifications. We could combine them? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have: - About the role: The introductory paragraph describing role, mission, etc. That's present. - Responsibilities: The bullet list of duties: develop, enhance, support enterprise applications; partner with stakeholders; modernize platforms; support data integration; improve batch/real-time processing; optimize data warehouse; contribute to migration; analyze complex problems; troubleshoot production issues; implement sustainable solutions; expand expertise across cloud technologies, enterprise data platforms, application modernization, and financial crime risk management solutions. Those are responsibilities. - Requirements: Could be required qualifications list. - Qualifications: Could be preferred qualifications list. - Skills: Could be derived from required/preferred but maybe we can treat required as Requirements and preferred as Qualifications. Or we could combine them into Requirements and Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine required and preferred into Requirements and Qualifications? But they are distinct. Could have both sections. - Benefits: The "What's in it for you" section includes benefits list. - Pay and Schedule: Not present, so omit. Thus output HTML with sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes some boilerplate like "Your opportunity Your Opportunity At Schwab, you’re empowered to make an impact on your career..." That's actually part of the role description; we keep it. Also there is "We believe in the importance of in-office collaboration..." etc. Keep. We need to remove duplicated lines, application instructions. There's no explicit application instructions. We need to format the content. Let's extract sections. About the role: The first paragraph(s) up to "What you have". Actually the posting: "Your opportunity Your Opportunity At Schwab, you’re empowered to make an impact on your career. Here, innovative thought meets creative problem solving, helping us challenge the status quo and transform the finance industry together. We believe in the importance of in-office collaboration and fully intend for the selected candidate for this role to work on site in the specified location(s). As an ETL Software Engineer supporting Financial Crime Risk Management (FCRM), you will play a critical role in strengthening the platforms that help protect Schwab, our clients, and the financial system. Working within a highly collaborative environment, you will develop, enhance, and support enterprise applications that power financial crime detection, monitoring, and regulatory compliance. You’ll partner closely with technology, operations, compliance, and business stakeholders to deliver secure, scalable, and resilient solutions that drive meaningful business outcomes. In this role, you will help modernize critical platforms by supporting data integration initiatives, improving batch and real-time processing systems, optimizing data warehouse solutions, and contributing to migration efforts from legacy on-premises applications to future-state technologies. Your ability to analyze complex problems, troubleshoot production issues, and implement sustainable solutions will directly influence system reliability, operational effectiveness, and regulatory readiness. As part of a team that values continuous improvement, innovation, and knowledge sharing, you will have opportunities to expand your expertise across cloud technologies, enterprise data platforms, application modernization, and financial crime risk management solutions." That's the About the role. Then "What you have" heading then Required Qualifications list. Then "Preferred Qualifications" list. Then "What’s in it for you" benefits list. Thus we can map: - About the role: the paragraph(s) before "What you have". - Responsibilities: Actually the responsibilities are embedded in the About the role paragraph (develop, enhance, support... partner..., help modernize..., ability to analyze..., As part of a team...). Could treat those as responsibilities. But we already used About the role for that paragraph. However we could split: About the role = general description; Responsibilities = bullet list of duties. The posting does not have a separate bullet list for responsibilities; it's embedded in prose. But we can still create a Responsibilities section with

  • items extracted from the sentences that describe duties. The instruction: "Use
    • for any list of duties/requirements/benefits". If we have duties expressed as sentences, we can convert to list items. That would preserve detail. Thus we need to extract duties: From the About the role paragraph: - develop, enhance, and support enterprise applications that power financial crime detection, monitoring, and regulatory compliance. - partner closely with technology, operations, compliance, and business stakeholders to deliver secure, scalable, and resilient solutions that drive meaningful business outcomes. - help modernize critical platforms by supporting data integration initiatives, improving batch and real-time processing systems, optimizing data warehouse solutions, and contributing to migration efforts from legacy on-premises applications to future-state technologies. - analyze complex problems, troubleshoot production issues, and implement sustainable solutions will directly influence system reliability, operational effectiveness, and regulatory readiness. - expand your expertise across cloud technologies, enterprise data platforms, application modernization, and financial crime risk management solutions. We could also include "play a critical role in strengthening the platforms that help protect Schwab, our clients, and the financial system." but that's more overview. We need to preserve all substantive information; we can include that as a duty as well. Thus Responsibilities section will have a list. Requirements: Required Qualifications list: - Bachelor’s degree in Computer Science, Information Systems, Engineering, or equivalent experience - 1+ years of experience developing, supporting, and optimizing Oracle database solutions, including PL/SQL packages, stored procedures, functions, and triggers - 2+ years of experience with SQL development and data warehousing concepts - 2+ years of hands-on experience developing ETL solutions using Informatica Intelligent Cloud Services (IICS) - 1+ years of experience writing Unix/Linux shell scripts - Experience troubleshooting complex applications, data integration processes, and production support issues - Demonstrated problem-solving skills with the ability to analyze root causes, evaluate alternatives, and implement effective solutions - Ability to collaborate across technical and business teams while adapting to changing priorities and business needs - Strong written and verbal communication skills with the ability to explain technical concepts to diverse audiences - Experience working with large-scale data processing, system performance optimization, and data quality initiatives Qualifications: Preferred Qualifications list: - 1+ years of experience supporting Oracle FCCM/FCRM version 8.0 or higher - 1+ years of experience supporting Anti-Money Laundering (AML), Financial Crime Risk Management, Anti-Bribery, or related compliance platforms - 1+ years of experience converting Informatica PowerCenter solutions to IICS - 1+ years of experience using Python for cloud-based applications, automation, or API integrations - 1+ years of experience using GitHub and GitHub Copilot - Experience within the financial services industry - Experience working within an Agile/Scrum environment - Knowledge of enterprise application modernization and migration initiatives - Understanding of software development lifecycle (SDLC) practices and enterprise engineering standards - Experience supporting large-scale data integration, analytics, and data platform environments - Familiarity with regulatory requirements and compliance frameworks related to financial crime monitoring and surveillance Benefits: What’s in it for you list: - 401(k) with company match and Employee stock purchase plan - Paid time for vacation, volunteering, and 28-day sabbatical after every 5 years of service for eligible positions - Paid parental leave and family building benefits - Tuition reimbursement - Health, dental, and vision insurance Also there is preceding text: "At Schwab, you’re empowered to shape your future. We champion your growth through meaningful work, continuous learning, and a culture of trust and collaboration—so you can build the skills to make a lasting impact. Our Hybrid Work and Flexibility approach balances our ongoing commitment to workplace flexibility, serving our clients, and our strong belief in the value of being together in person on a regular basis. We offer a competitive benefits package that takes care of the whole you – both today and in the future:" This is prose; we can put in a

      before the list. Thus Benefits section:

      At Schwab, you’re empowered to shape your future...

      then
      • ... items. Now we need to ensure we don't include Pay or Schedule sections. Now produce HTML fragment. We must not include markdown code fences. Just raw HTML. Let's craft. We'll start with

        About the role

        then

        ... the introductory paragraph(s) (maybe combine into one paragraph). Ensure we keep all sentences. We need to be careful not to lose any content. Let's copy the About the role paragraph exactly as in posting, but we can combine sentences. Original: "Your opportunity Your Opportunity At Schwab, you’re empowered to make an impact on your career. Here, innovative thought meets creative problem solving, helping us challenge the status quo and transform the finance industry together. We believe in the importance of in-office collaboration and fully intend for the selected candidate for this role to work on site in the specified location(s). As an ETL Software Engineer supporting Financial Crime Risk Management (FCRM), you will play a critical role in strengthening the platforms that help protect Schwab, our clients, and the financial system. Working within a highly collaborative environment, you will develop, enhance, and support enterprise applications that power financial crime detection, monitoring, and regulatory compliance. You’ll partner closely with technology, operations, compliance, and business stakeholders to deliver secure, scalable, and resilient solutions that drive meaningful business outcomes. In this role, you will help modernize critical platforms by supporting data integration initiatives, improving batch and real-time processing systems, optimizing data warehouse solutions, and contributing to migration efforts from legacy on-premises applications to future-state technologies. Your ability to analyze complex problems, troubleshoot production issues, and implement sustainable solutions will directly influence system reliability, operational effectiveness, and regulatory readiness. As part of a team that values continuous improvement, innovation, and knowledge sharing, you will have opportunities to expand your expertise across cloud technologies, enterprise data platforms, application modernization, and financial crime risk management solutions." Note there is a duplicated "Your opportunity Your Opportunity". We should keep as is? It's likely a typo but we must preserve substantive information; we can keep it exactly as given. It's not boilerplate; it's part of the posting. We'll keep. Thus About the role

        includes that entire block. Now Responsibilities

        Responsibilities

        then
        with
        • items. We need to ensure we don't miss any duty. Let's list duties derived: 1. Play a critical role in strengthening the platforms that help protect Schwab, our clients, and the financial system. 2. Develop, enhance, and support enterprise applications that power financial crime detection, monitoring, and regulatory compliance. 3. Partner closely with technology, operations, compliance, and business stakeholders to deliver secure, scalable, and resilient solutions that drive meaningful business outcomes. 4. Help modernize critical platforms by supporting data integration initiatives, improving batch and real-time processing systems, optimizing data warehouse solutions, and contributing to migration efforts from legacy on-premises applications to future-state technologies. 5. Analyze complex problems, troubleshoot production issues, and implement sustainable solutions (which directly influence system reliability, operational effectiveness, and regulatory readiness). 6. Expand your expertise across cloud technologies, enterprise data platforms, application modernization, and financial crime risk management