Lead Automation Software Engineer

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 like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Content: About this role: Wells Fargo is seeking a Lead Software Engineer for Network Automation and Software development (e.g., Nautobot, Ansible, Python, APIs, Terraform) and a solid understanding of the underlaying technologies in Network Infrastructure Then "In this role, you will:" bullet list. Let's extract responsibilities: - Lead complex technology initiatives including those that are companywide with broad impact - Act as a key participant in developing standards and companywide best practices for engineering complex and large scale technology solutions for technology engineering disciplines - Design, code, test, debug, and document for projects and programs - Review and analyze complex, large-scale technology solutions for tactical and strategic business objectives, enterprise technological environment, and technical challenges that require in-depth evaluation of multiple factors, including intangibles or unprecedented technical factors - Make decisions in developing standard and companywide best practices for engineering and technology solutions requiring understanding of industry best practices and new technologies, influencing and leading technology team to meet deliverables and drive new initiatives - Collaborate and consult with key technical experts, senior technology team, and external industry groups to resolve complex technical issues and achieve goals - Lead projects, teams, or serve as a peer mentor Then "Required Qualifications:" list: - 5+ years of Software Development / Network Automation experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience. - 3+ years of technical documentation experience - 3+ years of programming and scripting skills: e.g Python, Go, Django, Perl, Ansible, Terraform "Desired Qualifications:" list: - Prior experience in a lead or senior engineer capacity preferred - Relevant certifications (e.g CCIE Automation, JNCIE) preferred - Bachelor’s degree in Computer Science, Engineering, or other related area of study - Containers (docker, Kubernetes), Helm, Harness, and other package managers or AI driven CICD frameworks. - Temporal, Celery and other workflow or runtime execution environments. - Demonstrable Software development in Python, Go, .net API experience: Restconf, Netconf, Swagger, API based integration - Observability: gRPC, flow data, logging, Grafana, ELK, Prometheus - Experience with information security and risk management including policy and standards, information security assessments, security best practices, and mitigation solution design and implementation - Strong leadership skills Then "Job Expectations:" includes: - No visa sponsorship - Hybrid in-office schedule - Potential travel - 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. $119,000.00 - $224,000.00 - Benefits 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. - 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 - Posting End Date: 6 Oct 2026 * Job posting may come down early due to volume of applicants. - Then EEO etc which we must remove. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. "About the role": The introductory paragraph: "Wells Fargo is seeking a Lead Software Engineer for Network Automation and Software development (e.g., Nautobot, Ansible, Python, APIs, Terraform) and a solid understanding of the underlaying technologies in Network Infrastructure". Could also include the sentence about "About this role:" but we can just put that paragraph. "Responsibilities": The bullet list under "In this role, you will:". "Requirements": Could be the Required Qualifications? Usually Requirements = required qualifications. We'll put required qualifications there. "Qualifications": Could be Desired Qualifications? Or maybe combine? The instruction says use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need separate sections for Requirements and Qualifications. Likely Requirements = required qualifications, Qualifications = desired qualifications. We'll follow that. "Skills": Could be technical skills list from desired qualifications? Or we could extract skills like programming languages, tools, etc. The desired qualifications list includes many technical skills. We could put those under Skills. But we also have some skills in required qualifications (programming and scripting skills). Might be overlapping. We need to preserve all substantive info; we can distribute. Better: Put required qualifications under Requirements, desired qualifications under Qualifications, and then maybe Skills could be a summary of technical skills (like Python, Go, etc.) but that would duplicate. However instruction: "Prefer a few substantive sections over many thin ones." So we might combine some. But we need to follow the headings list; we can omit sections if no real specific content. So we could omit Skills if we don't have distinct content not already covered. But we have technical skills in desired qualifications; we could put them under Qualifications (desired). Then Skills could be omitted. However we need to include a section only when posting has real specific content for it. If we put desired qualifications under Qualifications, that's fine. Then we might not need Skills. But we also have "Benefits", "Pay", "Schedule". Pay we have explicit range. Schedule we have "Hybrid in-office schedule". Also "No visa sponsorship" and "Potential travel" maybe under Job Expectations but not schedule. We could put schedule under Schedule section: "Hybrid in-office schedule". Also maybe mention "Potential travel" but that's not schedule; could be omitted or put under Responsibilities? Probably better to keep schedule as hybrid in-office schedule. Pay section: include the pay range and note about variation. Benefits: list the benefits. Now we need to ensure we don't include boilerplate like EEO, legal, etc. Also remove "Posting End Date: 6 Oct 2026 * Job posting may come down early due to volume of applicants." That's metadata; we can drop it per instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can drop the posting end date. Also remove "No visa sponsorship" maybe we could keep as part of Job Expectations but not a section; we could incorporate into a short paragraph under maybe Responsibilities? But it's not a responsibility. Could be placed under a short

maybe under a generic "Job Expectations" but we don't have that heading. Since we are to output only the sections listed, we could incorporate minor metadata into a short

within maybe About the role or Responsibilities? Better to just drop it if not needed. However "No visa sponsorship" is substantive info about eligibility; maybe we should keep it somewhere. Could add a short

under About the role or Responsibilities? But it's not about role. Could add a

under a generic section like "Job Expectations" but we don't have that heading. The instruction says we can fold minor metadata into a short

or drop it. So we could add a

after the sections maybe? But they said output ONLY the HTML fragment — no /, no markdown code fences. They didn't forbid extra

not under headings? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. 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 have

  elements outside of sections? Probably yes, as minor metadata. But we should keep it minimal. Thus we could add a

  for "No visa sponsorship. Potential travel." after the sections. But we also have "Hybrid in-office schedule" which belongs to Schedule section. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now craft HTML. Structure:

  About the role

  Wells Fargo is seeking a Lead Software Engineer for Network Automation and Software development (e.g., Nautobot, Ansible, Python, APIs, Terraform) and a solid understanding of the underlying technologies in Network Infrastructure.

  Responsibilities

  • Lead complex technology initiatives including those that are companywide with broad impact
  • Act as a key participant in developing standards and companywide best practices for engineering complex and large scale technology solutions for technology engineering disciplines
  • Design, code, test, debug, and document for projects and programs
  • Review and analyze complex, large-scale technology solutions for tactical and strategic business objectives, enterprise technological environment, and technical challenges that require in-depth evaluation of multiple factors, including intangibles or unprecedented technical factors
  • Make decisions in developing standard and companywide best practices for engineering and technology solutions requiring understanding of industry best practices and new technologies, influencing and leading technology team to meet deliverables and drive new initiatives
  • Collaborate and consult with key technical experts, senior technology team, and external industry groups to resolve complex technical issues and achieve goals
  • Lead projects, teams, or serve as a peer mentor

  Requirements

  • 5+ years of Software Development / Network Automation experience, or equivalent demonstrated through work experience, training, or military experience.
  • 3+ years of technical documentation experience
  • 3+ years of programming and scripting skills: e.g., Python, Go, Django, Perl, Ansible, Terraform

  Qualifications

  • Prior experience in a lead or senior engineer capacity preferred
  • Relevant certifications (e.g., CCIE Automation, JNCIE) preferred
  • Bachelor’s degree in Computer Science, Engineering, or other related area of study
  • Experience with containers (Docker, Kubernetes), Helm, Harness, and other package managers or AI‑driven CI/CD frameworks
  • Experience with workflow/runtime execution environments such as Temporal, Celery
  • Demonstrable software development in Python, Go, .NET API experience: RESTCONF, NETCONF, Swagger, API‑based integration
  • Observability expertise: gRPC, flow data, logging, Grafana, ELK, Prometheus
  • Experience with information security and risk management including policy and standards, assessments, security best practices, and mitigation solution design and implementation
  • Strong leadership skills

  Benefits

  • Health benefits
  • 401(k) Plan
  • Paid time off
  • Disability benefits
  • Life insurance, critical illness insurance, and accident insurance