Network Engineer

About the role

The Opportunity

You'll own the network infrastructure that connects Nascent's trading systems to exchanges, colocations, and internal platforms — the physical and logical fabric that every microsecond of execution depends on. This is a hands-on build-and-operate role: you'll design low-latency network topologies, manage colocation cross-connects and exchange connectivity, maintain precision time synchronization, and keep firewall and routing policy tight. You'll work alongside systems engineers, SREs, and quant infrastructure teams who treat deterministic performance as a first-class engineering discipline.

This isn't a ticket-queue seat inside a large NOC. You'll be one of two network engineers with direct ownership over architecture decisions, vendor relationships, and the tooling you build to monitor and automate the stack — designing connectivity from scratch, not just maintaining what someone else built. The problems are real: packet captures at the switch port, PTP drift investigations, firewall policy reviews that directly affect trade flow — and you'll have the autonomy to solve them end to end. This position must be geographically located within +/- 3 hours EST.

Responsibilities

- Own colocation connectivity: cross-connects, exchange feeds, and carrier relationships across production colo facilities.

- Design and maintain low-latency L2/L3 network topologies for trading infrastructure.

- Configure, troubleshoot, and optimize BGP and OSPF routing in production.

- Maintain precision time synchronization (PTP / IEEE 1588) across trading and infrastructure systems.

- Manage firewall policy (Cisco ASA, Palo Alto, or equivalent) — changes that directly affect production traffic paths.

- Write Python tooling for network automation, configuration management, and operational monitoring.

- Perform packet capture and protocol-level troubleshooting (tcpdump, Wireshark).

- Build and maintain runbooks, network diagrams, and infrastructure documentation.

- Participate in the on-call rotation and own incidents end to end, from triage through post-mortem.

About you

- You've worked in latency-sensitive, colocation, or trading environments — you understand why microseconds matter and how network decisions land on execution.

- You design infrastructure from scratch rather than only operating what someone else built.

- You script your way out of repetitive work; automation is instinct, not an afterthought.

- You own incidents end to end — you don't escalate and wait, you dig in until it's resolved.

- You're comfortable as one of two network engineers: small team, real ownership, nowhere to hide.

- You treat on-call as part of the craft, not an imposition.

- You translate network decisions into language systems engineers, SREs, and quant teams can act on.

Preferred experience