Senior Software Engineer
Q2 · Charlotte, NC · 3 wk ago
Full-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, EEO, etc. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- Intro: "As passionate about our people as we are about our mission. Why Join Q2? Q2 is a leading provider..." That's about company. Could be "About the role"? Actually "About the role" maybe summary of role. The posting includes "Summary Q2 is seeking an innovative and experienced Senior Software Engineer..." That's summary. Could be placed under "About the role" or maybe "Summary". But we only allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have responsibilities list (bulleted). We have Experience And Knowledge (requirements). Also Preferred Experience (maybe qualifications). Also "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's requirements.
Benefits: There's a list: "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: "Being as passionate about our people as we are about our mission. We celebrate our employees..." etc. That's culture/benefits. So we can include Benefits section with those items.
Pay: Not mentioned. So we should not include Pay section.
Schedule: Not mentioned (maybe hybrid work opportunities). There's "Hybrid Work Opportunities". That could be schedule? It's about hybrid work. Could be considered schedule? The instruction: include Schedule section only if posting actually states them. It mentions hybrid work opportunities, flexible time off. That's schedule-ish. Could include Schedule section with hybrid work and flexible time off. But we need to see if that's considered schedule. The posting says "Hybrid Work OpportunitiesFlexible Time Off". Likely they intend schedule. We'll include Schedule section with those points.
We must not include boilerplate like EEO, equal opportunity, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions (Click here to find out more about the benefits we offer). Also remove "Click here to find out more about the benefits we offer." That's application instruction? It's a link; we should remove.
Also remove "Our Culture & Commitment" paragraph? That's culture but could be part of Benefits? Might be considered benefits? It's about supportive environment, wellness resources. Could be included in Benefits as prose. But we already have benefits list; we can include a paragraph about culture.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all specifics: e.g., "build and evolve the systems behind fraud prevention at scale, helping protect nearly two trillion dollars in transactions for millions of users each year." etc.
We need to format responsibilities as
- . Similarly for requirements/qualifications/skills/benefits.
We need to decide which heading for each block.
Possible mapping:
- About the role: Could include the summary paragraph: "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 seems appropriate for About the role.
- Responsibilities: The bullet list after "Responsibilities". We'll capture each line.
- Requirements: The "Experience And Knowledge" block (the required experience). Could be under Requirements.
- Qualifications: The "Preferred Experience" block (preferred). Could be under Qualifications.
- Skills: Could be maybe combine some? But we have no explicit skills separate; maybe we can put technical skills under Skills? But we already have experience and knowledge includes skills. Might be redundant. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But we have headings list; we can include both if they have content. We'll include Requirements (required) and Qualifications (preferred). Skills maybe not needed; we could omit if no specific skills beyond those. But we could put "Skills" as maybe the technical proficiencies: Python, AWS, etc. However those are already in Experience And Knowledge. To avoid duplication, we could omit Skills section.
- Benefits: The list of benefits: Health & Wellness, Hybrid Work Opportunities, Flexible Time Off, Career Development & Mentoring Programs, Health & Wellness Benefits (competitive health insurance, generous paid parental leave), Community Volunteering & Company Philanthropy Programs, Employee Peer Recognition Programs – “You Earned it”. Also earlier culture statements: "Being as passionate about our people as we are about our mission. We celebrate our employees..." etc. We'll include those as prose maybe.
- Pay: Not present, omit.
- Schedule: Could include Hybrid Work Opportunities and Flexible Time Off under Schedule. But those are also in Benefits. Might duplicate. Better to keep them under Benefits as they are benefits. Schedule maybe not needed. The instruction: include Schedule section only if posting actually states them. It does mention hybrid work opportunities and flexible time off, which are schedule-related. But they are also benefits. However we could still include Schedule section with those points, but we must not duplicate content. We could keep them under Benefits and not Schedule. Since we already have Benefits covering those, we can omit Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
Check if any other sections like "Skills" needed: maybe we can include Skills as a summary of technical proficiencies: "Strong experience building and operating production software systems; Deep proficiency in Python; Experience with AWS; Infrastructure as code; CI/CD; Distributed, event-driven, serverless systems; API design; System integration; Reliability; Observability; Ability to work in large enterprise codebases; Comfortable learning across technologies; Git-based workflows; Modern Python tooling; Analytical/problem-solving; Communication; Collaboration; Interest in AI-powered agentic tools." That's essentially the Experience And Knowledge block. If we put that under Requirements, we don't need Skills.
Thus final HTML:
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
- 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.
Qualifications
- Preferred 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
Benefits
- Health & Wellness
- 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”
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.