Production ownership: observability, on-call, RCAs, and making the system faster and cheaper with numbers to back it.
Tech stack
Python and PostgreSQL are the core; you don't need every item below on day one.
Backend: Python, SQLAlchemy + Alembic, PostgreSQL, OpenAPI
Supporting services: Go
Mobile and desktop: Kotlin Multiplatform + Compose Multiplatform (Android, iOS, macOS, Windows)
Web: Next.js, React, TypeScript
What we're looking for
A strong backend engineer who has also shipped real frontend work and is happy to keep doing both.
3+ years (SDE 2) or 5+ years (SDE 3) building and running production backend services.
Deep in at least one backend language; Python preferred, Go, Kotlin/JVM or TypeScript/Node also welcome.
Solid API and data-model design: REST/streaming APIs, PostgreSQL schema design, migrations, indexing, transactions.
Distributed-systems fundamentals: async processing, queues or event streams, idempotency, retries, failure handling.
Production experience on Kubernetes or a similar platform, with observability you actually used to debug an incident.
Has shipped user-facing features on at least one client platform: Android, iOS, desktop or web (React/Next.js). Kotlin/Compose experience is a plus, not a gate.
Willing to pick up the side of the stack they know less, and to learn agent and LLM systems on the job.
Clear written communication: design docs, PR descriptions, RCAs.
Nice to have
Built on LLM APIs: tool calling, streaming, prompt caching, evals, or an agent loop of your own.
MCP servers or clients, OAuth connector integrations, or sandboxed code execution.
Kotlin Multiplatform / Compose Multiplatform, or native Android/iOS.
Real-time systems: WebSockets/SSE, NATS, Kafka, or Temporal-style durable workflows.
Go services, or performance and cost work with measurable before/after numbers.
Open-source work or public writing we can read.