Camunda
Software Engineer - Infrastructure
About this role
Camunda is seeking a Software Engineer for its Infrastructure team to enhance its CI/CD infrastructure platform, enabling teams to deploy high-quality software efficiently. The ideal candidate will focus on scaling the platform and improving developer processes without increasing toil, contributing to the company's transition to an AI-first organization.
What you'll do
- Develop and scale the high-load Camunda Infrastructure Platform.
- Ensure reliable build and distribution of product versions.
- Identify and resolve developer pain points in the infrastructure.
- Act as a service-oriented partner to product teams.
- Contribute to the team's roadmap and technical decisions.
What they're looking for
- Kubernetes expertise
- Infrastructure as Code (Terraform, Pulumi, Ansible)
- Experience with cloud providers (GCP, AWS, Azure)
- High-scale CI systems (GitHub Actions, Jenkins)
- Programming knowledge in Python, Groovy, Go, JS, or Java
- Ability to work effectively in remote teams
- Familiarity with AI applications in engineering
Benefits
- Fully remote work environment
- Opportunity for meaningful work
- Focus on personal and professional growth
- Impactful contributions to large-scale projects
- Certification as a Great Place to Work
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Camunda
Camunda builds business process automation and CI/CD infrastructure platforms, with emerging focus on AI-powered process orchestration through products like ProcessOS. The company is hiring Software Engineers for infrastructure scaling and Forward Deployed Engineers to drive enterprise customer deployments across Java and React tech stacks.
- Website
- camunda.com
Likely interview questions
- Tell us about your production Kubernetes experience. What scale have you operated at, and what were the biggest challenges you faced?
- Describe a time when you identified and removed developer pain points in a CI/CD system. What was the impact?