Lead Java Software Engineer- Commodities Technology

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe combine Required and Desired?), Benefits, Pay, Schedule only if present. The posting includes: "About this role:" then description. Then "In this role, you will:" list of duties. Then "Required Qualifications:" and "Desired Qualifications:" then "Job Expectations:" includes visa sponsorship, hybrid work schedule, relocation assistance not available, location posting, posting end date. Also mentions "We Value Equal Opportunity" etc which is boilerplate to remove. Also "Living the Well Life" intro is generic fluff; we need to preserve substantive information but can we remove generic marketing? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The intro about Wells Fargo being a global trailblazer etc is likely boilerplate but could be considered substantive? It's generic marketing; but we might keep it as part of About the role? However they said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The intro about Wells Fargo being a global trailblazer is not EEO but could be considered marketing fluff. Not sure if we should keep. The instruction: "Prefer a few substantive sections over many thin ones." Probably we should keep the "About this role:" description as About the role section. Then responsibilities as bullet list. Then qualifications as Required and Desired maybe combined under Requirements? Could separate Required Qualifications and Desired Qualifications as subheadings? But only allowed headings are the listed ones: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use Requirements for required qualifications, Qualifications for desired? Or Skills for desired? Let's map: Required Qualifications -> Requirements section. Desired Qualifications -> Qualifications section (or Skills). The posting also mentions "Job Expectations: This position is not eligible for visa sponsorship This position offers a hybrid work schedule Relocation assistance is not available for this position". That's schedule info (hybrid work schedule) and maybe other expectations. So we can include Schedule section with hybrid work schedule. Benefits: not mentioned besides generic "robust benefits, competitive compensation" in intro but that's generic fluff; we should not create Benefits section unless posting actually states them. The intro says "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 generic but still mentions benefits and compensation. However instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state robust benefits, competitive compensation, programs for work-life balance. That is stating benefits and compensation. So we could include Benefits and Pay sections? But we need specific content; we have only generic statements. Might be considered filler? The instruction says 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. It does state them, albeit generic. I'd include Benefits and Pay sections with the statements. However we need to avoid duplication. The intro also mentions "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 sentence. We could put that in Benefits and Pay sections? Might be awkward. Better: Keep About the role includes that sentence? Actually About the role section could include the introductory paragraph about Wells Fargo and the role. But we should not repeat job title as heading. The page already shows it. So we can start with

About the role

then a

containing the description from "About this role:" plus maybe the introductory fluff? The introductory fluff about Wells Fargo being a global trailblazer is not specific to role; maybe we can drop as it's generic. But instruction says preserve ALL substantive information; is that substantive? It's about company culture, maybe considered substantive. However it's also generic marketing; but we could keep it as part of About the role. Let's extract substantive paragraphs: - 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! - About this role: Wells Fargo is seeking a Lead Specialty Software Engineer to be a part of the Commodities Technology team. This ideal candidate will be an individual contributor and technical expert in the development of trade processing, pricing and risk for the Commodities business. These systems are utilized across front and middle office and provide the full suite of front-to-back trading functionality. This individual will engage product and business stake holders to analyze highly complex business requirements and translate them into technical specifications. Also engage other technical teams within the firm as well as outside vendors to provide technical interfaces, estimates and deliverables. Design and/or redesign existing complex computer platforms and applications. Maintain full project life-cycle tasks, such as business and technical analysis, designing, coding, testing, and implementation plans. Coordinate implementation activities across a broad range of functions and departments; work with client groups to identify, arrange, and/or deliver training needs. Learn more about the career areas and lines of business at wellsfargojobs.com - In this role, you will: (list) - Required Qualifications: (list) - Desired Qualifications: (list) - Job Expectations: This position is not eligible for visa sponsorship This position offers a hybrid work schedule Relocation assistance is not available for this position Location Posting: 300 S Brevard Street, Charlotte, NC 28202 Posting End Date: 2 Oct 2026 *Job posting may come down early due to volume of applicants. We need to remove boilerplate: EEO, equal opportunity, drug policy, etc. Also remove "Learn more about the career areas and lines of business at wellsfargojobs.com" maybe considered application instruction? It's a link; maybe keep? It's not instruction to apply. Could keep as part of About the role. We need to output only HTML fragment. Structure:

About the role

... combine the introductory Wells Fargo paragraph and the About this role description? Might be too long but okay.

Responsibilities

• ... each bullet from "In this role, you will:"

Requirements

• ... Required Qualifications items

Qualifications

• ... Desired Qualifications items

Schedule

Hybrid work schedule. Not eligible for visa sponsorship. Relocation assistance not available.

We could also include Pay and Benefits sections using the generic statements. But we already have schedule. The intro mentions robust benefits, competitive compensation, programs for work-life balance. Could add Benefits and Pay sections. But we must not create sections with filler. The statements are specific enough? "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." That's specific enough? Might be okay. Let's add:

Benefits

Robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being.

Pay

Competitive compensation (as part of the total rewards package).

But that repeats compensation. Might be redundant. Better to combine: Benefits section includes robust benefits and programs; Pay section maybe not needed because compensation already mentioned. However we have no specific pay range. The instruction says never create Pay section unless posting actually states them. It does state "competitive compensation". That's a statement. So we can include Pay section with that phrase. But we risk duplication. Could put Pay: Competitive compensation. Benefits: Robust benefits and programs for work-life balance. Let's do that. Now ensure we don't repeat job title as heading. Not needed. Now produce HTML. We need to escape any special characters? Not needed. Let's craft the About the role paragraph: Combine: 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 Specialty Software Engineer to be a part of the Commodities Technology team. This ideal candidate will be an individual contributor and technical expert in the development of trade processing, pricing and risk for the Commodities business. These systems are utilized across front and middle office and provide the full suite of front-to-back trading functionality. This individual will engage product and business stake holders to analyze highly complex business requirements and translate them into technical specifications. Also engage other technical teams within the firm as well as outside vendors to provide technical interfaces, estimates and deliverables. Design and/or redesign existing complex computer platforms and applications. Maintain full project life-cycle tasks, such as business and technical analysis, designing, coding, testing, and implementation plans. Coordinate implementation activities across a broad range of functions and departments; work with client groups to identify, arrange, and/or deliver training needs. Learn more about the career areas and lines of business at wellsfargojobs.com That's a long paragraph but okay. Now Responsibilities bullets: - Lead complex initiatives on selected domains - Ensure systems are monitored to increase operational efficiency and managed to mitigate risk - Define opportunities to maximize resource utilization and improve processes while reducing cost - Lead, design, develop, test and implement applications and system components, tools and utilities, models, simulation, and analytics to manage complex business functions using sophisticated technologies - Resolve coding, testing and escalated platform issues of a technically challenging nature - Lead team to ensure compliance and risk management requirements for supported area are met and work with other stakeholders to implement key risk initiatives - Mentor less experienced software engineers - Collaborate and influence all levels of professionals including managers - Lead team to achieve objectives - Partner with production support and platform engineering teams effectively Now Required Qualifications bullets: - 5+ years of Specialty 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 development - 3+ years of experience in capital markets business and processes Desired Qualifications bullets: - Working knowledge of Open Link Endure trading platform - Working knowledge with tools required for regression test automation - Working knowledge on Agile best practices - Experience with JavaScript/Reacts is nice to have - Experience with middleware messaging technologies like Solace, Tibco RV, etc. - Experience with caching technologies such as Coherence, MongoDB, Redis, etc. - Experience with event processing technologies such as Apache Storm, Apache Flink, etc. Now Schedule section: hybrid work