Core Systems Architect (API / Execution Node)

MANDATORY: You must be a Turkish national or currently residing in Turkey. No exceptions.

Title: Core Systems Architect (API / Execution Node) - High-Frequency Trading
Location: Istanbul, Turkey (On-site sprint starting August)
Compensation: Austerity Fiat Baseline + Phase II Profit Yield (Revenue Share)

The Mandate:
WEAXESS is a sub-millisecond, institutional-grade digital asset exchange. We are seating our First 11 vanguard. You will own the gateway. You are the bridge between the chaotic public internet and our deterministic C++ core matching engine. You will build the high-throughput REST, WebSocket, and gRPC layers that handle tens of thousands of concurrent institutional and retail order requests without bottlenecking the core.

The Filter:

If your resume says "Full Stack," or your background is building CRUD web applications in PHP, Laravel, or Node.js, do not apply.

If you use LLMs to write your architecture, do not apply.

We require expert-level Go, Rust, or C++. You must dream in lock-free concurrency, memory pools, and zero-allocation critical paths.

The Reality:
We operate on a 70-day physical austerity sprint in Istanbul. You receive a basic fiat baseline to live, and your true compensation is a locked percentage of the system's global net profit pool upon launch.

Application Tripwire (Answer in 3 sentences max in your cover letter):
A client establishes a WebSocket connection and blasts 5,000 orders per second. The C++ matching engine is processing them perfectly, but the client’s network connection degrades and they stop reading their TCP receive buffer. How do you prevent this slow consumer from causing backpressure that crashes the core matching engine?