Trading Infrastructure Specialist

1What you'd actually do

• Monitoring trading systems around the market open and through the day - checking that market data feeds (live streams of prices from exchanges), order routing and risk systems are connecting and behaving normally, and reacting when something looks wrong
• Handling incidents: a trader reports slow prices or a rejected order, and you work out whether the cause is the network, the exchange, a vendor feed, an application or a configuration change, often with the clock running and money at stake
• Configuring and testing changes - adding a new market or instrument, onboarding a connection to an exchange or broker, updating symbol and product reference data, or deploying a new version of a trading application to a test environment first
• Writing and maintaining scripts and small tools (commonly Python, shell scripting, sometimes SQL) to automate checks, parse log files, compare configurations or generate monitoring alerts
• Working with Linux servers - reading logs, checking processes, disk and memory, looking at network captures or latency measurements to diagnose where delay is being introduced
• Coordinating with exchanges, market data vendors, network providers and internal teams on connectivity testing, certification of new links, and scheduled weekend or out-of-hours changes
• Participating in a support rota, plus disaster recovery and failover tests that are often run at weekends or overnight because markets are closed

2How graduates get in

• Technology graduate schemes at investment banks - the most common structured route. You typically apply to a broad 'technology' or 'engineering' programme and are placed into an infrastructure, production support or platform team, sometimes after rotations
• Direct entry as a junior/associate engineer at proprietary trading firms, market makers, hedge funds and brokerages - these tend to hire in smaller numbers, advertise ad hoc rather than on an annual cycle, and often move quickly through a technical interview process
• Joining a financial technology vendor, exchange or market data provider first (support, implementation or connectivity roles) and moving to a trading firm later - a very common sideways route, and often an easier first job to get
• Starting in general IT infrastructure, Linux systems administration or network engineering outside finance, then moving across once you have solid technical foundations - realistic but usually takes a couple of years
• Summer internships in technology at banks and trading firms, which often convert to graduate offers - the strongest single predictor of getting a place at the larger employers
• Apprenticeship or school-leaver technology programmes at banks, which lead to the same roles without a degree - less common than graduate entry but genuinely available

3What employers ask for

• A degree in computer science, software engineering, electronic engineering, physics, maths or a related numerate/technical subject is the usual expectation. Some employers accept any degree if you can demonstrate real technical ability; others screen fairly strictly on subject
• Grades vary a lot: many bank graduate schemes ask for a 2:1, some ask 2:2 or have no formal cut-off, and several trading firms ignore classification entirely and decide on technical tests. Some still filter on A-level or UCAS points, particularly the larger structured schemes
• Demonstrable hands-on technical experience - personal projects, a placement year, university society work, home lab setups, contributions to open-source. This matters more than coursework at most employers
• Comfort with Linux and at least one scripting language (Python is the most commonly requested) is close to universal. Networking fundamentals (TCP/IP, multicast, latency) are frequently asked about
• No professional exams are required to enter. Vendor certifications in networking, Linux or cloud can help, especially if your degree isn't technical, but they're rarely a condition of hire
• Finance knowledge is usually not required upfront - most employers expect to teach you how markets and order flow work. Some will still ask whether you understand what an order book or a market data feed is, so basic reading pays off

4Skills that matter

5Where it leads

1. First one to three years: learning the estate - which systems exist, how they connect, what breaks and why - while handling incidents with senior support and taking on your own small changes and onboarding tasks.

2. Moving from reactive support to ownership: becoming the go-to person for a particular platform, exchange connection or region, running projects such as migrating a system or adding a new venue. Timelines here vary widely by employer and by how fast the firm is growing.

3. Branching into a specialism: low-latency engineering, market data engineering, site reliability engineering (SRE), network engineering, or moving into software development on trading systems. Many people also move sideways into DevOps or cloud platform roles.

4. Senior individual contributor or team lead - designing infrastructure rather than maintaining it, setting standards, and being escalated to on major incidents. Some firms have a strong technical track that pays well without managing anyone.

5. Longer term, routes include head of trading technology or infrastructure, moving to a vendor or exchange in a technical or client-facing capacity, or - less commonly but it does happen - crossing into a trading, quantitative or product role using the market knowledge picked up along the way.

6Where this varies

The job title covers quite different jobs depending on the employer. At a large investment bank it usually means production support or platform engineering within a big, process-heavy technology function, with formal change control, defined escalation paths and rotations into other teams. At a proprietary trading firm or market maker it is often a small team where you touch everything - hardware, networks, deployment and code - with far less process and much more autonomy, and a strong focus on latency measured in microseconds. At an exchange, broker or technology vendor the emphasis shifts towards client connectivity, onboarding and certification testing. Location matters too: most roles are in London, with clusters in Belfast, Glasgow, Edinburgh, Birmingham and Manchester where banks have operations centres, and those non-London roles are more likely to be support-focused than latency-focused. Hybrid working is common but many firms require more on-site presence than typical tech jobs, because some of the work involves physical infrastructure and close contact with the trading desk.