Senior Storage Analyst
Salt River Project · Tempe, AZ · 4 wk ago
Full-time
We need to output HTML fragment with sections: headings for each section that has content: About the role? Actually the posting includes "Why Work at SRP", "Benefits", "Summary", "What You'll Do", "Education", "Experience", "Additional Requirements And Qualifications", "Hybrid Workplace", "Drug/Alcohol Policy Statement", "Equal Opportunity Employer Statement", "Work Authorization". But we must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop Equal Opportunity Employer Statement, Drug/Alcohol Policy Statement, Work Authorization? Those are legal boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should drop those sections. Also "Hybrid Workplace" is not boilerplate; it's a benefit/condition, we can keep as a section maybe under Benefits or separate. The instruction: include a section ONLY when posting has real, specific content for it. Hybrid Workplace has content: "SRP currently offers a hybrid workplace, which allows employees whose jobs can be performed remotely, and who have sufficient technical capability, to telework up to three days per week. Although teleworking is available, all employees must live and work in Arizona." That's specific, so we can include a section maybe "Hybrid Workplace". However the allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but not exclusive? The instruction: "use
for each section that has content: About the role? Actually the posting includes "Why Work at SRP", "Benefits", "Summary", "What You'll Do", "Education", "Experience", "Additional Requirements And Qualifications", "Hybrid Workplace", "Drug/Alcohol Policy Statement", "Equal Opportunity Employer Statement", "Work Authorization". But we must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop Equal Opportunity Employer Statement, Drug/Alcohol Policy Statement, Work Authorization? Those are legal boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should drop those sections. Also "Hybrid Workplace" is not boilerplate; it's a benefit/condition, we can keep as a section maybe under Benefits or separate. The instruction: include a section ONLY when posting has real, specific content for it. Hybrid Workplace has content: "SRP currently offers a hybrid workplace, which allows employees whose jobs can be performed remotely, and who have sufficient technical capability, to telework up to three days per week. Although teleworking is available, all employees must live and work in Arizona." That's specific, so we can include a section maybe "Hybrid Workplace". However the allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but not exclusive? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings where appropriate, but we can also use other headings? It says "use for section headings (e.g. ...)" meaning those are examples; we can use other headings if needed? Probably they want us to map content to those standard headings. But we have content like "Why Work at SRP" which could be "About the role". "Benefits" is a heading. "Summary" maybe "About the role". "What You'll Do" is Responsibilities. "Education" and "Experience" could be Qualifications/Requirements. "Additional Requirements And Qualifications" could be Requirements. "Hybrid Workplace" maybe Benefits or Schedule? It's about work arrangement, could be Schedule? But schedule is about hours/shift. Hybrid workplace is more about remote work; could be under Benefits or a separate section like "Work Arrangement". Since not in list, maybe we incorporate into Benefits or Schedule? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Hybrid Workplace into Benefits or maybe into a "Work Arrangement" but not in list. Safer to incorporate into Benefits as an extra bullet.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information; do not invent or summarize away detail.
We need to output only HTML fragment.
Let's extract substantive content:
- Intro: "Join us in building a better future for Arizona! SRP is one of the largest public power and water utilities in the U.S. providing electricity to approximately one million customers in the greater metropolitan Phoenix area. Since its founding in 1903, SRP has fostered a culture of stewardship and customer service consistently ranking as an industry leader in customer service according to J.D. Power and named one of Arizona's best employers by Forbes. SRP continues to adapt to its changing business environment by seeking innovative ways to reimagine utility service and the provision of critical resources essential to the life and economy of Arizona."
That's about the company; could be "About the role" or maybe a brief intro. We'll put under About the role
with a paragraph.
- "Why Work at SRP At SRP, we foster an inclusive work environment and believe everyone should have a fair chance to work, regardless of who they are. That’s why we value teams with diverse perspectives, experiences, and backgrounds to help SRP deliver on its mission of providing reliable, affordable and sustainable water and power."
That's also about culture; could be part of About the role. We'll combine.
- Benefits section: list of benefits.
We need to format as - for list.
Benefits content:
"Pension Plan (at no cost to the employee)
401(k) plan with employer matching
Available your first day: Medical, vision, dental, and life insurance
Over 200+ hours of PTO (includes vacation days, holidays, floating holidays, and sick leave)
Parental leave (up to 4 weeks) and adoption assistance
Wellness programs (including access to a recreation and fitness facility)
Short and long-term disability plans
Tuition assistance for both undergraduate and graduate programs
10 Employee Resource Groups for career development, community service, and networking"
Also "In addition to competitive pay and performance incentives" - mention competitive pay and performance incentives but no specific numbers. Since we should not create Pay section unless posting actually states them. It mentions competitive pay and performance incentives but not specific. Should we include Pay? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive pay and performance incentives" which is a statement about pay, albeit vague. Is that enough to create a Pay section? It says "competitive pay" - that's a statement about pay. However they also say "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive pay" is not filler; it's a statement. So we could include a Pay section with a short paragraph: "Competitive pay and performance incentives." But we also have Benefits section already. Could combine pay into Benefits? The instruction says prefer few substantive sections over many thin ones. So we could include Pay as a subsection within Benefits? But they want separate sections for Benefits, Pay, Schedule. However we can decide to not create Pay section if we think it's too vague. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive pay, so we could create Pay section. But we also have Benefits section already; we could keep both.
Schedule: The posting does not mention schedule specifics (like shift, hours). Hybrid Workplace mentions telework up to three days per week, but that's not schedule. No explicit schedule. So we should not create Schedule section.
Now "Summary": "Supports the SRP Storage Management strategy and aligns current and future storage technologies to support the strategic objectives of SRP business organizations. Has an advanced knowledge and experience in storage and backup system administration and support functions."
That's like a summary of role; could be part of About the role or Responsibilities. We'll put under About the role maybe.
"What You'll Do": list of duties. We'll make Responsibilities section with
.
Education: "A bachelor's degree relevant to the assignment from an accredited institution is preferred."
Experience: details about levels.
Additional Requirements And Qualifications: list.
Hybrid Workplace: description.
We need to avoid duplication: The "Experience" section includes levels; we should keep that.
We must not include boilerplate: Equal Opportunity Employer Statement, Drug/Alcohol Policy Statement, Work Authorization.
Now produce HTML.
Structure:
About the role
Join us in building a better future for Arizona! SRP is one of the largest public power and water utilities in the U.S. providing electricity to approximately one million customers in the greater metropolitan Phoenix area. Since its founding in 1903, SRP has fostered a culture of stewardship and customer service consistently ranking as an industry leader in customer service according to J.D. Power and named one of Arizona's best employers by Forbes. SRP continues to adapt to its changing business environment by seeking innovative ways to reimagine utility service and the provision of critical resources essential to the life and economy of Arizona. Why Work at SRP: At SRP, we foster an inclusive work environment and believe everyone should have a fair chance to work, regardless of who they are. That’s why we value teams with diverse perspectives, experiences, and backgrounds to help SRP deliver on its mission of providing reliable, affordable and sustainable water and power. Summary: Supports the SRP Storage Management strategy and aligns current and future storage technologies to support the strategic objectives of SRP business organizations. Has an advanced knowledge and experience in storage and backup system administration and support functions.
But we might split Summary into its own paragraph? It's okay.
Better to keep About the role covering company intro and why work at SRP. Then maybe a separate section "Role Summary" but not in list. Could incorporate into About the role.
Now Responsibilities (Responsibilities
) with list of duties from "What You'll Do".
List items:
- Storage administration of the NetApp and Qumulo suite of Enterprise Products: NetApp AFF and FAS systems, Data ONTAP, Metro Cluster IP, On Command Management Suite (Active IQ Unified Manager and System Manager), Qumulo Core file system
- Administration of the COHESITY Data Platform for Enterprise Backup Data protection
- Update the storage and backup environments as needed to improve features, reliability and to address critical security vulnerabilities and bug fixes.
- Implements enterprise storage and backup strategies around active archive data tiering, enterprise & hybrid cloud, and data protection as well as provide storage administration to support business continuity and disaster recovery for SRP applications and file share environments.
- Proficient with at least one of the following scripting languages, Python/Bash/Power shell.
- Advanced level skill with the Linux & Windows operating systems.
- Light database skills and knowledge of common databases (Oracle/SQL) performance from a storage perspective.
- Network skills with an understanding of routing, switching, port security, and firewalls.
- Utilize ServiceNow to manage Service Requests, Incidents, Problems, and Change Management activities.
- Participate in a rotating on-call schedule, providing 24x7 support for incident response and resolution in one-week intervals.
- Monitor the health and performance of the storage infrastructure using vendor-provided monitoring and alerting tools, proactively identifying and resolving issues before service impact occurs.
Now Qualifications (Qualifications
) maybe combine Education, Experience, Additional Requirements.
But we could have separate sections: Education, Experience, Additional Requirements. However instruction prefers few sections. Could combine into Qualifications with subpoints? But we need to use - for any list of duties/requirements/benefits. So we can have a Qualifications section with
containing education, experience, additional requirements as list items (maybe each item can contain subtext). That's acceptable.
Let's extract:
Education: "A bachelor's degree relevant to the assignment from an accredited institution is preferred."
Experience: details about levels.
Additional Requirements: "Experience designing, implementing, or supporting an Isolated Recovery Environment (IRE) is highly desirable. Hands-on participation in disaster recovery testing exercises, including storage failover, recovery validation, and operational readiness activities."
Hybrid Workplace: "SRP currently offers a hybrid workplace, which allows employees whose jobs can be performed remotely, and who have sufficient technical capability, to telework up to three days per week. Although teleworking is available, all employees must live and work in Arizona."
We could incorporate Hybrid Workplace into Benefits or Qualifications? It's about work arrangement; maybe better as its own section "Work Arrangement" but not in list. Could add to Benefits as a bullet: "Hybrid workplace: telework up to three days per week (must reside in Arizona)". That seems reasonable.
Pay: "competitive pay and performance incentives". We'll add to Benefits or separate Pay section. Since we already have Benefits, we could add a bullet: "Competitive pay and performance incentives". That keeps Benefits section comprehensive.
Thus Benefits section will include all benefits plus hybrid workplace and pay.
Now Benefits (Benefits
for section headings (e.g. ...)" meaning those are examples; we can use other headings if needed? Probably they want us to map content to those standard headings. But we have content like "Why Work at SRP" which could be "About the role". "Benefits" is a heading. "Summary" maybe "About the role". "What You'll Do" is Responsibilities. "Education" and "Experience" could be Qualifications/Requirements. "Additional Requirements And Qualifications" could be Requirements. "Hybrid Workplace" maybe Benefits or Schedule? It's about work arrangement, could be Schedule? But schedule is about hours/shift. Hybrid workplace is more about remote work; could be under Benefits or a separate section like "Work Arrangement". Since not in list, maybe we incorporate into Benefits or Schedule? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Hybrid Workplace into Benefits or maybe into a "Work Arrangement" but not in list. Safer to incorporate into Benefits as an extra bullet.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information; do not invent or summarize away detail.
We need to output only HTML fragment.
Let's extract substantive content:
- Intro: "Join us in building a better future for Arizona! SRP is one of the largest public power and water utilities in the U.S. providing electricity to approximately one million customers in the greater metropolitan Phoenix area. Since its founding in 1903, SRP has fostered a culture of stewardship and customer service consistently ranking as an industry leader in customer service according to J.D. Power and named one of Arizona's best employers by Forbes. SRP continues to adapt to its changing business environment by seeking innovative ways to reimagine utility service and the provision of critical resources essential to the life and economy of Arizona."
That's about the company; could be "About the role" or maybe a brief intro. We'll put under About the role
with a paragraph.
- "Why Work at SRP At SRP, we foster an inclusive work environment and believe everyone should have a fair chance to work, regardless of who they are. That’s why we value teams with diverse perspectives, experiences, and backgrounds to help SRP deliver on its mission of providing reliable, affordable and sustainable water and power."
That's also about culture; could be part of About the role. We'll combine.
- Benefits section: list of benefits.
We need to format as - for list.
Benefits content:
"Pension Plan (at no cost to the employee)
401(k) plan with employer matching
Available your first day: Medical, vision, dental, and life insurance
Over 200+ hours of PTO (includes vacation days, holidays, floating holidays, and sick leave)
Parental leave (up to 4 weeks) and adoption assistance
Wellness programs (including access to a recreation and fitness facility)
Short and long-term disability plans
Tuition assistance for both undergraduate and graduate programs
10 Employee Resource Groups for career development, community service, and networking"
Also "In addition to competitive pay and performance incentives" - mention competitive pay and performance incentives but no specific numbers. Since we should not create Pay section unless posting actually states them. It mentions competitive pay and performance incentives but not specific. Should we include Pay? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive pay and performance incentives" which is a statement about pay, albeit vague. Is that enough to create a Pay section? It says "competitive pay" - that's a statement about pay. However they also say "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive pay" is not filler; it's a statement. So we could include a Pay section with a short paragraph: "Competitive pay and performance incentives." But we also have Benefits section already. Could combine pay into Benefits? The instruction says prefer few substantive sections over many thin ones. So we could include Pay as a subsection within Benefits? But they want separate sections for Benefits, Pay, Schedule. However we can decide to not create Pay section if we think it's too vague. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive pay, so we could create Pay section. But we also have Benefits section already; we could keep both.
Schedule: The posting does not mention schedule specifics (like shift, hours). Hybrid Workplace mentions telework up to three days per week, but that's not schedule. No explicit schedule. So we should not create Schedule section.
Now "Summary": "Supports the SRP Storage Management strategy and aligns current and future storage technologies to support the strategic objectives of SRP business organizations. Has an advanced knowledge and experience in storage and backup system administration and support functions."
That's like a summary of role; could be part of About the role or Responsibilities. We'll put under About the role maybe.
"What You'll Do": list of duties. We'll make Responsibilities section with
.
Education: "A bachelor's degree relevant to the assignment from an accredited institution is preferred."
Experience: details about levels.
Additional Requirements And Qualifications: list.
Hybrid Workplace: description.
We need to avoid duplication: The "Experience" section includes levels; we should keep that.
We must not include boilerplate: Equal Opportunity Employer Statement, Drug/Alcohol Policy Statement, Work Authorization.
Now produce HTML.
Structure:
About the role
Join us in building a better future for Arizona! SRP is one of the largest public power and water utilities in the U.S. providing electricity to approximately one million customers in the greater metropolitan Phoenix area. Since its founding in 1903, SRP has fostered a culture of stewardship and customer service consistently ranking as an industry leader in customer service according to J.D. Power and named one of Arizona's best employers by Forbes. SRP continues to adapt to its changing business environment by seeking innovative ways to reimagine utility service and the provision of critical resources essential to the life and economy of Arizona. Why Work at SRP: At SRP, we foster an inclusive work environment and believe everyone should have a fair chance to work, regardless of who they are. That’s why we value teams with diverse perspectives, experiences, and backgrounds to help SRP deliver on its mission of providing reliable, affordable and sustainable water and power. Summary: Supports the SRP Storage Management strategy and aligns current and future storage technologies to support the strategic objectives of SRP business organizations. Has an advanced knowledge and experience in storage and backup system administration and support functions.
But we might split Summary into its own paragraph? It's okay.
Better to keep About the role covering company intro and why work at SRP. Then maybe a separate section "Role Summary" but not in list. Could incorporate into About the role.
Now Responsibilities (Responsibilities
) with list of duties from "What You'll Do".
List items:
- Storage administration of the NetApp and Qumulo suite of Enterprise Products: NetApp AFF and FAS systems, Data ONTAP, Metro Cluster IP, On Command Management Suite (Active IQ Unified Manager and System Manager), Qumulo Core file system
- Administration of the COHESITY Data Platform for Enterprise Backup Data protection
- Update the storage and backup environments as needed to improve features, reliability and to address critical security vulnerabilities and bug fixes.
- Implements enterprise storage and backup strategies around active archive data tiering, enterprise & hybrid cloud, and data protection as well as provide storage administration to support business continuity and disaster recovery for SRP applications and file share environments.
- Proficient with at least one of the following scripting languages, Python/Bash/Power shell.
- Advanced level skill with the Linux & Windows operating systems.
- Light database skills and knowledge of common databases (Oracle/SQL) performance from a storage perspective.
- Network skills with an understanding of routing, switching, port security, and firewalls.
- Utilize ServiceNow to manage Service Requests, Incidents, Problems, and Change Management activities.
- Participate in a rotating on-call schedule, providing 24x7 support for incident response and resolution in one-week intervals.
- Monitor the health and performance of the storage infrastructure using vendor-provided monitoring and alerting tools, proactively identifying and resolving issues before service impact occurs.
Now Qualifications (Qualifications
) maybe combine Education, Experience, Additional Requirements.
But we could have separate sections: Education, Experience, Additional Requirements. However instruction prefers few sections. Could combine into Qualifications with subpoints? But we need to use - for any list of duties/requirements/benefits. So we can have a Qualifications section with
containing education, experience, additional requirements as list items (maybe each item can contain subtext). That's acceptable.
Let's extract:
Education: "A bachelor's degree relevant to the assignment from an accredited institution is preferred."
Experience: details about levels.
Additional Requirements: "Experience designing, implementing, or supporting an Isolated Recovery Environment (IRE) is highly desirable. Hands-on participation in disaster recovery testing exercises, including storage failover, recovery validation, and operational readiness activities."
Hybrid Workplace: "SRP currently offers a hybrid workplace, which allows employees whose jobs can be performed remotely, and who have sufficient technical capability, to telework up to three days per week. Although teleworking is available, all employees must live and work in Arizona."
We could incorporate Hybrid Workplace into Benefits or Qualifications? It's about work arrangement; maybe better as its own section "Work Arrangement" but not in list. Could add to Benefits as a bullet: "Hybrid workplace: telework up to three days per week (must reside in Arizona)". That seems reasonable.
Pay: "competitive pay and performance incentives". We'll add to Benefits or separate Pay section. Since we already have Benefits, we could add a bullet: "Competitive pay and performance incentives". That keeps Benefits section comprehensive.
Thus Benefits section will include all benefits plus hybrid workplace and pay.
Now Benefits (Benefits
- .
Education: "A bachelor's degree relevant to the assignment from an accredited institution is preferred."
Experience: details about levels.
Additional Requirements And Qualifications: list.
Hybrid Workplace: description.
We need to avoid duplication: The "Experience" section includes levels; we should keep that.
We must not include boilerplate: Equal Opportunity Employer Statement, Drug/Alcohol Policy Statement, Work Authorization.
Now produce HTML.
Structure:
- for any list of duties/requirements/benefits. So we can have a Qualifications section with
- containing education, experience, additional requirements as list items (maybe each item can contain subtext). That's acceptable.
Let's extract:
Education: "A bachelor's degree relevant to the assignment from an accredited institution is preferred."
Experience: details about levels.
Additional Requirements: "Experience designing, implementing, or supporting an Isolated Recovery Environment (IRE) is highly desirable. Hands-on participation in disaster recovery testing exercises, including storage failover, recovery validation, and operational readiness activities."
Hybrid Workplace: "SRP currently offers a hybrid workplace, which allows employees whose jobs can be performed remotely, and who have sufficient technical capability, to telework up to three days per week. Although teleworking is available, all employees must live and work in Arizona."
We could incorporate Hybrid Workplace into Benefits or Qualifications? It's about work arrangement; maybe better as its own section "Work Arrangement" but not in list. Could add to Benefits as a bullet: "Hybrid workplace: telework up to three days per week (must reside in Arizona)". That seems reasonable.
Pay: "competitive pay and performance incentives". We'll add to Benefits or separate Pay section. Since we already have Benefits, we could add a bullet: "Competitive pay and performance incentives". That keeps Benefits section comprehensive.
Thus Benefits section will include all benefits plus hybrid workplace and pay.
Now Benefits (
Benefits
About the role
Join us in building a better future for Arizona! SRP is one of the largest public power and water utilities in the U.S. providing electricity to approximately one million customers in the greater metropolitan Phoenix area. Since its founding in 1903, SRP has fostered a culture of stewardship and customer service consistently ranking as an industry leader in customer service according to J.D. Power and named one of Arizona's best employers by Forbes. SRP continues to adapt to its changing business environment by seeking innovative ways to reimagine utility service and the provision of critical resources essential to the life and economy of Arizona. Why Work at SRP: At SRP, we foster an inclusive work environment and believe everyone should have a fair chance to work, regardless of who they are. That’s why we value teams with diverse perspectives, experiences, and backgrounds to help SRP deliver on its mission of providing reliable, affordable and sustainable water and power. Summary: Supports the SRP Storage Management strategy and aligns current and future storage technologies to support the strategic objectives of SRP business organizations. Has an advanced knowledge and experience in storage and backup system administration and support functions.
But we might split Summary into its own paragraph? It's okay. Better to keep About the role covering company intro and why work at SRP. Then maybe a separate section "Role Summary" but not in list. Could incorporate into About the role. Now Responsibilities (Responsibilities
) with- list of duties from "What You'll Do".
List items:
- Storage administration of the NetApp and Qumulo suite of Enterprise Products: NetApp AFF and FAS systems, Data ONTAP, Metro Cluster IP, On Command Management Suite (Active IQ Unified Manager and System Manager), Qumulo Core file system
- Administration of the COHESITY Data Platform for Enterprise Backup Data protection
- Update the storage and backup environments as needed to improve features, reliability and to address critical security vulnerabilities and bug fixes.
- Implements enterprise storage and backup strategies around active archive data tiering, enterprise & hybrid cloud, and data protection as well as provide storage administration to support business continuity and disaster recovery for SRP applications and file share environments.
- Proficient with at least one of the following scripting languages, Python/Bash/Power shell.
- Advanced level skill with the Linux & Windows operating systems.
- Light database skills and knowledge of common databases (Oracle/SQL) performance from a storage perspective.
- Network skills with an understanding of routing, switching, port security, and firewalls.
- Utilize ServiceNow to manage Service Requests, Incidents, Problems, and Change Management activities.
- Participate in a rotating on-call schedule, providing 24x7 support for incident response and resolution in one-week intervals.
- Monitor the health and performance of the storage infrastructure using vendor-provided monitoring and alerting tools, proactively identifying and resolving issues before service impact occurs.
Now Qualifications (