Network Implementation - Senior Network Engineer, Implementation
ECI · New York, NY · Today
On-siteInformation Technology$140k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About ECI" description, then "What you will do", "Who you are", "Bonus points if you have:", then compensation and benefits. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to decide which sections to include based on content.
We have:
- About ECI: description of company. Could map to "About the role"? Actually "About the role" is typical heading for role description. But we have "About ECI" which is company overview. Could treat as "About the role"? Might be better to use "About the role" heading and put the description of the role (the hybrid role description). However the posting includes "ECI has an exciting opportunity for an experienced Senior Network Engineer to join our Global Implementations team..." That's role overview. So we can put that under "About the role". The earlier "About ECI" paragraph could be considered company overview; maybe we can include it under same section or maybe we can omit as not required? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company description as well. Could put it under a heading like "About ECI" but we only allowed specific headings list. The instruction says: use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to decide which sections to include based on content.
We have:
- About ECI: description of company. Could map to "About the role"? Actually "About the role" is typical heading for role description. But we have "About ECI" which is company overview. Could treat as "About the role"? Might be better to use "About the role" heading and put the description of the role (the hybrid role description). However the posting includes "ECI has an exciting opportunity for an experienced Senior Network Engineer to join our Global Implementations team..." That's role overview. So we can put that under "About the role". The earlier "About ECI" paragraph could be considered company overview; maybe we can include it under same section or maybe we can omit as not required? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company description as well. Could put it under a heading like "About ECI" but we only allowed specific headings list. The instruction says: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should use those headings when appropriate. It doesn't forbid other headings? It says 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. So we need to map content to those headings.
Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content:
- About the role: hybrid role, onsite min 3 days, core hours US working hours, may require outside core hours. Also description of team and purpose. So we can put that.
- Responsibilities: bullet list from "What you will do". That's a list of duties.
- Requirements: maybe "Who you are" includes education, experience, certifications, etc. That's qualifications.
- Qualifications: maybe separate? Could combine. But we need to avoid thin sections. Could put education/experience under Requirements, and technical skills under Skills. Or we could have Requirements (education/experience) and Qualifications (certifications/technical). Let's decide.
- Skills: list of technical skills: CCNP, advance routing/switching, Cisco Nexus, BGP/OSPF, enterprise network design, public cloud, Palo Alto firewalls, FortiGate, Cisco FTD, Cisco traditional/SDWAN routers, catalyst, Nexus switches, communication, interpersonal, self-motivated, attention to detail, analytical, time management.
- Benefits: compensation package: max $140k annually, flexible PTO, health benefit eligibility first of month, life insurance, pet insurance, 401K, etc.
- Pay: we could put salary range under Pay. But Benefits also includes compensation. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into one Benefits section that includes salary and benefits. But they said include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide.
We have specific salary: maximum $140,000 annually. That's specific. So we can have Pay section with that.
Benefits: flexible PTO, health benefit eligibility first of month, life insurance, pet insurance, 401K, etc. That's specific.
Schedule: hybrid role, onsite min 3 days per week, core hours US working hours, may require outside core hours as needed. That's schedule.
Thus we can have sections: About the role, Responsibilities, Requirements (education/experience), Qualifications (certifications/technical), Skills (soft skills?), Benefits, Pay, Schedule. But that's many sections; maybe we can combine some.
We could have:
- About the role (company overview + role overview)
- Responsibilities (list)
- Requirements (education/experience + certifications)
- Skills (technical + soft)
- Benefits (PTO, health, life, pet, 401k)
- Pay (salary max)
- Schedule (hybrid, onsite 3 days, core hours)
That seems reasonable.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, scam warning, duplicated lines, application instructions, navigation, cookie, legal. The posting includes some duplicated culture paragraphs at end; we should deduplicate.
We need to preserve all substantive information. Let's extract.
Original text:
"About ECI ECI is the leading global provider of managed services, cybersecurity, and business transformation for mid-market financial services organizations across the globe. From its unmatched range of services, ECI provides stability, security and improved business performance, freeing clients from technology concerns and enabling them to focus on running their businesses. More than 1,000 customers worldwide with over $3 trillion of assets under management put their trust in ECI. At ECI, we believe success is driven by passion and purpose. Our passion for technology is only surpassed by our commitment to empowering our employees around the world. ECI has an exciting opportunity for an experienced Senior Network Engineer to join our Global Implementations team which is responsible to design and deploy network infrastructures(both on-prem and cloud) for our clients (distributed globally) , ensuring optimal performance, security, and scalability. This is a hybrid role being onsite a minimum of 3 days per week. The core hours will be U.S. working hours but may also require work outside of core hours as needed for projects and client support."
Then "What you will do:" list.
Then "Who you are:" list.
Then "Bonus points if you have:" list.
Then "ECI’s culture is all about connection - connection with our clients, our technology and most importantly with each other. In addition to working with an amazing team around the world, ECI also offers a competitive compensation package and the range for this role is a maximum of $ 140,000 annually with flexible PTO, health benefit eligibility the first of the month, life insurance, pet insurance, 401K and so much more! If you believe you’d be a great fit and are ready for your best job ever, we’d like to hear from you!! Love Your Job, Share Your Technology Passion, Create Your Future Here! ECI’s culture is all about connection - connection with our clients, our technology and most importantly with each other. In addition to working with an amazing team around the world, ECI also offers a competitive compensation package and so much more! If you believe you would be a great fit and are ready for your best job ever, we would like to hear from you!"
We need to remove duplicated culture paragraphs and the motivational fluff like "Love Your Job..." etc. Keep substantive: culture statement maybe not needed? It's somewhat fluff but it's about connection; could be considered boilerplate? It's repeated; but it's not EEO or legal. It's somewhat generic but still part of posting. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture statement is not exactly those categories, but it's somewhat fluff. However it's duplicated; we should keep one instance maybe. But it's not essential to role; but we need to preserve ALL substantive information. Is culture substantive? It's not about role specifics; it's more marketing. Might be considered boilerplate? Not sure. Safer to keep one instance of culture statement as part of About the role maybe.
But we also have "competitive compensation package and the range for this role is a maximum of $ 140,000 annually with flexible PTO, health benefit eligibility the first of the month, life insurance, pet insurance, 401K and so much more!" That's substantive for Pay and Benefits.
Thus we need to extract:
- About ECI: leading global provider... etc. plus the opportunity statement.
- Responsibilities: list of duties.
- Who you are: Bachelor’s Degree..., 5+ years..., CCNP, Advance routing and switching knowledge..., Ability to design enterprise networks., Knowledge and experience in public cloud..., Expert in Palo Alto firewalls..., FortiGate and Cisco FTD experience..., Experience with Cisco traditional and SDWAN routers..., Exceptional written and oral communication skills..., Exceptional interpersonal skills..., Highly self-motivated..., Sharp attention to detail..., Effective time management...
- Bonus points: CCIE a plus, Experience with Sonicwall N/W devices, Financial Services Industry experience.
- Pay/Benefits: maximum $140,000 annually, flexible PTO, health benefit eligibility first of month, life insurance, pet insurance, 401K.
- Schedule: hybrid role, onsite min 3 days per week, core hours US working hours, may require work outside core hours as needed.
We need to avoid filler like "and so much more". We can keep specific items.
Now produce HTML.
We'll use for each section heading.
Inside sections, 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. So we need to map content to those headings.
Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content:
- About the role: hybrid role, onsite min 3 days, core hours US working hours, may require outside core hours. Also description of team and purpose. So we can put that.
- Responsibilities: bullet list from "What you will do". That's a list of duties.
- Requirements: maybe "Who you are" includes education, experience, certifications, etc. That's qualifications.
- Qualifications: maybe separate? Could combine. But we need to avoid thin sections. Could put education/experience under Requirements, and technical skills under Skills. Or we could have Requirements (education/experience) and Qualifications (certifications/technical). Let's decide.
- Skills: list of technical skills: CCNP, advance routing/switching, Cisco Nexus, BGP/OSPF, enterprise network design, public cloud, Palo Alto firewalls, FortiGate, Cisco FTD, Cisco traditional/SDWAN routers, catalyst, Nexus switches, communication, interpersonal, self-motivated, attention to detail, analytical, time management.
- Benefits: compensation package: max $140k annually, flexible PTO, health benefit eligibility first of month, life insurance, pet insurance, 401K, etc.
- Pay: we could put salary range under Pay. But Benefits also includes compensation. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into one Benefits section that includes salary and benefits. But they said include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide.
We have specific salary: maximum $140,000 annually. That's specific. So we can have Pay section with that.
Benefits: flexible PTO, health benefit eligibility first of month, life insurance, pet insurance, 401K, etc. That's specific.
Schedule: hybrid role, onsite min 3 days per week, core hours US working hours, may require outside core hours as needed. That's schedule.
Thus we can have sections: About the role, Responsibilities, Requirements (education/experience), Qualifications (certifications/technical), Skills (soft skills?), Benefits, Pay, Schedule. But that's many sections; maybe we can combine some.
We could have:
- About the role (company overview + role overview)
- Responsibilities (list)
- Requirements (education/experience + certifications)
- Skills (technical + soft)
- Benefits (PTO, health, life, pet, 401k)
- Pay (salary max)
- Schedule (hybrid, onsite 3 days, core hours)
That seems reasonable.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, scam warning, duplicated lines, application instructions, navigation, cookie, legal. The posting includes some duplicated culture paragraphs at end; we should deduplicate.
We need to preserve all substantive information. Let's extract.
Original text:
"About ECI ECI is the leading global provider of managed services, cybersecurity, and business transformation for mid-market financial services organizations across the globe. From its unmatched range of services, ECI provides stability, security and improved business performance, freeing clients from technology concerns and enabling them to focus on running their businesses. More than 1,000 customers worldwide with over $3 trillion of assets under management put their trust in ECI. At ECI, we believe success is driven by passion and purpose. Our passion for technology is only surpassed by our commitment to empowering our employees around the world. ECI has an exciting opportunity for an experienced Senior Network Engineer to join our Global Implementations team which is responsible to design and deploy network infrastructures(both on-prem and cloud) for our clients (distributed globally) , ensuring optimal performance, security, and scalability. This is a hybrid role being onsite a minimum of 3 days per week. The core hours will be U.S. working hours but may also require work outside of core hours as needed for projects and client support."
Then "What you will do:" list.
Then "Who you are:" list.
Then "Bonus points if you have:" list.
Then "ECI’s culture is all about connection - connection with our clients, our technology and most importantly with each other. In addition to working with an amazing team around the world, ECI also offers a competitive compensation package and the range for this role is a maximum of $ 140,000 annually with flexible PTO, health benefit eligibility the first of the month, life insurance, pet insurance, 401K and so much more! If you believe you’d be a great fit and are ready for your best job ever, we’d like to hear from you!! Love Your Job, Share Your Technology Passion, Create Your Future Here! ECI’s culture is all about connection - connection with our clients, our technology and most importantly with each other. In addition to working with an amazing team around the world, ECI also offers a competitive compensation package and so much more! If you believe you would be a great fit and are ready for your best job ever, we would like to hear from you!"
We need to remove duplicated culture paragraphs and the motivational fluff like "Love Your Job..." etc. Keep substantive: culture statement maybe not needed? It's somewhat fluff but it's about connection; could be considered boilerplate? It's repeated; but it's not EEO or legal. It's somewhat generic but still part of posting. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture statement is not exactly those categories, but it's somewhat fluff. However it's duplicated; we should keep one instance maybe. But it's not essential to role; but we need to preserve ALL substantive information. Is culture substantive? It's not about role specifics; it's more marketing. Might be considered boilerplate? Not sure. Safer to keep one instance of culture statement as part of About the role maybe.
But we also have "competitive compensation package and the range for this role is a maximum of $ 140,000 annually with flexible PTO, health benefit eligibility the first of the month, life insurance, pet insurance, 401K and so much more!" That's substantive for Pay and Benefits.
Thus we need to extract:
- About ECI: leading global provider... etc. plus the opportunity statement.
- Responsibilities: list of duties.
- Who you are: Bachelor’s Degree..., 5+ years..., CCNP, Advance routing and switching knowledge..., Ability to design enterprise networks., Knowledge and experience in public cloud..., Expert in Palo Alto firewalls..., FortiGate and Cisco FTD experience..., Experience with Cisco traditional and SDWAN routers..., Exceptional written and oral communication skills..., Exceptional interpersonal skills..., Highly self-motivated..., Sharp attention to detail..., Effective time management...
- Bonus points: CCIE a plus, Experience with Sonicwall N/W devices, Financial Services Industry experience.
- Pay/Benefits: maximum $140,000 annually, flexible PTO, health benefit eligibility first of month, life insurance, pet insurance, 401K.
- Schedule: hybrid role, onsite min 3 days per week, core hours US working hours, may require work outside core hours as needed.
We need to avoid filler like "and so much more". We can keep specific items.
Now produce HTML.
We'll use for each section heading.
Inside sections, use
for prose,
- for lists. We need to ensure we don't repeat job title. Let's craft. Section About the role: combine company overview and role overview. Prose: "ECI is the leading global provider of managed services, cybersecurity, and business transformation for mid-market financial services organizations across the globe. From its unmatched range of services, ECI provides stability, security and improved business performance, freeing clients from technology concerns and enabling them to focus on running their businesses. More than 1,000 customers worldwide with over $3 trillion of assets under management put their trust in ECI. At ECI, we believe success is driven by passion and purpose. Our passion for technology is only surpassed by our commitment to empowering our employees around the world. ECI has an exciting opportunity for an experienced Senior Network Engineer to join our Global Implementations team which is responsible to design and deploy network infrastructures (both on-prem and cloud) for our clients (distributed globally), ensuring optimal performance, security, and scalability." That's fine. Section Responsibilities: list items from "What you will do:". List: - Design, implement, and maintain the client’s local area network (LAN), wide area network (WAN), and wireless network infrastructure. - Provide customer support to clients located across the globe. - Troubleshoot/resolve complex issues and handle service requests for clients related to Cisco routing and switching infrastructure, Cisco Meraki and legacy wireless infrastructure, Palo Alto technologies, Cisco, and Fortinet firewalls. - Collaborate with relevant teams, departments, or external parties to resolve cases that require specialized knowledge or resources. - Serve as the ultimate escalation point for critical network incidents and outages. Lead the response effort, coordinate with cross-functional teams, and drive resolution to minimize downtime and impact on business operations. - Provide technical leadership and guidance to the network services team. Mentor junior team members, share knowledge, and promote best practices for network design, implementation, and troubleshooting. - Research and evaluate emerging technologies, products, and solutions relevant to the organization's strategic objectives. Identify PoC opportunities that align with business needs and technical requirements. - Engage proactively with clients to comprehend their unique network requisites and collaboratively engineer tailored solutions that align with their goals. - Create and maintain network documentation, including network diagrams, configurations, and policies/procedures. Make each as
- . Section Requirements: maybe education/experience. List: - Bachelor’s Degree in related field or equivalent combination of education and experience - 5+ years of relevant work experience with exposure in