Senior Network Engineer - AI & Automation
St. Jude Children's Research Hospital · Tennessee, United States · 1 mo ago
$95k–$170k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Intro: "The Enterprise Network Team is looking for a senior engineer who thinks beyond traditional CLI-driven network management. This person will lead the shift toward automated, self-healing network operations, using AI and modern tooling to reduce manual work and increase reliability across a large, complex environment. This position may be eligible for remote work. However, St. Jude requires all remote employees to: Travel to our Memphis campus for the interview process and/or orientation, if selectedTravel to Memphis to work on-site for one week per quarter, or as requested based on business needs, if hired. By applying, you acknowledge and agree to these travel requirements as a condition of employment. This position is remote within approved U.S. locations. Due to state-specific employment regulations, we are unable to consider applicants currently residing in California for remote work; however, candidates based in California who are willing to relocate to an approved location may be considered."
That's about the role (description). Could be "About the role" section.
- Job Responsibilities: list of bullet points (starting with "Design and build automation workflows..." etc). So Responsibilities section.
- Minimum Education and/or Training: Bachelor's degree... Master's degree preferred. That's qualifications/requirements.
- Minimum Experience: list of experience items. That's also requirements/qualifications.
- Compensation: salary range $94,640 - $169,520 per year. That's Pay section.
- Benefits: "Explore our exceptional benefits! We are committed to a human-centered hiring experience..." Not specific benefits listed. It says "Explore our exceptional benefits!" but no list. So we should not create Benefits section unless specific benefits listed. There's no list, so we omit Benefits.
- Schedule: Not mentioned. So omit.
- Skills: Could be extracted from experience list (Python, Ansible, AI/ML, Cisco, etc). But we have a Requirements/Qualifications section that can include skills. The instruction: Use sections like Skills only if posting has real specific content. We could put skills under Requirements or Qualifications. Probably combine into Requirements (or Qualifications). We need to decide which headings to use.
We have: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role, Responsibilities, Requirements (education + experience), Pay. Possibly Qualifications could be same as Requirements; but we should not duplicate. We could put education under Requirements, experience under Requirements as well. Or split: Requirements for experience, Qualifications for education. But we need to avoid thin sections. Better to have one Requirements section that includes both education and experience. Or we could have Qualifications for education and Requirements for experience. But both would be thin? Education is a few lines, experience is many lines. Could be okay.
We need to preserve all substantive information. So we must include education details and experience details.
We'll create:
maybe). The experience list includes many bullet-like sentences. We'll put them in
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Intro: "The Enterprise Network Team is looking for a senior engineer who thinks beyond traditional CLI-driven network management. This person will lead the shift toward automated, self-healing network operations, using AI and modern tooling to reduce manual work and increase reliability across a large, complex environment. This position may be eligible for remote work. However, St. Jude requires all remote employees to: Travel to our Memphis campus for the interview process and/or orientation, if selectedTravel to Memphis to work on-site for one week per quarter, or as requested based on business needs, if hired. By applying, you acknowledge and agree to these travel requirements as a condition of employment. This position is remote within approved U.S. locations. Due to state-specific employment regulations, we are unable to consider applicants currently residing in California for remote work; however, candidates based in California who are willing to relocate to an approved location may be considered."
That's about the role (description). Could be "About the role" section.
- Job Responsibilities: list of bullet points (starting with "Design and build automation workflows..." etc). So Responsibilities section.
- Minimum Education and/or Training: Bachelor's degree... Master's degree preferred. That's qualifications/requirements.
- Minimum Experience: list of experience items. That's also requirements/qualifications.
- Compensation: salary range $94,640 - $169,520 per year. That's Pay section.
- Benefits: "Explore our exceptional benefits! We are committed to a human-centered hiring experience..." Not specific benefits listed. It says "Explore our exceptional benefits!" but no list. So we should not create Benefits section unless specific benefits listed. There's no list, so we omit Benefits.
- Schedule: Not mentioned. So omit.
- Skills: Could be extracted from experience list (Python, Ansible, AI/ML, Cisco, etc). But we have a Requirements/Qualifications section that can include skills. The instruction: Use sections like Skills only if posting has real specific content. We could put skills under Requirements or Qualifications. Probably combine into Requirements (or Qualifications). We need to decide which headings to use.
We have: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role, Responsibilities, Requirements (education + experience), Pay. Possibly Qualifications could be same as Requirements; but we should not duplicate. We could put education under Requirements, experience under Requirements as well. Or split: Requirements for experience, Qualifications for education. But we need to avoid thin sections. Better to have one Requirements section that includes both education and experience. Or we could have Qualifications for education and Requirements for experience. But both would be thin? Education is a few lines, experience is many lines. Could be okay.
We need to preserve all substantive information. So we must include education details and experience details.
We'll create:
About the role
... (the intro paragraph(s) including remote work details)
Responsibilities
- Design and build automation workflows using Ansible/AAP to standardize configuration, deployment, and remediation. ...
Requirements
Education: Bachelor's degree in Computer Science, Engineering, Business or related field of study required. Master's degree preferred.
Experience: ... list items (we need to keep each as
- ...
Pay
A reasonable estimate of the current salary range is $94,640 - $169,520 per year for the role of Senior Network Engineer - AI & Automation.
We should not include Benefits, Schedule, Skills sections because no specific content. We must not repeat job title as heading. Already not. We must not include Job ID etc. We must remove boilerplate: EEO, equal-opportunity, scam-warning, etc. The posting includes: "Explore our exceptional benefits! We are committed to a human-centered hiring experience. Technology may support portions of our process, but recruiting decisions involve human review and engagement. Learn more about our approach to AI. St. Jude is an Equal Opportunity Employer No Search Firms St. Jude Children's Research Hospital does not accept unsolicited assistance from search firms for employment opportunities. Please do not call or email. All resumes submitted by search firms to any employee or other representative at St. Jude via email, the internet or in any form and/or method without a valid written search agreement in place and approved by HR will result in no fee being paid in the event the candidate is hired by St. Jude." We must remove that boilerplate. So we omit that. Also remove "Compensation In recognition of certain U.S. state and municipal pay transparency laws, St. Jude is including a reasonable estimate of the compensation range for this role. This is an estimate offered in good faith and a specific salary offer takes into account factors that are considered in making compensation decisions including but not limited to skill sets, experience and training, licensure and certifications, and other business and organizational needs. It is not typical for an individual to be hired at or near the top of the salary range and compensation decisions are dependent on the facts and circumstances of each case." That's part of compensation description; we can keep the salary range but maybe we can keep a short sentence. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the compensation description? It's substantive but maybe we can keep it as part of Pay section. The instruction says: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state compensation range and some explanation. So we can include Pay section with that explanation and the range. Thus Pay section:In recognition of certain U.S. state and municipal pay transparency laws, St. Jude is including a reasonable estimate of the compensation range for this role. This is an estimate offered in good faith and a specific salary offer takes into account factors that are considered in making compensation decisions including but not limited to skill sets, experience and training, licensure and certifications, and other business and organizational needs. It is not typical for an individual to be hired at or near the top of the salary range and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the current salary range is $94,640 - $169,520 per year for the role of Senior Network Engineer - AI & Automation.
That's fine. Now ensure we removed duplicated lines: The intro had "Travel to our Memphis campus for the interview process and/or orientation, if selectedTravel to Memphis to work on-site for one week per quarter, or as requested based on business needs, if hired." There's a missing space between "selectedTravel". We need to keep as is? Probably we should keep the text but maybe add a space for readability? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Adding a space is not inventing content, just formatting. Might be okay but safer to keep exactly as given? The text appears to be a typo; but we should preserve it exactly? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Adding a space is not changing substantive info, just formatting. I'd keep as is but maybe add a space to make it readable. I'd keep original but maybe insert a space: "selectedTravel" -> "selected Travel". That's a minor edit but could be considered inventing? It's fixing a typo; not sure. Safer to keep exactly as given: "selectedTravel". However that looks odd. I'd keep as is but maybe it's okay. Now produce HTML fragment. Let's craft:About the role
The Enterprise Network Team is looking for a senior engineer who thinks beyond traditional CLI-driven network management. This person will lead the shift toward automated, self-healing network operations, using AI and modern tooling to reduce manual work and increase reliability across a large, complex environment. This position may be eligible for remote work. However, St. Jude requires all remote employees to: Travel to our Memphis campus for the interview process and/or orientation, if selectedTravel to Memphis to work on-site for one week per quarter, or as requested based on business needs, if hired. By applying, you acknowledge and agree to these travel requirements as a condition of employment. This position is remote within approved U.S. locations. Due to state-specific employment regulations, we are unable to consider applicants currently residing in California for remote work; however, candidates based in California who are willing to relocate to an approved location may be considered.
Responsibilities
- Design and build automation workflows using Ansible/AAP to standardize configuration, deployment, and remediation.
- Identify manual, repetitive network operations tasks and engineer them out through scripting and orchestration.
- Evaluate and pilot AI-driven tools for anomaly detection, predictive maintenance, and intelligent alerting.
- Build integrations across monitoring platforms, and network infrastructure to close the loop between detection and action.
- Contribute to a broader AI fluency initiative on the team, helping less automation-focused engineers build these skills.
- Partner with architecture and security teams to ensure automation is safe, auditable, and aligned with change control policy.
- Own high-visibility automation projects end to end, from proof of concept to production rollout.
- Stay current on emerging network AI/ML tooling and bring forward recommendations.
- Perform other duties as assigned to meet the goals and objectives of the department and institution.
- Maintains regular and predictable attendance.
Requirements
Education: Bachelor's degree in Computer Science, Engineering, Business or related field of study required. Master's degree preferred.
Experience:
- Minimum experience: Four (4) years of IT experience with experience in infrastructure operations and engineering environments.
- Experience in infrastructure design, systems analysis, and security management.
- Some experience working with commercial models around infrastructure capacity procurement.
- Experience in customer service and vendor management.
- Some experience in business stakeholder engagement and management.
- Demonstrated ownership of network automation initiatives, from identifying a manual process to designing, building, and deploying the automated solution in production preferred.
- Track record of taking automation projects beyond scripting, with real accountability for outcomes and reliability preferred.
- Strong Python skills, plus experience with Ansible or similar orchestration tools preferred.
- Practical experience applying AI/ML concepts to network operations, whether through vendor tools, custom models, or LLM-based workflows preferred.
- Deep understanding of Cisco routing/switching, and comfort working across Catalyst, Nexus, and NDFC environments preferred.
- Experience integrating network systems with ITSM platforms like ServiceNow preferred.
- Ability to translate a manual process into an automated one without cutting corners on reliability or security preferred.
- Experience with Cisco Catalyst Center, ThousandEyes, or StatSeeker preferred.
- Familiarity with Graph API, Power Automate, or similar low-code automation platforms preferred.
- Prior experience building or fine-tuning LLM-based tools for IT operations