Senior Software Engineer

We need to output only HTML fragment, with sections for headings where there is real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions like "Click here to find out more about the benefits we offer." Also remove duplicated lines. We need to preserve all substantive information. Let's parse the posting: - Intro: "As passionate about our people as we are about our mission. Why Join Q2? Q2 is a leading provider of digital banking and lending solutions to banks, credit unions, alternative finance companies, and fintechs in the U.S. and internationally. Our mission is simple: build strong and diverse communities through innovative financial technology—and we do that by empowering our people to help create success for our customers. What Makes Q2 Special? Being as passionate about our people as we are about our mission. We celebrate our employees in many ways through our year-round Q2 ChangeMakers awards program and global moments of recognition and connection. We invest in the growth and development of our team members through ongoing learning opportunities, internal mobility, and meaningful leadership relationships. We also know that nothing builds trust and collaboration like having fun and giving back together. From company-wide volunteer days to events like our Q2 Homecoming Week—featuring learning, community service, and culture-building experiences—we create opportunities to connect, grow, and make an impact." This is about company culture/benefits. Could be placed under Benefits or maybe a separate "About the role"? Actually "About the role" is a heading for description of role. The intro is more about company. Could be placed under "About the role" or maybe we can have a section "About Q2" but not allowed headings list only those given. We can put under "About the role" maybe? But "About the role" is supposed to describe the role. However we can still include company description there? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings only if there is real content. We can decide to include About the role (summary of role), Responsibilities, Requirements (maybe combine Experience And Knowledge), Qualifications (maybe preferred?), Skills, Benefits, Pay, Schedule. We need to extract: - Summary: "Q2 is seeking an innovative and experienced Senior Software Engineer to join our Digital Banking Fraud team. As part of this team, you will build and evolve the systems behind fraud prevention at scale, helping protect nearly two trillion dollars in transactions for millions of users each year. At that scale, improvements in reliability, latency, and engineering efficiency have a meaningful impact on financial institutions and their customers. You’ll work on real-time, cloud-native services while helping modernize and standardize an existing production ecosystem. This role is also an opportunity to help shape how the team uses AI and agentic engineering, leading by doing and finding practical ways to improve how we design, build, test, and operate software." That's About the role. - Responsibilities: bullet list after "Responsibilities". Let's capture each line: Design, build, and operate reliable, low-latency fraud prevention services and APIs Work individually and collaboratively to deliver new fraud capabilities and improve existing production systems Modernize and standardize Python services, shared patterns, development tooling, and engineering practices across the fraud platform Help advance the team’s use of AI-assisted and agentic software engineering, applying new approaches to improve development speed, quality, and maintainability Design and operate cloud-native architectures in AWS, including serverless and event-driven systems Work within and integrate with Q2’s enterprise banking platform, including navigating and modifying C#/.NET integration points when needed Improve observability, testing, deployment practices, and operational reliability across production services Partner with data scientists, product teams, and other engineers to bring fraud detection capabilities from concept into production Research new technologies and engineering approaches and apply them where they meaningfully improve the platform Mentor other engineers and help establish maintainable patterns and strong engineering practices - Experience And Knowledge (maybe Requirements): list: Strong experience building and operating production software systems Deep proficiency in Python and experience building maintainable services and APIs Strong understanding of cloud architecture and experience designing systems in AWS or a comparable cloud platform Experience with infrastructure as code and modern CI/CD practices Experience designing distributed, event-driven, or serverless systems Strong understanding of API design, system integration, reliability, and production observability Ability to work effectively in large or complex enterprise codebases Comfortable learning and working across technologies when the problem requires it Experience with Git-based development workflows and modern Python development tooling Strong analytical and problem-solving skills Effective communication skills and ability to collaborate across engineering, data science, and product teams Interest in using AI-powered and agentic development tools to improve software engineering workflows - Preferred Experience (maybe Qualifications or Skills): list: Experience with AWS services such as Lambda, DynamoDB, SQS, Kinesis, and S3 Experience with infrastructure-as-code tools such as CloudFormation, SAM, Terraform, or CDK Experience modernizing or incrementally improving mature production systems Experience with banking, payments, fraud prevention, or other high-volume financial systems Experience integrating modern services with legacy or enterprise platforms Familiarity with modern Python dependency and build tooling such as UV Experience working with machine learning systems or real-time model inference Experience with C#, .NET, Java, or another strongly typed enterprise application framework - This position requires fluent written and oral communication in English. Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time. That could be under Requirements or Qualifications. We'll treat as Requirements (maybe under "Requirements"). - Benefits: list after "Health & Wellness Hybrid Work OpportunitiesFlexible Time Off Career Development & Mentoring Programs Health & Wellness Benefits, including competitive health insurance offerings and generous paid parental leave for eligible new parents Community Volunteering & Company Philanthropy Programs Employee Peer Recognition Programs – “You Earned it” Click here to find out more about the benefits we offer." Also earlier: "We celebrate our employees ... Q2 ChangeMakers awards program ... global moments of recognition and connection. We invest in the growth and development of our team members through ongoing learning opportunities, internal mobility, and meaningful leadership relationships. We also know that nothing builds trust and collaboration like having fun and giving back together. From company-wide volunteer days to events like our Q2 Homecoming Week—featuring learning, community service, and culture-building experiences—we create opportunities to connect, grow, and make an impact." These are benefits/culture. Also "Our Culture & Commitment" paragraph. We need to extract benefits: Hybrid Work Opportunities, Flexible Time Off, Career Development & Mentoring Programs, Health & Wellness Benefits (including competitive health insurance offerings and generous paid parental leave for eligible new parents), Community Volunteering & Company Philanthropy Programs, Employee Peer Recognition Programs – “You Earned it”. Also maybe "Q2 ChangeMakers awards program", "global moments of recognition and connection", "ongoing learning opportunities, internal mobility, and meaningful leadership relationships", "company-wide volunteer days", "Q2 Homecoming Week—featuring learning, community service, and culture-building experiences". Also "Spark Program" (volunteer work and nonprofit support). Also "Our Culture & Commitment" paragraph about supportive inclusive environment, career growth, collaboration, wellness prioritized, benefits beyond healthcare—resources for physical, mental, professional well-being. We should include all substantive benefit info. Pay and Schedule: Not mentioned. So we should NOT create Pay or Schedule sections. Thus we will have sections: About the role, Responsibilities, Requirements (maybe combine Experience And Knowledge + visa etc), Qualifications (maybe Preferred Experience), Skills (maybe we could separate technical skills vs soft skills? But we have many skill-like items. Could put under Skills: Deep proficiency in Python, experience with AWS, etc. But we already have Requirements and Qualifications. The instruction says we can use those headings if there is real content. We need to avoid thin sections. Perhaps we can combine Experience And Knowledge and Preferred Experience into Requirements and Qualifications respectively. Skills could be maybe not needed if we already covered. But we could still have Skills section for technical skills like Python, AWS, etc. However we risk duplication. Better to follow typical structure: About the role, Responsibilities, Requirements (mandatory), Qualifications (preferred), Benefits. That seems reasonable. We must not repeat job title. No mention of Pay or Schedule. We must output only HTML fragment, no markdown fences. Let's craft:

About the role

Q2 is seeking an innovative and experienced Senior Software Engineer to join our Digital Banking Fraud team. As part of this team, you will build and evolve the systems behind fraud prevention at scale, helping protect nearly two trillion dollars in transactions for millions of users each year. At that scale, improvements in reliability, latency, and engineering efficiency have a meaningful impact on financial institutions and their customers. You’ll work on real-time, cloud-native services while helping modernize and standardize an existing production ecosystem. This role is also an opportunity to help shape how the team uses AI and agentic engineering, leading by doing and finding practical ways to improve how we design, build, test, and operate software.

Responsibilities

• Design, build, and operate reliable, low-latency fraud prevention services and APIs
• Work individually and collaboratively to deliver new fraud capabilities and improve existing production systems
• Modernize and standardize Python services, shared patterns, development tooling, and engineering practices across the fraud platform
• Help advance the team’s use of AI-assisted and agentic software engineering, applying new approaches to improve development speed, quality, and maintainability
• Design and operate cloud-native architectures in AWS, including serverless and event-driven systems
• Work within and integrate with Q2’s enterprise banking platform, including navigating and modifying C#/.NET integration points when needed
• Improve observability, testing, deployment practices, and operational reliability across production services
• Partner with data scientists, product teams, and other engineers to bring fraud detection capabilities from concept into production
• Research new technologies and engineering approaches and apply them where they meaningfully improve the platform
• Mentor other engineers and help establish maintainable patterns and strong engineering practices

Requirements

• Strong experience building and operating production software systems
• Deep proficiency in Python and experience building maintainable services and APIs
• Strong understanding of cloud architecture and experience designing systems in AWS or a comparable cloud platform
• Experience with infrastructure as code and modern CI/CD practices
• Experience designing distributed, event-driven, or serverless systems
• Strong understanding of API design, system integration, reliability, and production observability
• Ability to work effectively in large or complex enterprise codebases
• Comfortable learning and working across technologies when the problem requires it
• Experience with Git-based development workflows and modern Python development tooling
• Strong analytical and problem-solving skills
• Effective communication skills and ability to collaborate across engineering, data science, and product teams
• Interest in using AI-powered and agentic development tools to improve software engineering workflows
• Fluent written and oral communication in English
• Authorized to work for any employer in the U.S.; unable to sponsor or take over sponsorship of an employment visa at this time

Qualifications

• Experience with AWS services such as Lambda, DynamoDB, SQS, Kinesis, and S3
• Experience with infrastructure-as-code tools such as CloudFormation, SAM, Terraform, or CDK