Senior Python Developer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, etc. We need to extract content: - About the role: Overview paragraph(s). Could be "Overview Seeking a Core Python Engineer..." etc. Also maybe "Job Description Preferred Education Bachelor's Degree or equivalent experience". Actually "Job Description" includes "Preferred Education Bachelor's Degree or equivalent experience". But we need to decide sections. We have sections: About the role (overview), Responsibilities (Job Duties), Requirements (Must Have Skills/Attributes, Experience Desired), Qualifications (Preferred Qualifications/Skills/Experience), Skills (maybe combine Must Have and Preferred?), Benefits (they have a Benefits line but just says "For information and details on employment benefits offered with this position, please visit here." That's not substantive content; it's a placeholder. According to rule: never create Benefits section unless posting actually states them. It does not state actual benefits, just a link. So we should NOT include Benefits section. Pay: They have Min Hourly Rate $85.00 Max Hourly Rate $90.00. That's specific pay info. So we should include Pay section with that info. Schedule: They have Work Model: Hybrid, Work Model Details: Hybrid Model- 3 Days onsite/ 2 days remote, Shift: Standard working hours. That's schedule info. So include Schedule section. We also have Estimated Duration (In months): 7. That could be part of About the role or maybe separate but not a required section. Could include in About the role as extra detail. We must not include Job ID etc. We must not repeat job title as heading. We must use

for section headings. We must use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive info. Let's extract substantive info: From posting: - Date Posted: 09/17/2026 (maybe not needed) - Hiring Organization: Rose International - Position Number: 507698 (drop) - Industry: Financial Services - Job Title: Senior Python Developer (not heading) - Job Location: Tampa, FL, USA, 33610 - Work Model: Hybrid - Work Model Details: Hybrid Model- 3 Days onsite/ 2 days remote - Shift: Standard working hours - Employment Type: Temporary FT/PT: Full-Time - Estimated Duration (In months): 7 - Min Hourly Rate($): 85.00 - Max Hourly Rate($): 90.00 - Must Have Skills/Attributes: Big Data, CI/CD tools, Hadoop, Hive, Python, Spark, SQL - Experience Desired: Hands-on Python and Apache Spark (Big data) development in enterprise environments (5+ yrs); Strong SQL skills with enterprise databases such as Oracle, PostgreSQL, SQL Server, or MySQL. (5+ yrs); Experience with GitHub, Tekton, Harness, and other CI/CD pipeline technologies (3+ yrs) - Preferred Education: Bachelor’s Degree - **C2C is not available** (maybe note) - Job Description Preferred Education Bachelor's Degree or equivalent experience (duplicate) - Required Qualifications/Skills/Experience: Core Python Engineer with expertise in big data processing, particularly within the TechFin industry. Candidate should have experience working with financial enterprise technologies and large-scale distributed computing systems. 7+ years of software development experience with at least 5 years of hands-on Python and Apache Spark development in enterprise environments. Must have experience building backend applications and services using Python, not solely data engineering or analytics solutions. Must have: OOP, OOD, exception handling, concurrency, functional programming concepts. 5+ years of experience with Strong SQL skills with enterprise databases such as Oracle, PostgreSQL, SQL Server, or MySQL. 3+ years of experience leading/owning software development projects from beginning to end with multiple team members. Experience working in financial market and credit risk enterprise software systems including, but not limited to, scenario analysis and stress testing. Experience with GitHub, Tekton, Harness, and other CI/CD pipeline technologies. Ability to work in a fast-paced TechFin environment. Experience leveraging AI-assisted development tools such as GitHub Copilot, Claude, Devin, or similar technologies to improve engineering productivity. - Preferred Qualifications/Skills/Experience: Experience with NoSQL platforms is a plus. - Overview: Seeking a Core Python Engineer with expertise in big data processing, particularly within the TechFin industry. The candidate should have experience working with financial enterprise technologies and large-scale distributed computing systems. This role involves developing and optimizing scalable data pipelines for credit risk calculations and regulatory reporting. The candidate will lead projects involving batch pipeline processes for credit risk analytics, including stress loss (GSST, CCAR) and expected credit loss (CECL, IFRS9, ICAAP). Strong hands-on experience with Python and Apache Spark in enterprise environments is required, along with experience building backend applications and services using Python. The role requires strong knowledge of OOP, OOD, exception handling, concurrency, functional programming concepts, and SQL with enterprise databases such as Oracle, PostgreSQL, SQL Server, or MySQL. Experience with Hadoop, Hive, Impala, Spark, GitHub, Tekton, Harness, CI/CD technologies, and Spark performance tuning is important. Candidates should also have experience leading software development projects and working with financial market and credit risk enterprise software systems. Experience with AI-assisted development tools such as GitHub Copilot, Claude, Devin, or similar technologies is required. - Job Duties: Design, develop, optimize, and maintain scalable data pipelines for processing and analyzing large scale financial data. Lead projects for developing batch pipeline processes for credit risk analytics including, but not limited to, stress loss (GSST, CCAR) and expected credit loss (CECL, IFRS9, ICAAP). Ensure the efficient storage of and retrieval of all risk data in our big data platform systems (Hadoop, Hive, Impala, Spark, etc.). Implement best practices for spark performance tuning including, but not limited to, partitioning, caching, and memory management. Maintain code quality through high-efficiency testing, CI/CD pipelines (Tekton, Harness), and version control (GitHub). 3+ years of experience leading/owning software development projects from beginning to end with multiple team members. **Only those lawfully authorized to work in the designated country associated with the position will be considered.** **Please note that all Position start dates and duration are estimates and may be reduced or lengthened based upon a client’s business needs and requirements.** - Benefits: For information and details on employment benefits offered with this position, please visit here. Should you have any questions/concerns, please contact our HR Department via our secure website. - California Pay Equity etc (boilerplate) - Equal Opportunity Employer etc (boilerplate) - etc. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, etc. Also remove "California Pay Equity", "Rose International is an Equal Opportunity Employer", etc. Also remove "If you need assistance..." etc. Also remove "Rose International has an official agreement..." etc. We need to keep substantive info: location, work model, shift, employment type, estimated duration, pay rate, must have skills, experience desired, preferred education, required qualifications, preferred qualifications, overview, job duties. We need to structure into sections. Possible sections: - About the role: could combine Overview and maybe location, work model, shift, employment type, estimated duration. But we need to follow instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have those headings exactly as given if we include them. Thus we need to decide which sections to include based on content. We have content for: - About the role: we can put overview paragraph(s) plus maybe location, work model, shift, employment type, estimated duration. That's substantive. - Responsibilities: Job Duties. - Requirements: Must Have Skills/Attributes and Experience Desired (maybe combine). Could also include Required Qualifications? But we have separate Qualifications section. - Qualifications: Required Qualifications/Skills/Experience (maybe also Preferred Education?). Actually Preferred Education is a qualification. - Skills: Could list Must Have Skills/Attributes and maybe also Preferred Qualifications? But we already have Qualifications. Might be redundant. However we need to follow instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But they gave examples of headings; we can choose to include only those with real content. We have content for Requirements (must have skills/experience). We have content for Qualifications (required qualifications/skills/experience and preferred qualifications). There's overlap. Might be better to have Requirements for must-have skills/experience, and Qualifications for required/preferred qualifications (including education, years, etc.). Skills section could list technical skills (Big Data, CI/CD tools, Hadoop, Hive, Python, Spark, SQL, etc.) but that's similar to must have. To avoid thin sections, we could omit Skills and put skills under Requirements. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. We must not include Benefits because no substantive content. Now we need to format. About the role: include overview paragraph(s) plus location, work model, shift, employment type, estimated duration. Could be multiple

  tags. Responsibilities: list of duties as

  • . Requirements: list of must have skills/attributes and experience desired. Could be
    • each. Qualifications: list of required qualifications (core python engineer, 7+ years, etc.) and preferred qualifications (NoSQL plus plus). Also include Preferred Education: Bachelor's Degree. Could be
      • . Pay: include min and max hourly rate. Could be

        or

        . Use

        for prose. Schedule: include work model details, shift. Could be

        . We must not repeat job title as heading. We must not include Job ID etc. Now let's craft. First, About the role: We can start with overview paragraph: "Seeking a Core Python Engineer with expertise in big data processing, particularly within the TechFin industry. The candidate should have experience working with financial enterprise technologies and large-scale distributed computing systems. This role involves developing and optimizing scalable data pipelines for credit risk calculations and regulatory reporting. The candidate will lead projects involving batch pipeline processes for credit risk analytics, including stress loss (GSST, CCAR) and expected credit loss (CECL, IFRS9, ICAAP). Strong hands-on experience with Python and Apache Spark in enterprise environments is required, along with experience building backend applications and services using Python. The role requires strong knowledge of OOP, OOD, exception handling, concurrency, functional programming concepts, and SQL with enterprise databases such as Oracle, PostgreSQL, SQL Server, or MySQL. Experience with Hadoop, Hive, Impala, Spark, GitHub, Tekton, Harness, CI/CD technologies, and Spark performance tuning is important. Candidates should also have experience leading software development projects and working with financial market and credit risk enterprise software systems. Experience with AI-assisted development tools such as GitHub Copilot, Claude, Devin, or similar technologies is required." Then add location, work model, shift, employment type, estimated duration as separate sentences or maybe a

        with details. We could combine: "Located in Tampa, FL, USA (33610). Hybrid work model: 3 days onsite, 2 days remote. Standard working hours. Temporary full‑time position with an estimated duration of 7 months." That seems good. Now Responsibilities: Job Duties list: - Design, develop, optimize, and maintain scalable data pipelines for processing and analyzing large scale financial data. -