Principal Storage Engineer

We need to output HTML fragment with sections: About the role? The posting includes Position Summary, What We Do, What You'll Do (with sub-sections), Required Qualifications, Preferred Qualifications, Leadership Competencies, Salary Range, Benefits, Schedule (Weekly Hours 40, Time Type Regular), Location (multiple locations). Also mention office presence requirement (5 days per week). Also mention no relocation, no sponsorship. We must not repeat job title as heading. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must include a section only when posting has real, specific content. So we need sections: About the role? The posting has "Position Summary" which is a paragraph. Could be "About the role". Use heading About the role. Then "What We Do" could be "About the team" or "Our Infrastructure Engineering organization". Could be "About the team". But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. We can omit sections if no content. Thus we need to map content: - About the role: Position Summary paragraph. - Responsibilities: "What You'll Do" with subcategories. Could be a list of responsibilities. - Requirements: "Required Qualifications". - Qualifications: maybe "Preferred Qualifications"? But we already have Requirements and Qualifications separate. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications. - Skills: maybe "Leadership Competencies" or "Skills". Could include leadership competencies and technical skills. - Benefits: list of perks. - Pay: Salary Range. - Schedule: Weekly Hours 40, Time Type Regular, office presence 5 days per week. Also location info: could be included in About the role or maybe as a separate paragraph but not a heading. Could embed in About the role or as a p after schedule. We must not include boilerplate like EEO, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific technologies, years, etc. We need to format lists with

  • . For prose use

    . We must not repeat job title. We must not put Job ID/requisition numbers as headings (none present). We must not include filler like "commensurate with experience". Not present. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range, benefits, weekly hours, time type, office presence. So include those. We must prefer a few substantive sections over many thin ones. But we have to follow headings list; we can combine some if appropriate? The instruction: "Prefer a few substantive sections over many thin ones." So we should not create many sections with little content. But we have to include sections only when posting has real specific content. We can combine some headings if content fits multiple categories? However they gave examples of headings; we can still use them but maybe combine some? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings. It doesn't say we must use all; we can use subset. Prefer few substantive sections over many thin ones. So we should aim to have maybe 5-6 sections. We could combine Responsibilities and Requirements? But they are distinct. Might be okay to have all eight sections if each has substantive content. Let's see if each has enough content. - About the role: Position Summary paragraph (substantive). - Responsibilities: What You'll Do includes many bullet-like paragraphs; we can turn into

    • list. - Requirements: Required Qualifications (list). - Qualifications: Preferred Qualifications (list). - Skills: Leadership Competencies (list) maybe also technical skills? Could combine leadership competencies and technical skills? But we already have technical skills in Responsibilities/Requirements. Could make Skills section for leadership competencies. - Benefits: list of perks. - Pay: Salary Range. - Schedule: Weekly Hours, Time Type, office presence. That's eight sections, each substantive. Might be okay. The instruction says prefer few over many thin ones, but these are not thin; each has decent content. So okay. We must not include filler like "commensurate with experience". Not present. Now we need to extract exact content. Let's parse the posting. Position Summary: "We are seeking a highly skilled and experienced Principal Storage Engineer to serve as a technical leader responsible for the design, engineering, automation, reliability, and lifecycle management of enterprise storage platforms. This role provides technical leadership across SAN, NAS, storage networking, storage fabrics, backup and recovery, performance engineering, and infrastructure modernization initiatives. The ideal candidate possesses deep expertise in enterprise storage technologies, Fiber Channel SAN architectures, NAS platforms, storage networking, and large-scale infrastructure operations. This individual will drive architectural decisions, establish engineering standards, mentor senior engineers, and lead strategic initiatives that enhance availability, scalability, resiliency, security, and operational efficiency across the storage ecosystem." That's the summary. What We Do: paragraph describing environment. Could be part of About the role? But we already used About the role for summary. Could incorporate What We Do into About the role as additional paragraph. But we might keep About the role as summary only; What We Do could be part of About the role as well. However we need to avoid too many sections. Could merge What We Do into About the role as additional paragraph(s). That would keep sections fewer. But the instruction: "Prefer a few substantive sections over many thin ones." So we could combine About the role and What We Do into one About the role section. That seems reasonable. Thus About the role section will contain both Position Summary and What We Do paragraphs. Now Responsibilities: "What You'll Do" with subheadings: Architecture & Technical Leadership, SAN & Storage Fabric Engineering, NAS & File Services, Storage Networking, Storage Performance Engineering, Automation & Infrastructure as Code, Reliability, Availability & Recovery, Governance & Security, Mentorship & Leadership. We need to capture all bullet points under each. We'll turn each bullet into
    • . Could group under a single
      list, but maybe better to keep subheadings? However we cannot use headings inside sections besides

      ? The instruction only says use

      for section headings. It doesn't forbid other headings like

      but we should avoid extra headings? Not prohibited but we can keep simple: just a flat list of responsibilities. However we risk losing structure but still preserving all info. The instruction: "Use

      • for any list of duties/requirements/benefits". So we can make a single list of duties. That's okay. Thus we will extract each duty sentence. Let's list them: From Architecture & Technical Leadership: - Lead the design and strategic direction of enterprise storage platforms and services. - Define architecture standards, engineering patterns, and operational best practices. - Evaluate emerging storage technologies and recommend modernization strategies. - Serve as the highest-level technical escalation point for complex storage issues. - Drive storage transformation initiatives across on-premises and hybrid cloud environments. SAN & Storage Fabric Engineering: - Design, implement, and support large-scale Fiber Channel SAN infrastructures. - Engineer highly available storage fabric architectures with redundant paths and fault-tolerant designs. - Manage SAN zoning, host connectivity, multipathing configurations, and fabric optimization. - Lead storage migrations, technology refreshes, and lifecycle management initiatives. - Ensure storage platforms meet enterprise performance and resiliency requirements. NAS & File Services: - Design and support enterprise NAS solutions supporting NFS, SMB, and file-based workloads. - Define storage allocation, data lifecycle management, and tiering strategies. - Optimize file service performance, availability, and scalability. - Develop standards for enterprise file storage consumption and operational support. Storage Networking: - Collaborate with network engineering teams on storage transport design and connectivity. - Optimize storage network performance, throughput, and latency. - Troubleshoot complex storage-to-host communication issues. - Define standards for storage network security, segmentation, and resiliency. Storage Performance Engineering: - Analyze IOPS, latency, throughput, and workload characteristics across enterprise environments. - Conduct proactive performance assessments and capacity modeling. - Identify bottlenecks and implement remediation strategies. - Drive performance benchmarking and optimization efforts. - Establish monitoring dashboards, KPIs, and service health metrics. Automation & Infrastructure as Code: - Develop automation solutions for storage provisioning, reporting, monitoring, and lifecycle management. - Leverage APIs, scripting, and infrastructure automation frameworks to reduce manual operations. - Standardize operational processes through automation and self-service capabilities. - Drive continuous improvement across engineering and operational workflows. Reliability, Availability & Recovery: - Design disaster recovery and business continuity strategies for storage platforms. - Lead recovery testing, failover exercises, and resiliency assessments. - Ensure backup, replication, and data protection capabilities meet business requirements. - Participate in major incident response and root cause analysis activities. Governance & Security: - Ensure compliance with enterprise security, audit, and regulatory requirements. - Collaborate with cybersecurity teams on storage hardening initiatives. - Define access control models and secure data storage practices. - Support risk assessments and remediation planning. Mentorship & Leadership: - Mentor senior engineers and technical leads. - Provide architectural guidance across infrastructure and platform organizations. - Lead design reviews, technical forums, and engineering governance efforts. - Influence long-term technology roadmaps and strategic investments. Now Required Qualifications list: - Bachelor's degree in Computer Science, Engineering, Information Systems, or related discipline, or equivalent experience. - 12+ years of experience managing enterprise storage environments. - 5+ years in a senior architect, principal engineer, or technical leadership role. - Deep expertise with enterprise SAN technologies and Fiber Channel architectures. - Extensive experience with NAS platforms and file services. - Strong understanding of storage networking concepts, switches, fabrics, and connectivity. - Expertise in performance tuning, troubleshooting, and capacity management. - Experience supporting mission-critical production environments requiring high availability. - Strong scripting and automation experience using Python, PowerShell, Bash, Ansible, or similar tools. - Experience leading complex infrastructure modernization and migration projects. - Strong analytical, communication, and leadership skills. Preferred Qualifications list: - Experience with HPE Primera, Alletra, NetApp, Dell PowerScale/Isilon, Pure Storage, or equivalent enterprise platforms. - Experience with Brocade and Cisco SAN fabrics. - Knowledge of cloud storage services in Azure, AWS, or GCP. - Experience with Kubernetes persistent storage architectures and CSI integrations. - Familiarity with disaster recovery, replication, backup, and business continuity solutions. - Experience implementing Infrastructure as Code and platform automation frameworks. - Storage industry certifications (NetApp, HPE, Dell EMC, Cisco, Brocade, SNIA, etc.). - Experience operating storage platforms supporting large-scale private cloud or virtualized infrastructure environments. Leadership Competencies list: - Strategic thinker with strong business and technical acumen. - Exceptional problem-solving and troubleshooting abilities. - Ability to influence decisions across organizational boundaries. - Strong executive communication and presentation skills. - Proven ability to lead through complex technical transformations. - Demonstrated commitment to operational excellence and continuous improvement. Benefits list (from "Joining Our Team Comes With Amazing Perks And Benefits"): - Medical/Dental/Vision coverage - 401(k) plan - Tuition reimbursement program - Paid Time Off and Holidays (based on date of hire, at least 23 days of vacation each year and 9 company-designated holidays) - Paid Parental Leave - Paid Caregiver Leave - Additional sick leave beyond what state and local law require may be available but is unprotected - Adoption Reimbursement - Dis