Reliability Engineer

Flow Traders is hiring Reliability Engineers to safeguard the production performance of our global trading platform and the technology estate around it. Undetected degradation costs P&L by the minute.

Most of what makes failures smaller, shorter and easier to contain happens before anything breaks. You automate the repetitive parts of triage, keep alerts to the ones that need a human, and close monitoring gaps. Root causes go back to the teams that own them.

When something does break, control of the room is yours. You're first on it: you size it up, decide who is on the call, and run the response as Incident Commander under our Global Incident Management framework. You coordinate and delegate rather than dropping into the debugging, and your decisions hold even when the room is more senior than you.

You'll sit alongside traders, developers, infrastructure and specialist teams, with the standing to push any of them when operational standards slip.

• Automate repeatable triage work so first-line responds faster and more consistently, including alert enrichment, routing, correlation and operational workflows

• Push for monitoring, alerting and visibility where gaps exist

• Track reliability and availability across critical trading applications and the platforms they depend on, and work with users, development teams and IT to find where service levels are degrading

• Call out weak ownership, missed SLAs, poor alerts and ineffective runbooks, and drive the owning teams to fix them

• Triage incoming alerts, issues and escalations, and assess impact, urgency and ownership

• Decide when incident criteria are met, declare the incident, and act as Incident Commander

• Coordinate responders and stakeholders, and keep incident calls focused on facts, mitigation and recovery

• Maintain clear timelines, actions and status updates throughout an incident

• Recover or stabilise systems using approved runbooks, and escalate cleanly through the defined support and development path when the issue goes beyond documented recovery steps

• Perform common operational tasks across adjacent teams where needed

• Support PIR follow-up and recurring issue review

• Hand over cleanly between EMEA, AMER and APAC under one global model, one incident standard, one handover process

• Experience in production operations, SRE, NOC/command centre, trading operations or a similar first-line technical role, ideally in a trading, financial services or other latency-sensitive environment

• Track record of running or coordinating major incidents, and comfort taking command of a call with senior people on it

• Strong triage and prioritisation. You can separate facts from assumptions under time pressure and keep the response moving

• Clear verbal and written communication. Your status updates are readable by a trader and an engineer at the same time

• Strong judgment and escalation discipline. You know when to keep going and when to pull in a specialist

• Willingness to hold the line on process, and to push back when poor operational behaviour creates risk for trading

• Technically broad rather than deep. You need enough understanding of how most teams operate to be useful across domains, not to be the specialist resolver

• Solid Linux and networking fundamentals, and the ability to read alerts, logs, dashboards and symptoms quickly

• Working knowledge of common operational tasks across adjacent teams (application support, infrastructure, connectivity, data)

• Familiarity with incident and observability tooling: PagerDuty or equivalent, Jira Service Management or equivalent, Grafana, Prometheus, log search

• Scripting and automation ability (Python preferred; Bash, Go a plus) applied to triage, enrichment, routing and correlation rather than to product code

• Exposure to containerised and cloud-hosted production systems (Kubernetes, Docker, GCP) is a plus

Six months in, a strong Reliability Engineer here has already made the next incident smaller. They've automated something that used to be manual, retired alerts nobody could act on, and closed a monitoring gap that was costing us detection time. When something does break they are calm under pressure, clear in communication and disciplined in process. They can control a noisy incident without trying to become the specialist resolver, and they know how to use a runbook safely and when to escalate. And they don't let poor operational standards slide when trading is exposed.