Short Facts <ul><li>Location: Munich, Germany</li><li>Employment Type: Full-Time, indefinite term</li><li>Salary Range: € 95,000 – 115,000 per year gross, depending on seniority level</li><li>Office First work setup</li><li>Language Requirement: C1 Level English</li></ul> Your Responsibilities <ul><li>Act as the technical bridge between data science and software engineering, helping research models become reliable, maintainable production systems, and helping engineering understand what ML workloads actually need</li><li>Design and build the data and feature pipelines that support Flexa's forecasting and trading models at scale across hundreds of thousands of distributed systems</li><li>Leverage Flexa’s deployment, orchestration, and serving platform to bring models into production, for both batch and real-time workloads</li><li>Establish monitoring and observability for models in production, like drift, data quality, latency, and failure modes </li><li>Partner closely with data scientists on model design and validation, bringing an engineering perspective on scalability, maintainability, and production risk from early on</li><li>Champion engineering rigor and ML best practices to foster an open, data-driven engineering culture.</li><li>Contribute to the technical roadmap, anticipating scaling needs as data volume and model complexity grow</li><li>Opportunity to guide and develop more junior colleagues through design review, code review, and structured feedback</li><li>Be part of a cross-functional team of data scientists, software engineers, and other teams across Flexa's partner ecosystem </li></ul> Your Profile <h3 style="line-height:1.38;margin-top:14pt;margin-bottom:4pt;">Mandatory Requirements</h3><ul style="margin-top:0;margin-bottom:0;"><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">University degree in an engineering or analytical field (Computer Science, Mathematics, Physics, Statistics, Engineering or a related discipline)</li><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">5+ years of engineering experience, with significant time spent supporting or building ML systems in production</li><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">Proficiency in Python and software engineering best practices: testing, code quality, code review, CI/CD, monitoring, and modular code design </li><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">Solid working knowledge of MLOps practices: pipeline setup, deployment, monitoring </li><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">Enough fluency in ML/statistical modeling to collaborate effectively with data scientists and make sound architectural tradeoffs together</li><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">Independent, pragmatic problem-solving with strong attention to detail in a fast-paced environment</li><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">Excellent English communication and interpersonal skills</li><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">Cross-functional collaboration mindset across data scientists, software engineers, and partner-company stakeholders</li></ul> <h3 style="line-height:1.38;margin-top:14pt;margin-bottom:4pt;">Skills to Set You Apart</h3><ul style="margin-top:0;margin-bottom:0;"><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">Experience in energy, power markets, or other near-real-time operational domains</li><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">Familiarity with orchestration tools (Airflow or similar), MLOps toolchains (MLflow, Sagemaker, or similar), and streaming systems (Kafka or similar)</li><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">Hands-on experience with large-scale data tooling: Spark, Dask, or comparable frameworks</li><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">Experience designing or owning near-real-time analytics and/or ML workflows, including observability</li><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">Track record of taking models from research into production on AWS or comparable cloud provider</li></ul> <h3 style="line-height:1.38;margin-top:14pt;margin-bottom:4pt;">This won’t be the right role for you if…</h3><ul style="margin-top:0;margin-bottom:0;"><li style="list-style-type:disc;font-size:11pt;font-family:Arial, sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;text-decoration:none;">You don’t have the habit of defining your own tasks and have a preference for working in clearly separated functions</li></ul> Benefits <ul><li>Virtual Share Options: we offer virtual share options to all our employees</li><li>Professional Development: annual development budget of €3,000 for coachings, trainings, books, and similar</li><li>Health & Sport Subsidy: company-subsidised sports facilities membership, or Public Transportation Subsidy</li><li> Lunch/Dinner Allowance Vouchers: allowance for meals on working days as digital meal vouchers</li><li>Work Equipment: MacBook or Windows laptop, iPhone (also for private use), and an ergonomic workplace setup with company-funded access to leading AI developer tools</li><li>Regular Team Events: knowledge sessions, afterwork, sports, offsites, Halloween, Pride Month, and more</li></ul> A Short Note from Your Future Lead <a style="text-decoration:none;" href="https://www.linkedin.com/in/willirichert/">Willi Richert</a>, VP of Technology — flexa Hi there!I'm Willi, VP of Technology at flexa. I've spent the last 15 years building engineering teams around systems that have to make good decisions fast and at scale. Most recently at Lyft, where I led the mapping organization — 30+ engineers across five countries — and we moved more than 96% of rides off Google Maps onto our own mapping product. Before that I worked on machine learning and conversational AI at Microsoft Bing, and I did a PhD on learning in heterogeneous robot groups, which is a long way of saying that distributed decision-making has held my attention for a while. What pulled me to flexa is that it's the same class of problem with something physical at the other end. We dispatch energy of the Enpal customer fleet in real time against energy markets. If our infrastructure is a few seconds late or a few percent off, customers lose money and the grid gets less flexibility than it could have had. That makes cloud engineering a first-order product concern here rather than a supporting function — which is why this role sits close to the decisions that actually matter. How I work: I'd rather hand you the whole problem, context and constraints included, than a ticket. I care that engineers can see the consequences of what they build, and I'll be direct with feedback and expect the same back — the fastest way to lose a year is for everyone to stay polite about an architecture that isn't working. You won't find everything already built. Some of it is greenfield, some of it needs replacing, and you'll have real influence over which is which. If that sounds like your kind of problem, I'd like to hear from you — and if you're not sure your profile is a perfect match, apply anyway and let's talk. Looking forward to meeting you,Willi

Senior MLOps Engineer (m/w/d) @ Flexa

About this role

Ready to apply?