Forward Deployed Engineer

🕒 il y a 10 jours

Postuler Maintenant

Trouver des Emplois à Distance Similaires

Configurer une alerte email pour les nouveaux emplois

📊 Vérifiez votre score de CV pour ce poste

Améliorez vos chances d'obtenir un entretien en vérifiant votre score de CV avant de postuler.

Télécharger le CV

Redpanda Data

Site WebLinkedInTous les Emplois

51 - 200 employés

Fondée en 2019

🏢 Entreprise

☁️ SaaS

🤝 B2B

💰 €100 000 000 Series D - Redpanda Data en 2025-04

Enterprise • SaaS • B2B

Redpanda Data est l'entreprise derrière Redpanda, une plateforme de streaming de données haute performance compatible avec l'API d'Apache Kafka. Redpanda offre un moteur de diffusion de messages à un seul binaire, avec une faible latence et un débit élevé, ainsi que des offres cloud managées conçues pour remplacer facilement Kafka afin de simplifier les pipelines de données en temps réel, les applications orientées événements, les journaux et les métriques. L'entreprise se concentre sur la fourniture d'une infrastructure de streaming de qualité professionnelle pour les équipes de développement et d'exploitation à travers un logiciel auto-géré et des services SaaS/cloud managés.

Description

• Build at the customer site. Write production-quality agents, integrations, and data pipelines on Redpanda ADP, inside the customer’s environment and codebase. What you ship has to work after you leave. • Work in unfamiliar territory, fast. Every customer engagement is a new codebase, a new data environment, a new set of constraints. Ramp quickly, orient to what exists, build on top of it without breaking it. • Own the technical deliverable. Understand what the engagement is supposed to produce, design the technical approach, build it, and hand it off clean — documented, maintainable, and running in production. • Be the Redpanda technical voice with the customer’s engineers. Work alongside their team daily. Earn their trust. Make sure the work integrates correctly with what they already have and what they’ll maintain after you leave. • Drive toward exit from day one. Build with handoff in mind. Write documentation that their team can actually use. Train them on what you built. Don’t create dependencies on you. • Feed learnings back. Identify patterns across engagements — what customers keep needing to build, where ADP makes things hard, what should be productized. Bring that back to Product and Engineering clearly.

🎯 Exigences

• Engineering depth. You write production software. You’ve built backend systems, data pipelines, APIs, or agent systems that ran in production and had real consequences when they broke. Language background is flexible; what matters is that you build things that work. • Agent and integration experience. You’ve built agents, worked with LLM APIs, or built integrations between complex systems. You know what makes an agent reliable vs. brittle, and you’ve made that call in production. • Ability to operate in any environment. You’ve worked in someone else’s codebase, with constraints you didn’t set, in a stack you didn’t choose. You can read unfamiliar code, understand what it does, and extend it without breaking it. • Customer-facing communication. You can work directly with a customer’s engineering team — their leads, their architects, their individual contributors — and be a credible, trusted technical partner. You don’t need a PM to translate for you. • Shipped at a customer site or in a deployment context. You’ve personally been in the room when something hard went live. You know the difference between a demo and a production deployment.

🏖️ Avantages

• Health insurance • Professional development opportunities