Systems Engineer - m/f/d

Systems Engineers solve our most complex technical problems inside and across Langdock's shared services when existing building blocks or standard architectures are insufficient. These are problems where correctness under failure, performance, scale, security, and cost interact.

• Distributed state and execution. Design systems that remain correct when work is concurrent, long-running, retried, resumed, or moved between processes. Define explicit invariants for ordering, idempotency, recovery, and tenant isolation.
• Storage and data systems. Improve how large volumes of customer and agent-generated data are stored, versioned, moved, and recovered while preserving consistency, data residency, and predictable performance.
• Secure compute for agents. Develop the isolation, runtime, and scheduling mechanisms behind a shared sandbox service for untrusted code. The system needs persistent filesystems, deny-by-default networking, scoped mounts, fast startup, suspension, resumption, and predictable scheduling without weakening the security boundary.
• Inference systems. Improve the serving systems beneath the Model Gateway, optimizing throughput, latency, accelerator utilization, reliability, and cost. The work is measurement driven: understand the workload, identify the actual bottleneck, and decide where changes to serving, scheduling, caching, model format, or hardware create structural advantage.
• Resource scheduling and isolation. Make CPU, memory, storage, network, and accelerator capacity explicit so one workload cannot degrade another. Improve placement, admission control, backpressure, autoscaling, and recovery across deployment environments.
• Billing and usage metering. Build the concurrent metering mechanism behind the billing capability, accounting for heterogeneous units such as model tokens and sandbox compute time. It must stay correct when many workloads report concurrently, events arrive late or more than once, and long-running jobs reserve capacity before their final usage is known. This involves idempotent ingestion, atomic reservations, reconciliation, and auditable records.
• Own the difficult mechanism and the measurable improvement it creates, whether in correctness, capability, performance, reliability, or cost. Operate what you build, while the Platform owner remains accountable for the service contract and long-term lifecycle around it.

• You have owned technically difficult production systems in areas such as distributed systems, databases, runtimes, inference, networking, or storage. You operate what you build and remain responsible for it after deployment.
• You reason from first principles, form testable hypotheses, and use measurement to understand unfamiliar behavior. You investigate beyond the first working solution until you understand the underlying mechanism.
• Given an underspecified problem, you identify the most important invariant, decide where depth will change the outcome, and defend what you deliberately leave out.
• You reason precisely about concurrency, isolation, ordering, data loss, and failure, while finding pragmatic ways to improve performance, reliability, or cost without unnecessary complexity.
• You use AI tools as leverage while verifying their output and retaining ownership of the result. You communicate complex systems clearly, expose uncertainty, and work constructively with others.
• You need an existing right to work in Germany. We do not currently sponsor visas.

• All roles include equity.
• Salaries are tied to levels, not negotiation.
• Most engineers start around 8:30. We usually eat lunch together, and dinner is available for people who stay later. Running and gym are part of the routine for many of us.