The Job

Grow Space Engineers. That's it.

Space Engineers has sold 6 million copies with no paid acquisition - just a strong internal PR and community team. Space Engineers 2 is in early access. Your job is to turn a cult classic into something bigger - more players, more revenue, a successful SE2 launch.

You report directly to the CEO. You own franchise growth - and the delivery it depends on.

What You´ll Do

• Own SE franchise growth - SE2 exit from early access, SE1 cross-sell, the whole funnel
• Build the growth engine - creator partnerships, Steam visibility, campaigns, monetization strategy. We have a tiny marketing team. You'll shape it.
• Lead SE2 - work directly with production leads to ship SE2 out of early access. On time, at quality, right scope. You own the outcome, not just the strategy.
• Oversee SE1 at a high level - cross-sell, lifecycle, keeping the engine running
• Convert the existing base - 6M SE1 owners is a massive acquisition channel that's barely been touched
• Be a business partner to the founder - not a middle manager waiting for instructions
• Raise the bar - we have a high-standards culture. Your job is to push it higher, not maintain it. That means honest feedback, clear expectations, and the courage to have hard conversations when they matter.
• Stay close to execution to spot blockers, force trade-offs, and step in where escalation is needed — while teams handle normal day-to-day delivery.
• Bridge core community and mainstream growth - understand what existing Space Engineers players value, where the product loses new players, and how to grow SE2 into a bigger, more accessible success without flattening its identity.

What You Won't Do

• General operations or administration
• Own every individual task or solve every small problem personally. Teams are expected to handle normal day-to-day execution.
• Creative or technical direction. Founder stays hands-on there.
• Approve budgets unilaterally. You propose, CEO decides.

What Makes This Interesting

• A franchise with room to run. 13 years in the market, three major updates a year, deeply engaged community. The player base keeps growing — and we haven't done any paid acquisition yet.
• Real authority within clear lanes. You'll work directly with the founder as a business partner. You own growth, commercial strategy, and execution. The founder remains hands-on in creative and technical direction. Strategic decisions, real ownership, direct impact.
• AI intersection. Our sister company GoodAI does serious AI research and swarm robotics. AI companions and AI NPCs may come to SE. This isn't a buzzword — it's the roadmap.
• Independent, European, founder-led. ~80 people. One owner. No publishers. No committees.
• A real product challenge. Space Engineers already has a loyal core audience. The opportunity now is to grow beyond it without losing what made it special in the first place.

This Role Is NOT For You If

• You think strategy means a 40-slide deck. Here it means: whiteboard, 15 minutes, what would you do?
• You need a big org to be effective. We're ~80 people, founder-led, and we like it that way.
• You're looking for a safe role. This is a reset, not a continuation. We are in a scale-up / acceleration moment.
• You can't work within CET ±2 hours.
• You lead by consensus. We respect people, but we don't wait for everyone to be comfortable before moving.

Location

Remote. CET ±2h timezone required.

Compensation

Competitive salary + profit share tied to company performance.

What you’ll find at Keen Software House:

Impact

• Leave your mark on one of the most technically ambitious sandbox engineering games ever made.
• Join an international team tackling hard problems

How we work

• Hybrid by default: work from home when you want
• Low bureaucracy, fast decisions

Time off & wellbeing

• 5 weeks’ vacation
• Flexible sick leave

Workspace

• Modern offices at Oranžerie, Prague — quiet focus zones, beautiful garden, great daylight, quality equipment, bike storage, gym and shower, fully stocked kitchen, lunches prepared by our private chefs

Community

• Regular team breakfasts, workshops, and relaxed meetups (BBQ, game nights, parties, teambuildings)

To Apply

Please send us following:

1. CV - keep it tight
2. 90-day plan (max 1 page) - what would you actually do? Be specific.
3. One growth example - a time you grew a player base, audience, or business. Include numbers.

No cover letters about your passion for gaming. Show us what you'd do.

Nebius Managed Kubernetes (mk8s) mission is to grow the Nebius cloud platform by providing a Kubernetes-native way to run AI systems with high efficiency and low operational overhead.
With a single click, it provides a Kubernetes cluster on top of Nebius services for compute (VMs) and networking.
In 2026, the service is scaling 10× and is expected to manage customer workloads across tens of thousands of GPU servers in more than 10 data centers.

You will lead the mk8s Core team, one of three mk8s teams. The Core team owns the API, the core of the service control plane, cluster autoscaling, platform integrations, and running k8s add-ons.

At Nebius, team leads are hands-on. We expect you to be a senior or staff engineer now (or earlier in your career). You will start as an individual contributor to gain context, then take on managerial responsibilities.

In this position, you will be responsible to:

• Lead by example. Set the quality bar by spending a significant portion of your time on IC work: writing and reviewing code, leading projects, and participating in on-call rotation, incident mitigation, and post-incident analysis.
• Manage 4–8 mid-to-senior engineers. Provide context, coach, and give regular feedback.
• Maintain the technical vision for your area of responsibility.
• Collaborate with the Product Manager and Service Owner to shape product vision and plans.

Examples of outcomes you could drive as a Team Lead

• Optimize the service control plane to create and manage 20K GPU nodes in a single Kubernetes cluster, enabling a major contract for the company.
• Integrate cluster autoscaling approaches (e.g., Karpenter) to improve resource utilization and support seamless auto-upgrades.
• Provide a Kubernetes-native way to use local disks to reduce disk I/O bottlenecks for AI training and inference, improving efficiency.
• Deliver managed Layer 7 load balancers to reduce operational overhead for customers.

What you will bring to the table:

• 8+ years of professional software engineering or management experience
• Excellent knowledge of Golang, or you are ready to quickly switch to this programming language
• Expertise with
• Multi-month technical projects
• Tech leading engineers
• Owning multi-month technical projects.

It would be an added bonus if you had:

• Experience with Team management, Kubernetes administration, Developing Kubernetes controllers

At JetBrains, we build developer tools that help engineers stay focused on solving hard problems instead of fighting routine work.

Within JetBrains AI, we are collaborating with Zed on the Agent Client Protocol (ACP), an open protocol that lets AI coding agents work inside editors and IDEs. ACP is already supported in JetBrains AI Assistant, and the project is jointly governed by JetBrains and Zed. We see ACP as a long-term investment in interoperability, developer choice, and durable AI-powered workflows across the JetBrains ecosystem. (The JetBrains Blog).

ACP evolves in the open. Real-time coordination happens in Zulip, actionable work is tracked in GitHub Issues, longer-form discussion happens in GitHub Discussions, and substantial protocol changes move through the RFD process. We need someone who can help JetBrains shape that work from the product side: define the right developer scenarios, align internal and external stakeholders, and turn ecosystem needs into clear priorities for JetBrains and for the protocol. (Agent Client Protocol).

This is not a generalist product management role. It is also not a pure protocol engineering role. It sits between developer-experience product work and protocol evolution.

This role is often a strong fit for someone who has spent several years as a software engineer – ideally on APIs, SDKs, web/backend systems, libraries, frameworks, or platform integrations – and then moved into product management or a hybrid product or engineering role.

This will be an exciting opportunity if you:

• Want to shape an open interoperability layer for AI-native software development.
• Enjoy turning messy cross-team technical discussions into clear product direction.
• Like working with engineers, agent developers, and external partners to make complex systems usable and durable.

In this role, you will:

• Identify and prioritize the developer scenarios JetBrains should support through ACP in JetBrains IDEs.
• Study how those scenarios are already handled in CLIs and agents, and define coherent IDE-native flows that JetBrains should support.
• Work on examples such as plan mode, sub-agent workflows, or agent-to-agent communication, and turn them into clear scenario definitions and product requirements.
• Talk to JetBrains product and engineering teams, external agent developers, and partners to collect requirements, constraints, and compatibility concerns.
• Turn those inputs into crisp problem statements, GitHub Issues, success criteria, and roadmap priorities.
• Partner closely with protocol engineers and ACP maintainers to translate validated scenarios into protocol proposals, implementation requirements, and delivery plans.
• Represent JetBrains in regular protocol conversations with Zed and the broader ACP community, helping drive alignment on what belongs in the protocol, what should remain implementation-specific, and what should wait.
• Balance immediate JetBrains product needs against long-term protocol design concerns such as extensibility, backward compatibility, clarity, and ecosystem fit.
• Define and monitor the right telemetry and product metrics for ACP-related surfaces, including agent installation success, authentication success, protocol feature adoption, task completion, reliability, and developer satisfaction.
• Help JetBrains make long-term, product-quality decisions about supporting ACP across multiple IDE experiences.
• Communicate decisions, trade-offs, and priorities clearly to highly technical stakeholders inside and outside JetBrains.

We’ll be happy to have you on our team if you:

• Have 1-4 years of product management experience, or equivalent end-to-end ownership in a hybrid engineering/product role.
• Have a substantial software engineering background and hands-on production coding experience in real systems.
• Understand how modern web and integration primitives work in practice, including OAuth, WebSockets, HTTP, JSON-RPC, and service-to-service communication.
• Are comfortable reasoning about APIs, protocols, payload schemas, event-driven systems, authentication flows, local/remote execution, and backward compatibility.
• Can discuss technical details credibly with engineers and agent developers, even when the conversation goes deep into protocol behavior, edge cases, or extensibility.
• Can take raw technical feedback and turn it into clear user scenarios, requirements, issue tickets, and written decisions.
• Have strong product judgment and can distinguish between a JetBrains-specific UX choice and a protocol-level capability that should be standardized.
• Have a data-driven mindset and know how to combine telemetry, qualitative feedback, and ecosystem signals in product decisions.
• Have strong spoken and written English.

We’d be especially thrilled if you:

• Previously worked as a senior software engineer, staff engineer, library/framework maintainer, SDK owner, or platform/integration engineer before moving closer to product work.
• Have experience with developer tools, IDEs, AI coding agents, CLI workflows, or interoperability layers such as LSP, MCP, or ACP.
• Have contributed to open-source projects or standards-like processes.
• Are comfortable working in public GitHub workflows with Issues, Discussions, pull requests, and proposal documents.
• Have built or supported products where compatibility, extensibility, and future-proofing mattered.
• Use JetBrains IDEs regularly.

#LI-KL1