AI Software Engineer III - Senior Lead
Entergy · New Orleans, LA · 4 wk ago
HybridFull-time
We need to output HTML fragment with sections only if real content. No job title heading. No metadata like Job ID etc. Remove boilerplate. Need to preserve substantive info: job summary/purpose, duties/responsibilities, minimum requirements (but there are multiple levels: Senior Lead, Senior, Engineer III). The posting seems to have multiple job titles? Actually the posting includes multiple roles: AI Software Engineer III - Senior Lead PS, AI Software Engineer Sr Staff. The content includes sections for each level. We need to reformat into clean semantic HTML. Likely we should combine requirements? The instruction: "Prefer a few substantive sections over many thin ones." So we could have sections: About the role (job summary/purpose), Responsibilities (duties), Requirements (minimum requirements, maybe combine). Could also have Qualifications, Skills, Benefits, Pay, Schedule only if present. There's no explicit pay or schedule. Benefits not mentioned. So we omit those sections.
We need to include for each section heading. Use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Do not put Job ID etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from job summary, duties, requirements (including education, experience, preferred experience, technical capabilities, general capabilities, skills and abilities, minimum knowledge, skills and abilities). Also location info? The posting includes location preferences. Should we include location? It's substantive. Could be part of About the role or maybe a separate section? There's no explicit heading for location, but we can include it in a paragraph under About the role or maybe a separate "Location" section? The instruction: include a section ONLY when the posting has real, specific content for it. There's location info, but no heading like "Location". We could create a section like "Location" if we have content. However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive. It says use those headings for section headings. Likely we should stick to those headings. So location could be part of About the role paragraph.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove duplicated lines. The posting repeats some sections for each level. We need to consolidate? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot omit details like specific years for each level. We could keep them as separate bullet points under Requirements, maybe grouped by level. That's preserving detail.
Thus we will create:
About the role
Job summary/purpose paragraph.
Responsibilities
- ... each duty
Requirements
Maybe break into subheadings? But we only allowed h3 for section headings. Could we have nested? Probably not. We could just list all requirements as bullet points, preserving details for each level.
We need to include education, experience, preferred experience, technical capabilities, general capabilities, skills and abilities, minimum knowledge, skills and abilities.
We'll create bullet points under Requirements.
We must not include fluff like "N/A". Not present.
Let's extract content.
Job Summary/Purpose:
"As a core member of the AI team, the software engineer is responsible for designing, building, and maintaining scalable, reliable and maintainable software systems. These systems often power AI-enabled applications, ranging from internal tools to customer-facing platforms. The engineer works across the full development lifecycle-from architecture and coding to deployment and support-ensuring that software products meet high standards of performance, usability, and security. While many solutions incorporate AI technologies, the focus is on delivery robust, well-engineered applications that integrate with business workflows. These tools are designed to help users solve real-world problems more efficiently, enabling smarter decisions and more streamlined operations across the organization."
That's the prose.
Job Duties/Responsibilities list:
- Design, develop, and implement software solutions on system design specifications.
- Collaborate with cross-functional teams to define, design, and ship new features.
- Refine and optimize data and machine learning algorithms into production environments.
- Ensure scalability, efficiency, and maintainability of the codebase.
- Ensure the performance, quality, and responsiveness of applications.
- Identify, correct, and improve inefficient code.
- Participate in code reviews to maintain code quality.
- Document software development and monitor systems to ensure they meet both user needs and business goals.
- Stay updated on new technologies and best practices in software engineering.
Now Requirements: There are multiple levels: Senior Lead, Senior, Engineer III. Also there is "Minimum Knowledge, Skills And Abilities Required Of The Position" etc.
We need to preserve all.
Let's extract each:
Senior Lead:
- Minimum Education Required: A Bachelor’s Degree in Computer Science, Engineering, or related field. Master’s Degree preferred.
- Experience Required: Minimum experience required of the position. 8-10 years’ experience in software engineering, software development, or related field.
- Preferred Experience: Experience working with cloud-based platforms such as AWS, GCP.
Engineer Senior (maybe "Senior"):
- Minimum Education Required: A Bachelor’s Degree in Computer Science, Engineering, or related field. Master’s Degree preferred.
- Minimum Experience Required: 6-8 years’ experience in software engineering, software development, or related field.
- Preferred Experience: Experience working with cloud-based platforms such as AWS, GCP, or Azure. 2+ years’ experience working in the electric or gas utility sector.
Engineer III:
- Minimum Education Required: A Bachelor’s Degree in Computer Science, Engineering, or related field.
- Minimum Experience Required: 4-6 years’ experience in software engineering, software development, or related field.
- Preferred Experience: Experience working with cloud-based platforms such as AWS, GCP , or Azure. 2+ years’ experience working in the electric or gas utility sector.
Technical Capabilities:
- Mastery in one or more programming languages.
- Mastery in version control systems and repository hosting systems, e.g., Git and GitHub.
- Strong understanding of the software development lifecycle.
General Capabilities:
- Excellent written, verbal and presentation skills
- Succeed in a fast paced / highly demanding environment.
Skills And Abilities Required Of The Position:
- Functional Knowledge: Strong knowledge of utility and power generation operating models. Understands key business drivers; uses this understanding to accomplish own work. Ability to foster creative and innovative culture.
- Leadership: Demonstrated ability to provide guidance to junior team members. Willingness and experience to teach and mentor others in software engineering and software development.
- Problem Solving: Strong analytical and problem-solving skills. Demonstrated skills in selecting the right technology stack and engineering methodologies to address business requirements effectively and efficiently.
- Impact: Must be self-motivated, have high integrity and credibility and be able to work independently. Must be flexible and have ability to interface with a diverse group of individuals, cross-functional teams and manage multiple projects.
- Interpersonal Skills: Strong interpersonal and communication skills at all levels of the organization, both internally and externally. Excellent report writing and presentation skills. Ability to foster creative and innovative culture.
Minimum Knowledge, Skills And Abilities Required Of The Position:
- Proficiency in software development languages and frameworks, e.g. Python, JavaScript, React, along with a solid understanding of software design patterns, data structures, and algorithms.
Also location: Primary Location: Louisiana-New Orleans Louisiana : New Orleans || Arkansas : Little Rock || Mississippi : Jackson || Texas : The Woodlands
Job Function: Corporate FLSA Status: Professional Relocation Option: Union description/code: NON BARGAINING UNIT Number of Openings: 1 Req ID: 124988 PS Job Title: AI Software Engineer Sr Staff Travel Percentage:Up to 25%
We need to decide what to keep. Location is substantive. Could be included in About the role paragraph or a separate section? Since we only have defined headings, maybe we add a Location
but not in examples. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive. So we could add Location heading if we want. However they say "Prefer a few substantive sections over many thin ones." Adding Location might be thin but it's specific. Could incorporate location into About the role.
We also have Job Function, FLSA Status, Relocation Option, Union description/code, Number of Openings, Req ID, Travel Percentage. Those are metadata; we should drop minor metadata per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could fold some like Job Function, FLSA Status, Relocation Option, Travel Percentage into a short paragraph under About the role or maybe a separate "Details" paragraph. But they said fold minor metadata into a short
or drop it. So we can include a short paragraph with those details.
We must not repeat job title as heading. Already not.
We must not include boilerplate like EEO etc. Remove.
Thus final HTML:
About the role
[job summary] Additionally, the role is based primarily in New Orleans, LA or The Woodlands, TX, with other locations within the service territory considered. Job function: Corporate; FLSA status: Professional; relocation option available; union description: non‑bargaining unit; travel up to 25%.
Responsibilities
... list items
Requirements
... list items covering all requirements
We need to ensure we don't lose any detail. Let's craft bullet points for Requirements, grouping by level maybe.
We'll include:
- Senior Lead:
- Education: Bachelor’s Degree in Computer Science, Engineering, or related field; Master’s Degree preferred.
- Experience: 8‑10 years in software engineering/development or related field.
- Preferred: Experience with cloud platforms (AWS, GCP).
- Senior:
- Education: Bachelor’s Degree in Computer Science, Engineering, or related field; Master’s Degree preferred.
- Experience: 6‑8 years in software engineering/development or related field.
- Preferred: Experience with AWS, GCP, or Azure; 2+ years in electric or gas utility sector.
- Engineer III:
- Education: Bachelor’s Degree in Computer Science, Engineering, or related field.
- Experience: 4‑6 years in software engineering/development or related field.
- Preferred: Experience with AWS, GCP, or Azure; 2+ years in electric or gas utility sector.
- Technical Capabilities:
- Mastery in one or more programming languages.
- Mastery in version control systems (e.g., Git, GitHub).
- Strong understanding of the software development lifecycle.
- General Capabilities:
- Excellent written, verbal, and presentation skills.
- Ability to succeed in a fast‑paced, highly demanding environment.
- Skills and Abilities:
- Functional Knowledge: Strong knowledge of utility and power generation operating models; understands key business drivers and applies this understanding; ability to foster creative and innovative culture.
- Leadership: Demonstrated ability to guide junior members; willingness and experience to teach and mentor others.
- Problem Solving: Strong analytical and problem‑solving skills; ability to select appropriate technology stack and engineering methodologies.
- Impact: Self‑motivated, high integrity and credibility; able to work independently; flexible; able to interface with diverse individuals and cross‑functional teams; manage multiple projects.
- Interpersonal Skills: Strong interpersonal and communication skills at all levels; excellent report writing and presentation skills; ability to foster creative and innovative culture.
- Minimum Knowledge, Skills and Abilities:
- Proficiency in software development languages and frameworks (e.g., Python, JavaScript, React); solid understanding of
for prose. We must not repeat job title as heading. Do not put Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from job summary, duties, requirements (including education, experience, preferred experience, technical capabilities, general capabilities, skills and abilities, minimum knowledge, skills and abilities). Also location info? The posting includes location preferences. Should we include location? It's substantive. Could be part of About the role or maybe a separate section? There's no explicit heading for location, but we can include it in a paragraph under About the role or maybe a separate "Location" section? The instruction: include a section ONLY when the posting has real, specific content for it. There's location info, but no heading like "Location". We could create a section like "Location" if we have content. However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive. It says use those headings for section headings. Likely we should stick to those headings. So location could be part of About the role paragraph.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove duplicated lines. The posting repeats some sections for each level. We need to consolidate? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot omit details like specific years for each level. We could keep them as separate bullet points under Requirements, maybe grouped by level. That's preserving detail.
Thus we will create:
About the role
Job summary/purpose paragraph.
Responsibilities
- ... each duty
Requirements
Maybe break into subheadings? But we only allowed h3 for section headings. Could we have nested? Probably not. We could just list all requirements as bullet points, preserving details for each level. We need to include education, experience, preferred experience, technical capabilities, general capabilities, skills and abilities, minimum knowledge, skills and abilities. We'll create bullet points under Requirements. We must not include fluff like "N/A". Not present. Let's extract content. Job Summary/Purpose: "As a core member of the AI team, the software engineer is responsible for designing, building, and maintaining scalable, reliable and maintainable software systems. These systems often power AI-enabled applications, ranging from internal tools to customer-facing platforms. The engineer works across the full development lifecycle-from architecture and coding to deployment and support-ensuring that software products meet high standards of performance, usability, and security. While many solutions incorporate AI technologies, the focus is on delivery robust, well-engineered applications that integrate with business workflows. These tools are designed to help users solve real-world problems more efficiently, enabling smarter decisions and more streamlined operations across the organization." That's the prose. Job Duties/Responsibilities list: - Design, develop, and implement software solutions on system design specifications. - Collaborate with cross-functional teams to define, design, and ship new features. - Refine and optimize data and machine learning algorithms into production environments. - Ensure scalability, efficiency, and maintainability of the codebase. - Ensure the performance, quality, and responsiveness of applications. - Identify, correct, and improve inefficient code. - Participate in code reviews to maintain code quality. - Document software development and monitor systems to ensure they meet both user needs and business goals. - Stay updated on new technologies and best practices in software engineering. Now Requirements: There are multiple levels: Senior Lead, Senior, Engineer III. Also there is "Minimum Knowledge, Skills And Abilities Required Of The Position" etc. We need to preserve all. Let's extract each: Senior Lead: - Minimum Education Required: A Bachelor’s Degree in Computer Science, Engineering, or related field. Master’s Degree preferred. - Experience Required: Minimum experience required of the position. 8-10 years’ experience in software engineering, software development, or related field. - Preferred Experience: Experience working with cloud-based platforms such as AWS, GCP. Engineer Senior (maybe "Senior"): - Minimum Education Required: A Bachelor’s Degree in Computer Science, Engineering, or related field. Master’s Degree preferred. - Minimum Experience Required: 6-8 years’ experience in software engineering, software development, or related field. - Preferred Experience: Experience working with cloud-based platforms such as AWS, GCP, or Azure. 2+ years’ experience working in the electric or gas utility sector. Engineer III: - Minimum Education Required: A Bachelor’s Degree in Computer Science, Engineering, or related field. - Minimum Experience Required: 4-6 years’ experience in software engineering, software development, or related field. - Preferred Experience: Experience working with cloud-based platforms such as AWS, GCP , or Azure. 2+ years’ experience working in the electric or gas utility sector. Technical Capabilities: - Mastery in one or more programming languages. - Mastery in version control systems and repository hosting systems, e.g., Git and GitHub. - Strong understanding of the software development lifecycle. General Capabilities: - Excellent written, verbal and presentation skills - Succeed in a fast paced / highly demanding environment. Skills And Abilities Required Of The Position: - Functional Knowledge: Strong knowledge of utility and power generation operating models. Understands key business drivers; uses this understanding to accomplish own work. Ability to foster creative and innovative culture. - Leadership: Demonstrated ability to provide guidance to junior team members. Willingness and experience to teach and mentor others in software engineering and software development. - Problem Solving: Strong analytical and problem-solving skills. Demonstrated skills in selecting the right technology stack and engineering methodologies to address business requirements effectively and efficiently. - Impact: Must be self-motivated, have high integrity and credibility and be able to work independently. Must be flexible and have ability to interface with a diverse group of individuals, cross-functional teams and manage multiple projects. - Interpersonal Skills: Strong interpersonal and communication skills at all levels of the organization, both internally and externally. Excellent report writing and presentation skills. Ability to foster creative and innovative culture. Minimum Knowledge, Skills And Abilities Required Of The Position: - Proficiency in software development languages and frameworks, e.g. Python, JavaScript, React, along with a solid understanding of software design patterns, data structures, and algorithms. Also location: Primary Location: Louisiana-New Orleans Louisiana : New Orleans || Arkansas : Little Rock || Mississippi : Jackson || Texas : The Woodlands Job Function: Corporate FLSA Status: Professional Relocation Option: Union description/code: NON BARGAINING UNIT Number of Openings: 1 Req ID: 124988 PS Job Title: AI Software Engineer Sr Staff Travel Percentage:Up to 25% We need to decide what to keep. Location is substantive. Could be included in About the role paragraph or a separate section? Since we only have defined headings, maybe we add aLocation
but not in examples. The instruction: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive. So we could add Location heading if we want. However they say "Prefer a few substantive sections over many thin ones." Adding Location might be thin but it's specific. Could incorporate location into About the role. We also have Job Function, FLSA Status, Relocation Option, Union description/code, Number of Openings, Req ID, Travel Percentage. Those are metadata; we should drop minor metadata per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could fold some like Job Function, FLSA Status, Relocation Option, Travel Percentage into a short paragraph under About the role or maybe a separate "Details" paragraph. But they said fold minor metadata into a short
or drop it. So we can include a short paragraph with those details. We must not repeat job title as heading. Already not. We must not include boilerplate like EEO etc. Remove. Thus final HTML:
About the role
[job summary] Additionally, the role is based primarily in New Orleans, LA or The Woodlands, TX, with other locations within the service territory considered. Job function: Corporate; FLSA status: Professional; relocation option available; union description: non‑bargaining unit; travel up to 25%.
Responsibilities
- ... list items