InterviewHack.ai
Start free
Jobs / Langdock

Systems Engineer - m/f/d

Langdock·Berlinmid

In short

  • →Ingeniero de sistemas que resuelve problemas técnicos complejos en infraestructura crítica.
  • →Trabajas en proyectos rotativos: ejecución distribuida, almacenamiento, aislamiento seguro, servidores de modelos, orquestación de recursos.
  • →Destacado: construyes sistemas que deben ser correctos bajo fallos, escalables y seguros, con foco en medición y mejora real.

Experiencia o habilidad en inglés para trabajo técnico.

Apply on company site ↗Share on WhatsApp
✓ Free to start✓ Runs in your browser✓ First dossier, no card✓ Ready in ~1 minute

In ~1 minute you get: who interviews you, the likely questions answered from your CV, and your CV tailored to this job. Your first dossier is free.

The questions they'll ask you

1. ¿Cómo diseñarías un sistema de ejecución distribuida que garantice idempotencia y resiliencia ante fallos en trabajos largos?

2. Explica cómo manejarías el problema de consistencia en un sistema de metering concurrente con eventos retrasados o duplicados.

3. ¿Qué métricas y herramientas usarías para identificar el cuello de botella en un servicio de inferencia de modelos?

🔒 +7 more questions

No card. Upload your resume and the full dossier is ready in ~1 minute.

🎧Land the interview? Bring the copilot. Our free extension listens to the live interview and flashes 3-4-word anchors from your resume and prep — glance, connect, talk. Get the extension →

💵 USD · Remote · No visa

Not finding what you want? Try Micro1

Micro1 places engineers directly at US companies paying in USD. One vetting, multiple offers — no cold applying.

Get matched by Micro1 →
📬Jobs picked for YOUR resume, every morning on WhatsApp. Free: text “vacantes” and the bot sends your daily matches. Subscribe →

What they ask for

  • ✓Experiencia en sistemas distribuidos o infraestructura de alto rendimiento
  • ✓Capacidad de investigar y resolver problemas técnicos complejos sin documentación
  • ✓Conocimiento profundo en concurrencia, consistencia, y recuperación de errores
  • ✓Habilidades en diseño de arquitecturas escalables y seguras
  • ✓Experiencia con código en producción y operación de sistemas
  • ✓Aptitud para trabajar en un entorno ágil y orientado a resultados

Don't tick every box? That's normal — your free dossier shows your gaps and how to cover them in the interview.

GoPythonKubernetesgRPCPostgreSQLRedisPrometheusGrafanaOpenTelemetryAWS

Who should you write to at Langdock?

Your free dossier identifies the people who'd interview you — their background, what they value, and how to reach out so you stand out before applying.

Where Europe's enterprises adopt AI Langdock is the AI platform used by more than 10,000 companies to give employees secure access to the leading AI models, to build and share agents and to automate repetitive workflows. We have grown past $40M ARR while remaining a small team, and we care deeply about operating efficiently across the entire company. For many enterprises, Langdock is becoming the place where most of the net-new work is produced. As people and agents create more documents, analyses, decisions, and automations inside AI interfaces, the context and data behind that work accumulate within Langdock. This gives us the opportunity to earn a larger role in their technology stack by building a platform they choose to rely on. Our ambition is to build that platform for European enterprises while preserving their control over data, model providers, and deployment environments. We have made meaningful progress at the application layer, but much of the foundation beneath it still needs to be built. You can watch the Meet the engineering team video to get a feeling for how we work. The role 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. This is a project-oriented role rather than ownership of one permanent layer. You might spend a period on distributed execution, then move into storage architecture, workload isolation, or model serving as company priorities change. The constant is sustained investigation of unfamiliar systems and responsibility for turning that understanding into a production system. Systems Engineers own the difficult mechanism and the measurable improvement it creates, whether in correctness, capability, performance, reliability, or cost. They operate what they build, while the Platform owner remains accountable for the service contract and long-term lifecycle around it. What you might work on The systems agenda includes: 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.

Looking for something similar?

Leave your email and we'll alert you when matching jobs appear.

Don't apply unprepared

We research who's interviewing you, tailor your CV and rehearse you live — first one free.

InterviewHack.ai

Prepare for the exact interview: who's interviewing you, a tailored CV, and a real coach.

Product

JobsCompanies hiringAll free toolsResume verdict (Jev)Free cover letterInterview questions by role"Tell me about yourself" answerFree ATS checkerInterview-English checkSalary checkSalary negotiation scriptFree STAR answerLinkedIn headline + AboutLATAM salary reportFree coursesBlogTailored CVSpoken practicePricingAffiliates — 30%

Remote jobs

ReactPythonFull-StackLATAMArgentinaMexicoSee all →

Prepare

Spoken practiceFrontendBackendAI EngineerBy companySell with your CV

Company

For employersAboutContactPrivacyTerms

© 2026 InterviewHack.ai · Your CV is yours. Never used to train anything. · A product of IA-PTY

Similar open roles

Working Student / Internship – Office Operations (m/f/d)

Langdock · Berlin

→

(Senior) Distributed Systems Engineer - m/f/d

Langdock · Berlin

→

(Senior) Platform Engineer - m/f/d

Langdock · Berlin

→

Events Intern (September - December) or Working Student

Langdock · Berlin

→