Want to get involved?

We’re looking for 2 profiles of engineers to join us at the founding or principle engineer level. From a business standpoint this means your responsibilities might include:

Now - the profiles

  1. Orderbook Exchange Frontend Experts:
    You have experience with orderbook exchanges at the technical product level. You understand why the exchange looks and feels the way it does - and how it delivers the performance users expect.

    t+ depends on running a highly performant orderbook as the user entrypoint. We need to process a high volume of orders efficiently with minimal room for downtime or errors. Your job is figuring out how to get from user landing on our website to submitting a trade as quickly as possible.
  2. Searcher/Solver/Quant/Market Maker/Block Builder
    You’ve built and maintained high-volume strategies.

    Many of the skills and expertise involved in the above fields are highly relevant to t+. We’re trying to run a high-performance program that enables orderflow monetization by market makers. As a searcher or quant you likely have experience with implementing highly performant technical architecture that interacts with external exchanges constantly. We also plan on running the initial market making algorithm on t+ to kickstart the liquidity flywheel, your experience is highly relevant here.

    One other important aspect here is knowing what market makers expect from a trading venue. What kind of API endpoints and discoverability is valuable? What can we reasonably support with our infrastructure?

Nice To Have

The following skills aren’t required, but are useful for candidates to have

  1. Experience or interest in Rust or other high-performance languages

    Our off-chain components are currently written in rust, although that isn’t mandatory, I just like it and Go/C++ scare me a little.

  2. Smart Contract Development

    We will be writing smart contracts.

  3. Risk Engines

    t+ heavily depends on having a highly effective risk engine. We want market makers to have as much capital efficiency as possible, but the efficacy of our confirmations requires market makers remaining solvent. Managing system risk is everything.

  4. Node Management

    Our off-chain components must run light-clients inside TEEs to have trustless access to on-chain state.

  5. Crypto Orderflow Supply Chain

    We live or die by being able to efficiently execute and monitize unsettled user intents. Experience or interest in how execution works in crypto is useful.

Anything Else?

If you think we’re missing something here that would be valuable and you can provide let me know!

Contact: markus@tplus.cx