Jupyter Experts in Munich
in minutes from 15,000 CVs with the power of AIHire experts who use Jupyter notebooks and JupyterLab for data analysis, model prototyping, reproducible research, and internal reporting. FRATCH matches you fast and precisely with vetted, available freelancers.
Meet FRATCH Experts in Munich, who have recently used Jupyter
Michael Nelz
Last position:
Senior ML Engineer, AI Engineer at Lanxess AG
- Deployment and scaling of existing ML initiatives, including demand and cash flow forecasts.
- Building robust monitoring with mlflow for data stability, model performance, and drift detection, as well as implementing additional ML use cases.
- Further development of an Agentic AI chatbot for transparent and easy-to-understand model explanations.
Philipp Grunert
Last position:
Data Scientist & ML Engineer at Data-Science Factory GmbH
- Building, implementing and selling automated Data Science solutions such as Scorecard Factory and Forecast Factory
- Implementation of automated end-to-end cloud processes
- Development of LLM and NLP models
- Creation of interactive reports
- Support for national and international large corporations as well as medium-sized companies in implementing ML projects
Thomas Hoefkens
Last position:
Senior MLOps, DevOps Engineer at Trianel Energy
- Build and operate an end-to-end MLOps platform on Azure ML and Kubernetes (Kubeflow) for the automated deployment, monitoring, and scaling of forecasting models (including Temporal Fusion Transformer, Informer, Autoformer).
- Implement CI/CD pipelines in Azure DevOps for the full ML lifecycle – from resource provisioning (Terraform), data transformation (Hugging Face Datasets, Pandas, PyTorch, CUDA cluster) through training and evaluation to model registry and endpoint deployment.
- Integrate MLflow for experiment tracking, model versioning, performance monitoring, and automated registration in the Azure Model Registry.
- Develop and containerize PyTorch training jobs (Azure Notebook, Jupyter Notebooks) for price and time series forecasting (PFC models) with automatic rollout via Azure ML Endpoints and REST/gRPC interfaces, Docker containerization, secured with OAuth 2.0.
- Set up monitoring and alerting mechanisms (Prometheus, MLflow Metrics), log centralization, and cost monitoring.
- Automate infrastructure provisioning and model deployment using Terraform, Helm, and Azure CLI; connect to existing market data systems and event pipelines.
- Migrate existing workloads and databases (IONOS → Azure, MongoDB) with integration into central MLOps workflows and internal networks.
- Extend the platform with LLM-based tools (LangChain, LangServe) to integrate GPT-based analysis modules into existing Spring Boot services for market anomaly detection and automated reports.
- Analyze and architect a software solution to process large volumes of data efficiently (>3000 messages/sec.) (market data store).
- Spring Boot / Java 21 container development with RabbitMQ for distributing stock market data via MongoDB (Kubernetes) with fast storage of data in Redis RMaps, deduplication, forwarding messages to Read Model queues, and building Read Models for UI display in MongoDB.
- Integration of RESTHeart to create a REST API for MongoDB.
- Build an Angular frontend to simplify data queries and master data maintenance.
- Agentic coding with remote and local LLMs (Claude Sonnet, Ollama Qwen) and MCP servers.
- Develop Python scripts for transforming and cleaning incoming stock market data (Pandas, scikit-learn).
Serge Kalinin
Last position:
MLOps (machine learning operations) at REWE Digital GmbH
- It is like a startup within REWE, where we have to build a new forecasting system on Google Cloud Platform from the scratch. Although, officially my role is called MLOps, my actual tasks also include development of data processing pipelines (data engineering) and data scientists tasks such as feature engineering and model trainings.
- GCP: Terraform (tofu), Vertex AI (Kubeflow), Cloud Run, IAM, Google Cloud Storage, BigQuery, Artifact Registry
- Data engineering: Snowflake as the main data warehouse, Terraform, DBT for data model implementations
- CI/CD: GitLab. We have built a CI/CD pipeline that automates deployments of new releases up to production environment
Michael Ternes
Last position:
ETL Developer at Insurance service provider
DWH for customer and financial data
- Extension of the DWH with new data sources
- Report development
- Data quality management
Methodology: Scrum
Tools: Atlassian Confluence & Jira
Databases: Microsoft SQL Server
Programming languages: SQL, T-SQL
ETL: Microsoft SQL Server Integration Services (SSIS)
Frontend platform: PowerBI, Microsoft Reporting Services
Vitaliy Ryumshyn
Last position:
DevOps GitOps (temp) at Signal Iduna
- Responsible for Openshift/Kubernetes on-prem administration and developer support.
- Developed URP infrastructure automation with Python, Ansible, Kustomize and ArgoCD, Argo Workflow/Events stack.
- Wrote smoke and load tests for URP infrastructure utilizing Python, Kustomize and ApplicationSets.
- Helped to set up and deploy URP infrastructure in Google Cloud, GKE.
- Set up monitoring for URP and ArgoCD stack with Splunk Cloud.
- Performed system administration tasks across RedHat Linux, Kubernetes/Openshift, ArgoCD, GitLab, Bitbucket Enterprise, Kafka and MongoDB.
Sara Zarei
Last position:
Data Analyst / Analytics Engineer at IDG Tech Media GmbH
- Designed, built, and maintained scalable ETL/ELT data pipelines using Python, SQL, REST APIs, AWS Lambda, S3, PostgreSQL RDS, EventBridge, CloudWatch, Docker, Apache Airflow, and BigQuery – integrating data from GA4, Google Ads, Meta Ads, CMS, CRM, newsletters, events, and B2C ordering systems into analytics-ready datasets.
- Built a cross-brand lakehouse architecture from AWS to BigQuery – transforming raw JSON/CSV data into structured, partitioned, and reusable reporting layers with staging, intermediate, canonical, and mart models.
- Designed relational and dimensional data models: 3NF staging models, star schemas, fact tables, dimension tables, daily KPI aggregates, and dashboard-optimized marts for marketing, content, subscription, event, CRM, and revenue analysis.
- Implemented production-grade data quality and pipeline reliability features: incremental loads, idempotent upserts, deduplication, schema validation, row matching, null checks, anomaly detection, freshness monitoring, logging, retries, and error alerts.
- Automated cross-brand reporting processes and data products – pipelines for 73 newsletter campaigns, 31 lead list syncs, 52 event partner reports, and a 500K-record company matching pipeline; reduced manual data preparation by approx. 70% and increased analyst productivity by approx. 30%.
Christian Schulz
Last position:
Data-Scientist/AI Engineer at The Marcom Engine GmbH & Co. KG
- Concept creation and implementing AI Agents in AWS Cloud
- Continuously alignment with stakeholders
- Collaborate with DevOps
- Technologies: Git, CI/CD (GitHub Actions), Python/ML, Streamlit, Deno/typescript, AWS SAM, AWS Bedrock, AWS Lambda, AWS Dynamo DB, AWS S3, AWS Event Bridge etc.
Raghu Ram Vadali
Last position:
Telco Customer Churn Prediction – End-to-End ML Pipeline at Self-Initiated Project
- Designed and implemented a full machine learning pipeline for churn prediction using the Telco dataset.
- Applied preprocessing techniques including missing value handling, categorical encoding, feature scaling, and PCA.
- Built and compared over 15 models (logistic regression, random forest, XGBoost, etc.) and evaluated them using accuracy, precision, recall, F1 score, ROC AUC, and PR AUC.
- Tuned hyperparameters with GridSearchCV, achieving 80.6% accuracy with random forest and XGBoost.
- Created visual reports (bar plots, heatmaps, radar charts) to interpret model performance and churn drivers.
- Exported reusable pipelines and trained models with joblib for deployment.
Sebastian Dirndorfer
Last position:
Data Scientist at CLADE GmbH
- Designed and implemented a robust Python-based data processing framework that supported the transition from R to Python and significantly improved data science productivity by providing maintainable, standardized modules for frequently used workflows, following coding best practices and DevOps principles
- Evaluated, trained, and deployed machine learning models on cloud platforms and edge devices, enabling fully automated mid-infrared (MIR) data evaluation pipelines that eliminated manual analysis steps and significantly shortened the time from measurement to prediction for customers and internal stakeholders
- Analyzed and interpreted multivariate MIR spectral data from the company’s proprietary analyzer using R and Python, supporting reliable identification and quantitation of chemical compounds in solution
Stephan Sahm
Last position:
Senior Data/ML Consultant & Technical Lead at Jolin.io
Role: Software Engineer & Applied Mathematician (Mathematical optimization for scheduling; duration: 1 months; team setting: Team of 2, remote; technologies: JuMP, Julia, Pluto, Svelte, JavaScript, TypeScript, JetBrains Space, Terraform, Nomad)
Role: Software & Cloud & Web Engineer (Building scalable data science compute cluster from scratch; duration: 11 months; team setting: Team of 1, on-site; technologies: Terraform, Kubernetes, k8s ingress, k8s services, k8s RBAC, k8s networking, k3s, etcd, S3, DNS, certificates, Julia, Pluto, JavaScript, Tailwind, Astro, npm, Parcel, Preact, MUI, JWT, AWS SQS, AWS RDS, Python, GitLab, GitHub)
Role: AI & Web Engineer (Custom ChatGPT service; duration: 1 months; team setting: Team of 2, remote; technologies: Python, Poetry, LangChain, Tailwind, ChatGPT API, Flask, FastAPI)
Role: Architect & Data Engineer (Central datalake setup and ingestion; duration: 9 months; team setting: Team of 5, remote; technologies: Infrastructure-as-code, AWS CDK, Python, Boto3, PySpark, AWS Glue, IAM, S3, ECS, Fargate, Lambda, Apache Hudi, DeltaLake, Databricks, GitHub, Jira, Miro)
Role: Software Engineer (PoC Julia migration of scikit-decide; duration: 1 months; team setting: Team of 2, remote; technologies: Python, Julia, GitHub)
Maziyar Khorrami
Last position:
Data Engineer at MSD Germany
- Lead Architect to design and implement the data lake and ETL Pipeline using AWS Stack
- Performance Optimization of Data Ingestion of ETL Pipeline
- Development of Data Validation using Great Expectations
- Leading of the data migration for two sources exchanges
- Data Modeling in AWS Redshift
MLOps
- Model inference implementation by mlflow and AWS SageMaker
- Feature Engineering for the running ML Models ( Recommender Engineer, Clustering )
- Implementatino of Model Registry and artifactory using mlflow
- Historization an Profiling of the Input Data Using AWS Glue Crawler and AWS Data Catalog
- Feature importance using mlflow
Tech. Stack: Python 3, AWS Glue, AWS Step Fucntion, AWS Lambda, AWS EventBridge, AWS IAM Role, AWS SageMaker, AWS EC2, AWS Glue Crawler, AWS CloudWatch, MLFlow, ETL, Data lake, GitHub Action, Terraform, Jenkins, Ansible playbooks (Infrastructure as Code), CI/CD, GitLab, SQL, PySparkSCRUM, Agile, Jira, BigData, VSCode, DBeaver, MSSQL, MySQL, grafana, Docker, Linux, Bash, MapReduce, Data Modeling (ORM), Pandas, YAML, SQL-Alchemy
Stefan Corsten
Last position:
SSIS Development at Stadtsparkasse München
- Replacement of a Java application and the Oracle DB for loading the internal WerWasWo system using SSIS.
- Development of SSIS packages to load text files into the database (SQL Server)
- Development of a database project for deployment on various servers
- Creation of queries to monitor the loading runs
- Development of a PowerShell script to automate the deployment of the SSDT projects.
- Oracle, SQL Developer, Microsoft SQL Server 2022 on-premises, SQL Server Management Studio v21, Visual Studio 2022, SSIS, SSDT, PowerShell.
Martin SvÃtek
Last position:
Business Intelligence Data Analyst at webeet
- Optimized SQL data pipelines for clean insights.
- Analyzed and visualized trends with Python.
- Improved dashboards and automations.
- Worked with Google Sheets, GCP, Snowflake, dbt, Spreadsheets/Excel, Databricks, PySpark, and Fivetran.
Nina Nowak
Last position:
ESG Data Analyst (Volunteer, part-time) at Climate Accountability API
- Development and validation of a data model and ESG rating pipeline
- GenAI governance
Discover over 15,000 top freelancers
Statistics of experts using Jupyter
Aggregated from the professional profiles of matched freelancers.
Experience
18 years (Germany: 15 years)
Position duration
2.1 years (Germany: 2.9 years)
Positions per freelancer
12 (Germany: 9)
Top business areas
Information Technology, Product Development, Business Intelligence
Top industries
Information Technology, Education, Healthcare
Certification focus areas
Information Technology, Business Intelligence, Project Management
Bachelor's degree or higher
100% (Germany: 98%)
Master's degree or higher
74% (Germany: 80%)
Doctorate
21% (Germany: 19%)
Certifications per freelancer
2 (Germany: 3)
Most common languages
German, English, Spanish
Speak two or more languages
100% (Germany: 99%)
Based on our profile pool as of 30 Aug 2026.
Daily rate distribution
The chart shows how the daily rates of freelancers in this technology in Munich are distributed, based on recent contracts on our platform. Each bar covers a rate range — its height shows how many freelancers charge within that range.
Average rates of experts in Munich using Jupyter
Rates are based on recent contracts and do not include FRATCH margin.
The average daily rate is the mean of all daily rates from recent contracts of comparable freelancers on our platform.
The median daily rate is the middle value of all daily rates — half of comparable freelancers charge less, half charge more. Unlike the average, it is barely affected by outliers.
Calculated based on our freelancers’ daily rates as of 30 Aug 2026. Actual rates may vary depending on seniority level, experience, skill specialization, project complexity, and engagement length.
About the technology
Notebook work
Jupyter is an interactive environment for Python, R and other languages. Companies use it to explore data, test ideas, document analysis and share results in a readable format. It is common in analytics, research, and machine learning work where code and explanation belong together.
Common setups
- Jupyter Notebook for step-by-step analysis and reports
- JupyterLab for larger projects and multi-file workflows
- Kernels, widgets and extensions for richer notebooks
- Version control practices that keep notebooks usable
- Export paths to HTML, PDF or slides for stakeholders
Where it helps
Teams bring in Jupyter specialists when they need clear, repeatable analysis instead of one-off scripts. Typical work includes data cleaning, exploratory analysis, model prototyping, dashboard support and internal knowledge sharing. In Munich, this often fits analytics, mobility, software and industrial projects that need fast insight.
Strong profiles
Good professionals keep notebooks tidy, readable and reproducible. They know when to split logic into modules, how to manage dependencies, and how to avoid fragile notebook state. Strong Jupyter work is not just writing cells; it is making analysis easy to rerun, review and extend.
When to hire
- A notebook prototype needs to become a stable workflow
- Results must be explained to non-technical stakeholders
- Data exploration is slow or hard to repeat
- Jupyter runs locally but needs cleaner team usage
- Python, pandas and visualization work need support
Ecosystem fit
Jupyter is often used with pandas, NumPy, scikit-learn, matplotlib, seaborn and SQL tools. In larger teams, JupyterHub can support shared environments and controlled access. The best freelancers also understand data sources, file formats and basic deployment paths so notebooks fit the wider stack.
Frequently asked questions
Before you brief your next project: the most common questions about Jupyter.
Jupyter is used for interactive data work where teams need to explore, explain and share analysis in one place. It fits data cleaning, reporting, experiment tracking and model prototyping. Many companies also use Jupyter Notebook or JupyterLab for internal research and reviewable workflows.
Jupyter is better when you need visible steps, quick iteration and mixed text plus code. Plain scripts are often better for production jobs, automation and packaged software. Many specialists use both: notebooks for discovery, scripts or modules for the stable end result.
Jupyter work often starts in Notebook, but JupyterLab is usually the better choice for larger, more complex work. It gives a stronger interface for multiple files, terminals and extensions. If your team shares many notebooks or moves between analysis and debugging, JupyterLab is usually easier to manage.
A strong Jupyter specialist usually knows Python well, especially pandas, NumPy and plotting tools like matplotlib or seaborn. SQL is also common when notebooks connect to databases. For machine learning work, scikit-learn and good data handling habits matter a lot.
Jupyter projects vary widely. A simple analysis notebook may need only a focused specialist, while reproducible research, shared environments or machine learning workflows need someone who understands structure, dependency handling and collaboration. The key is matching the scope to the notebook’s role in your process.
Yes, Jupyter work is often remote because notebooks, data files and review comments travel well online. For Munich-based teams, remote collaboration works well when access to data is controlled and expectations are clear. On-site sessions can still help when a project needs workshops, stakeholder review or sensitive data handling.
Look for clean notebooks, clear reasoning and results that can be rerun without guesswork. A strong Jupyter professional explains assumptions, separates exploratory steps from final logic and avoids notebooks that only work on one machine. Good signs are readable structure, stable outputs and careful data handling.
Jupyter is a strong starting point for discovery, prototypes and communication, but it is not always the final form. Good specialists know how to move useful logic into reusable Python modules or services when the project matures. That makes it a practical choice for teams that want to test ideas before they harden them.
The average hourly rate of freelancers in Munich, Germany who have used Jupyter in their recent projects is 90 €, which corresponds to a daily rate of about 720 € based on an 8-hour working day.
Of the freelancers in Munich, Germany who have used Jupyter in their recent projects, 100% hold at least a Bachelor's degree, 74% hold at least a Master's degree, and 21% hold a doctorate.
On average, freelancers in Munich, Germany who have used Jupyter in their recent projects have 18 years of professional experience, with a single engagement typically lasting around 2.1 years.
The most common languages among freelancers in Munich, Germany who have used Jupyter in their recent projects are German (100%), English (100%), and Spanish (29%).
The most common industries among freelancers in Munich, Germany who have used Jupyter in their recent projects are Information Technology (90%), Education (48%), and Healthcare (48%).
The most common business areas among freelancers in Munich, Germany who have used Jupyter in their recent projects are Information Technology (95%), Product Development (76%), and Business Intelligence (71%).
Main locations of FRATCH Experts, who have recently used Jupyter
Our freelancers and interim experts are at home across the DACH region — available on-site in the major business hubs or fully remote. Choose a location to discover matched specialists, local market insights and up-to-date availability.
Request a free demo
Get in touch with the FRATCH team and we will get back to you within 4 hours.
Would you rather directly get in touch?
We always have the time for a call or email!

Berlin
Frankfurt