Lead Java Engineer | Payments Technology

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. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate, EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: Intro: "Why Wells Fargo Are you looking for more? Find it here. At Wells Fargo, we're more than a financial services leader -we're a global trailblazer committed to driving innovation, empowering communities, and helping our customers succeed. We believe that a meaningful career is much more than just a job - it's about finding all of the elements to help you thrive, in one place. Living the Well Life means you're supported in life, not just work. It means having robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being. You'll be rewarded for investing in your community, celebrated for being your authentic self, and empowered to grow. And we're recognized for it - Wells Fargo continues to rank on the LinkedIn Top Companies lists of best workplaces "to grow your career." Join us!" That's generic company description; could be considered "About the role"? Actually "About This Role" heading appears later. The intro is more about Wells Fargo overall; maybe we can put under "About the role"? But the instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role section with description of role and maybe company overview. Then "About This Role" paragraph: "Wells Fargo is seeking a Lead Software Engineer to join the Commercial and Corporate & Investment Banking Technology (CCIBT) team within Corporate & Investment Banking (CIB). In this role, you will help design, build, and deliver innovative technology solutions that support critical banking and capital markets platforms used by clients around the world. Working on complex, large-scale initiatives, you will collaborate closely with software engineers, architects, product teams, and business stakeholders to deliver scalable solutions that align with strategic business objectives. You will play a key role in driving engineering excellence, advancing modern technology capabilities, and enabling growth across a diverse portfolio of banking, lending, investment banking, and markets services. This is an opportunity to make a meaningful impact while partnering with teams across the organization to solve complex challenges and deliver value to clients globally." That's role description. Then "In This Role, You Will" bullet list (looks like sentences separated by line breaks). Let's extract each bullet: - Lead complex technology initiatives including those that are companywide with broad impact - Act as a key participant in developing standards and companywide best practices for engineering complex and large-scale technology solutions for technology engineering disciplines - Design, code, test, debug, and document for projects and programs - Review and analyze complex, large-scale technology solutions for tactical and strategic business objectives, enterprise technological environment, and technical challenges that require in-depth evaluation of multiple factors, including intangibles or unprecedented technical factors - Make decisions in developing standard and companywide best practices for engineering and technology solutions requiring understanding of industry best practices and new technologies, influencing and leading technology team to meet deliverables and drive new initiatives - Collaborate and consult with key technical experts, senior technology team, and external industry groups to resolve complex technical issues and achieve goals - Lead projects, teams, or serve as a peer mentor These are responsibilities/duties. Then "Required Qualifications:" list: - 5+ years of Software Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education - 5+ years of experience with Java application development - 3+ years of experience in Spring Boot - 2+ years of experience with Kafka - 2+ years of experience with cloud implementation technologies (Azure, Kubernetes, Google Cloud, or PCF) Then "Desired Qualifications:" list: - 3+ years of experience in Business Process Orchestration - 3+ years of experience in database technologies such as Oracle or MongoDB - 2+ years of experience with Microservices or SOA and REST APIs - 2+ years' experience with API Gateway and Containerization - 2+ years of experience in Agile working environment such as Scrum or Kanban - Experience with front-end development using Angular or ReactJS - Experience with Oracle Service Bus - Strong Design experience in Design Patterns, Domain Driven Design, and Event-based integration - Experience working with Wholesale Payments Then "Job Expectations:" bullet list: - This position is not eligible for visa sponsorship - This position offers a hybrid work schedule - Must be able to work on-site at the listed location - Relocation assistance is not available for this position Then "Job Location: 300 S Brevard St. Charlotte, NC 28202" Then "Posting End Date: 16 Oct 2026" Then "Job posting may come down early due to volume of applicants." Then EEO etc which we must remove. We need to decide sections. We have: - About the role: could combine company overview + About This Role paragraph. - Responsibilities: the "In This Role, You Will" list. - Requirements: maybe Required Qualifications. - Qualifications: maybe Desired Qualifications? But we have both Required and Desired. The instruction list includes Requirements, Qualifications, Skills. We could map Required Qualifications to Requirements, Desired Qualifications to Qualifications (or Skills). But we need to avoid duplication. Could also put Skills under Skills section (like specific tech skills). However we have many tech skills in Desired Qualifications; could treat them as Skills. Better: Use sections: - About the role (company overview + role summary) - Responsibilities (the bullet list) - Requirements (Required Qualifications) - Qualifications (Desired Qualifications) maybe as "Preferred Qualifications" - Skills (maybe extract specific technical skills from Desired Qualifications? But we could also put Desired Qualifications under Qualifications and not have Skills separate if not needed. But we need to follow instruction: prefer a few substantive sections over many thin ones. So we could combine Desired Qualifications into Qualifications section and not have Skills separate unless we have distinct skills list. We also have Job Expectations (visa, hybrid schedule, on-site, relocation). Those could go under Schedule (hybrid work schedule) and maybe Benefits? Not exactly benefits. Could put under Schedule (hybrid work schedule) and maybe under Benefits (none). There's no explicit benefits statement besides generic earlier about robust benefits, competitive compensation, programs for work-life balance. That is in the company overview paragraph: "Living the Well Life means you're supported in life, not just work. It means having robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." That's a benefits statement. So we can create Benefits section with that sentence. Pay: Not mentioned specifically; only "competitive compensation" but not specific. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention "competitive compensation" but not specific numbers or range. Is that enough? It says "competitive compensation" is a statement but not specific. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "competitive compensation" is somewhat vague but still a statement. However it's not a specific number or range; but it's still stating that compensation is competitive. Might be considered substantive? The instruction says avoid filler like "commensurate with experience". "competitive compensation" is similar but not exactly filler. I'd lean to not create Pay section because it's not specific. Safer to omit Pay. Schedule: we have hybrid work schedule mentioned. That's specific: hybrid work schedule. So we can create Schedule section with that. Benefits: we have robust benefits, competitive compensation, programs for work-life balance and well-being. That's substantive enough. Job Location: we could include under a short p maybe not a heading. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Job location is minor metadata; we can put in a p. Posting End Date: also minor metadata; could be in p. We must remove boilerplate like EEO, drug policy, etc. Now produce HTML fragment. Structure:

About the role

At Wells Fargo, we're more than a financial services leader - we're a global trailblazer committed to driving innovation, empowering communities, and helping our customers succeed. We believe that a meaningful career is much more than just a job - it's about finding all of the elements to help you thrive, in one place. Living the Well Life means you're supported in life, not just work. It means having robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being. You'll be rewarded for investing in your community, celebrated for being your authentic self, and empowered to grow. And we're recognized for it - Wells Fargo continues to rank on the LinkedIn Top Companies lists of best workplaces "to grow your career." Join us!

Wells Fargo is seeking a Lead Software Engineer to join the Commercial and Corporate & Investment Banking Technology (CCIBT) team within Corporate & Investment Banking (CIB). In this role, you will help design, build, and deliver innovative technology solutions that support critical banking and capital markets platforms used by clients around the world. Working on complex, large-scale initiatives, you will collaborate closely with software engineers, architects, product teams, and business stakeholders to deliver scalable solutions that align with strategic business objectives. You will play a key role in driving engineering excellence, advancing modern technology capabilities, and enabling growth across a diverse portfolio of banking, lending, investment banking, and markets services. This is an opportunity to make a meaningful impact while partnering with teams across the organization to solve complex challenges and deliver value to clients globally.

Responsibilities

• Lead complex technology initiatives including those that are companywide with broad impact
• Act as a key participant in developing standards and companywide best practices for engineering complex and large-scale technology solutions for technology engineering disciplines
• Design, code, test, debug, and document for projects and programs
• Review and analyze complex, large-scale technology solutions for tactical and strategic business objectives, enterprise technological environment, and technical challenges that require in-depth evaluation of multiple factors, including intangibles or unprecedented technical factors
• Make decisions in developing standard and companywide best practices for engineering and technology solutions requiring understanding of industry best practices and new technologies, influencing and leading technology team to meet deliverables and drive new initiatives
• Collaborate and consult with key technical experts, senior technology team, and external industry groups to resolve complex technical issues and achieve goals
• Lead projects, teams, or serve as a peer mentor

Requirements

• 5+ years of Software Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education
• 5+ years of experience with Java application development
• 3+ years of experience in Spring Boot
• 2+ years of experience with Kafka
• 2+ years of experience with cloud implementation technologies (Azure, Kubernetes, Google Cloud, or PCF)

Qualifications

• 3+ years of experience in Business Process Orchestration
• 3+ years of experience in database technologies such as Oracle or MongoDB
• 2+ years of experience with Microservices or SOA and REST APIs
• 2+ years' experience with API Gateway and Containerization