Network Engineer - Trading Infrastructure

Raven is a proprietary crypto market-making and high-frequency trading firm. We trade spot, perpetuals, and prediction markets with dedicated low-latency infrastructure across eight major trading regions.

We hire competitive individuals and natural problem solvers with a record of ranking at something hard, whether competitive programming, games, or mathematics, who treat an unfamiliar problem as a challenge rather than an obstacle. 

We can teach markets; we cannot teach drive. We build our own stack end to end, from connectivity and pricing through execution, monitoring, and research data.

We hire on aptitude, judgment, and evidence of self-driven learning rather than years served, and we expect output well above average.We run a global, latency-critical trading network. Our multi-region, multi-cloud estate connects trading systems to exchanges across the US, Europe, and Asia over private circuits, carrier links, and cross-connects, with every path held to an explicit RTT budget. It is all defined as code, with automation we write ourselves.You will ramp onto owning regions and services, not ticketed tasks, and your changes reach infrastructure carrying live traffic. Nothing ships that you cannot explain line by line and defend in review. Do that consistently and you will grow faster than most places would let you.You are not expected to know our whole stack on day one. You are expected to be comfortable in a terminal, unafraid of Linux internals, ruthless about verifying your own output, careful with production, and genuinely curious about how packets get from A to B.

• Changes across our estate as code, from a single firewall rule to a new server, subnet, peering entry, or small reusable module, reviewing every plan before it applies and never introducing hidden drift
• DNS, firewall rules, and SSH access staying accurate as servers come and go, reconciled from a single source of truth
• Day-to-day operation of the automation that switches traffic between private circuits and cloud peering based on link health
• Latency and reachability checks against our documented RTT targets, and packet capture when you need to prove what actually left and arrived
• Host-level Linux tuning under a senior's guidance, kernel network parameters, NIC settings, IRQ affinity, CPU pinning,baked into our bootstrap scripts so it stays reproducible
• Bootstrap, monitoring, and blockchain-node scripts you improve rather than merely maintain, the runbooks that keep the next person oriented, and the next thing worth automating

‍

• Working knowledge of Linux - shell, services, filesystems, permissions, and reading logs when something breaks
• Enough scripting to automate anything you would otherwise repeat, and the patience to read code and config you did not write
• The networking basics - IP/CIDR, subnets, routing tables, TCP versus UDP, DNS, TLS, and firewalls - plus curiosity about the layers underneath
• Enough packet-capture literacy to tell "the request never left" from "we got no reply"
• Some hands-on time with a cloud platform, even if only on your own projects
• Evidence you teach yourself hard things, whether a home lab, a personal project, or a competitive result you are proud of
• Care and humility around production systems. You verify rather than assume, read before you write, and ask early rather than guess
• Fluent English. It is the working language across both offices

‍

- Sofia (Bulgaria) or Milan (Italy), with no preference between them. Whichever city the right person is in 
- In office, not remote
- Crypto trades around the clock. You will share a sane on-call rotation with the team that owns these systems