Principal Engineer - Java Full Stack

We need to output HTML fragment with sections: About the role? The posting includes description includes intro about Wells Fargo (company description). Should we include "About the role" heading? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Include a section ONLY when posting has real, specific content for it. So we need to decide which sections have content. We have: - Intro about Wells Fargo: "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 ...". This is more about company culture, could be "About the role"? Actually "About the role" is about the job, not company. But we could treat that as "About the role" maybe includes description of role? The posting includes "Wells Fargo is seeking a Principal Engineer as part of the Commercial and Corporate & Investment Banking Technology (CCIBT) team to support Payment Solutions, Capital Markets Services, Wholesale Digitization, and International Technology." That's about the role. So we can put that under

About the role

with paragraphs. - Responsibilities: The bullet list after "In This Role, You Will Act as an advisor..." includes many responsibilities. So we can put under

Responsibilities

with

• items. - Requirements: There's "Required Qualifications:" list. That's qualifications. Could be

  Qualifications

  or

  Requirements

  . The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Required Qualifications and Desired Qualifications. Could combine into Qualifications section with required and desired? But we need to preserve all substantive info. Could have

  Required Qualifications

  and

  Desired Qualifications

  but those aren't in the list of allowed headings? The list is examples, not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are typical but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely we should stick to those headings. So we can map Required Qualifications to

  Qualifications

  and maybe include both required and desired under that? But we also have Desired Qualifications separate. Could treat Desired Qualifications as

  Skills

  ? Not exactly. Could create

  Qualifications

  for required, and

  Skills

  for desired? But desired includes many technical skills, could be skills. However the instruction says prefer a few substantive sections over many thin ones. So maybe combine required and desired into Qualifications section, with subheadings? But we cannot add extra headings beyond h3? We could still use

  for sub-sections? Might be okay but risk. Better to follow the examples: we can have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Also maybe Location? Not in list. Could fold location into a short

  under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Location is minor metadata? Could be placed in a

  . We'll include location in a paragraph after About the role maybe. Pay: we have pay range $159,000 - $305,000. So we need a Pay section. Benefits: we have benefits list. So Benefits section. Schedule: not mentioned (hybrid environment mentioned under Job Expectations). Could be Schedule? Not explicit. Could omit Schedule. We also have Job Expectations: Ability to work in a hybrid environment, not eligible for visa sponsorship, ability to work additional hours as needed. Could be placed under a section like "Job Expectations" but not in allowed headings. Could fold into About the role or Responsibilities? Probably better to create a section "Job Expectations" but not in list. However instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those categories. Safer to stick to those. We could put hybrid environment info under About the role or Responsibilities? Maybe under Responsibilities as a note? But it's not a responsibility. Could put under About the role as a brief note. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out the EEO statement, disability, drug policy, recruitment requirements, reference number, posting end date, etc. We must preserve all substantive information: company description, role description, responsibilities, required qualifications, desired qualifications, pay, benefits, location, hybrid expectation, visa sponsorship, additional hours. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

  About the role

  Wells Fargo is seeking a Principal Engineer as part of the Commercial and Corporate & Investment Banking Technology (CCIBT) team to support Payment Solutions, Capital Markets Services, Wholesale Digitization, and International Technology. This diverse portfolio spans multiple technology disciplines and strategic innovations. CCIBT provides strategic, enterprise-wide technology capabilities and enabling services to our lines of business and management of the applications in terms of skills, stability, security, scalability, speed, and cost. As part of the CCIBT technology team, this Principal Engineer will lead the innovative end-to-end technology solution delivery for commercial lending product capabilities across loan origination, loan servicing and loan delivery. They will have focused product knowledge with strong hands-on technical expertise to lead the solution delivery for commercial lending products and services offered by Wells Fargo. They will participate in agile ceremonies like big room planning, reviewing, and analyzing complex strategies for product functionality, feature delivery and priority, making architecture decisions, strategically collaborating with product teams and stakeholders defining product delivery roadmaps, directing scrum teams based on business value delivery, providing consistent architecture guidance, extensive code reviews, guiding development teams with the day to day delivery task and collaborating with scrum teams in producing results, conducting Proof of concepts with latest technologies and enabling innovation by demonstrating thought leadership.

  Location: 401 Las Colinas Blvd W Bldg B., Irving, TX 75039; 194 Wood Avenue S., Iselin, NJ 08830. This position is hybrid‑eligible, not eligible for visa sponsorship, and may require additional hours as needed.

  Then Responsibilities:

  Responsibilities

  • Act as an advisor to leadership to develop or influence solution design for complex business needs in an applied and end‑to‑end owner manner.
  • Solve and, as needed, perform hands‑on design and code, resolution of highly complex and unique challenges requiring in‑depth evaluation across multiple areas or the enterprise, delivering solutions that are long‑term, large‑scale and require vision, creativity, innovation, advanced analytical and inductive thinking.
  • Translate advanced technology experience, an in‑depth knowledge of the organization's tactical and strategic business objectives, the enterprise technological environment, the organization structure, and strategic technological opportunities and requirements into technical engineering solutions.
  • Provide vision, direction, and expertise to leadership on implementing innovative and significant business solutions.
  • Maintain knowledge of industry best practices and new technologies and recommend innovations that enhance operations or provide a competitive advantage to the organization.
  • Leverage AI, automation, and data engineering capabilities to improve business outcomes.
  • Collaborate with Architecture, Platforms, Technology Leadership and Product teams to shape and develop technical strategies and roadmaps and ensure key capability and dependencies are being progressed/managed.
  • Partner closely with product and program leadership teams to ensure technology implementation and delivery are aligned with business goals and timelines.
  • Lead and drive ongoing improvements for platform stability and performance, by addressing technical debt and enhancing operational efficiency.
  Qualifications: we need Required and Desired. Could combine into one Qualifications section with two sublists? Could use

  Qualifications

  then

  Required:

  ... then

  Desired:

  ... That seems okay. Let's extract Required Qualifications list: - 7+ years of Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education - 7+ years of experience in Java 17+, Spring Boot 3.x, Spring Security, Spring Cloud, Hibernate, JPA, Python, Scala REST APIs, and Microservices Architecture - 7+ years of experience with Angular 16, JavaScript, HTML5, CSS3, Bootstrap, jQuery, and AJAX - 3+ years of Teradata and Unix experience - 2+ years of AI technology implementation experience - 2+ years of experience working in Agile environments - 2+ years of experience using Teradata Utilities, Load/Unload processes, and BigQuery - 2+ years of database experience with Oracle, Teradata, SQL Server, and relational database design - 2+ years of SQL development and performance tuning skills - 2+ years of Microsoft Excel skills utilizing Power Query Desired Qualifications list: - Experience with AWS, Azure, and Google Cloud Platform services - Experience with Docker, Kubernetes, and OpenShift - Experience with Kafka and event-driven architecture - Experience with Jenkins, GitHub Actions, Maven, Gradle, and SonarQube - Knowledge of Ansible, Shell Scripting, F5, AVI, and infrastructure automation - Experience deploying applications on Tomcat, JBoss, and WebSphere - Strong understanding of MVC architecture, J2EE design patterns, and enterprise application design - Experience with Apache Spark, ETL technologies (Ab Initio, Informatica, DataStage), DBMS platforms (Teradata, SQL Server) - Experience implementing secure, scalable, and highly available solutions in large enterprise environments - Cloud-native application modernization and migration initiatives - Enterprise data engineering and analytics platforms - AI-driven automation and intelligent workflow implementations - Financial services or large-scale enterprise technology environments - Ability to manage multiple priorities in a fast-paced Agile environment - Passion for innovation, continuous improvement, and engineering excellence. - Strong communication skills and ability to collaborate effectively with a cross-functional and technical teams to drive the solution engineering decisions - Strong analytical skills with high attention to detail and accuracy - Excellent verbal, written, and interpersonal communication skills We'll put those. Pay section:

  Pay

  $159,000.00 - $305,000.00 base pay range. Pay may vary depending on factors including demonstrated prior performance, skills, experience, or work location. Employees may also be eligible for incentive opportunities.

  Benefits section:

  Benefits

  • Health benefits
  • 401(k) Plan
  • Paid time off
  • Disability benefits
  • Life insurance, critical illness insurance, and accident insurance
  • Parental leave
  • Critical caregiving leave
  • Discounts and savings
  • Commuter benefits
  • Tuition reimbursement
  • Scholarships for dependent children
  • Adoption reimburs