Time since we first saw it
Day 30
Similar jobs usually come down between day 6 and day 70.
From 4,444 similar postings that came down. Coming down is not always a hire.
Employment Type: Full-Time, indefinite term Salary Range: € 95,000 – 115,000 per year gross, depending on seniority level Office First work setupRead the full posting
Location: Munich, Germany Employment Type: Full-Time, indefinite term Salary Range: € 95,000 – 115,000 per year gross, depending on seniority level
Employment type in the employer’s posting: FestanstellungFrom the employer’s posting
Build data and feature pipelines for forecasting and trading models at scale
Deploy batch and real-time models using Flexa's serving platform
Set up monitoring for models in production: drift, data quality, latency, failures
Partner with data scientists on model design and validation
Guide junior colleagues through design and code reviews
Design and build the data and feature pipelines that support Flexa's forecasting and trading models at scale
Leverage Flexa’s deployment, orchestration, and serving platform to bring models into production, for both batch and real-time workloads
Establish monitoring and observability for models in production, like drift, data quality, latency, and failure modes
Partner closely with data scientists on model design and validation
Opportunity to guide and develop more junior colleagues through design review, code review, and structured feedback
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.
From the employer’s posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 30
Similar jobs usually come down between day 6 and day 70.
From 4,444 similar postings that came down. Coming down is not always a hire.
2 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- 5+ years of engineering experience, with significant time spent supporting or building ML systems in production - Proficiency in Python and software engineering best practices: testing, code quality, code review, CI/CD, monitoring, and modular code design - Solid working knowledge of MLOps practices: pipeline setup, deployment, monitoring
- Experience designing or owning near-real-time analytics and/or ML workflows, including observability - Track record of taking models from research into production on AWS or comparable cloud provider This won’t be the right role for you if…
- Experience in energy, power markets, or other near-real-time operational domains - Familiarity with orchestration tools (Airflow or similar), MLOps toolchains (MLflow, Sagemaker, or similar), and streaming systems (Kafka or similar) - Hands-on experience with large-scale data tooling: Spark, Dask, or comparable frameworks
- Familiarity with orchestration tools (Airflow or similar), MLOps toolchains (MLflow, Sagemaker, or similar), and streaming systems (Kafka or similar) - Hands-on experience with large-scale data tooling: Spark, Dask, or comparable frameworks - Experience designing or owning near-real-time analytics and/or ML workflows, including observability
Complete your application on flexa.jobs.personio.com. The employer’s form will show what is required.
Already applied? Track this application
New ML Engineer postings at the employers we follow are up 12% over the last 5 weeks compared with the 5 before.
Each bar is one week of new postings. The darkest bars are the last 5 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under ML Engineer, by the work the posting describes.
ML engineers put machine learning models into products. They write the code that trains, ships, serves and monitors models so a recommendation or prediction works for real users.
Postings ask for strong Python and software engineering, a framework such as PyTorch, cloud services, and more and more often experience with large language models.
A data scientist often works out which model to build; an ML engineer makes it run reliably in production.
The government has no code for ML engineers, so these figures are for the closest group, computer and information research scientists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1221.
Location: Munich, Germany
Employment Type: Full-Time, indefinite term
Salary Range: € 95,000 – 115,000 per year gross, depending on seniority level
Office First work setup
Language Requirement: C1 Level English
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
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
Leverage Flexa’s deployment, orchestration, and serving platform to bring models into production, for both batch and real-time workloads
Establish monitoring and observability for models in production, like drift, data quality, latency, and failure modes
Partner closely with data scientists on model design and validation, bringing an engineering perspective on scalability, maintainability, and production risk from early on
Champion engineering rigor and ML best practices to foster an open, data-driven engineering culture.
Contribute to the technical roadmap, anticipating scaling needs as data volume and model complexity grow
Opportunity to guide and develop more junior colleagues through design review, code review, and structured feedback
Be part of a cross-functional team of data scientists, software engineers, and other teams across Flexa's partner ecosystem
University degree in an engineering or analytical field (Computer Science, Mathematics, Physics, Statistics, Engineering or a related discipline)
5+ years of engineering experience, with significant time spent supporting or building ML systems in production
Proficiency in Python and software engineering best practices: testing, code quality, code review, CI/CD, monitoring, and modular code design
Solid working knowledge of MLOps practices: pipeline setup, deployment, monitoring
Enough fluency in ML/statistical modeling to collaborate effectively with data scientists and make sound architectural tradeoffs together
Independent, pragmatic problem-solving with strong attention to detail in a fast-paced environment
Excellent English communication and interpersonal skills
Cross-functional collaboration mindset across data scientists, software engineers, and partner-company stakeholders
Experience in energy, power markets, or other near-real-time operational domains
Familiarity with orchestration tools (Airflow or similar), MLOps toolchains (MLflow, Sagemaker, or similar), and streaming systems (Kafka or similar)
Hands-on experience with large-scale data tooling: Spark, Dask, or comparable frameworks
Experience designing or owning near-real-time analytics and/or ML workflows, including observability
Track record of taking models from research into production on AWS or comparable cloud provider
You don’t have the habit of defining your own tasks and have a preference for working in clearly separated functions
Virtual Share Options: we offer virtual share options to all our employees
Professional Development: annual development budget of €3,000 for coachings, trainings, books, and similar
Health & Sport Subsidy: company-subsidised sports facilities membership, or Public Transportation Subsidy
Lunch/Dinner Allowance Vouchers: allowance for meals on working days as digital meal vouchers
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
Regular Team Events: knowledge sessions, afterwork, sports, offsites, Halloween, Pride Month, and more
Willi Richert, 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
Selected passages from the saved posting. Check the full description for conditions and exceptions.
Employment Type: Full-Time, indefinite term Salary Range: € 95,000 – 115,000 per year gross, depending on seniority level Office First work setup
München
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.