Software Engineer - Model API Platform

Own one or more major parts of the platform, such as the WebSocket streaming layer, a speech recognition pipeline…

Turn loosely defined goals into RFCs, milestones and shipped results, and write down the decisions and trade-offs.

Be accountable after launch: on-call, incident response, root-cause analysis and follow-through on fixes.

Make the call when a decision is needed, and own the outcome.

At least one service you owned end to end under real load, including what broke and what you changed.

Strong distributed-systems fundamentals: concurrency, networking, queues, caching, consistency and failure modes.

Experience with low-latency or high-throughput services, and comfort reasoning about p95 and p99 latency.

Solid fundamentals with a relational database and a cache, such as PostgreSQL and Redis: schema design, query performance and caching strategy.