Analyst II, End User
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading (the page already shows it). Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the job posting.
Key sections:
- Job Summary: description of role. Could be "About the role" heading.
- Education Minimum Requirement: could be under "Requirements" or "Qualifications". We have Education Minimum Requirement and Preferred Bachelor's degree etc.
- Major Responsibilities: list of duties.
- Preferred Qualifications: list.
- Knowledge, Skills And Abilities: list.
- Behavioral Attributes: list.
- Physical Requirements: list.
- Other Requirements: list (NERC background check, driver's license, transportation).
- About Southern Company: description of company.
- Benefits: mention of benefits link.
- Pay: not specified (no salary). So we should NOT create Pay section.
- Schedule: mentions "Job Schedule: Full time". That's specific content. So we can have Schedule section with that.
- Job Identification etc: minor metadata (Job ID, Job Category, Company). Should fold into short
or drop. Probably include a short
with Job ID, Category, Company.
We must not repeat job title as heading. So we will not have heading for "Technology Organization End User Analyst". We'll start with maybe
About the role
with summary.
We need to preserve all substantive info. So we need to include details from summary, responsibilities, etc.
We must use - for any list of duties/requirements/benefits. For prose, use
. For sections like Knowledge, Skills And Abilities we can treat as list.
We must not create sections with filler like "commensurate with experience". Not present.
We need to decide which sections to include: About the role, Responsibilities, Requirements (maybe combine Education and Preferred Qualifications?), Skills (Knowledge, Skills And Abilities), Behavioral Attributes maybe part of Skills or separate? Could combine into Skills section. Physical Requirements maybe its own section? Could be under Requirements? But we have to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to use. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to use all. We should include sections only when posting has real specific content.
Thus we can have:
- About the role (summary)
- Responsibilities (Major Responsibilities)
- Requirements (Education Minimum Requirement)
- Qualifications (Preferred Qualifications)
- Skills (Knowledge, Skills And Abilities + Behavioral Attributes maybe)
- Benefits (mention of benefits link)
- Schedule (Job Schedule: Full time)
We could also include Physical Requirements under Requirements or maybe as its own but not in list; but we could incorporate into Requirements as a list item.
Other Requirements (NERC, driver's license) could be under Requirements as well.
We need to preserve all substantive info, so we must include those details somewhere.
We must not repeat job title as heading.
We must not include Job ID etc as headings; we can put them in a short
maybe after the sections or before.
We must remove boilerplate like EEO, etc. The posting includes "Southern Company is an equal opportunity employer..." which we must remove.
Also remove "Lastly, this position description does not state or imply that the above are the only responsibilities and responsibilities assigned to this position." That's boilerplate; remove.
Also remove "About Southern Company" maybe we can keep as part of About the role? But it's about company, not role. Could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About Southern Company is substantive info about company. Should we keep? It's not about the role but it's part of posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it, maybe under a section like "About the company" but not in the given headings list. However we can incorporate into About the role? Might be okay to add a section "About Southern Company" but not in the list of allowed headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings; we could put company info under About the role? Might be stretching. But we could include a brief paragraph about company within About the role section? Might be considered summarizing away detail? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we merge company info into About the role, we are not summarizing away; we are just including it. That's okay.
Thus About the role section can contain both the role summary and company description.
Now we need to format lists.
Let's extract content.
Job Summary paragraph:
"The End User Analyst within Workplace Support (WPS) is responsible for delivering high-quality, efficient, and proactive end-user technology support across desktop, hardware, and conferencing environments. This role focuses on improving business partners (BPs) digital experience through proactive monitoring, automation, standardization, and customer-centric service delivery. The End User Analyst partners with multiple Technology Organization (TO) departments and business stakeholders to reduce incidents, improve resolution times, and enable scalable, self-service support models. This role also plays a key part in supporting enterprise initiatives including end user and conference room technology refresh programs, storm restorations, and major events. This position is located at 3610 Gentian Blvd, Columbus, Ga and supports sites in east Alabama and West Georgia."
We'll put that in
under About the role.
Education Minimum Requirement:
"Education Minimum Requirement Associate degree in a technology-related field, or equivalent military or relevant work experience. Preferred Bachelor’s degree in computer science, Information Technology, Engineering, or a related technical discipline with minimum of 3 years related experience."
We'll put under Requirements as list items? Could be two items: Associate degree...; Preferred Bachelor's degree...
But we also have Preferred Qualifications separate.
Better: Requirements: Education Minimum Requirement (Associate degree...). Qualifications: Preferred Bachelor’s degree... plus Preferred Qualifications list.
But we have both Education Minimum Requirement and Preferred Bachelor's degree (which is also a qualification). We'll treat Education Minimum Requirement as Requirements, and Preferred Bachelor's degree as Qualifications (maybe also part of Preferred Qualifications). However the Preferred Qualifications list includes experience with tools etc. So we can separate.
Thus:
Requirements
- Associate degree in a technology-related field, or equivalent military or relevant work experience.
Qualifications
- Bachelor’s degree in computer science, Information Technology, Engineering, or a related technical discipline with minimum of 3 years related experience.
Then Preferred Qualifications list:
"Experience with Digital Experience Monitoring tools (e.g., Nexthink or similar)
Experience with automation, scripting, or workflow design
Experience with Co-Pilot and Co-Pilot Agents
Experience with Microsoft Power Platform – Power Automate, Power BI
Knowledge of ITIL practices including incident, problem, and change management
Experience supporting conference room technologies and AV environments"
We'll put under Qualifications as well? But we already used Qualifications for education. Could combine education and preferred qualifications under Qualifications? Might be messy. Better to have Requirements (education minimum) and Qualifications (preferred education + experience). But we have two sets: education preferred and experience preferred. Could combine.
Alternatively, we could have Requirements (education minimum) and Skills (knowledge, skills, abilities) and then have a separate section for Preferred Qualifications? Not in headings list. But we could put under Qualifications.
Thus Qualifications section will contain both the preferred education and the preferred qualifications list.
Let's do:
Qualifications
- Bachelor’s degree in computer science, Information Technology, Engineering, or a related technical discipline with minimum of 3 years related experience.
- Experience with Digital Experience Monitoring tools (e.g., Nexthink or similar)
- Experience with automation, scripting, or workflow design
- Experience with Co-Pilot and Co-Pilot Agents
- Experience with Microsoft Power Platform – Power Automate, Power BI
- Knowledge of ITIL practices including incident, problem, and change management
- Experience supporting conference room technologies and AV environments
Now Knowledge, Skills And Abilities list:
"Proficient technical knowledge of office computing environments including PC hardware, Microsoft Windows, Microsoft Office suite (i.e. Outlook, Word, Excel, PowerPoint, Teams, SharePoint) and infrastructure as well as their interaction and relevance in solving business problems.
Strong analytical and problem-solving skills
Customer-focused mindset with a commitment to service excellence
Ability to identify trends and drive continuous improvement
Collaboration across technical and business teams
Strong communication and documentation skills
Commitment to safety, inclusion, integrity, and performance excellence
Demonstrated ability to build strong relationships with BPs, vendors and other TO departments.
Ability to develop effective working relationships with all levels of employees.
Customer service focused with the ability to deliver on commitments and deadlines.
Demonstrated ability to share best practices within business units, across business units, and within Southern Company to maximize value and provide consistency in the TO operations for our BPs.
Ability to manage small, local projects using proven concepts to apply technology to business problems.
Experience supporting Microsoft Teams rooms or other video conferencing technology is desired."
We'll put under Skills.
Behavioral Attributes list:
"Demonstrates behaviors aligned with Southern Company’s Values: Safety First, Intentional Inclusion, Superior Performance, and Act with Integrity.
Shows initiative, stays motivated, and works independently.
Highly self-directed, proactive in identifying opportunities, and focused on achieving measurable outcomes.
Demonstrates strong organizational skills and a customer-focused mindset.
Manages multiple projects and tasks effectively at the same time.
Commits to continuous learning and training to keep up with new developments in hardware and software technologies.
Builds strong relationships with business partners and works effectively in a distributed team environment.
Follows established safety policies and procedures."
We could include these under Skills as well, or maybe under a separate section but not in headings list. Since we already have Skills, we can add them there.
Physical Requirements list:
"Routine physical agility to move in various positions to execute duties effectively, which may include kneeling, walking, pushing/pulling, squatting, twisting, turning, bending, stooping and reaching overhead; physical stamina sufficient to sustain light physical labor and ability to remain in stationary position for up to 8 hours.
Occasional lifting of objects more than 30 pounds and may require lifting 50 pounds with the assistance of another analyst.
Handling and/or transporting equipment and tools necessary for this position.
Physical mobility is sufficient to move about the work environment for sustained periods of time on concrete, hard flooring, stairs, ramps, carpet, etc.
Ability to access and maneuver in small and large company trucks"
We could put under Requirements maybe as a sublist? But we already have Requirements for education. Could add another list under Requirements for physical? Might be confusing. Better to have
for prose. Do NOT repeat job title as heading (the page already shows it). Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the job posting. Key sections: - Job Summary: description of role. Could be "About the role" heading. - Education Minimum Requirement: could be under "Requirements" or "Qualifications". We have Education Minimum Requirement and Preferred Bachelor's degree etc. - Major Responsibilities: list of duties. - Preferred Qualifications: list. - Knowledge, Skills And Abilities: list. - Behavioral Attributes: list. - Physical Requirements: list. - Other Requirements: list (NERC background check, driver's license, transportation). - About Southern Company: description of company. - Benefits: mention of benefits link. - Pay: not specified (no salary). So we should NOT create Pay section. - Schedule: mentions "Job Schedule: Full time". That's specific content. So we can have Schedule section with that. - Job Identification etc: minor metadata (Job ID, Job Category, Company). Should fold into short
or drop. Probably include a short
with Job ID, Category, Company. We must not repeat job title as heading. So we will not have heading for "Technology Organization End User Analyst". We'll start with maybe
About the role
with summary. We need to preserve all substantive info. So we need to include details from summary, responsibilities, etc. We must use- for any list of duties/requirements/benefits. For prose, use
. For sections like Knowledge, Skills And Abilities we can treat as list. We must not create sections with filler like "commensurate with experience". Not present. We need to decide which sections to include: About the role, Responsibilities, Requirements (maybe combine Education and Preferred Qualifications?), Skills (Knowledge, Skills And Abilities), Behavioral Attributes maybe part of Skills or separate? Could combine into Skills section. Physical Requirements maybe its own section? Could be under Requirements? But we have to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to use. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to use all. We should include sections only when posting has real specific content. Thus we can have: - About the role (summary) - Responsibilities (Major Responsibilities) - Requirements (Education Minimum Requirement) - Qualifications (Preferred Qualifications) - Skills (Knowledge, Skills And Abilities + Behavioral Attributes maybe) - Benefits (mention of benefits link) - Schedule (Job Schedule: Full time) We could also include Physical Requirements under Requirements or maybe as its own but not in list; but we could incorporate into Requirements as a list item. Other Requirements (NERC, driver's license) could be under Requirements as well. We need to preserve all substantive info, so we must include those details somewhere. We must not repeat job title as heading. We must not include Job ID etc as headings; we can put them in a short
maybe after the sections or before. We must remove boilerplate like EEO, etc. The posting includes "Southern Company is an equal opportunity employer..." which we must remove. Also remove "Lastly, this position description does not state or imply that the above are the only responsibilities and responsibilities assigned to this position." That's boilerplate; remove. Also remove "About Southern Company" maybe we can keep as part of About the role? But it's about company, not role. Could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About Southern Company is substantive info about company. Should we keep? It's not about the role but it's part of posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it, maybe under a section like "About the company" but not in the given headings list. However we can incorporate into About the role? Might be okay to add a section "About Southern Company" but not in the list of allowed headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings; we could put company info under About the role? Might be stretching. But we could include a brief paragraph about company within About the role section? Might be considered summarizing away detail? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we merge company info into About the role, we are not summarizing away; we are just including it. That's okay. Thus About the role section can contain both the role summary and company description. Now we need to format lists. Let's extract content. Job Summary paragraph: "The End User Analyst within Workplace Support (WPS) is responsible for delivering high-quality, efficient, and proactive end-user technology support across desktop, hardware, and conferencing environments. This role focuses on improving business partners (BPs) digital experience through proactive monitoring, automation, standardization, and customer-centric service delivery. The End User Analyst partners with multiple Technology Organization (TO) departments and business stakeholders to reduce incidents, improve resolution times, and enable scalable, self-service support models. This role also plays a key part in supporting enterprise initiatives including end user and conference room technology refresh programs, storm restorations, and major events. This position is located at 3610 Gentian Blvd, Columbus, Ga and supports sites in east Alabama and West Georgia." We'll put that in
under About the role. Education Minimum Requirement: "Education Minimum Requirement Associate degree in a technology-related field, or equivalent military or relevant work experience. Preferred Bachelor’s degree in computer science, Information Technology, Engineering, or a related technical discipline with minimum of 3 years related experience." We'll put under Requirements as list items? Could be two items: Associate degree...; Preferred Bachelor's degree... But we also have Preferred Qualifications separate. Better: Requirements: Education Minimum Requirement (Associate degree...). Qualifications: Preferred Bachelor’s degree... plus Preferred Qualifications list. But we have both Education Minimum Requirement and Preferred Bachelor's degree (which is also a qualification). We'll treat Education Minimum Requirement as Requirements, and Preferred Bachelor's degree as Qualifications (maybe also part of Preferred Qualifications). However the Preferred Qualifications list includes experience with tools etc. So we can separate. Thus:
Requirements
- Associate degree in a technology-related field, or equivalent military or relevant work experience.
Qualifications
- Bachelor’s degree in computer science, Information Technology, Engineering, or a related technical discipline with minimum of 3 years related experience.
Qualifications
- Bachelor’s degree in computer science, Information Technology, Engineering, or a related technical discipline with minimum of 3 years related experience.
- Experience with Digital Experience Monitoring tools (e.g., Nexthink or similar)
- Experience with automation, scripting, or workflow design
- Experience with Co-Pilot and Co-Pilot Agents
- Experience with Microsoft Power Platform – Power Automate, Power BI
- Knowledge of ITIL practices including incident, problem, and change management
- Experience supporting conference room technologies and AV environments