🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
You want to take the cloud world by storm with us STACKITEERs and shape the future of Europe with us? That's great! Then STACKIT is the right place for you. Our vision is ambitious: An independent Europe - digital, leading. As a cloud and colocation provider, we are building the secure infrastructure for this. With our server locations exclusively in Germany and Austria, we offer both the Schwarz Group, to which we belong, and external customers a European alternative to international cloud providers and support our customers holistically with individual solutions. As a dedicated STACKITEER, you are part of the STACKIT Products division. This is where our products and services are developed, tested and improved. The impact you will create: Main tasks: As an integral member of the IaaS Infraservices & Observability Team, you will help develop core frameworks and safeguard the reliability of our cloud environment. In this versatile role, you will have the opportunity to work across both observability and stateful service automation. Observability & System Health: Support the design, optimization, and lifecycle management of our central observability stack (including Grafana, Prometheus, VictoriaMetrics, and OpenSearch) to ensure seamless tracing, logging, and metric processing. Kubernetes Automation: Assist in developing and maintaining Kubernetes Operators for stateful services such as MariaDB, Redis, and RabbitMQ. Shared Infrastructure: Manage and maintain central shared services, including the Harbor Container Registry and internal NTP servers. Process Automation: Contribute to automating and enhancing database operations, including backup/restore mechanisms and scaling optimizations. Experience and skills you will need: Programming Skills: Solid foundation in Go (Golang) or Python, with a commitment to writing clean, well-tested code. Cloud-Native & Kubernetes: Good understanding of Kubernetes architecture. Familiarity with-or a strong willingness to learn about-Kubernetes Operators (Controller patterns, CRDs). Versatile Tech Stack: Practical experience or strong familiarity with modern observability ecosystems (Grafana, Prometheus, OpenTelemetry) AND/OR stateful infrastructure (relational databases like MariaDB/PostgreSQL, message queues like RabbitMQ). Agile Mindset: You thrive in an agile "You Build It, You Run It" environment, value quality rigor (Definition of Done), and have a basic understanding of Infrastructure-as-Code (e.g., Terraform, Ansible). Communication & Drive: You are a highly motivated, proactive team player capable of expressing technical ideas clearly within an international, collaborative team. Bonus: Familiarity with OpenStack components and architecture (especially Keystone) is a significant plus. We look forward to receiving your application. [[recruiterName]] · Reference no. [[id]] Stiftsbergstraße 1 · 74172 Neckarsulm, Germany
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.