Skip to content
Pegel

Python jobs in Berlin with no German required

467 active roles

Python backend and data roles at Berlin startups are unusually friendly to people who do not speak German, and the reason is structural. The companies with significant Python codebases are disproportionately AI-native startups, fintech platforms, and data infrastructure companies, and all three of those categories built their engineering cultures around international hiring from the start. A startup building a machine learning product cannot hire only from one country's talent pool and stay competitive; English becomes the working language as a result, and it stays that way.

I classify the German requirement on each job description individually. A data engineering role at a company whose product is entirely B2B SaaS is very likely to be English-first. A Python backend role at a company whose customers are German consumers might expect you to read German error reports or communicate with German-speaking ops staff. The filter here catches the roles where the description is clear that German is not required.

What the roles look like in practice: Python backend here usually means services in Django or FastAPI, with Postgres, some form of async job queue, and a Kubernetes target. Python data roles lean on dbt and Airflow, plus a cloud warehouse, often BigQuery or Snowflake. ML engineering roles pair Python with PyTorch or JAX, model-serving infrastructure, and enough MLOps tooling to make the serving story production-grade. Each subset is meaningfully different, and the job description is where you find out which kind of Python a given team actually needs.

Pegel pulls these from the companies' own ATS feeds daily. When a role is posted, it appears on this page the next morning. When a company closes it, it leaves. Nothing here is stale by design.

Open roles

Showing the 100 most recent of 467 active roles. Browse the full list.

Questions

Why do Berlin Python roles skew English-friendly compared to other backend stacks?
The companies with the largest Python footprints in Berlin are AI startups and fintechs, and data-platform companies. All three built internationally from early rounds. Java and .NET shops, by contrast, tend to serve the German Mittelstand and have always hired locally. That is the difference you see in the language filter data.
What is the typical seniority band for no-German Python roles in Berlin?
Mid to senior, with a noticeable cluster around senior-IC and staff-adjacent titles. Data engineering roles in particular skew senior because the tools and the judgment required have a steep ramp. Junior Python roles without a German requirement are rare but not absent, mostly at AI startups that are growing fast and are not yet selective about entry-level track.
Does the Python / no-German combination narrow the list significantly?
It does narrow it, but Python is deep enough in Berlin's startup layer that the filtered list stays meaningful. Most months there are enough active roles that subscribing with this filter set will send you at least a few alerts per week.
DAILY DIGEST

New Berlin startup roles in your inbox, every morning, Monday to Saturday. Pulled straight from company career pages, filtered to exactly what you ask for. Your current filters are saved with the subscription.

Double opt-in, one-click unsubscribe, no tracking. See privacy for the details.

Related searches