Operations Analyst

Some of it is the same every morning.

The satisfaction is in the set being complete and right — and in finding ways to make tomorrow’s version faster than today’s.

This role suits someone who likes a clear rhythm and recurring responsibilities, but still wants to understand the 'why', solve problems and make the process better over time.

Operations and Trading teams work two shifts to cover the UK and US markets: 7:30am–3:30pm or 12pm–8pm.

You would work the earlier one but there are occasions we may need to temporarily move to the other for business coverage reasons (holidays/sickness etc) and would typically be notified in advance.

Whilst we will initially ask you to be in-office for training and set-up purposes, we are flexible on whether you do your work from home or the office once you can work autonomously.

We value output not presenteeism.

Coming back after a break

A gap on your CV is not a problem here.

If you have been out of the workplace — parental leave, caring for someone, or anything else — we are interested in what you can do now, not the last date on your CV.

How we work

• Small team, low process, high ownership
• We value pragmatism over perfection (80/20 mindset)
• We prioritise impact over activity, we roll up our sleeves and get it done
• We expect people to challenge ideas and contribute to better solutions

We set high standards, but we don't expect perfection.

You'll make mistakes as you learn; what matters is taking ownership, learning from them and improving.

You'll get direct, timely feedback and we expect you to give feedback too.

What are you going to do?

The role sits in our Operations team, reporting to our Chief of Staff (Iain).

You will own the operational processes that keep the trading team running.

The daily rhythm

• Daily P&L (profit and loss) reconciliation and resolving errors and breaks when the numbers do not agree.
• Daily reporting and operational processes that help the trading team prepare for the day ahead.
• Monitoring live P&L and issuing alerts throughout the day.
• Monitoring and managing trade flows so that every deadline is met.
• Monitoring and updating key market alerts.

Owning and improving

• Maintaining and taking ownership of a range of models and reports.
• Improving and automating workflows across the business — the parts of your own day that are slow and repetitive are fair game, and we would rather you fixed them than endured them.
• Quality assurance on Engineering output, holding it to solutions that actually work for the trading team.

Working across the team

• Working directly with your immediate team, Engineering and Trading to flag issues and changes.
• Responding and solving requests or queries from the Trading team on a timely basis
• Representing the Trading team’s requirements for new products or enhancements and translating them for Engineering to build.
• Liaising with third parties (brokers, vendors) and IT support to resolve issues.

We need someone who has…

Read these one at a time, not as a checklist.

If some are missing, message us anyway.

• Strong Excel skills and an appetite to learn more.
• Fundamental SQL (Structured Query Language) skills — enough to write a query, pull data and check it. If you have taught yourself the basics and want to go further, that counts.
• You have worked with data where accuracy mattered, and you can describe how you check your own work before it goes out.
• You have spotted a repetitive task and made it faster, and you can explain what you changed and why.
• You can explain something complicated simply, and you raise problems early rather than sitting on them — including to people more senior than you.
• You can work 7:30am–3:30pm as your regular shift, and switch to the later one occasionally when the team needs it. This will likely evolve over time to be more flexible as we automate move to a new platform.
• You can get critical work done without someone checking on you.

Things you will have the opportunity to learn and work with…

None of these are required.

If you have one or two, say so; if you have none, apply anyway.

• VBA (Visual Basic for Applications) or macros in Excel; SQL and python.
• Operations experience in a financial services environment.
• Middle or back office experience.
• Bloomberg or Reuters.
• A support role focused on error resolution.
• Derivatives and the trade lifecycle — nobody arrives knowing this and we will teach you.
• Agile, Scrum or Kanban ways of working.

You’ll fit well here if…

These aren't screening criteria — they're what the job actually asks of you day to day.

• You take real satisfaction in a set of things being complete and correct, and you notice when one of them is not.
• You've dropped your own approach because someone else's was better, and in a discussion you can summarise someone's point back to them accurately before making your own.
• You've got something wrong and can describe plainly what you did next. When you're stuck, you say so.
• You have worked out how a system or tool behaves by poking at it, rather than waiting to be trained on it.
• You've explained something technical to someone non-technical and checked they'd followed it. You write short messages rather than long ones.
• You've noticed a teammate struggling and done something about it without being asked.
• You say when your work will be done, and tell people early when that changes.
• You want to work somewhere with a purpose beyond the profit.

How we use AI

We're direct about this because you'll want to know before you apply.

• We expect you to use it. We pay for the tooling and we'd rather you got to a working answer in two hours than two days. That's 80/20 applied to your own workflow.
• We expect you to understand what you’ve done. Whoever or whatever wrote the code, you own it — which means being able to explain why it works and debug it when it doesn't. Use AI in the technical task if you want to; we'll be asking about your understanding of what you produced, not whether you typed it yourself.
• Humans make the decisions. Trading calls, code review, anything that touches production. No exceptions, and no plans to change that.
• What we don't do, and won't: share any trading data, company data and employee data - these don't go into third-party AI tools. We don't connect agents to our infrastructure. We don't take a vendor's word for how our data is handled.