> Markdown version of [/jobs/ext/4567977-senior-network-engineer](https://www.wearedevelopers.com/jobs/ext/4567977-senior-network-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior Network Engineer

- **Company:** Trumid Financial LLC
- **Location:** New York, NY, United States
- **Experience:** Expert
- **Salary:** $225,000 - $250,000
- **Contract:** Permanent contract
- **Skills:** Amazon Web Services, Amazon Elastic Compute Cloud, Application Layers, Border Gateway Protocol, Cloud Computing, Data Centers, Domain Name System (DNS), Firmware, HAProxy, Networking Hardware, Virtual Private Networks (VPN), Network Architecture, Network Load Balancing, Routing, Nginx, Peering, Ansible, Prometheus, Data Logging, Google Cloud, Load Balancing, Istio, Grafana, Firewalls (Computer Science), Amazon Virtual Private Cloud (VPC), Git, Git Flow, Kubernetes, Terraform, Open Network Automation Platform, Cisco
- **Published:** November 4, 2026
- **Apply:** https://www.careerbuilder.com/job-details/senior-network-engineer-new-york-ny--d894dc4e-407c-4a94-ac1f-eae9be2bea31

## About the Role

Network Architecture/Engineering, Finance, Fixed Income Investments, Trading Platforms, Sales, Trading/Stockbroking, Product Development, Consumer Market Share, Business Model, Team Player, * Seven or more years running production networks that include physical gear: routing and switching, BGP, firewalls, circuits and cross-connects.

 * Real cloud networking depth in AWS or GCP: VPC design, transit gateways and peering, network load balancers, DNS, hybrid connectivity.
 * The automation habit. If you've done it twice by hand, you script it; your configs live in Git and your changes go through review.
 * Working fluency at the application layer of delivery: L4-L7 load balancing (HAProxy, NGINX, or Envoy), TLS termination, health checking - and enough Kubernetes to operate ingress confidently.
 * Reliability instincts: you would rather rehearse a failover on a quiet Tuesday than discover one during an incident.
 * Clear writing and the ability to work directly with clients' network teams.

Nice to have.

 * Experience with:
 * Envoy or another service mesh in production; Kubernetes ingress at scale.
 * Cisco IOS-XE fleets, Palo Alto/Panorama, or network source-of-truth tooling (Infrahub, NetBox, Nautobot).
 * Prometheus/Grafana/ELK-style observability stacks.

## Description

You'd join the networking side of our SRE team, working alongside experienced network engineers. Some of what you'd walk into:

 * A live migration of our trading edge onto HAProxy Kubernetes Ingress Controller - cut over in production one elastic IP at a time, each step reversible, each step qualified by synthetic trading traffic before real clients ride it.
 * A network device fleet headed for full config-as-code: version-controlled, CI-validated configuration, centralized AAA, and a proper source of truth with IPAM.
 * Client-connectivity request load that we are deliberately engineering away - standardized intake, per-client connectivity dashboards, and eventually self-service for the common low-risk changes. Your job is to automate this work out of existence, not to absorb it.

What you'll do?

 * Own reliability across the full request delivery path - edge network gear, DNS, load balancing, service mesh - spanning our data centers, AWS, and GCP.
 * Drive network automation: config-as-code (Ansible, Terraform, GitOps) with CI validation, a network source of truth with IPAM, and changes that are reviewed, repeatable, and reversible.
 * Find single points of failure on critical paths and retire them; design and run the failover drills that prove they're gone.
 * Engineer client connectivity - circuits, VPNs, cross-connects, FIX network paths - and build the workflows and dashboards that turn it from interrupt work into a product.
 * Build network observability with the rest of SRE: streaming device telemetry, syslog into our logging stack, and full-path alerting so we detect faults before clients report them.
 * Harden the fleet: firmware currency, centralized AAA tied to our identity provider, control-plane protection, firewall policy as code.
 * Share a sane, deliberately interrupt-contained on-call rotation with the rest of the team.