Jobs · Information Technology · North Carolina

Lead Software Automation Engineer (Python)

Wells Fargo · Charlotte, NC · 3 wk ago
Information Technology$119k–$187k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have content: About the role (first paragraph). Responsibilities (list of duties). Required Qualifications, US (list). Desired Qualifications (list). Job Expectations (some statements). Benefits (list). Pay Range (specific numbers). Schedule? Not mentioned. So we should not include Schedule. Also maybe include Qualifications? The posting has Required Qualifications and Desired Qualifications; we could combine into a Qualifications section or separate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading and include both required and desired? Or we could have Requirements heading for required qualifications, and Qualifications heading for desired? But they said "Prefer a few substantive sections over many thin ones." So maybe combine required and desired into Qualifications. Also we have Skills maybe from desired qualifications (like Agile, CI/CD, etc). Could create Skills section. But we need to avoid thin sections. Let's think: The posting includes many bullet-like items under Required Qualifications and Desired Qualifications. Could treat them as Requirements (required) and Skills (desired). But we need to decide. We have content for About the role (paragraph). Responsibilities (list). Requirements (maybe required qualifications). Qualifications (maybe desired qualifications). Skills (maybe specific technical skills). Benefits (list). Pay (range). No Schedule. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO etc. Also remove Posting End Date, Job posting may come down early..., We Value Equal Opportunity etc. Also remove Drug and Alcohol Policy etc. Also remove Reference Number. We must preserve all substantive information: that includes the pay range, benefits list, responsibilities list, required qualifications, desired qualifications, job expectations (like not eligible for visa sponsorship, ability to work on-site, relocation assistance not available). Those are substantive; we should include them perhaps under a section like Job Expectations or Requirements? There's no heading for Job Expectations in the list but we could put under Requirements or maybe a separate section like "Job Expectations". But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings. Job Expectations could go under Requirements or Qualifications? Probably under Requirements (since they are expectations). But we have separate Required Qualifications already. Could combine job expectations into Requirements as bullet points. We need to preserve all substantive info: visa sponsorship not eligible, on-site work, no relocation assistance. Those are job expectations. We also have "Pay Range Reflected is the base pay range offered for this position. Pay may vary depending on factors..." That's substantive; we should include under Pay heading. Benefits list: we should include under Benefits heading. Now we need to format: Use

for each section heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not include filler like "commensurate with experience". Not present. We must not include duplicated lines. Let's extract content. About the role: The first paragraph(s) before "In this role, you will:" includes multiple sentences. Let's capture: "About this role: Wells Fargo is seeking a Lead Software Engineer in Technology as part of Cybersecurity. Learn more about the career areas and lines of business at wellsfargojobs.com. The Lead Python Software Engineer will drive the design and delivery of enterprise-scale infrastructure automation solutions, transforming manual operational processes into secure, API-driven, and highly scalable services across network and cryptographic infrastructure platforms. This role combines deep Python engineering expertise with cloud-native architecture, Infrastructure-as-Code, and workflow orchestration to accelerate self-service capabilities, improve operational reliability, and advance Wells Fargo's software-defined infrastructure strategy. Wells Fargo is seeking a Lead Python Software Engineer in infrastructure automation organization with a goal to deliver automation solutions that enable a software driven Infrastructure environment. If you're passionate about automation, cloud-native technologies, and building scalable systems, this is your opportunity to make a real impact in a large-scale enterprise environment." We can combine into a paragraph. Responsibilities: The list after "In this role, you will:" includes many items each starting with a verb. Let's capture each as bullet: - Lead complex technology initiatives including those that are companywide with broad impact - Design and build automation to streamline provisioning, configuration, and lifecycle management of infrastructure resources across a range of cryptographic and network infrastructure. - Create API‑driven integrations between network platforms and internal systems. - Develop and maintain automation frameworks that improve reliability and reduce operational toil. - Translate manual operational procedures into codified, repeatable automation. - Ensure automation artifacts follow best practices for performance, maintainability, and security. - Collaborate with network engineering and platform teams to align automation with broader architectural strategies. - Lead the automation of product deployments, customer journeys, and creation of APIs for our Load Balancing and other infrastructure services - Demonstrate proficiency in using AI‑assisted development and analysis tools (e.g., GitHub Copilot and approved code‑centric agents) - Leverage AI to accelerate system design, coding, testing, analysis, and troubleshooting - Apply strong technical judgment when validating and integrating AI‑assisted outputs into solutions - Understand and account for model limitations, security risks, and operational considerations - Apply AI responsibly in development and production environments - Ensure AI usage aligns with security, compliance, privacy, and ethical standards We should keep them as list items. Requirements: Could be the Required Qualifications, US section plus job expectations (visa, on-site, relocation). Let's list: Required Qualifications, US: - 5+ years of Software Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education - 5+ years python development experience leveraging Django, Flask or FastAPI - 2+ years working with private cloud or hybrid platforms and a proven track record of building complex infrastructure programmatically with IaC tools. - 2+ years of hands-on experience with Infrastructure as Code tools Ansible and GitHub. Job Expectations (maybe under Requirements): - This position is not eligible for Visa sponsorship - Ability to work on-site at approved location - Relocation assistance is not available for this position We could combine. Qualifications: Desired Qualifications list: - Demonstrated experience automating infrastructure platforms and services, including the development of self-service capabilities and operational workflows. - 5+ years experience with Agile, CI/CD, DevOps concepts and SRE principles. - Extensive expertise in microservices, RESTful APIs, and event-driven architectures. - Experience developing modern user interfaces using micro-frontend frameworks, including React or Angular. - Strong hands-on experience supporting and enhancing web and API platforms built with Django, FastAPI, and Apigee. - Experience with one or more workflow and orchestration platforms such as Temporal, Camunda, or Cadence. - Working knowledge of Unix/Linux operating systems, database querying, and API testing tools such as Postman. - Familiarity with infrastructure services including data protection, cryptographic key management, PKI, certificate management, or load balancing technologies. - Strong troubleshooting, operational support, and problem-resolution skills across distributed application environments. Skills: Could be overlapping with desired qualifications; but we might not need separate Skills if we already have Qualifications. However instruction says we can include Skills section if there is real specific content. The desired qualifications include many skills; we could treat them as Skills. But we already have Qualifications section for desired qualifications. To avoid thin sections, maybe combine desired qualifications into Qualifications and not have separate Skills. But we have Required Qualifications already; we could have Requirements (required) and Qualifications (desired). That seems appropriate. Thus sections: About the role (p), Responsibilities (ul), Requirements (ul) (includes required qualifications + job expectations), Qualifications (ul) (desired qualifications), Benefits (ul), Pay (p with range). No Schedule. We must not include heading for Requirements if content is empty; but we have content. Now format HTML. We need to ensure we don't include any extra text outside HTML fragment. Let's craft:

    About the role

    Wells Fargo is seeking a Lead Software Engineer in Technology as part of Cybersecurity. Learn more about the career areas and lines of business at wellsfargojobs.com. The Lead Python Software Engineer will drive the design and delivery of enterprise-scale infrastructure automation solutions, transforming manual operational processes into secure, API-driven, and highly scalable services across network and cryptographic infrastructure platforms. This role combines deep Python engineering expertise with cloud-native architecture, Infrastructure-as-Code, and workflow orchestration to accelerate self-service capabilities, improve operational reliability, and advance Wells Fargo's software-defined infrastructure strategy. Wells Fargo is seeking a Lead Python Software Engineer in infrastructure automation organization with a goal to deliver automation solutions that enable a software driven Infrastructure environment. If you're passionate about automation, cloud-native technologies, and building scalable systems, this is your opportunity to make a real impact in a large-scale enterprise environment.

    Responsibilities

    • Lead complex technology initiatives including those that are companywide with broad impact
    • Design and build automation to streamline provisioning, configuration, and lifecycle management of infrastructure resources across a range of cryptographic and network infrastructure.
    • Create API‑driven integrations between network platforms and internal systems.
    • Develop and maintain automation frameworks that improve reliability and reduce operational toil.
    • Translate manual operational procedures into codified, repeatable automation.
    • Ensure automation artifacts follow best practices for performance, maintainability, and security.
    • Collaborate with network engineering and platform teams to align automation with broader architectural strategies.
    • Lead the automation of product deployments, customer journeys, and creation of APIs for our Load Balancing and other infrastructure services
    • Demonstrate proficiency in using AI‑assisted development and analysis tools (e.g., GitHub Copilot and approved code‑centric agents)
    • Leverage AI to accelerate system design, coding, testing, analysis, and troubleshooting
    • Apply strong technical judgment when validating and integrating AI‑assisted outputs into solutions
    • Understand and account for model limitations, security risks, and operational considerations
    • Apply AI responsibly in development and production environments
    • Ensure AI usage aligns with security, compliance, privacy, and ethical standards

    Requirements

    • 5+ years of Software Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education
    • 5+ years python development experience leveraging Django, Flask or FastAPI
    • 2+ years working with private cloud or hybrid platforms and a proven track record of building complex infrastructure programmatically with IaC tools.
    • 2+ years of hands-on experience with Infrastructure as Code tools Ansible and GitHub.
    • This position is not eligible for Visa sponsorship
    • Ability to work on-site at approved location
    • Relocation assistance is not available for this position

    Qualifications

    • Demonstrated experience automating infrastructure platforms and services, including the development of self-service capabilities and operational workflows.
    • 5+ years experience with Agile, CI/CD, DevOps concepts and SRE principles.
    • Extensive expertise in microservices, REST

Similar jobs