Tasks
- Design and evolve core platform infrastructure: compute, storage, networking, tenant isolation
- Write production Go for our control plane, reconcilers, and API services
- Work on distributed storage architecture and scaling (Ceph/RADOS)
- Work on network design for multi-tenant isolation and multi-region expansion
- Work on Kubernetes control plane internals and cluster lifecycle management
- Review and challenge what we've built so far, tell us what's fragile, what won't scale, and what needs to change before it's too late
- Mentor a strong engineer who's learning fast but hasn't operated infrastructure at this scale before
- Help us make architecture decisions that hold up under growth, not just under demo load
- Write Engineering Requirement Documents to take something from idea, to defined tasks, to implementation, to monitoring its success
Benefits
- Founding Engineer title. You're not employee #47. You're building this from day one.
- VSOP equity participation.
- Competitive salary. Below BigCorp, honest about it. The tradeoff is ownership, equity and impact.
- Remote first within EU. We care about what you build, not where you sit. Working language is English, German is a plus.
- Hardware of your choice.
- No layers. You talk to the founders, you write code, it ships. That's it.
- Bootstrapped. We built this with our own money, our own hardware, and paying customers. No VC dependencies, no burn-rate panic. Fundraising is a strategic next step, not a survival one.
- Ambitious mission. We're not building another SaaS tool. We're building the European public cloud platform to compete with hyperscalers. Few companies let you work on problems at this scope.**
We're a startup. That changes things.
- There's no "platform team" you're joining. You are the platform team, together with the founder. There's no one to escalate to. You own it.
- We ship fast. Architecture decisions go from whiteboard to production in days, not quarters. If that sounds stressful rather than exciting, this isn't the role.
- We're building something that doesn't exist yet: A European public cloud that's technically competitive with the hyperscalers. That means ambiguity, unknowns, and decisions with incomplete information. Constantly.
- We don't do Jira. We don't do daily standups. We don't do permission chains. We talk, we decide, we build.
- You'll be on-call. At this stage, everyone is. If production breaks at 2am, we fix it. That's the deal.
- We're honest about where we are: early, lean, in production with paying customers, and building the foundation for something much bigger. If you need structure, process, and a 50-page onboarding doc, we're not there yet.