Principal Engineer (AI Engineering)

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to parse the posting. First, "About This Role" paragraph: description of role. That's about the role. So we can have

About the role

then

with that paragraph. Then responsibilities: The bullet list under "In This Role, You Will" includes many items. Those are responsibilities. So we can have

Responsibilities

then

• each bullet. Then qualifications: There's "Required Qualifications:" and "Desired Qualifications:" We could combine into a Qualifications section? The spec says we can have Qualifications heading. We'll include both required and desired as list items maybe separate subheadings? But we should not create extra headings beyond allowed list. We can put under Qualifications heading a
  with items, maybe marking required vs desired within text. But we must preserve all substantive info. Could separate into Required Qualifications and Desired Qualifications as separate

  ? Not allowed; only those specific headings. Could we put both under Qualifications and differentiate via bold? Probably okay. Then Skills: The posting includes many skill-like items under Desired Qualifications etc. Could map to Skills section. But we already have Qualifications; maybe we can put skill-like items under Skills. However we need to avoid duplication. Let's think: The spec says we can use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where each piece goes. "Requirements" could be for required qualifications. "Qualifications" could be for desired qualifications? Or we could combine. But we need to avoid thin sections. Let's map: - About the role: paragraph. - Responsibilities: the "In This Role, You Will" list. - Requirements: Required Qualifications (7+ years experience etc.) - Qualifications: Desired Qualifications list (the bullet items after Desired Qualifications:). That includes many items like experience coordinating rollout, managing adoption operations, analytical capability, etc. - Skills: maybe we could extract specific skill items like "Working knowledge of AI-assisted and autonomous engineering tools...", "Understanding of software delivery workflows...", "Experience working through a distributed network...", "Strong executive communication skills...", "Proven ability to operate in a large, matrixed...", "Experience with developer productivity frameworks...", "Experience evaluating relationships between AI tool usage...", "Familiarity with Power BI, Tableau...", "Experience operating a champion network...", "Experience managing software licenses...", "Familiarity with financial management...", "Experience preparing executive-level updates...", "Prior experience in financial services...". Those are essentially skills/qualifications. But they are already in Desired Qualifications. Could we just put Desired Qualifications under Qualifications and not have Skills? The spec says we can include a section only when posting has real specific content for it. If we put all desired qualifications under Qualifications, we might not need Skills. But we need to decide if we want to include Skills section to avoid thin Qualifications? The spec says prefer a few substantive sections over many thin ones. So better to have fewer sections. So we can have About the role, Responsibilities, Requirements (required qualifications), Qualifications (desired qualifications). Then Benefits, Pay, Schedule. Check if we have content for Benefits: yes, list of benefits. Pay: yes, pay range $159,000 - $305,000. Schedule: yes, hybrid work schedule, ability to travel up to 25% of the time. Also Job Expectations: "This position is not eligible for Visa sponsorship." That's maybe not schedule but could be included under Schedule? Or maybe we could put under Schedule: hybrid work schedule, travel up to 25%, not eligible for visa sponsorship. That seems okay. We must not include boilerplate like EEO, etc. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must not include application instructions. We must not include Posting End Date? That's metadata; could be folded into a short p or drop. The spec says fold minor metadata into a short

  or drop it. So we could include a short p at top maybe with Posting End Date? But it's minor; we could drop it. Probably better to drop. Now produce HTML:

  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, and actionable recommendations.
  • Proven ability to operate in a large, matrixed, regulated enterprise with established risk, security, access, and governance requirements.
  • Experience with developer productivity frameworks such as DORA, SPACE, or internal engineering productivity scorecards.
  • Experience evaluating relationships between AI tool usage and delivery outcomes such as throughput, cycle time, quality, backlog reduction, and pull request completion.
  • Familiarity with Power BI, Tableau, GitHub analytics, Jira, Azure DevOps, or equivalent reporting ecosystems.
  • Experience operating a champion network, field enablement model, community of practice, or train-the-trainer program.
  • Experience managing software licenses or technology entitlements based on utilization and business value.
  • Familiarity with financial management, vendor oversight, pilot governance, or build-versus-buy decisions for engineering tools.
  • Experience preparing executive-level updates for CIO, COO, finance, engineering, or transformation leadership.
  • Prior experience in financial services or another highly regulated industry.

  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 reimbursement

  Pay

  $159,000.00 - $305,000.00

  Schedule

  Hybrid work schedule; ability to travel up to 25% of the time; not eligible for Visa sponsorship.

  Check we didn't include any boilerplate. We omitted Job Expectations about visa sponsorship but we included it in Schedule. Good. We omitted "Job Expectations: This position is not eligible for Visa sponsorship." we placed in Schedule. We omitted "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." That's extra detail about pay; we should preserve ALL substantive information. The spec says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that explanatory text about pay, not just the range. So we need to include that paragraph under Pay. Thus Pay section should have

  with the full description: "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" We need to keep the dollar range. Similarly for Benefits we listed items; we should keep the introductory sentence: "Wells Fargo provides eligible employees with a comprehensive set of benefits, many of which are listed below. Visit Benefits - Wells Fargo Jobs for an overview of the following benefit plans and programs offered to employees." That's substantive? It's a bit generic but it's part of the posting. Should we include? The spec says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that sentence as a

  before the list. Similarly for Schedule we might include the sentence about hybrid work schedule and travel etc. Already we have that. For Requirements we might need to include the line "Required Qualifications: 7+ years of Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education". We already have that as a p. For Qualifications we might need to include the heading "Desired Qualifications:" but we can drop that heading as it's minor; we already have list items. We need to ensure we didn't lose any substantive content from the "