Kestra is the universal orchestration platform — open source, declarative, and designed to orchestrate data pipelines, IT automation, business workflows, and AI/agentic systems.
Trusted by over 10,000 organizations worldwide — including JPMorgan Chase, Bloomberg, FILA, and Crédit Agricole — Kestra orchestrates mission-critical workloads at scale. The open-source project has close to 30,000 GitHub stars, hundreds of contributors, and a fast-growing global community.
In March 2026, we closed a $25M Series A led by RTP Global, with participation from Alven, ISAI, and Axeleo – backed by founders from Datadog, dbt Labs, and Hugging Face.
The RoleWe're looking for a Solution Engineer based in Germany to serve as the technical counterpart to our sales team in the DACH region. You'll work alongside Account Executives to help enterprise prospects understand how Kestra fits their architecture, run technical evaluations, and remove the engineering barriers between interest and adoption.
This is a deeply technical, customer-facing role. You need to be comfortable leading architecture discussions, building proof-of-concept deployments, and answering hard questions about infrastructure, security, and integrations.
This is a fully remote position. We're hiring from Germany for proximity to DACH enterprise customers and timezone alignment with the sales team.
What You'll DoPartner with Account Executives on enterprise deals: lead technical discovery, run product demos tailored to each prospect's architecture, and build proof-of-concept implementations.
Serve as the trusted technical advisor during the sales cycle, answering questions about deployment models, integrations, security, scalability, and migration paths.
Design and build custom demo environments, reference architectures, and workflow examples that map Kestra's capabilities to specific customer use cases.
Lead technical evaluations and POCs, working directly with prospects' engineering teams to validate Kestra in their environment.
Translate customer technical requirements into feedback for the Product and Engineering teams, helping shape the product roadmap based on real field experience.
Contribute to technical sales collateral: architecture diagrams, integration guides, competitive comparisons, and best-practice documentation.
Strong engineering background with hands-on experience in infrastructure, data engineering, or platform tooling (Docker, Kubernetes, Terraform, CI/CD, cloud platforms, or similar).
Experience in a pre-sales, solutions engineering, or technical consulting role, working directly with enterprise customers on technical evaluations.
Ability to lead technical conversations with senior engineers and architects, covering topics like deployment, security, scaling, and system integration.
Fluent in both English and German (written and spoken) at a professional level. You'll engage with DACH enterprise buyers in their preferred language.
Comfortable building working demos and proof-of-concept deployments. You don't hand off a slide deck and walk away; you get into the environment and make it work.
Strong communicator who can bridge the gap between customer requirements and product capabilities, both in live conversations and in written proposals.
Familiarity with orchestration, workflow automation, or data pipeline tools (Airflow, n8n, Terraform, Ansible, or similar).
Experience working with open-source products where technical credibility and community trust influence the sales process.
Past experience as a software engineer, data engineer, or infrastructure engineer before moving into a customer-facing role.
Experience in a B2B SaaS or open-source company, particularly in an early or growth-stage environment.
Knowledge of compliance and security requirements common in DACH enterprise environments (for instance, data residency, on-premise deployment).
Real ownership in a globally distributed, technical team.
Direct exposure to product strategy and company priorities.
A product used for mission-critical workloads — not demos.
Competitive compensation, equity, and health insurance.
Skills Required
- Based in Germany for proximity to DACH customers and timezone alignment
- Strong engineering background with hands-on experience in infrastructure, data engineering, or platform tooling
- Hands-on experience with Docker, Kubernetes, Terraform, CI/CD, and cloud platforms
- Experience in pre-sales, solutions engineering, or technical consulting working with enterprise customers
- Ability to lead technical conversations with senior engineers and architects about deployment, security, scaling, and integrations
- Fluent in English and German (written and spoken) at a professional level
- Comfortable building working demos and proof-of-concept deployments (hands-on)
- Strong communication skills to translate customer requirements into product/technical solutions and written proposals
- Familiarity with orchestration, workflow automation, or data pipeline tools (Airflow, n8n) and configuration/automation tools (Ansible)
- Experience working with open-source products and community-influenced sales processes
- Past experience as a software engineer, data engineer, or infrastructure engineer before moving into a customer-facing role
- Experience in a B2B SaaS or open-source company, particularly early or growth-stage environments
- Knowledge of DACH enterprise compliance and security requirements (data residency, on-prem deployment)
What We Do
Kestra is an open-source orchestration platform that makes both scheduled and event-driven workflows easy. By bringing Infrastructure as Code best practices to data, process, and microservice orchestration, you can build reliable workflows and manage them with confidence. In just a few lines of code, you can create a flow directly from the UI. Thanks to the declarative YAML interface for defining orchestration logic, business stakeholders can participate in the workflow creation process. Kestra offers a versatile set of language-agnostic developer tools while simultaneously providing an intuitive user interface tailored for business professionals. The YAML definition gets automatically adjusted any time you make changes to a workflow from the UI or via an API call. Therefore, the orchestration logic is always managed declaratively in code, even if some workflow components are modified in other ways (UI, CI/CD, Terraform, API calls).









