Analyst, Technology Operations - Infrastructure

We need to produce HTML fragment with sections: About the role? Actually the posting includes description paragraphs before "What You'll Do". We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Please note that the percentage breakdowns..." maybe keep? It's part of duties but it's a note; we can keep as prose. Remove "TO APPLY" and application instructions. Remove EEO statements etc. Also remove "Physical Requirements" maybe? It's substantive? It's about physical requirements; could be part of Requirements? Might keep as a list under Requirements? The instruction: include a section ONLY when posting has real, specific content for it. Physical Requirements is specific content; we could put under Requirements or maybe a separate section? The allowed headings are limited to those listed; we cannot create new headings like Physical Requirements. So we need to fit that content into one of the allowed sections. Probably under Requirements (or Qualifications). We'll put physical requirements as a

  under Requirements. We need sections: About the role (intro paragraph), Responsibilities (What You'll Do), Requirements (What You'll Bring + physical requirements), Qualifications (maybe education/certifications?), Skills (maybe technical skills?), Benefits, Pay, Schedule. We must not create sections with filler like "commensurate with experience" etc. For Pay we have salary ranges; we can include that. Benefits: we have "competitive salary and excellent, comprehensive benefits. We also offer a casual and congenial work environment." That's benefits; we can include that. Schedule: "full-time schedule of 37.5 hours per week. This position requires working a hybrid schedule in office two days per week in one of the following locations: San Francisco, New York City, Denver, Los Angeles, Chicago, or Washington, D.C." That's schedule. We must not repeat job title. No markdown. We need to ensure we don't include boilerplate like EEO statements, application instructions, etc. Let's extract substantive content: Intro: "Earthjustice is the nation's leading environmental law organization. We wield the power of law and the strength of partnership to protect people's health, preserve magnificent places and wildlife, advance clean energy, and combat climate change. We are here because the Earth needs a good lawyer. Driven by a passion for justice, inclusion, partnership, and excellence, our core values lead us to seek a broad range of perspectives and backgrounds to achieve our mission and maintain an inclusive environment where all staff are valued and respected. The Analyst, Technology Operations role supports the design, implementation, administration, and continuous improvement of Earthjustice’s technology infrastructure and connectivity environment. This role is responsible for maintaining reliable and secure network, systems, and cloud infrastructure services that enable staff collaboration, operational efficiency, and organizational resilience across distributed offices and remote work environments. This position partners closely with service desk, enterprise systems, cybersecurity, vendors, and cross-functional stakeholders to administer core infrastructure platforms, support connectivity and telecommunications services, and assist with infrastructure engineering initiatives. The Analyst plays a key role in overseeing vendor delivery and vendor management activities, ensuring service providers meet operational expectations, service level agreements, and project timelines while aligning with organizational priorities. The role combines operational support, technical administration, systems analysis, and project coordination responsibilities, balancing day-to-day infrastructure reliability with long-term modernization and optimization initiatives. This role is a non-supervisory position." That's the About the role. Responsibilities: "What You'll Do" with subsections and percentages. We can combine into a list of duties. We'll produce a
  with each bullet maybe summarizing each subsection but preserving details. Must not invent or summarize away detail; we need to preserve all substantive information. So we need to include the details from each bullet: Infrastructure Administration & Operations (35%) etc. We'll keep the percentages maybe as part of bullet text. We'll produce list items like: - Infrastructure Administration & Operations (35%): Administer and optimize hybrid infrastructure across cloud and on prem (Azure, M365, Google Workspace, networking, identity, connectivity). Monitor system performance, security, and availability; lead troubleshooting, patching, and incident resolution. Support disaster recovery, backups, and documentation to ensure scalable, secure, and resilient operations. - Infrastructure Engineering & Continuous Improvement (25%): Contribute to infrastructure modernization (cloud migrations, network upgrades, system integrations). Partner across teams to implement security controls, monitoring, and operational best practices. Support testing, deployment, and automation to improve efficiency and reduce operational overhead. - Vendor Delivery & Vendor Management (20%): Oversee vendor delivery for infrastructure and connectivity services, ensuring quality and timeliness. Support vendor relationships, monitor SLAs, and drive issue resolution and performance improvements. Support procurement, budgeting, licensing, and contract lifecycle management. - Service Support, Coordination & Reporting (15%): Provide technical support and escalation management for infrastructure-related incidents and service requests. Coordinate communications with internal teams and vendors regarding outages, maintenance, and projects. Maintain observability practices (metrics, logging, alerting) and support incident response and continuous improvement. - Ongoing Learning & Collaboration (5%): Actively pursue professional development and contribute to a culture of learning by building skills and sharing knowledge. Uphold Earthjustice’s mission and values by fostering a respectful, inclusive, and collaborative work environment. Support cross-functional collaboration and knowledge sharing across Technology Operations and partner teams. We can keep the note about percentages as guideline; we can include as prose after list: "Please note that the percentage breakdowns provided above serve as a guideline and that other duties may be assigned as part of the job's requirements." Now Requirements: "What You'll Bring" list. We'll convert each line into bullet points. Also include physical requirements as bullets. Let's list: - Minimum 5+ years of experience supporting infrastructure operations, systems administration, networking, telecommunications, cloud services, or related technology operations functions. - Hands-on experience administering hybrid cloud infrastructure across Microsoft (Azure, Active Directory, Microsoft 365), Google Cloud, and AWS, with a strong understanding of identity and access management, resource management and endpoint management systems in multi-cloud and on-premises environments. - Proficiency in scripting and automation (e.g., PowerShell, Python, Bash), and experience with infrastructure-as-code and automation tooling (e.g., Terraform, Ansible) and platform-native CLIs (Azure CLI, gcloud, AWS CLI) to provision resources, enforce consistent configuration, and improve operational efficiency. - Proficient in networking technologies including TCP/IP, DNS, DHCP, wireless networking, and remote connectivity technologies, with hands-on experience with enterprise network infrastructure using Cisco technologies (routing, switching, firewalls, and VPN), including integrating on-premises connectivity with cloud networking such as Azure ExpressRoute, AWS Direct Connect, or Google Cloud Interconnect. - Experience implementing observability tooling e.g., Azure Monitor, Datadog for system visibility and incident response in hybrid environments. - Experience supporting infrastructure monitoring, incident response, troubleshooting, and operational service delivery processes. - Demonstrated experience coordinating with external vendors and managed service providers, including overseeing vendor delivery, tracking SLAs, and supporting contract and support management activities. - Strong analytical and problem-solving skills with the ability to diagnose technical issues, evaluate operational risks, and recommend practical solutions. - Ability to manage multiple priorities and projects in a fast-paced operational environment with strong organizational and time management skills. - Excellent written and verbal communication skills, including the ability to explain technical concepts to technical and non-technical audiences. - Experience working in environments with elevated confidentiality and security requirements is preferred. - Bachelor’s degree or equivalent practical experience in Information Technology, Computer Science, Engineering, or a related field. - Relevant certifications such as Azure Administrator Associate, CompTIA Network+, Security+, Microsoft, Cisco Certified Network Associate, AWS, or Azure certifications are a plus. - Demonstrated commitment to Earthjustice’s values of Justice, Excellence, Inclusion, and Partnership. - Physical Requirements: This role may require the ability to: Sit for extended periods with occasional standing and walking; Type, file, and/or handle office equipment; Lift and carry materials; Read documents, conduct computer work and document review; Conduct consultations and meetings, and have telephone and video communications. We could split physical requirements into its own list. Now Qualifications: maybe education and certifications? But we already included those in Requirements. The allowed headings include Qualifications separate from Requirements. We could move education and certifications to Qualifications. But we need to avoid duplication. Let's decide: Requirements: experience and skills. Qualifications: education, certifications, commitment to values. Skills: technical proficiencies? But we already have many technical skills. Could split: Requirements = experience; Qualifications = education/certifications; Skills = technical proficiencies (scripting, networking, observability, etc). However the instruction: Prefer a few substantive sections over many thin ones. So maybe combine into Requirements and Skills only. But we have headings list; we can use as many as needed but prefer few substantive sections. We'll create sections: About the role, Responsibilities, Requirements (includes experience, education, certifications, commitment, physical), Skills (technical proficiencies), Benefits, Pay, Schedule. We must ensure not to repeat content. Let's parse: Experience bullets: Minimum 5+ years..., Hands-on experience administering hybrid cloud..., Proficiency in scripting and automation..., Proficient in networking technologies..., Experience implementing observability..., Experience supporting infrastructure monitoring..., Demonstrated experience coordinating with external vendors..., Strong analytical..., Ability to manage multiple priorities..., Excellent written..., Experience working in environments with elevated confidentiality..., Demonstrated commitment to Earthjustice’s values... Education/certifications: Bachelor’s degree..., Relevant certifications..., (these could be Qualifications). Physical Requirements: separate. Technical skills: many of the experience bullets already cover skills; but we could keep them under Requirements. To avoid too many sections, maybe just have About the role, Responsibilities, Requirements (includes experience, education, certifications, commitment, physical), Benefits, Pay, Schedule. That's 5 sections. But we need to include Skills heading if we have specific skill list; but we can embed skills within Requirements. The instruction: Use headings only when posting has real, specific content for it. If we put skills under Requirements, that's fine. Thus we will have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Check if we have any content for Qualifications separate? Not needed. Now Benefits: "We offer a competitive salary and excellent, comprehensive benefits. We also offer a casual and congenial work environment." That's benefits. Pay: salary ranges. Schedule: full-time 37.5 hours per week, hybrid schedule two days per week in listed locations. Now we need to ensure we don't include boilerplate like EEO, application instructions, etc. We'll strip those. Now produce HTML:

  About the role

  ... (intro paragraph)

  Responsibilities

  • ...
  ...

  Please note that the percentage breakdowns provided above serve as a guideline and that other duties may be assigned as part of the job's requirements.

  Requirements

  • ... (experience bullets)
  ...
  • ... (education/certifications)
  ...
  • ... (commitment)
  ...

  Physical Requirements

  ??? Not allowed heading. We need to embed physical requirements maybe as a list under Requirements as well. But we already have a list; we can add another bullet for physical requirements with sub-bullets? Could be a nested list? But we can just add a bullet: "Physical requirements: ability to sit for extended periods with occasional standing and