Playson·1 day ago
🎯 What You’ll Actually Do
Own delivery and technical direction for a platform domain that runs high-load, distributed services where uptime and correctness matter.
Lead by example: review, debug, prototype, unblock — you’re not a “status manager.”
Drive technical decisions: architecture trade-offs, tech debt priorities, platform reliability improvements.
Partner tightly with Product Owners / Architects — no handoffs, shared ownership of outcomes.
Raise execution quality: set engineering standards, improve estimation realism, reduce chaos in delivery.
Jump into incidents, drive RCA, make fixes stick (not band-aids).
Help the team grow through real work: pairing, code reviews, crisp feedback, pragmatic coaching.
🧠 What You Bring
Strong backend background (5+ years) with real production ownership.
Comfort operating in microservices / distributed systems (failure modes, async patterns, queues).
Hands-on with Node.js / TypeScript (or very close stack), plus Kafka/event streaming.
Solid cloud + runtime experience: Kubernetes, Docker, AWS.
Data-driven mindset: performance metrics, observability, reliability thinking.
Leadership without politics: you’re direct, structured, and you don’t hide behind process.
Bonus: ClickHouse / PostgreSQL / MongoDB / DynamoDB.
🔧 How We Work
Speed > perfection. Measure, learn, iterate.
Impact > output. We care about scalable fixes.
Direct > polite. Say what’s broken, fix it.
No silos. Shared responsibility for outcomes.
🔥 What We Offer
Fully remote (Europe).
Unlimited vacation + paid sick leave.
Quarterly bonuses.
Medical insurance for you + partner.
Learning budget.
High ownership, low bureaucracy.
👉 Apply if you want leadership with real engineering weight, not a calendar full of meetings.