Trading Infrastructure Engineer · Zürich, Switzerland

I run the infrastructure that trading depends on, and I understand the trading itself.

Over nine years across regulated crypto, banking and ETP issuers, I build and run the systems that stay up while the market is live, without anyone holding them up by hand.

Software Engineering

These are real projects I have written, and every one is tested. 6 of the tools below link to a working example that I validate locally against LocalStack 4.14 and Postgres. Anything without a passing test is marked no tested example rather than faked.

Software Engineering

Real code I have written. Every example here is tested before it ships.

I crawl the live Hyperliquid markets into Postgres. It keeps the latest state with idempotent upserts and a snapshot history that only ever grows. 18 tests, one of which hits the real API.

Tested example Python and Postgres

Infrastructure and Observability

These are the 12 tools I actually reach for to build and run trading infrastructure. They come from real production work, not a wishlist. Where a tool has a tested example you will find it on the card, along with how deep I go.

Cloud and Compute

Where trading systems run, and how they scale while the market is live.

My main cloud across every role. Networking, IAM, and keeping the bill sane for trading infrastructure.

Tested example S3 and DynamoDB on LocalStack

Runs the trading and venture builder workloads. I ran EKS in production while trades were live.

no tested example I cannot reproduce this faithfully on LocalStack, it needs a real cluster, so there is no tested example yet.

I designed the EKS and Fargate setup across a whole venture builder portfolio.

no tested example EKS does not reproduce faithfully on LocalStack, so there is no tested example yet.

Serverless containers. It took node management off my plate on the EKS platform.

no tested example There is no honest way to test this locally without a real cluster.

Infrastructure as Code

Infrastructure I can reproduce and review. Nothing is held up by hand.

How I describe and version cloud infrastructure. I have used it to provision real production infra.

Tested example tflocal, apply then assert

CI/CD and Automation

A solid lifecycle so changes ship safely and often.

I automate the whole path from commit to production. Here, GitHub Actions runs every example test suite on each push.

Tested example GitHub Actions workflow

Feature branch environments

A throwaway environment for every branch, so every change can be reviewed on its own.

no tested example This is a way of working rather than a library, so there is no standalone test. You can see it in the CI setup.

Observability

Monitoring as code, because you cannot run what you cannot see.

Traces, metrics, and logs that are not tied to any vendor, instrumented across the services.

Tested example spans via an in memory exporter

Collects the metrics and drives the alerts for production trading systems.

Tested example the exposition format

Dashboards for the health of the systems and the trading on top of them.

no tested example Dashboards are just JSON config, so there is nothing meaningful to unit test on its own yet.

FinOps and Cost

Reliability and efficiency are the same discipline.

Guardrails that keep cloud spend predictable.

no tested example This API only lives in LocalStack Pro, so I cannot test it on the free tier.

I used anomaly analysis to cut cloud cost across a portfolio of projects.

no tested example This API only lives in LocalStack Pro, so I cannot test it on the free tier.