[Hiring] Technical Delivery Analyst @Reactive Markets

Role Description

We're hiring the first dedicated Technical Delivery Analyst. You will own the delivery of software projects end-to-end — from requirements through to production — working alongside engineers to ensure work lands on time, risks are visible, and stakeholders always know where things stand. As our engineering organisation grows into more specialised teams, you are the person who sits across the space between them — owning the dependencies, coordination, and communication that no single team owns.

This is not an administrative role. You need to understand the technology being built, speak credibly with engineers about architecture and trade-offs, and translate technical reality into clear communication for the business. You are the person who knows what is happening, why it matters, and what might go wrong — and you make sure everyone else knows too.

You will work closely with the Head of Technical Delivery and daily with Engineering, TechOps, and Product, with regular interaction with client-facing teams (Sales, Client Services). The role offers a clear path to Delivery Manager as the team grows and you take on broader ownership.

What You'll Work On

• Delivery Ownership:
  • Own projects from inception to production — responsible for outcomes, not just process
  • Understand technical scope, architecture, and dependencies well enough to anticipate problems before they surface
  • Ensure infrastructure, testing, performance, and operational readiness are considered from the start
  • Know the current state of your projects at all times
• Communication:
  • Communicate early and often — bad news delivered early is manageable; bad news delivered late is a crisis
  • Provide honest, accurate status updates — never spin, never hide, never assume someone else will raise it
  • Tailor to the audience — technical detail for engineers, business impact for leadership, actionable clarity for everyone
• Technical Engagement:
  • Participate meaningfully in technical discussions — you don't write code, but you understand what is being built and why
  • Engage with engineers on architecture, dependencies, and integration points to accurately assess delivery risk
  • Bridge engineering and business by translating technical constraints into language stakeholders can act on
• Risk Management:
  • Identify risks early through genuine understanding of the work, not by reading ticket statuses
  • Escalate with context — what is the risk, what is the impact, what are the options
  • Contribute to post-incident reviews with a delivery lens — impact, learnings, prevention
• Continuous Improvement:
  • Look for friction in how work flows and propose practical improvements
  • Experiment with AI tooling to improve delivery efficiency — reporting, analysis, coordination, and communication
  • Maintain delivery tooling as a means to an end, not an end in itself

Qualifications

• 2+ years' experience in technical delivery, project management, or software engineering
• Previously worked as a software developer, or strong hands-on technical experience with software systems
• Comfortable reading code, reviewing pull requests for context, and understanding technical trade-offs without simplification
• Knows what "done" looks like in production — tested, deployed, monitored, documented
• Familiarity with Agile practices and tools (Jira, Confluence) — values principles over ceremony
• Financial services or trading technology experience is a strong advantage

Requirements

• You own it. End-to-end responsibility. If it's your project, it's your problem — you don't wait for someone to tell you something is off
• You communicate clearly. Exceptional written and verbal communication. Concise, precise, and honest under pressure.
• You build trust. Engineers respect people who understand the work, tell the truth, and follow through — not a title.
• You steady the room. When a project is drifting or an incident is live, you lower the temperature rather than raise it.
• You think in outcomes. Updating a board is not the same as delivering software.
• You stay technically curious. You genuinely want to understand how systems work and fit together.
• You write things down. Documentation is how we scale knowledge across a distributed team.
• You exercise judgement. You know when to escalate, when to solve, and when to ask for help.
• You embrace AI tooling. We use AI tools to amplify our delivery capability.

Benefits

• Real delivery problems — owning end-to-end project outcomes on a market-leading trading platform with genuine scale and technical depth
• Breadth of exposure — work across the full engineering organisation: backend, frontend, platform, infrastructure, and TechOps
• An excellent team — senior engineers who care about craft, collaborate openly, and hold each other to high standards
• Direct mentorship — access to the Head of Technical Delivery for coaching, feedback, and professional development
• Career progression — a clear path to Delivery Manager as the team grows and you take on broader ownership
• Competitive package — up to 30 days leave + bank holidays, private health insurance, pension, life insurance, dental/optical cashback, cycle to work, socials and offsites
• Remote-friendly — work from home with flexibility. We trust our people to deliver
• Sustainable pace — we work hard, but we don't burn people out. Balance is how we stay sharp