Algorithmic and electronic trading development
Design and development of electronic and algorithmic trading systems, from platform architecture and implementation to back-testing.
What this work is
We design and build the software that carries a trading decision through to an order, and the order through to a fill. That includes the shape of an algorithmic or electronic trading platform, the services that hold orders and positions, and the paths that take market data in and send executions back. The engagement may be a new platform, or a change to one that already runs in production and has to stay up while it is changed.
An algorithm here is the set of rules that decides when to send, change, or pull an order. It might slice a larger order, respond to a price, or stop when a condition fails. The platform around those rules has to keep the decision, the live orders, and the record of what happened in line with each other. If they drift, the desk cannot tell whether the strategy did what it was asked to do.
High-level design is part of the same job. Before implementation is the useful next step, the components have to be named. Where an order lives, what happens on a restart, which events can be recovered, and which decisions a person is still expected to make. We have spent years on that design with large trading platforms and with systems built from scratch for a smaller team.
Who it is for
Clients are trading desks, brokers, and fintech firms that run electronic flow, and smaller teams that want a bespoke algorithm or a platform of their own. We have done this with tier-1 investment banks in London and Hong Kong, and with startups and individual traders. The same kind of system appears in traditional markets and in crypto. The venue and the asset change. Operators still need software that shows them when something has failed.
A team may already have a platform and want a review of one algorithm, a second opinion on a design, or a short implementation sprint. That is a smaller engagement than building the platform. The consulting packages are there so the size can match the brief.
Typical work
A design engagement names the parts of the platform and the way an order moves between them. An implementation engagement writes the trading logic and the services around it, in the languages listed on the about page. The two usually run together. We write the design so it can be built, and we keep a picture of the whole platform while the code is written.
Back-testing and regression testing sit in this area as well. A change to an algorithm needs a comparison with earlier results before it is put in front of a market. We set that comparison up so a later change can be run again on the same basis. The team then has a record they can use when they decide whether a change is ready.
The screens a trader or an operator uses are described on the trading user interfaces page. Connectivity to the venue is covered under exchange connectivity. When the algorithm works a parent order against a benchmark, that detail is on the benchmark execution page. This page is the platform and the algorithm around those pieces.
How an engagement runs
A single session is enough for a design review or a reading of an existing algorithm. A block of hours covers a defined slice of implementation. A monthly retainer suits a desk that wants the same people available while a platform is changing. A long-running platform is agreed before anyone calls it a long-term engagement. Prices and the shape of each package are on the packages page.
Contact us with the system you have, or the system you want, and with what has to be true when the work is finished.