Lead Engineering Systems Administrator

We need to output HTML fragment with sections: About the role? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for section headings. 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. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". So we need to extract content: Description includes application window close date, location, hybrid. That's maybe metadata; we can put in a short

  . The "About Envestnet" is about company; could be part of About the role? Probably "About the role" heading includes description of role? The posting includes "About Envestnet" and "The Team You’ll Join". Could be considered "About the role". We'll include that content under About the role. Responsibilities: The "How You’ll Contribute" section lists many bullet-like sentences. We'll turn each sentence into

• under a
  . Requirements: "What You’ll Need to Bring" includes bullet-like sentences; also "Nice-to-Haves". We'll treat those as Requirements (maybe separate Qualifications? but we can combine). We'll include Requirements heading with list. Skills: maybe we can extract specific skills from requirements: expertise administering Windows Server, AD, DNS, DHCP, Group Policy, certificate services; identity and access management; privileged access; least-privilege/tiered administration; secure configuration baselines; proficiency with automation and scripting (PowerShell, IaC); experience with patch/vuln management, backup/disaster recovery, ITIL framework; ability to communicate technical concepts. We'll put those under Skills as list. Qualifications: maybe "Nice-to-Haves" 6+ years experience etc. Could be Qualifications. We'll put Qualifications heading with list. Benefits: The "Our Investment in You" mentions base salary range (Pay) and benefits list: medical insurance, paid time off (PTO), 401k company match, paid parental leave, education reimbursement, disability coverage, mental health & wellness support. Also mention incentive component. So we need Benefits section with list of benefits. Pay section with salary range. Schedule? Not mentioned besides hybrid work model (location). Could be Schedule: hybrid work model? Might be considered schedule? The posting says "primary work location for this role is Berwyn, PA with a hybrid work model." That's location, not schedule. No explicit schedule. So we should not create Schedule section unless posting actually states them. It does not state schedule like full-time, part-time, shift. So omit Schedule. We also need to include application window close date and location maybe as a short p at top. We must not include boilerplate like EEO, recruitment fraud, etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from sections we include. Let's extract content: - Application window will close October 26, 2026. - Job Location: primary work location Berwyn, PA with hybrid work model. - About Envestnet: paragraph about Envestnet being adaptive WealthTech, etc. Also link. - The Team You’ll Join: paragraph about Engineering Systems Administration team role. - How You’ll Contribute: list of responsibilities (multiple sentences). We'll break each sentence into li. - What You’ll Need to Bring: list of required expertise. - Nice-to-Haves: 6+ years experience etc. - Why You’ll Enjoy Working at Envestnet: paragraph about impact, flexibility, rewards. - Sponsorship: "This position is not open to candidates requiring visa sponsorship" - that's substantive; maybe include under Requirements? Could be a note. We'll include as a p under Requirements maybe. - Our Investment in You: base salary range, incentive component, benefits list. - Our Commitment to Inclusion & Belonging: EEO boilerplate - remove. - Recruitment Fraud: remove. We need to avoid duplication. Ensure we don't repeat same content. Now produce HTML: Start with maybe a p for metadata:

  Application window: October 26, 2026. Location: Berwyn, PA (hybrid work model).

  Then sections:

  About the role

  ... combine About Envestnet and The Team You’ll Join? Might be two paragraphs.

  We could split: About the role includes About Envestnet and The Team You’ll Join. Provide two

  under that heading. Then Responsibilities heading with

  • ... each sentence. Then Requirements heading with
    • ... required expertise plus maybe Nice-to-Haves? But we have Qualifications heading for nice-to-haves. We need Skills heading: list of specific skills. Qualifications heading: nice-to-haves. Benefits heading: list benefits. Pay heading: salary range. Let's extract responsibilities sentences from "How You’ll Contribute". The paragraph is a long run-on with many clauses separated by periods? Let's copy: "Designs, maintains and supports the core technology infrastructure and services that power wealth management, financial services and other company platforms. Ensures that systems are secure, reliable, scalable and compliant with company and regulatory standards. Collaborates with development, security and operations teams to deploy infrastructure, manage and maintain SaaS platforms, automate processes and resolve system issues. Manages cloud and on-premise environments, monitors performance and implements best practices for availability, security and disaster recovery. Leads and/or advises on site, regional and or cross-organizational systems-related initiatives. Contributes to planning and implementing new releases, updates or corrections to hardware, software, applications or connectivity. Participates in strategic planning and development associated with future design, performance and capacity management. Effectively translates, communicates and relays technical subject matter content to non-technical audiences. Evaluates, recommends and maintains hardware and software management and monitoring tools to meet current and future organizational needs. Defines and develops comprehensive user and related training and information. Ensures security and compliance requirements are built into all initiatives. Participates in design and architectural discussions based on requirements from customers and leadership. Leads incident recovery using the ITIL framework and ITIL certification. Leads and advises on enterprise systems initiatives focused on Active Directory, identity management, and infrastructure security, contributing to solution design, strategic planning, and capacity management across on-premise and cloud environments. Designs and implements secure identity and privileged access management solutions, including least-privilege and tiered administration models, to protect critical systems and organizational assets. Drives automation and infrastructure reliability through scripting, secure configuration management, and the development of backup, recovery, and business continuity capabilities that support operational resilience and compliance requirements." We'll make each line a
    • . Now Requirements: "What You’ll Need to Bring" bullet-like sentences: "Candidates should demonstrate the relevant experience, skills, and capabilities needed to successfully perform in the role. Relevant experience may be gained through current responsibilities, prior roles, project work, leadership opportunities, or other comparable experiences. Demonstrated expertise administering and securing Windows Server environments, including Active Directory, DNS, DHCP, Group Policy, and certificate services. Strong background in identity and access management and infrastructure security, including privileged access, least-privilege/tiered administration, and secure configuration baselines aligned to recognized industry standards. Proficiency with automation and scripting (e.g., PowerShell, infrastructure-as-code) to standardize configuration and reduce manual effort. Experience with patch and vulnerability management, backup/disaster recovery, and operating within an ITIL-aligned framework, with the ability to communicate technical concepts to non-technical audiences." Also "Nice-to-Haves" separate. Also "Sponsorship This position is not open to candidates requiring visa sponsorship" - we can include as a p under Requirements maybe. Now Skills: we could list the specific skills from requirements: Administering and securing Windows Server environments (AD, DNS, DHCP, Group Policy, certificate services); Identity and access management; Privileged access; Least-privilege/tiered administration; Secure configuration baselines; Automation and scripting (PowerShell, IaC); Patch and vulnerability management; Backup/disaster recovery; ITIL framework; Communicating technical concepts to non-technical audiences. We'll put those as
    • . Qualifications (nice-to-haves): "6+ years of systems administration or infrastructure engineering experience in an enterprise environment, including hands-on ownership of Active Directory and identity services." Also maybe "Why You’ll Enjoy Working at Envestnet" could be under Benefits? But it's more about culture; maybe we could include under Benefits? But Benefits section is for benefits; we could add a separate section like "Why Envestnet"? Not in allowed headings. The allowed headings list includes Benefits, Pay, Schedule. So we should not create extra headings. The "Why You’ll Enjoy Working at Envestnet" is descriptive; maybe we can incorporate into About the role? Or we could put under Benefits as a paragraph? But it's not a benefit. The instruction: "Prefer a few substantive sections over many thin ones." We could omit that paragraph if it's not fitting into allowed headings? But we must preserve ALL substantive information; cannot omit. So we need to place it somewhere. The allowed headings are just examples; we can use other headings? The instruction: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use other headings if needed? But they say "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. However they also say "include a section ONLY when the posting has real, specific content for it". So we can use those headings as needed. The "Why You’ll Enjoy Working at Envestnet" could be considered part of Benefits? Not really. Could be part of About the role? Could be a paragraph under About the role describing the team and culture. We'll add a paragraph under About the role after the team description. Thus About the role will have multiple paragraphs: About Envestnet, The Team You’ll Join, Why You’ll Enjoy Working at Envestnet. Now Benefits: list medical insurance, paid time off (PTO), 401k company match, paid parental leave, education reimbursement, disability coverage, mental health & wellness support. Also mention incentive component? That's part of Pay maybe. We'll include incentive component under Pay? Pay section: base salary range and incentive component. Pay: base salary range $114,500 to $143,100; eligible for additional incentive component as part of total rewards. Schedule: not present, omit. Now ensure we don't include boilerplate: remove EEO, recruitment fraud, etc. Now produce HTML. Let's craft. We'll start with metadata p. Then

      About the role

      About Envestnet: ...

      The Team You’ll Join: ...

      Why You’ll Enjoy Working at Envestnet: ...

      Then Responsibilities. Then Requirements. Then Skills. Then Qualifications. Then Benefits. Then Pay. Make sure to close tags. Let's write content precisely. About Envestnet paragraph: "Envestnet is an adaptive WealthTech company that is redefining the future of wealth management by helping advisors meet the moment with its comprehensive technology, actionable insights, and industry leading support. Backed by over 25 years of experience and approximately $7.0 trillion in platform assets, Envestnet is trusted by over one third of financial advisors across leading banks, wealth managers, brokerages, and RIAs. For a deeper look at how Envestnet is