STACKIT CLOUD SENIOR SOFTWARE ENGINEER - IAAS PLATFORM (m/f/d)

Job description

Make an amazing climb in your career in an international team of experts. Our company provides technological services for the whole Schwarz group of more than 30 countries in Europe and the US. Our vision is to be the leading ecosystem for a better life. We built the European sovereign cloud STACKIT. With XM Cyber we set new standards in differing cyber crimes. We run AI better than anyone. With us you will find a variety of opportunities to grow and do your best at your calling – IT. We exist to improve life with our products and services - for today's generation and future generations. We act future proof! The impact you will create: Build a hyperscaler from scratch. Work in IaaS domain who owns the compute, storage and networking primitives customers run their workloads on. Improve the IaaS API: stability, scalability, code quality, new features. Scale the billing pipeline to 10x and 100x volume and new resource types. Own features end-to-end - "You Build It, You Run It": ship, operate, get paged, fix. Make architectural decisions across service boundaries. Review API contributions from other IaaS teams. Raise the bar in code review, mentor, document the things that aren't obvious. Experience and skills you will need: Strong Software engineer background with DevOps and systems skills. Several years of production Go. Idiomatic, well-tested, and you can justify your design choices. Effective testing - you know when to use each level of the test pyramid. Distributed systems experience: idempotency, retries, partial failures, eventual consistency. Deep relational database knowledge; experience at large scale is a plus. Linux fundamentals: logs, network, processes. Kubernetes and Helm as daily tools. You can debug a misbehaving pod. OpenStack sits beneath our API. You don't need to be an expert, but you should be willing to debug at that layer and learn as you go. You fix what is in front of you. Broken pipeline, flaky test, missing/outdated documentation - you address it, or you bring it up. You can take a half-formed problem statement, identify what needs to happen, challenge it if it's wrong, and drive it to production.