Principal Engineer (Governance, Risk, Compliance & Control)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention, no filler. Remove boilerplate like EEO, legal, etc. Also remove application instructions. Must not include sections with placeholder like "commensurate with experience". Pay and Schedule: posting includes Pay Range and hybrid work schedule. So we can include Pay and Schedule sections. Benefits: they list benefits. So include Benefits. Responsibilities: there is description of role: "In This Role, You Will ..." bullet list. So include Responsibilities. Requirements: there is "Required Qualifications:" list. Also "Desired Qualifications:" maybe under Skills? Could treat as Qualifications. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. About the role: initial paragraph describing role, team, etc. That's about the role. Responsibilities: the bullet list starting "In This Role, You Will ..." includes many responsibilities. Requirements: maybe the "Required Qualifications:" list. Qualifications: maybe the "Desired Qualifications:" list? Or we could combine Required and Desired under Qualifications? But we have both headings. Could put Required under Requirements, Desired under Qualifications. Skills: maybe we could list core technologies (Java, React, .NET, AI tooling) as Skills. Or we could put under Skills. Pay: include pay range. Schedule: include hybrid work schedule. Benefits: include benefits list. We must not include sections with filler like "commensurate with experience". Not present. We must not include Job ID etc. Also remove "Posting End Date", "Job posting may come down early", "We Value Equal Opportunity", etc. Also remove "Reference Number". Also remove "Job Expectations" maybe? It includes visa sponsorship, hybrid schedule, relocation assistance. Hybrid schedule we already have in Schedule. Visa sponsorship and relocation assistance maybe not needed as separate sections; could be omitted as they are not under headings we have. But we could include them under Schedule? Probably not needed. The instruction: include a section ONLY when posting has real, specific content for it. So we can include Schedule with hybrid work schedule. Visa sponsorship and relocation assistance maybe not needed; they could be omitted. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting that are relevant. Let's extract content. About This Role paragraph: "Wells Fargo is seeking a Principal Engineer (Governance, Risk, Compliance & Control) to join the Enterprise Functions Technology Organization. The Enterprise Functions Technology (EFT) group provides technology solutions and support for Risk, Audit, Finance, Marketing, Human Resources, Corporate Properties, and Stakeholder Relations business lines. In addition, EFT provides unique technology solutions and innovation for Wells Fargo Technology, Enterprise Shared Services, and Enterprise Data Management. This combined portfolio of applications and tools are purpose built to meet the challenges of stability, security, scalability, and speed. This role is a deeply hands-on senior engineering position focused on building, fixing, and evolving large-scale systems that support risk management. The individual is expected to work directly in the codebase, prototype solutions, troubleshoot complex issues alongside engineers, and step in to resolve problems when they arise. Rather than operating at a purely theoretical level, this role emphasizes practical execution-applying the right technology to the problem and delivering working solutions. While remaining hands-on, the role also influences technical direction by guiding solution design, driving key engineering decisions, and promoting reusable patterns and best practices across the organization. The role partners closely with engineers, providing coaching through real-world problem solving. Core technologies include Java and React, with minimal .NET, and growing use of modern AI tooling such as agent development, model integration, and prompt engineering, with openness to continued learning and AI certifications." That's about the role. Responsibilities: "In This Role, You Will Act as an advisor to leadership to develop or influence applications, network, information security, database, operating systems, or web technologies for highly complex business and technical needs across multiple groupsLead the strategy and 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 thinkingTranslate advanced technology experience, an in-depth knowledge of the organizations tactical and strategic business objectives, the enterprise technological environment, the organization structure, and strategic technological opportunities and requirements into technical engineering solutionsProvide vision, direction and expertise to leadership on implementing innovative and significant business solutionsMaintain knowledge of industry best practices and new technologies and recommends innovations that enhance operations or provide a competitive advantage to the organizationStrategically engage with all levels of professionals and managers across the enterprise and serve as an expert advisor to leadership" It seems the bullet list lost formatting; but we can treat each sentence as a responsibility. We'll output as

• each. 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 architecting, designing and leading the delivery of large-scale solutions 4+ years of Financial Services industry 4+ years experience presenting technology strategy and concepts to C-level executives and large audiences 2+ years experience delivering cloud ready and cloud native solutions 2+ years experience with Java full stack development" Desired Qualifications: "2+ years experience AI utilization and agentic development Preferred experience with Google Cloud Compute (GCP) or Microsoft Azure Experience with the Wells Fargo Risk Technology ecosystem Experience with Wells Fargo application delivery and application management processes and standards Experience mentoring others and leading informally in matrixed organizational structures Current ability and desire to continue developing solutions personally, "hands on keyboard", for the hardest problems facing the product" Skills: maybe core technologies: Java, React, minimal .NET, modern AI tooling (agent development, model integration, prompt engineering), openness to continued learning and AI certifications. Pay: "$159,000.00 - $305,000.00" Schedule: "This position offers a hybrid work schedule." Benefits list: "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 reimbursement" We should keep as list. We must not include boilerplate like "Visit Benefits - Wells Fargo Jobs for an overview..." etc. So we just list benefits. We must not include "Posting End Date", "Job posting may come down early", "We Value Equal Opportunity", etc. We must not include "Job Expectations" section (visa sponsorship, relocation assistance). Could we include them under Schedule? Probably not; they are separate. Since we don't have a heading for them, we can omit them as they are not required headings. But we must preserve ALL substantive information. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit visa sponsorship and relocation assistance, we are omitting substantive info. However, we are only allowed to output sections under the given headings. We could include them under Schedule? But schedule is about hybrid work schedule. Visa sponsorship and relocation assistance are not schedule. Could we add a separate section like "Other Details"? Not allowed headings list only those. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the examples suggest we should stick to those. Safer to only use those headings. But then we would lose visa sponsorship and relocation assistance info. However, maybe those are considered "Job Expectations" which is not in the list, but we could treat them as part of Schedule? Not really. Could we put them under Requirements? No. Could we put them under Qualifications? No. Maybe we can include them under "About the role" as extra sentences? But they are not about the role. Could we add a paragraph after About the role? The instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid extra paragraphs outside headings? It says output ONLY the HTML fragment. It didn't say we must wrap everything in headings. We could have a

  for miscellaneous info not under headings. But the instruction about headings: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings or paragraphs. It just says use h3 for section headings. So we could have a

  for other details like visa sponsorship and relocation assistance. However, the instruction also says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can fold minor metadata into a short

  or drop it. Visa sponsorship and relocation assistance could be considered minor metadata? Possibly. But they are substantive? Might be considered job expectations. The instruction says "fold minor metadata into a short

  or drop it." So we could put them in a

  under maybe no heading. That seems acceptable. Thus we can output:

  About the role

  ... (the about paragraph)

  Responsibilities

  • ... each responsibility

  Requirements

  • ... each required qualification

  Qualifications

  • ... each desired qualification

  Skills

  • ... core technologies

  Benefits

  • ... each benefit

  Pay

  $159,000.00 - $305,000.00

  Schedule

  This position offers a hybrid work schedule.

  Then maybe a

  for visa sponsorship and relocation assistance: "This position is not eligible for Visa sponsorship. Relocation assistance is not available for this position." We should not include "Job Expectations" heading. Now ensure we preserve all substantive info: we have about role, responsibilities, requirements, qualifications, skills, benefits, pay, schedule, plus visa/relocation note. Check that we didn't miss any details: The about role paragraph includes core technologies etc. We also have skills section that repeats core technologies; but that's okay as we preserve info. However, we might be duplicating core technologies info (already in about role). But instruction says preserve ALL substantive information; duplication is okay as long as we don't lose info. Could we avoid duplication by moving core technologies to skills only and not repeat in about role? But about role already mentions them; we could keep them there and also in skills; it's fine. Check responsibilities: we need to split the long block into separate li items. The original block: "Act as an advisor to leadership to develop or influence applications, network, information security, database, operating systems, or web technologies for highly complex business and technical needs across multiple groupsLead the strategy and 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 thinkingTranslate advanced technology experience,