Trade Platform Operations Lead

Trade Platform Operations Lead

Fully remote · Reports to CEO (transitioning to CTO once baseline is established) · Hands-on team lead with hiring authority

A broker's MT4/MT5 operation has outgrown its outsourced model — the incident rate is costing real money, no baseline metrics exist yet, and the person who fixes that reports directly to the CEO from day one.

This is a turnaround-and-build seat, not a maintenance role. Platform operations are currently managed externally, and that arrangement has reached its limit: client-facing incidents are frequent enough to cause direct financial losses, and the business has no instrumented view of exactly how frequent. The first act of authority here is to find out — instrument the infrastructure, establish the first reliable uptime baseline this business has ever had, and own that number as the foundation for everything that follows.

From there, the mandate is to bring MT4/MT5 fully in-house: build the monitoring stack, design the recovery playbooks, hire and structure a small team with genuine 24/7 timezone coverage, and manage the vendor relationships (MetaQuotes, Microsoft, others) that make independent operation sustainable. The proprietary TradingView-based platform is already owned internally — MT4/MT5 is the open problem.

What makes this unusual is not the scope alone. It is that the scope comes with direct CEO reporting and board-level visibility for as long as the recovery work requires it. Most roles offer one or the other: the autonomy to build, or the seniority of the audience watching you do it. This one offers both — which is what makes the decisions consequential rather than just interesting.

Why this beats the seat you're in now

- Zero-baseline mandate. There are no inherited metrics to defend and no legacy process to preserve. You define what good looks like, instrument it yourself, and own the improvement curve.
- CEO air cover from day one. Platform reliability is a board-level priority here, not an IT ticket. You will have the organisational weight behind you to make decisions that stick.
- Your bonus is wired to the outcome. The performance component is tied directly to uptime improvement and incident reduction targets set at onboarding — no ambiguity about whether your work counts.
- Genuinely remote, no asterisks. No location requirement, no relocation expectation, no timezone constraint. The business means it.
- You build it, then you lead it. The person who establishes this function and hits the reliability targets is the natural long-term head of platform operations — with the team, the tooling, and the track record already in place.
- The problem is hard and the feedback loop is short. Within two quarters you will know whether you've moved the needle. There is no version of this role where your contribution is invisible.

This is for you if

- You are already managing MT4/MT5 server infrastructure for a broker or prop firm — hands-on, at the infrastructure level — and you know exactly what a production crisis looks like from the inside.
- You have built or significantly improved a monitoring and incident-response regime: playbooks, preventive maintenance, observability tooling (Grafana, Prometheus, Datadog, or equivalent), and the discipline to make it stick across a team.
- You have run, or are ready to run, a small 24/7 ops team — timezone planning, shift resilience, no single points of failure.
- You are frustrated by the ceiling of your current setup: inherited process, limited authority, or a reliability problem you can see but cannot fully own.
- You are comfortable starting without a playbook — diagnosing first, then building — and you find that energising rather than unsettling.
- You are drawn to a role where the first deliverable is the truth: an honest picture of how bad it is, before anything else.

Your first year

The first 30 days are about instrumentation: you get MT4/MT5 monitored to the point where the business has its first real uptime baseline. From there, the work splits into two tracks running in parallel — reducing client-facing incidents fast enough to stop the financial bleeding, and building the team and processes that make the improvement durable. By mid-year you are running a structured 24/7 operation with coverage that does not depend on any one person, including you. You are also an active participant in the cross-functional network access workstream — a prerequisite for long-term independent control of both trading environments. By the end of the year, platform operations are no longer a source of financial or competitive risk, and you have the metrics to prove it.

The ask

What does your current MT4/MT5 setup look like — and what's the reliability problem you haven't been able to fully solve?