Principal Engineer (AI Engineering)

We need to output HTML fragment with sections: 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. Must preserve all substantive info. We need to parse the posting. Content: - About This Role: description: Wells Fargo is seeking a Principal Engineer (AI Engineering Productivity & Enablement) within Technology as part of COO (Chief Operating Office) Technology's Engineering Productivity & AI Adoption organization. In this highly visible role, you will lead the adoption and operational execution of AI-powered engineering tools across the enterprise, helping technology teams increase productivity, accelerate software delivery, and realize measurable business value. Partnering with engineering leaders, technical champions, platform teams, and analytics partners, you will drive enablement, adoption strategy, performance insights, and continuous optimization across solutions such as GitHub Copilot, Devin, Claude Code, and Cursor. Success in this role requires a blend of technology transformation leadership, operational excellence, and data-driven decision making. You will leverage adoption and engineering productivity metrics to inform investment decisions, identify opportunities to improve outcomes, and scale proven AI engineering practices that enhance how software is built across the organization. Then "In This Role, You Will" bullet list (actually sentences). Let's extract responsibilities. List: - 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 groups - Lead 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 thinking - Translate 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 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 recommends innovations that enhance operations or provide a competitive advantage to the organization - Strategically engage with all levels of professionals and managers across the enterprise and serve as an expert advisor to leadership These are responsibilities. Then "Required Qualifications:" bullet: 7+ years of Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education Then "Desired Qualifications:" list many items. We need to separate sections: Requirements (maybe required qualifications), Qualifications (desired?), Skills (maybe desired qualifications?), but we must follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content. - About the role: the introductory paragraph(s) before responsibilities. - Responsibilities: the "In This Role, You Will" list. - Requirements: maybe the "Required Qualifications:" (7+ years experience). Could also include other mandatory items? There's only that. - Qualifications: maybe the "Desired Qualifications:" list. - Skills: maybe we could extract specific skills from desired qualifications? But we might combine desired qualifications into Qualifications section and not create Skills unless there is explicit skill list. The desired qualifications list includes many skill-like items: experience coordinating large-scale tech rollout, managing adoption operations, analytical capability, define dashboard requirements, working knowledge of AI-assisted tools, understanding software delivery workflows, experience working through distributed network, strong executive communication skills, proven ability to operate in large matrixed regulated enterprise, experience with developer productivity frameworks, experience evaluating relationships between AI tool usage and delivery outcomes, familiarity with Power BI etc., experience operating champion network, experience managing software licenses, familiarity with financial management, experience preparing executive-level updates, prior experience in financial services or another highly regulated industry. These could be considered Qualifications or Skills. Since we have both Qualifications and Skills headings allowed, we could put the desired qualifications under Qualifications, and maybe extract specific skills under Skills (like "Strong analytical capability", "Experience with Power BI, Tableau, etc.", "Strong executive communication skills", "Experience with developer productivity frameworks", etc.). But we must not invent or summarize away detail; we must preserve all substantive information. So we need to include all desired qualifications items somewhere. If we put them all under Qualifications, that's fine; we can leave Skills empty or omit it. But we must not create a heading with filler/placeholder text. So if we don't have specific content for Skills, we should omit the Skills section entirely. Similarly, Benefits: we have a list of benefits under "Benefits Wells Fargo provides eligible employees with a comprehensive set of benefits, many of which are listed below." Then 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 need to include Benefits section with those items as

• . Pay: we have "Pay Range Reflected is the base pay range offered for this position. Pay may vary depending on factors including but not limited to demonstrated examples of prior performance, skills, experience, or work location. Employees may also be eligible for incentive opportunities. $159,000.00 - $305,000.00". So we have pay range. Must include Pay section with that info. Schedule: we have "This position offers a hybrid work schedule." and "Ability to travel up to 25% of the time". Also "Job Expectations: This position is not eligible for Visa sponsorship." That's not schedule but maybe we could include under Schedule? The schedule heading expects schedule info. We have hybrid work schedule and travel up to 25%. So we can put that under Schedule. Also visa sponsorship not schedule; maybe we could include under Job Expectations but we don't have a heading for that; we could incorporate into Schedule or maybe omit. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include Schedule with hybrid work schedule and travel up to 25%. The visa sponsorship is not schedule; we could maybe put under a separate section like "Job Expectations" but not in allowed headings. Since we must only use allowed headings, we could either omit that info or incorporate into Schedule? It's not schedule but maybe we can put under Schedule as additional note? Might be considered filler if not schedule. Better to omit visa sponsorship? But we must preserve ALL substantive information; we cannot omit info. So we need to include that info somewhere. Since we don't have a heading for "Job Expectations", we could maybe put it under Schedule as a note? But that would be misrepresenting. However the instruction says we must preserve ALL substantive information; we cannot invent or summarize away detail. So we need to include that info. Perhaps we can add a

  under Schedule that includes hybrid work schedule, travel up to 25%, and also note that visa sponsorship is not eligible. That's still under Schedule heading but includes non-schedule info; but it's still preserving info. The heading is Schedule, but content includes other details; maybe acceptable as we are not creating a new heading. The instruction: "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 mixing other info under a heading as long as the heading has real specific content. So we can put all job expectations under Schedule. Alternatively, we could create a section "Requirements" for visa sponsorship? Not appropriate. So we will put under Schedule. Now Benefits: we have list. Now we need to output HTML fragment with headings

  for each section. We must not include / tags. We must use

  • for any list of duties/requirements/benefits. We must use

    for prose. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to remove the EEO statement, drug policy, disability inclusion, etc. Also remove "Posting End Date: 24 Sep 2026", "Job posting may come down early due to volume of applicants.", "We Value Equal Opportunity", etc. Also remove "Reference Number R-576430-3". Also remove "Job Expectations:" heading? We'll incorporate its content. We must preserve all substantive information: that includes the description, responsibilities, required qualifications, desired qualifications, benefits, pay, schedule (hybrid, travel, visa sponsorship not eligible). Also maybe note "This position is not eligible for Visa sponsorship." We'll keep. Now structure:

    About the role

    Wells Fargo is seeking a Principal Engineer (AI Engineering Productivity & Enablement) within Technology as part of COO (Chief Operating Office) Technology's Engineering Productivity & AI Adoption organization. In this highly visible role, you will lead the adoption and operational execution of AI-powered engineering tools across the enterprise, helping technology teams increase productivity, accelerate software delivery, and realize measurable business value. Partnering with engineering leaders, technical champions, platform teams, and analytics partners, you will drive enablement, adoption strategy, performance insights, and continuous optimization across solutions such as GitHub Copilot, Devin, Claude Code, and Cursor. Success in this role requires a blend of technology transformation leadership, operational excellence, and data-driven decision making. You will leverage adoption and engineering productivity metrics to inform investment decisions, identify opportunities to improve outcomes, and scale proven AI engineering practices that enhance how software is built across the organization.

    Responsibilities

    • 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 groups
    • Lead 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 thinking
    • Translate 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 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 recommends innovations that enhance operations or provide a competitive advantage to the organization
    • Strategically engage with all levels of professionals and managers across the enterprise and serve as an expert advisor to leadership

    Requirements

    7+ years of Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education

    Qualifications

    • Demonstrated experience coordinating a large-scale technology rollout across multiple business or technology organizations
    • Experience managing adoption operations, including user prioritization, onboarding, access readiness, usage monitoring, communications, and intervention routines
    • Strong analytical capability with experience interpreting adoption, utilization, delivery, and engineering productivity data
    • Ability to define dashboard requirements, validate data quality, analyze trends, and translate findings into leadership decisions
    • Working knowledge of AI-assisted and autonomous engineering tools such as GitHub Copilot, Devin, Claude Code, Cursor, or comparable platforms
    • Understanding of software delivery workflows, repositories, pull requests, engineering metrics, and common adoption barriers
    • Experience working through a distributed network of engineering leaders, champions, administrators, analysts, and vendor partners
    • Strong executive communication skills, including concise status reporting, decision framing, risk escalation