For The Way
Limassol —:—· EET
Autonomous trading researchLimassol, Cyprus

For The Way

We trade our own capital and nobody else’s. No clients, no investors, nothing to explain to anyone outside the room. What we build with it: machine-learning systems that read market microstructure and act on it without a human in the loop — one office, Limassol.

Research cluster snapshot

Features in store0
p99 internal path6.8 µs
Signal refresh · median42 ms
Strategy-years / night0
2023
Founded
9
Venues live
3
Colocation sites
CY
Limassol · EU
§ 01

What we build

Four systems, one loop. Most of it is written in-house, because the off-the-shelf versions are either too slow or too general for what we do.

01 / Signal

Signal engine

A continuously retrained ensemble that turns order-book updates, funding and trade flow into probability estimates over horizons from a few seconds to a few hours. Each estimate carries an uncertainty interval, and the execution layer reads that interval before it reads the estimate.

  • Transformers
  • Gradient boosting
  • Online learning
  • Conformal bounds
02 / Execution

Execution layer

Our own routing and order-management stack, written in Rust and C++ against a fixed latency budget, with kernel-bypass networking and per-order tracing. We reach venues through clearing and DMA relationships rather than as a direct member, and colocate at the halls where it changes the fill.

  • Rust
  • C++20
  • Kernel bypass
  • Broker colo
03 / Risk

Risk kernel

Position, concentration, drawdown and per-venue limits are enforced in code on the order path, not reviewed after the fact. The kernel can reduce or flatten the book without waiting for anyone, and it is the one component no strategy can configure around.

  • Pre-trade checks
  • Kill switch
  • Stress sims
  • Post-trade recon
04 / Platform

Research OS

The internal platform the team works in: a point-in-time feature store, an event-driven simulator that replays captured book data, and an evaluation harness that runs the same checks on every idea. Most new researchers put a live experiment up in their second week.

  • Feature store
  • Event-driven sim
  • Eval harness
  • Ray · Kubernetes
§ 02

How we work

Five working rules. Most of them came out of things that went wrong first.

01

Falsify first

An idea gets a null hypothesis and a pre-registered test before it gets a backtest. In practice we spend more cluster time trying to break signals than finding them, and most of what we look at does not survive that.

02

Small size, fast loop

Everything goes live at a size where being wrong is cheap, and only grows on out-of-sample evidence collected after the fact. We prefer a large number of small experiments over a few large ones.

03

Latency where it decides the trade

We measure the whole path, from packet arrival to order out, and optimise the segments where microseconds change which fill we get. On the rest of the system we spend the engineering time on correctness instead.

04

Own the whole stack

Data capture, feature engineering, models, execution, monitoring. When something breaks overnight, the person who can fix it is on the same team and has the source in front of them.

05

Risk has the last word

Limits apply to everyone in the same way, founders included. Changing one takes two people and leaves a record, and limits are reviewed on a schedule rather than in response to how the past week went.

§ 03

About us

How the company is funded, how it works, and why it is in Cyprus.

One room.
One book.
No clients.

FOR THE WAY is a research and technology company in Limassol, Cyprus. We trade our own capital and nobody else’s. It started in 2023 on an engineering bet — that the problems worth attacking in these markets are modelling and execution problems, not information ones — and everything since, from data capture to the risk kernel, has been built in-house to test it.

Everyone works from one office, on one floor, in person. The person who owns the execution path sits within earshot of the person who owns the model, which shortens the distance between a result and someone competent poking a hole in it. Every system here has exactly one name attached to it, and decisions are made in the room, on the day, by the people who then have to implement them. We do not publish a team page; if you are talking to us about a role, you meet everyone you would work with in the first conversation.

Cyprus is deliberate. An EU jurisdiction, and a working day that opens into the Hong Kong afternoon, covers the whole European session and is still at the desk for the US open at 16:30 local. The US close lands at 23:00, which is one reason the risk kernel and not a person has the last word overnight. Infrastructure, payments and compliance we hire locally; research and low-latency people we relocate, and the permits and the move are our problem rather than yours.

Being self-funded is the whole design, not a stage we are passing through. No outside mandate to report against, no raise to survive, no quarter to dress up — so an idea lives or dies on out-of-sample evidence and nothing else, and the only people you have to convince are the ones sitting next to you. What the business generates goes back into people, data and hardware.

The name is about method. Results expire; the way you got them is the part you keep.

Limassol, CyprusEET / EEST · UTC+2 / +3EU jurisdiction Founded 2023
§ 04

Open roles

All roles are on-site in Limassol. We are a registered Company of Foreign Interests and sponsor third-country work and residence permits through the Business Facilitation Unit. Cyprus is in the EU but outside Schengen.

Each of these is ownership of a system, not a queue of tickets: one person is responsible for it, has the source in front of them, and there is no layer between a result and the decision to run it in small size. Most people put a live experiment up in their second week, so you see your own work in the market rather than in a deck. The process is short, you meet everyone you would work with before there is an offer, and the permits, the relocation and the paperwork are our job rather than yours.

Talk to
us.

Send a CV or a link to something you have built. A short note about what the problem was and how you approached it is more useful to us than a cover letter. The team reads applications directly.

We use what you send only to consider your application. See our privacy notice for retention and your rights.