IT Associate Software Engineer (Hybrid)
NSTAR, now Eversource Energy- Follow our new company page, Eversource Energy · Berlin, NH · 3 wk ago
Hybrid$82k–$91k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We need to extract content from the job description.
Let's parse the job description.
Key info:
- Title: IT Associate Software Engineer (Hybrid) (but we do not repeat as heading)
- Locations: East Berlin, Connecticut; Westwood, Massachusetts; Manchester, New Hampshire
- Date: 09/28/2026 (maybe not needed)
- Visa sponsorship: none.
- Hybrid schedule: eligibility based on job responsibilities, operational needs, nature of work and team dynamics. Current guidelines require employees to work at least three days in the office, including Tuesdays and Wednesdays, with third day set by employee and supervisor based on department needs. Must be able to work up to five days in office if needed.
- Role description: Associate Software Engineer will work as part of a team to complete basic end to end software engineering tasks. Perform basic analysis, development, testing, debugging, configuration, incident investigation, documentation, health monitoring/alerting, and implementing based on and related to user or system design specifications. Work within guidelines set by team to independently tackle well-scoped problems. Seek opportunities to expand technical knowledge and capabilities.
- Essential Functions: list of bullet-like sentences (some run together). We need to extract list items.
Essential Functions text: "Works with direct supervision on projects / assignments. Sets objectives for own area of responsibility to meet the objectives or goals of projects and assignments.Develops and configures customizations and configurations of various Engineering Operations systemsWorks with managed service provider teams to prioritize and execute backlog assignmentsProblems and issues faced are general and may require understanding of broader set of issues.Problems may span a range of issues or work areas and are typically solved through exercise of discretion and / or judgment, drawing from prior experiences, with analysis of the issueResponsible for making minor changes or enhancements in systems and processes to solve problems or improve effectiveness of work area.Communicates with parties within and outside of own team.Explains policies, practices, and procedures of the work area to others within the organization, influencing decision- makers with recommended courses of action."
We need to split into list items. Likely each sentence separated by period. Let's break:
1. Works with direct supervision on projects / assignments.
2. Sets objectives for own area of responsibility to meet the objectives or goals of projects and assignments.
3. Develops and configures customizations and configurations of various Engineering Operations systems.
4. Works with managed service provider teams to prioritize and execute backlog assignments.
5. Problems and issues faced are general and may require understanding of broader set of issues.
6. Problems may span a range of issues or work areas and are typically solved through exercise of discretion and / or judgment, drawing from prior experiences, with analysis of the issue.
7. Responsible for making minor changes or enhancements in systems and processes to solve problems or improve effectiveness of work area.
8. Communicates with parties within and outside of own team.
9. Explains policies, practices, and procedures of the work area to others within the organization, influencing decision- makers with recommended courses of action.
We'll keep these as
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We need to extract content from the job description.
Let's parse the job description.
Key info:
- Title: IT Associate Software Engineer (Hybrid) (but we do not repeat as heading)
- Locations: East Berlin, Connecticut; Westwood, Massachusetts; Manchester, New Hampshire
- Date: 09/28/2026 (maybe not needed)
- Visa sponsorship: none.
- Hybrid schedule: eligibility based on job responsibilities, operational needs, nature of work and team dynamics. Current guidelines require employees to work at least three days in the office, including Tuesdays and Wednesdays, with third day set by employee and supervisor based on department needs. Must be able to work up to five days in office if needed.
- Role description: Associate Software Engineer will work as part of a team to complete basic end to end software engineering tasks. Perform basic analysis, development, testing, debugging, configuration, incident investigation, documentation, health monitoring/alerting, and implementing based on and related to user or system design specifications. Work within guidelines set by team to independently tackle well-scoped problems. Seek opportunities to expand technical knowledge and capabilities.
- Essential Functions: list of bullet-like sentences (some run together). We need to extract list items.
Essential Functions text: "Works with direct supervision on projects / assignments. Sets objectives for own area of responsibility to meet the objectives or goals of projects and assignments.Develops and configures customizations and configurations of various Engineering Operations systemsWorks with managed service provider teams to prioritize and execute backlog assignmentsProblems and issues faced are general and may require understanding of broader set of issues.Problems may span a range of issues or work areas and are typically solved through exercise of discretion and / or judgment, drawing from prior experiences, with analysis of the issueResponsible for making minor changes or enhancements in systems and processes to solve problems or improve effectiveness of work area.Communicates with parties within and outside of own team.Explains policies, practices, and procedures of the work area to others within the organization, influencing decision- makers with recommended courses of action."
We need to split into list items. Likely each sentence separated by period. Let's break:
1. Works with direct supervision on projects / assignments.
2. Sets objectives for own area of responsibility to meet the objectives or goals of projects and assignments.
3. Develops and configures customizations and configurations of various Engineering Operations systems.
4. Works with managed service provider teams to prioritize and execute backlog assignments.
5. Problems and issues faced are general and may require understanding of broader set of issues.
6. Problems may span a range of issues or work areas and are typically solved through exercise of discretion and / or judgment, drawing from prior experiences, with analysis of the issue.
7. Responsible for making minor changes or enhancements in systems and processes to solve problems or improve effectiveness of work area.
8. Communicates with parties within and outside of own team.
9. Explains policies, practices, and procedures of the work area to others within the organization, influencing decision- makers with recommended courses of action.
We'll keep these as - .
Technical Knowledge/Skill/Education/Licenses/Certifications: includes bullet points.
Technical Knowledge/Skill list:
- Effectively uses code version control systems such as git
- Understands basic programming and OOP concepts (languages may include Python, JSON, C++)
- Understands core application development patterns
- Experienced using data structures
- Familiar with traditional data stores
- Familiar with REST API syntax and tools for documenting and testing the REST APIs such as Postman
- Familiar with Agile methodology
- Theoretical knowledge of work area
- Ability to work autonomously with limited supervision
- Displays strong work ethic
- Understands direction provided and implements assigned tasks effectively
- Displays Project/team level impact
- Troubleshoots simple engineering problems by checking logs, using developer tools and debugger effectively
- Able to use existing knowledge of algorithms, structures and patterns to design and implement solutions of light to moderate complexity.
- Objectively evaluates whether they've met their goals.
- Communicates effectively during meetings
- Completes work or raises roadblocks in a timely manner
- Open to change and learning new skills to get work done
- Accepts feedback graciously and learns from experience.
- Shows respect towards other team members
Education: Bachelor’s Degree or equivalent experience
Experience: Minimum of 0 to 3 years of relevant experience
Licenses & Certifications: N/A (we should not include a section if content is N/A or placeholder. So we skip Licenses & Certifications.)
Working Conditions: Must be available to work emergency restoration assignment as required. Must be available to travel between MA/CT/NH as necessary.
Compensation And Benefits: Eversource offers a competitive total rewards program. Check out our careers site for an overview of our benefits programs. Salary is commensurate with your experience. This position is eligible for a potential incentive. The annual salary range for this position is: $82,300.00-$91,440.00
We have Pay and Benefits content. The instruction: include Pay/Schedule/Benefits sections only if posting actually states them. It does state salary range and benefits mention. So we can include a Pay section (maybe combine with Benefits?). They said prefer few substantive sections over many thin ones. Could combine Pay and Benefits into one section? But headings are predefined: Benefits, Pay, Schedule. We could have Pay and Benefits separate if content exists. However we have both pay and benefits info. Benefits: "Eversource offers a competitive total rewards program. Check out our careers site for an overview of our benefits programs." Pay: salary range and potential incentive. So we could have two sections:
Pay
with salary range and incentive; Benefits
with description of total rewards program.
Schedule: we have hybrid schedule guidelines. So we can include Schedule section.
Also we might have About the role section: maybe a brief summary. The description includes role overview. Could put that under About the role.
Responsibilities: could be Essential Functions.
Requirements/Qualifications/Skills: we have Technical Knowledge/Skill, Education, Experience. Could combine into Requirements or Qualifications. Since we have many, we could make a Requirements section that includes Education, Experience, Technical Skills. Or separate Qualifications and Skills. But we should avoid many thin sections. Perhaps combine into one Requirements section that includes Education, Experience, Technical Skills. Or we could have Qualifications (Education + Experience) and Skills (Technical Knowledge). Let's see.
We need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must only include sections when posting has real specific content. So we need to decide which sections to include.
We have content for About the role (role overview). Responsibilities (Essential Functions). Requirements (maybe Education + Experience). Qualifications (maybe same as Requirements? Could be redundant). Skills (Technical Knowledge). Benefits, Pay, Schedule.
We could include all of them, but ensure each has substantive content.
Let's extract content for each.
About the role: a paragraph summarizing the role: "The Associate Software Engineer will work as part of a team to complete basic end to end software engineering tasks. The engineer will perform basic analysis, development, testing, debugging, configuration, incident investigation, documentation, health monitoring/alerting, and implementing based on and related to user or system design specifications. Work within guidelines set by team to independently tackle well-scoped problems. Seek opportunities to expand technical knowledge and capabilities."
Responsibilities: the Essential Functions list.
Requirements: maybe Education and Experience. Education: Bachelor’s Degree or equivalent experience. Experience: Minimum of 0 to 3 years of relevant experience.
Qualifications: maybe same as Requirements? Could be "Theoretical to advanced knowledge of work area typically obtained through University Degree combined with experience." But that's vague. Might be better to skip Qualifications if it's redundant. However we need to avoid filler. If we include Qualifications, we need substantive content. Could combine Education and Experience into Qualifications. But then Requirements could be something else? Hmm.
Alternatively, we could treat Requirements as Education+Experience, Qualifications as Technical Knowledge/Skill, Skills as maybe same? But we already have Skills heading for technical knowledge. Let's map:
- Requirements: Education and Experience.
- Qualifications: maybe "Theoretical to advanced knowledge of work area typically obtained through University Degree combined with experience." That's a sentence from the description: "Requires theoretical to advanced knowledge of work area typically obtained through University Degree combined with experience." That's substantive enough.
- Skills: Technical Knowledge/Skill list.
Thus we have three sections: Requirements, Qualifications, Skills.
Check if any content is placeholder like "N/A". We skip Licenses & Certifications.
Now Benefits: we have description.
Pay: salary range and potential incentive.
Schedule: hybrid schedule details.
Now we need to output HTML fragment only, no extra markup.
Let's craft.
We'll need to escape any HTML special characters? Not needed.
We'll produce:
About the role
...
Responsibilities
- ...
...
Requirements
- Bachelor’s Degree or equivalent experience
- Minimum of 0 to 3 years of relevant experience
Qualifications
Requires theoretical to advanced knowledge of work area typically obtained through University Degree combined with experience.
Skills
- Effectively uses code version control systems such as git
- Understands basic programming and OOP concepts (languages may include Python, JSON, C++)
- Understands core application development patterns
- Experienced using data structures
- Familiar with traditional data stores
- Familiar with REST API syntax and tools for documenting and testing the REST APIs such as Postman
- Familiar with Agile methodology
- Theoretical knowledge of work area
- Ability to work autonomously with limited supervision
- Displays strong work ethic
- Understands direction provided and implements assigned tasks effectively
- Displays Project/team level impact
- Troubleshoots simple engineering problems by checking logs, using developer tools and debugger effectively
- Able to use existing knowledge of algorithms, structures and patterns to design and implement solutions of light to moderate complexity.
- Objectively evaluates whether they've met their goals.
- Communicates effectively during meetings
- Completes work or raises roadblocks in a timely manner
- Open to change and learning new skills to get work done
- Accepts feedback graciously and learns from experience.
- Shows respect towards other team members
Benefits
Eversource offers a competitive total rewards program. Check out our careers site for an overview of our benefits programs.
Pay
The annual salary range for this position is: $82,300.00‑$91,440.00. This position is eligible for a potential incentive.
Schedule
Eligibility for hybrid schedule is based on job responsibilities, operational needs, nature of work and team dynamics. Current guidelines require employees to work at least three days in the office, including Tuesdays and Wednesdays, with the third day set by the employee and supervisor based on department needs. Employees must be able to work up to five days in the office if needed (for example: emergencies, training, or other business needs) or should
Pay
with salary range and incentive;Benefits
with description of total rewards program. Schedule: we have hybrid schedule guidelines. So we can include Schedule section. Also we might have About the role section: maybe a brief summary. The description includes role overview. Could put that under About the role. Responsibilities: could be Essential Functions. Requirements/Qualifications/Skills: we have Technical Knowledge/Skill, Education, Experience. Could combine into Requirements or Qualifications. Since we have many, we could make a Requirements section that includes Education, Experience, Technical Skills. Or separate Qualifications and Skills. But we should avoid many thin sections. Perhaps combine into one Requirements section that includes Education, Experience, Technical Skills. Or we could have Qualifications (Education + Experience) and Skills (Technical Knowledge). Let's see. We need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. So we need to decide which sections to include. We have content for About the role (role overview). Responsibilities (Essential Functions). Requirements (maybe Education + Experience). Qualifications (maybe same as Requirements? Could be redundant). Skills (Technical Knowledge). Benefits, Pay, Schedule. We could include all of them, but ensure each has substantive content. Let's extract content for each. About the role: a paragraph summarizing the role: "The Associate Software Engineer will work as part of a team to complete basic end to end software engineering tasks. The engineer will perform basic analysis, development, testing, debugging, configuration, incident investigation, documentation, health monitoring/alerting, and implementing based on and related to user or system design specifications. Work within guidelines set by team to independently tackle well-scoped problems. Seek opportunities to expand technical knowledge and capabilities." Responsibilities: the Essential Functions list. Requirements: maybe Education and Experience. Education: Bachelor’s Degree or equivalent experience. Experience: Minimum of 0 to 3 years of relevant experience. Qualifications: maybe same as Requirements? Could be "Theoretical to advanced knowledge of work area typically obtained through University Degree combined with experience." But that's vague. Might be better to skip Qualifications if it's redundant. However we need to avoid filler. If we include Qualifications, we need substantive content. Could combine Education and Experience into Qualifications. But then Requirements could be something else? Hmm. Alternatively, we could treat Requirements as Education+Experience, Qualifications as Technical Knowledge/Skill, Skills as maybe same? But we already have Skills heading for technical knowledge. Let's map: - Requirements: Education and Experience. - Qualifications: maybe "Theoretical to advanced knowledge of work area typically obtained through University Degree combined with experience." That's a sentence from the description: "Requires theoretical to advanced knowledge of work area typically obtained through University Degree combined with experience." That's substantive enough. - Skills: Technical Knowledge/Skill list. Thus we have three sections: Requirements, Qualifications, Skills. Check if any content is placeholder like "N/A". We skip Licenses & Certifications. Now Benefits: we have description. Pay: salary range and potential incentive. Schedule: hybrid schedule details. Now we need to output HTML fragment only, no extra markup. Let's craft. We'll need to escape any HTML special characters? Not needed. We'll produce:About the role
...
Responsibilities
- ... ...
Requirements
- Bachelor’s Degree or equivalent experience
- Minimum of 0 to 3 years of relevant experience
Qualifications
Requires theoretical to advanced knowledge of work area typically obtained through University Degree combined with experience.
Skills
- Effectively uses code version control systems such as git
- Understands basic programming and OOP concepts (languages may include Python, JSON, C++)
- Understands core application development patterns
- Experienced using data structures
- Familiar with traditional data stores
- Familiar with REST API syntax and tools for documenting and testing the REST APIs such as Postman
- Familiar with Agile methodology
- Theoretical knowledge of work area
- Ability to work autonomously with limited supervision
- Displays strong work ethic
- Understands direction provided and implements assigned tasks effectively
- Displays Project/team level impact
- Troubleshoots simple engineering problems by checking logs, using developer tools and debugger effectively
- Able to use existing knowledge of algorithms, structures and patterns to design and implement solutions of light to moderate complexity.
- Objectively evaluates whether they've met their goals.
- Communicates effectively during meetings
- Completes work or raises roadblocks in a timely manner
- Open to change and learning new skills to get work done
- Accepts feedback graciously and learns from experience.
- Shows respect towards other team members
Benefits
Eversource offers a competitive total rewards program. Check out our careers site for an overview of our benefits programs.
Pay
The annual salary range for this position is: $82,300.00‑$91,440.00. This position is eligible for a potential incentive.
Schedule
Eligibility for hybrid schedule is based on job responsibilities, operational needs, nature of work and team dynamics. Current guidelines require employees to work at least three days in the office, including Tuesdays and Wednesdays, with the third day set by the employee and supervisor based on department needs. Employees must be able to work up to five days in the office if needed (for example: emergencies, training, or other business needs) or should