Engineering Manager (Developer Experience and Platform)

Only the best engineers are being built here.

Salary range (annual, CZK): 2,950,000 - 4,430,000.

The opportunity

What you would build

• A pipeline where a merged change reaches production the same day, with the tests and gates that make that safe rather trustworthy.
• A context layer in the repo. Versioned guidance that Cursor, Claude Code, and Codex load on their own, so every engineer gets better AI output without configuring it themselves.
• AI code review that catches the real issues. Correctness, security, and maintainability flagged before a human opens the pull request, with the false positives filtered out so reviewers trust it. 
• Develop PR segmentation to route a higher percentage towards auto deployments without human reviews.
• Own Engineering dashboards and team health dashboards, with both leading and lagging indicators. Highlight what next constraints we will face and plan to address them.
• On-call system engineers do not dread. Clear ownership, runbooks that execute, alerts that mean something, and a reliability target the whole organization can see.
• Incident agents. They triage the alert, pull the logs, surface the last few times this broke, and propose a fix. The on-call engineer decides.
• Infrastructure and a tooling stack that are chosen, not inherited. Cost and capacity visible per team, fewer vendors, and a reason for every one we keep.

Why this matters for your career

What you will do

• Own developer experience end to end. Find the friction in how engineers build, test, release, and operate, then remove it. Measure it before and after.
• Own production operations for the platform. On-call health, incident response, reliability targets, and the unglamorous work that keeps a system healthy.
• Own infrastructure, cloud cost, and capacity. Make the tradeoffs visible to the teams making them.
• Own engineering tooling and vendors. Choose, consolidate, negotiate, and retire. Every tool in the stack has a reason or it goes.
• Define your team's engineering strategy and roadmap, balancing developer needs, reliability, cost, and long-term sustainability.
• Treat internal engineers as customers. Talk to them, watch how they work, and prioritize from evidence rather than from your own preferences.
• Own your team's AI-first system: machine-readable contracts, maintained context, executable runbooks, and AI used across planning, coding, review, debugging, and on-call.
• Bring problems to leadership with two or three options and a clear recommendation. Be honest about uncertainty and what would change your mind.
• Work closely with senior engineers on technical direction. Attend design reviews, run incidents, and explain how the platform is built without scheduling a meeting.
• Collaborate with other engineering managers so platform work fits how product teams actually operate.
• Make the success of your team visible and create a sense of pride in what it achieves.
• Act as a knowledge multiplier, sharing what you learn across and beyond your team to raise the bar for everyone.

About you

• A backend engineer at depth. You read and write production code. You are not a former engineer.
• Two or more years managing engineers, growing both individuals and the team.
• Real empathy for developers. You have sat with the pain you are fixing. You know the difference between a tool that looks good in a demo and one an engineer reaches for on a bad Friday.
• You understand developer workflows and have made engineers measurably faster. You can name the before and the after.
• You have owned production operations. On-call, incidents, and reliability.
• You bring options and recommendations, not just status. When you raise a problem, you come with a view on what to do about it.
• You value direct feedback, given and received. We practise Radical Candor. Always with good intent, always constructive.
• You use AI as a daily tool in your own work. Coding assistants, prompt iteration, and a constant look for ways to move faster.

• Infrastructure ownership, including cloud cost and capacity.
• Vendor and tooling management. Contract cycles, consolidation, FinOps.

Our tech stack

• Kubernetes, AWS, Docker, Helm, Kafka, Git, and CI/CD
• Terraform for infrastructure as code
• Datadog, Sentry, and Looker for observability and analytics
• GraphQL and Postgres
• Python, Celery, and LangGraph where we run AI workloads
• Business tools: Slack, Google suite, Zoom, Notion
• [Full Tech Stack]

Our benefits include

Relocation Opportunities

About Productboard