Max Kaido

I build live backend systems where correctness, reliability, and operational ownership matter.

Senior backend/platform engineer for trading, fintech, Web3, infra, and data-heavy products. I work close to production: live state, execution flows, runtime signals, incidents, and product feedback loops.

I can go full hero mode when production needs it, but I treat that pressure as signal: turn hard edges into better architecture, observability, rollout safety, and calmer operations.

Email [email protected] View selected work View CV

Live systems

Production systems with real users, live state, operational constraints, failure modes, and incident feedback. I prefer systems that fail loudly and teach the next iteration.

Trading / Web3 depth

Execution flows, market data, deterministic risk boundaries, oracle-style integrations, and correctness-sensitive backend work where mistakes have a price.

AI-native delivery

Closed frontier AI for coding and strategy development; local open-model workflows where validation and execution-adjacent evaluation need controlled, repeatable behavior.

Proof under pressure

Selected systems that show the kind of ownership I bring: live money, high-concurrency state, operational surfaces, and feedback loops where reality gives fast answers.

Mercury: AI-native trading engine

Profitable, production-ready private trading engine in an unfamiliar, execution-sensitive domain with a blunt success metric: PnL. Multi-intent execution, deterministic risk controls, portfolio neutrality, and AI-assisted strategy iteration.

Selective Mercury conversations: [email protected].

High-concurrency portfolio systems

Flagship backend for 10k+ concurrent users: per-minute portfolio recomputation against live market data, dual-state anti-cheat design, API contracts, and fast product delivery under funding pressure.

Bot fleets and telemetry

80 concurrent Hummingbot instances with Telegram control surfaces and acoustic telemetry for real-time operational awareness, parameter tuning, and market-regime learning.

Good fit

  • Trading, fintech, Web3, infra, or data-heavy product work.
  • Backend/platform problems where correctness and production ownership matter.
  • Teams that value clear constraints, fast feedback, and operational reality.
  • Remote-first contract / B2B, or serious full-time startup roles with real authority.

Stack

TypeScript, Node.js, NestJS, Python, Solidity, PostgreSQL, TimescaleDB, Redis, Docker, Swarm, Kubernetes, Terraform, Ansible, GCP, AWS, Prometheus, Grafana, OpenTelemetry, REST, gRPC, WebSockets, queues, React, Next.js, TanStack, Zustand, Tailwind.

Hiring for a serious backend/platform problem?

Send the context: what you are building, where the system hurts, what must not break, and what success should look like in production.

Best inbound path: [email protected]. Include the problem, timeline, expected ownership, and whether this is contract, B2B, or full-time. LinkedIn / Wellfound under Max Kaido are useful for background checks.