Erhalte eine Antwort von diesem Arbeitgeber — ein Lebenslauf und ein Anschreiben, die genau auf die Eigenschaften eingehen, die gesucht werden.
LiveEO is seeking an experienced backend engineer to join its product team in Berlin. You will architect, design and implement new features for large geospatial datasets, focusing on scalable, production-grade systems and strong UX considerations across mobile, browser, and backend.
You will lead cross-functional squads and own API evolution, while embracing autonomous, agentic development. We offer a pragmatic hybrid work model in Berlin with senior peers to collaborate with, and a strong
You will work on applications that use deep learning and satellite data and other data sources to help companies and governments fight deforestation, monitor critical infrastructure, and respond faster and more precisely to natural disasters. Our aim is to empower any user in the world to harness the power of earth observation satellites to simplify and improve their daily work.
As one of the most senior engineers on our product team, you will architect, design and implement new features and refactorings from initial idea to production release and then monitoring and maintenance, often in temporary cross-functional squads. Concrete topics you would work on are, for example, the rendering and querying of large volumes of geospatial data efficiently in mobile app, browser and backend, writing the database queries that make that fast, implementing smart logic on this data and building integrations for the growing number of third‑party consumers of our services.
Key responsibilities
Our development lifecycle is a pragmatic scrumban: structured enough to coordinate, loose enough to move fast. Engineers here have real autonomy - you will make plenty of decisions yourself, and you will have senior engineers to think out loud with on the ones that carry more weight. Asking is normal here, at every level.
We take agentic development seriously but we are, sometimes painfully, aware of its limits. Tickets with solid acceptance criteria become agentic specs that agents implement in test‑driven setups. Code review is a mix of agent and human - whichever is most effective for the change at hand. We ship to production at least weekly. And we actively encourage engineers to keep coding and debugging manually to stay sharp; the goal is augmented engineers, not engineers who've forgotten how to program.
Must have
Nice to have
You do not need all of the \"nice to haves,\" and you do not need to match every \"must have\" perfectly.