Lead Network Engineer - Telecommunications
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out Privacy Statement, EEOC Statement, ADA Disclaimer, Sourcing Model, etc. Also remove "Position Type Full time Type Of Hire Experienced (relevant combo of work and education)"? That's metadata; we can fold minor metadata into a short
or drop it. Probably we can include a short paragraph about position type? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a
for Position Type etc. But maybe better to drop it as it's minor. However we need to preserve ALL substantive information; position type is substantive? It's not crucial but maybe we can include a short
at top: "Position Type: Full-time; Hire Type: Experienced." That is minor metadata; we can fold into a short
. Let's do that.
Now sections:
- About the role: content from "About The Role" paragraph(s). It includes: "We are FIS... If you’re ready...". Actually "About The Role" includes description: "The FIS Telecommunications Team is hiring a Senior Lead Network Engineer who is responsible for developing Telecom strategy, including Global backbone and network aggregation topology, evaluation of emerging Telecom products and services, establishing Telecom contractual standards, and financial savings opportunities. This person will help to coach and mentoring engineers, drive technical rigor, and leading complex problem solving and escalation efforts related to circuit design, provisioning, and implementation. Responsibilities span Layers 1, 2 and 3 transport, modern optical and IP based architectures, dark fiber and wavelength services, global aggregation, colocation and interconnection strategy, and wireless and satellite connectivity solutions. This includes leading initiatives to decommission legacy technologies while enabling scalable, software driven and high bandwidth network designs. The Senior Lead Network Engineer will work closely with Data and Voice Engineering, Infrastructure Architecture, Product and Project Management, Information Security, Finance, and Data Center Operations to scope, plan, and execute large scale transport and network initiatives. The role also partners closely with Supply Chain to define telecom vendor strategy, support RFPs, evaluate carrier performance, and optimize cost structure."
We can put that in
under
About the role
.
- About the Team: maybe we can treat as separate section? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About The Team" is not in list but could be considered part of About the role? However we can include as a separate section if we think it's substantive. The instruction: "Prefer a few substantive sections over many thin ones." Might combine About the role and About the Team into one? But they are distinct. However the allowed headings list does not include About The Team. It only lists those specific headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. So we should map content to those headings. About the Team could be folded into About the role or maybe omitted? But we must preserve ALL substantive information. If we omit About the Team, we lose info. So we need to include it somewhere. Perhaps we can treat About the Team as part of About the role (since it's about the team). Or we could create a section "About the Team" but that's not in the list; maybe it's okay as it's still a section heading. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples; you can use other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." So we could add About the Team as its own heading.
But we also have "What You Will Be Doing" which is essentially Responsibilities. So we can map that to Responsibilities heading.
We have Required Qualifications and Preferred Qualifications -> can map to Requirements (maybe combine) or Qualifications. The list includes Requirements and Qualifications as separate possible headings. We could have Requirements for required qualifications, and Qualifications for preferred? Or combine both under Requirements. But we have both headings available; we could use Requirements for required, and Qualifications for preferred. That seems logical.
Skills: we could extract skills from responsibilities or qualifications? Might be thin. Could omit if not substantive.
Benefits: from "What We Offer You" includes: Opportunities to innovate in fintech, Inclusive and diverse team atmosphere, Professional and personal development, Resources to contribute to your community, Competitive salary and benefits. That's benefits.
Pay: not specified; we should not create Pay section unless posting actually states them. It does not state specific pay, only "Competitive salary and benefits". That's not a specific pay figure. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." For Benefits, we have statements about benefits, so we can include Benefits section. For Pay, we do not have specific pay, so we should not create Pay section. Schedule: not stated; we have Position Type Full time, but schedule not specified; we could maybe include Schedule if we have full-time? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Position Type Full time, which implies schedule full-time. But is that enough? It says "Schedule" maybe they expect something like "Full-time". The posting says "Position Type Full time". That's schedule info. So we could include Schedule section with "Full-time". However we need to avoid filler like "not specified". It's specified as Full time. So we can include Schedule.
But we also have "Type Of Hire Experienced (relevant combo of work and education)". That's not schedule.
Thus we can include Schedule: Full-time.
Now Benefits: we have bullet list from "What We Offer You". We'll make - .
Now Responsibilities: from "What You Will Be Doing" which is a list of duties. We'll make
- .
Now About the role: we have paragraph.
Now About the Team: we could include as separate section or fold into About the role. Let's decide to include as separate section "About the Team". It's substantive.
Now Requirements: Required Qualifications list.
Now Qualifications: Preferred Qualifications list.
Now Skills: maybe we can extract from responsibilities or qualifications like "Strong verbal, written, and interpersonal communication skills", "Proven ability to lead technical problem solving", etc. Those are in Preferred Qualifications. Could treat as Skills. But we already have Qualifications for preferred. Might be redundant. Better to not create Skills if it's thin. We'll omit Skills.
Now we need to output only HTML fragment, no /, no markdown.
Let's construct:
Position Type: Full-time; Hire Type: Experienced.
About the role
... (the paragraph)
About the team
... (the team paragraph)
Responsibilities
- Lead and mentor Network Circuit Engineering team members across circuit design, carrier selection, ordering, provisioning, implementation, carrier escalations, and inventory accuracy
- Provide technical leadership and design expertise for large scale network initiatives requiring complex Layer 1 transport diversity, resiliency, and route analysis
- Design and support modern transport solutions including high-capacity optical services, 100G wavelengths to support US and global backbone aggregation
- Support SD-WAN and hybrid WAN architectures, including MPLS, carrier Ethernet, internet underlay, and secure cloud connectivity
- Design and implement connectivity for cloud and interconnection services including colocation environments, cloud on ramps, and carrier neutral facilities
- Lead deployment and support of wireless and alternative access technologies including LTE, private wireless, satellite-based connectivity, and emerging mobility solutions
- Own carrier escalations and service delivery risk management to meet business timelines and resiliency objectives
- Partner with Supply Chain on RFP development, contract discussions, vendor product strategy, and financial analysis
- Drive legacy technology decommissioning efforts, including TDM retirement and migration to modern transport architectures
- Ensure accurate documentation, circuit inventory, and design artifacts across inventory, ordering, and network management systems
- Demonstrate a high level of professionalism, accountability, and commitment to delivering secure, resilient, and scalable network solutions on time
Requirements
- 10+ years of experience leading or providing senior-level support to a network provisioning or circuit engineering team
- 10+ years of Network Engineering experience, or equivalent demonstrated through one or a combination of the following~ work experience, training, military experience, education
- 10+ years of experience working directly with telecom carriers, including escalations and service delivery management
- 10+ years of experience in network operations, network engineering, or a combination of both
- Experience supporting modern transport technologies including carrier Ethernet, optical wavelength services, and backbone connectivity
- Proficiency with Microsoft Office tools including Excel, PowerPoint, Visio, SharePoint and Word
- Experience with Ethernet based networking and transport services
- Experience using mapping or route visualization tools for transport diversity analysis
Qualifications
- Strong verbal, written, and interpersonal communication skills
- Proven ability to lead technical problem solving in a fast paced, highly regulated environment
- Demonstrated experience coaching, mentoring, or providing technical leadership to engineering teams
- Knowledge of SD-WAN, hybrid WAN, and secure connectivity architecture
- Knowledge of MPLS, carrier Ethernet, and internet-based transport solutions
- Experience with modern optical networking concepts including IP over DWDM and high-capacity wavelength services
- Familiarity with cloud connectivity, colocation environments, and interconnection ecosystems
- Understanding of wireless and satellite-based access technologies
- Strong understanding of telecom vendor ecosystems, network diversity strategies, and resiliency design
- Experience with circuit engineering lifecycle management including design, sourcing, deployment, testing, and documentation
- Experience utilizing Calero / Verasmart TEM application
- Experience utilizing Service Now
Benefits
- Opportunities to innovate in fintech
- Inclusive and diverse team atmosphere
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out Privacy Statement, EEOC Statement, ADA Disclaimer, Sourcing Model, etc. Also remove "Position Type Full time Type Of Hire Experienced (relevant combo of work and education)"? That's metadata; we can fold minor metadata into a short
or drop it. Probably we can include a short paragraph about position type? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a
for Position Type etc. But maybe better to drop it as it's minor. However we need to preserve ALL substantive information; position type is substantive? It's not crucial but maybe we can include a short
at top: "Position Type: Full-time; Hire Type: Experienced." That is minor metadata; we can fold into a short
. Let's do that. Now sections: - About the role: content from "About The Role" paragraph(s). It includes: "We are FIS... If you’re ready...". Actually "About The Role" includes description: "The FIS Telecommunications Team is hiring a Senior Lead Network Engineer who is responsible for developing Telecom strategy, including Global backbone and network aggregation topology, evaluation of emerging Telecom products and services, establishing Telecom contractual standards, and financial savings opportunities. This person will help to coach and mentoring engineers, drive technical rigor, and leading complex problem solving and escalation efforts related to circuit design, provisioning, and implementation. Responsibilities span Layers 1, 2 and 3 transport, modern optical and IP based architectures, dark fiber and wavelength services, global aggregation, colocation and interconnection strategy, and wireless and satellite connectivity solutions. This includes leading initiatives to decommission legacy technologies while enabling scalable, software driven and high bandwidth network designs. The Senior Lead Network Engineer will work closely with Data and Voice Engineering, Infrastructure Architecture, Product and Project Management, Information Security, Finance, and Data Center Operations to scope, plan, and execute large scale transport and network initiatives. The role also partners closely with Supply Chain to define telecom vendor strategy, support RFPs, evaluate carrier performance, and optimize cost structure." We can put that in
under
About the role
. - About the Team: maybe we can treat as separate section? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About The Team" is not in list but could be considered part of About the role? However we can include as a separate section if we think it's substantive. The instruction: "Prefer a few substantive sections over many thin ones." Might combine About the role and About the Team into one? But they are distinct. However the allowed headings list does not include About The Team. It only lists those specific headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. So we should map content to those headings. About the Team could be folded into About the role or maybe omitted? But we must preserve ALL substantive information. If we omit About the Team, we lose info. So we need to include it somewhere. Perhaps we can treat About the Team as part of About the role (since it's about the team). Or we could create a section "About the Team" but that's not in the list; maybe it's okay as it's still a section heading. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples; you can use other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." So we could add About the Team as its own heading.
But we also have "What You Will Be Doing" which is essentially Responsibilities. So we can map that to Responsibilities heading.
We have Required Qualifications and Preferred Qualifications -> can map to Requirements (maybe combine) or Qualifications. The list includes Requirements and Qualifications as separate possible headings. We could have Requirements for required qualifications, and Qualifications for preferred? Or combine both under Requirements. But we have both headings available; we could use Requirements for required, and Qualifications for preferred. That seems logical.
Skills: we could extract skills from responsibilities or qualifications? Might be thin. Could omit if not substantive.
Benefits: from "What We Offer You" includes: Opportunities to innovate in fintech, Inclusive and diverse team atmosphere, Professional and personal development, Resources to contribute to your community, Competitive salary and benefits. That's benefits.
Pay: not specified; we should not create Pay section unless posting actually states them. It does not state specific pay, only "Competitive salary and benefits". That's not a specific pay figure. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." For Benefits, we have statements about benefits, so we can include Benefits section. For Pay, we do not have specific pay, so we should not create Pay section. Schedule: not stated; we have Position Type Full time, but schedule not specified; we could maybe include Schedule if we have full-time? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Position Type Full time, which implies schedule full-time. But is that enough? It says "Schedule" maybe they expect something like "Full-time". The posting says "Position Type Full time". That's schedule info. So we could include Schedule section with "Full-time". However we need to avoid filler like "not specified". It's specified as Full time. So we can include Schedule.
But we also have "Type Of Hire Experienced (relevant combo of work and education)". That's not schedule.
Thus we can include Schedule: Full-time.
Now Benefits: we have bullet list from "What We Offer You". We'll make - .
Now Responsibilities: from "What You Will Be Doing" which is a list of duties. We'll make
- .
Now About the role: we have paragraph.
Now About the Team: we could include as separate section or fold into About the role. Let's decide to include as separate section "About the Team". It's substantive.
Now Requirements: Required Qualifications list.
Now Qualifications: Preferred Qualifications list.
Now Skills: maybe we can extract from responsibilities or qualifications like "Strong verbal, written, and interpersonal communication skills", "Proven ability to lead technical problem solving", etc. Those are in Preferred Qualifications. Could treat as Skills. But we already have Qualifications for preferred. Might be redundant. Better to not create Skills if it's thin. We'll omit Skills.
Now we need to output only HTML fragment, no /, no markdown.
Let's construct:
Position Type: Full-time; Hire Type: Experienced.
About the role
... (the paragraph)
About the team
... (the team paragraph)
Responsibilities
- Lead and mentor Network Circuit Engineering team members across circuit design, carrier selection, ordering, provisioning, implementation, carrier escalations, and inventory accuracy
- Provide technical leadership and design expertise for large scale network initiatives requiring complex Layer 1 transport diversity, resiliency, and route analysis
- Design and support modern transport solutions including high-capacity optical services, 100G wavelengths to support US and global backbone aggregation
- Support SD-WAN and hybrid WAN architectures, including MPLS, carrier Ethernet, internet underlay, and secure cloud connectivity
- Design and implement connectivity for cloud and interconnection services including colocation environments, cloud on ramps, and carrier neutral facilities
- Lead deployment and support of wireless and alternative access technologies including LTE, private wireless, satellite-based connectivity, and emerging mobility solutions
- Own carrier escalations and service delivery risk management to meet business timelines and resiliency objectives
- Partner with Supply Chain on RFP development, contract discussions, vendor product strategy, and financial analysis
- Drive legacy technology decommissioning efforts, including TDM retirement and migration to modern transport architectures
- Ensure accurate documentation, circuit inventory, and design artifacts across inventory, ordering, and network management systems
- Demonstrate a high level of professionalism, accountability, and commitment to delivering secure, resilient, and scalable network solutions on time
Requirements
- 10+ years of experience leading or providing senior-level support to a network provisioning or circuit engineering team
- 10+ years of Network Engineering experience, or equivalent demonstrated through one or a combination of the following~ work experience, training, military experience, education
- 10+ years of experience working directly with telecom carriers, including escalations and service delivery management
- 10+ years of experience in network operations, network engineering, or a combination of both
- Experience supporting modern transport technologies including carrier Ethernet, optical wavelength services, and backbone connectivity
- Proficiency with Microsoft Office tools including Excel, PowerPoint, Visio, SharePoint and Word
- Experience with Ethernet based networking and transport services
- Experience using mapping or route visualization tools for transport diversity analysis
Qualifications
- Strong verbal, written, and interpersonal communication skills
- Proven ability to lead technical problem solving in a fast paced, highly regulated environment
- Demonstrated experience coaching, mentoring, or providing technical leadership to engineering teams
- Knowledge of SD-WAN, hybrid WAN, and secure connectivity architecture
- Knowledge of MPLS, carrier Ethernet, and internet-based transport solutions
- Experience with modern optical networking concepts including IP over DWDM and high-capacity wavelength services
- Familiarity with cloud connectivity, colocation environments, and interconnection ecosystems
- Understanding of wireless and satellite-based access technologies
- Strong understanding of telecom vendor ecosystems, network diversity strategies, and resiliency design
- Experience with circuit engineering lifecycle management including design, sourcing, deployment, testing, and documentation
- Experience utilizing Calero / Verasmart TEM application
- Experience utilizing Service Now
Benefits
- Opportunities to innovate in fintech
- Inclusive and diverse team atmosphere
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples; you can use other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." So we could add About the Team as its own heading.
But we also have "What You Will Be Doing" which is essentially Responsibilities. So we can map that to Responsibilities heading.
We have Required Qualifications and Preferred Qualifications -> can map to Requirements (maybe combine) or Qualifications. The list includes Requirements and Qualifications as separate possible headings. We could have Requirements for required qualifications, and Qualifications for preferred? Or combine both under Requirements. But we have both headings available; we could use Requirements for required, and Qualifications for preferred. That seems logical.
Skills: we could extract skills from responsibilities or qualifications? Might be thin. Could omit if not substantive.
Benefits: from "What We Offer You" includes: Opportunities to innovate in fintech, Inclusive and diverse team atmosphere, Professional and personal development, Resources to contribute to your community, Competitive salary and benefits. That's benefits.
Pay: not specified; we should not create Pay section unless posting actually states them. It does not state specific pay, only "Competitive salary and benefits". That's not a specific pay figure. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." For Benefits, we have statements about benefits, so we can include Benefits section. For Pay, we do not have specific pay, so we should not create Pay section. Schedule: not stated; we have Position Type Full time, but schedule not specified; we could maybe include Schedule if we have full-time? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Position Type Full time, which implies schedule full-time. But is that enough? It says "Schedule" maybe they expect something like "Full-time". The posting says "Position Type Full time". That's schedule info. So we could include Schedule section with "Full-time". However we need to avoid filler like "not specified". It's specified as Full time. So we can include Schedule.
But we also have "Type Of Hire Experienced (relevant combo of work and education)". That's not schedule.
Thus we can include Schedule: Full-time.
Now Benefits: we have bullet list from "What We Offer You". We'll make - .
Now Responsibilities: from "What You Will Be Doing" which is a list of duties. We'll make
- .
Now About the role: we have paragraph.
Now About the Team: we could include as separate section or fold into About the role. Let's decide to include as separate section "About the Team". It's substantive.
Now Requirements: Required Qualifications list.
Now Qualifications: Preferred Qualifications list.
Now Skills: maybe we can extract from responsibilities or qualifications like "Strong verbal, written, and interpersonal communication skills", "Proven ability to lead technical problem solving", etc. Those are in Preferred Qualifications. Could treat as Skills. But we already have Qualifications for preferred. Might be redundant. Better to not create Skills if it's thin. We'll omit Skills.
Now we need to output only HTML fragment, no /, no markdown.
Let's construct:
Position Type: Full-time; Hire Type: Experienced.
About the role
... (the paragraph)
About the team
... (the team paragraph)
Responsibilities
- Lead and mentor Network Circuit Engineering team members across circuit design, carrier selection, ordering, provisioning, implementation, carrier escalations, and inventory accuracy
- Provide technical leadership and design expertise for large scale network initiatives requiring complex Layer 1 transport diversity, resiliency, and route analysis
- Design and support modern transport solutions including high-capacity optical services, 100G wavelengths to support US and global backbone aggregation
- Support SD-WAN and hybrid WAN architectures, including MPLS, carrier Ethernet, internet underlay, and secure cloud connectivity
- Design and implement connectivity for cloud and interconnection services including colocation environments, cloud on ramps, and carrier neutral facilities
- Lead deployment and support of wireless and alternative access technologies including LTE, private wireless, satellite-based connectivity, and emerging mobility solutions
- Own carrier escalations and service delivery risk management to meet business timelines and resiliency objectives
- Partner with Supply Chain on RFP development, contract discussions, vendor product strategy, and financial analysis
- Drive legacy technology decommissioning efforts, including TDM retirement and migration to modern transport architectures
- Ensure accurate documentation, circuit inventory, and design artifacts across inventory, ordering, and network management systems
- Demonstrate a high level of professionalism, accountability, and commitment to delivering secure, resilient, and scalable network solutions on time
Requirements
- 10+ years of experience leading or providing senior-level support to a network provisioning or circuit engineering team
- 10+ years of Network Engineering experience, or equivalent demonstrated through one or a combination of the following~ work experience, training, military experience, education
- 10+ years of experience working directly with telecom carriers, including escalations and service delivery management
- 10+ years of experience in network operations, network engineering, or a combination of both
- Experience supporting modern transport technologies including carrier Ethernet, optical wavelength services, and backbone connectivity
- Proficiency with Microsoft Office tools including Excel, PowerPoint, Visio, SharePoint and Word
- Experience with Ethernet based networking and transport services
- Experience using mapping or route visualization tools for transport diversity analysis
Qualifications
- Strong verbal, written, and interpersonal communication skills
- Proven ability to lead technical problem solving in a fast paced, highly regulated environment
- Demonstrated experience coaching, mentoring, or providing technical leadership to engineering teams
- Knowledge of SD-WAN, hybrid WAN, and secure connectivity architecture
- Knowledge of MPLS, carrier Ethernet, and internet-based transport solutions
- Experience with modern optical networking concepts including IP over DWDM and high-capacity wavelength services
- Familiarity with cloud connectivity, colocation environments, and interconnection ecosystems
- Understanding of wireless and satellite-based access technologies
- Strong understanding of telecom vendor ecosystems, network diversity strategies, and resiliency design
- Experience with circuit engineering lifecycle management including design, sourcing, deployment, testing, and documentation
- Experience utilizing Calero / Verasmart TEM application
- Experience utilizing Service Now
Benefits
- Opportunities to innovate in fintech
- Inclusive and diverse team atmosphere
- .
Now About the role: we have paragraph.
Now About the Team: we could include as separate section or fold into About the role. Let's decide to include as separate section "About the Team". It's substantive.
Now Requirements: Required Qualifications list.
Now Qualifications: Preferred Qualifications list.
Now Skills: maybe we can extract from responsibilities or qualifications like "Strong verbal, written, and interpersonal communication skills", "Proven ability to lead technical problem solving", etc. Those are in Preferred Qualifications. Could treat as Skills. But we already have Qualifications for preferred. Might be redundant. Better to not create Skills if it's thin. We'll omit Skills.
Now we need to output only HTML fragment, no /, no markdown.
Let's construct:
Position Type: Full-time; Hire Type: Experienced.
About the role
... (the paragraph)
About the team
... (the team paragraph)
Responsibilities
- Lead and mentor Network Circuit Engineering team members across circuit design, carrier selection, ordering, provisioning, implementation, carrier escalations, and inventory accuracy
- Provide technical leadership and design expertise for large scale network initiatives requiring complex Layer 1 transport diversity, resiliency, and route analysis
- Design and support modern transport solutions including high-capacity optical services, 100G wavelengths to support US and global backbone aggregation
- Support SD-WAN and hybrid WAN architectures, including MPLS, carrier Ethernet, internet underlay, and secure cloud connectivity
- Design and implement connectivity for cloud and interconnection services including colocation environments, cloud on ramps, and carrier neutral facilities
- Lead deployment and support of wireless and alternative access technologies including LTE, private wireless, satellite-based connectivity, and emerging mobility solutions
- Own carrier escalations and service delivery risk management to meet business timelines and resiliency objectives
- Partner with Supply Chain on RFP development, contract discussions, vendor product strategy, and financial analysis
- Drive legacy technology decommissioning efforts, including TDM retirement and migration to modern transport architectures
- Ensure accurate documentation, circuit inventory, and design artifacts across inventory, ordering, and network management systems
- Demonstrate a high level of professionalism, accountability, and commitment to delivering secure, resilient, and scalable network solutions on time
Requirements
- 10+ years of experience leading or providing senior-level support to a network provisioning or circuit engineering team
- 10+ years of Network Engineering experience, or equivalent demonstrated through one or a combination of the following~ work experience, training, military experience, education
- 10+ years of experience working directly with telecom carriers, including escalations and service delivery management
- 10+ years of experience in network operations, network engineering, or a combination of both
- Experience supporting modern transport technologies including carrier Ethernet, optical wavelength services, and backbone connectivity
- Proficiency with Microsoft Office tools including Excel, PowerPoint, Visio, SharePoint and Word
- Experience with Ethernet based networking and transport services
- Experience using mapping or route visualization tools for transport diversity analysis
Qualifications
- Strong verbal, written, and interpersonal communication skills
- Proven ability to lead technical problem solving in a fast paced, highly regulated environment
- Demonstrated experience coaching, mentoring, or providing technical leadership to engineering teams
- Knowledge of SD-WAN, hybrid WAN, and secure connectivity architecture
- Knowledge of MPLS, carrier Ethernet, and internet-based transport solutions
- Experience with modern optical networking concepts including IP over DWDM and high-capacity wavelength services
- Familiarity with cloud connectivity, colocation environments, and interconnection ecosystems
- Understanding of wireless and satellite-based access technologies
- Strong understanding of telecom vendor ecosystems, network diversity strategies, and resiliency design
- Experience with circuit engineering lifecycle management including design, sourcing, deployment, testing, and documentation
- Experience utilizing Calero / Verasmart TEM application
- Experience utilizing Service Now
Benefits
- Opportunities to innovate in fintech
- Inclusive and diverse team atmosphere