Software Engineer II (Python) - Supply & Demand at Kpler
Athens
—
Jul 23, 2026
Athens
Jul 24, 2026
What this job asks for AI summary
A mid-level backend engineering role focused on a commodity Supply & Demand platform that processes trade flows, production, and consumption data into market intelligence. Day-to-day work spans data pipelines (Airflow/ETL), Python-based backend services, anomaly-detection systems, and TypeScript distribution APIs, with ownership extending to production monitoring and incident response. Suits an engineer comfortable with complex, messy data who can independently shape loosely defined problems into shipped solutions.
Mid level · 2+ years · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (6)
The job title is 'Software Engineer II', which maps to a Mid-level band. The requirements (2+ years, end-to-end ownership of a feature/service) are consistent with that level, though the mentoring and on-call responsibilities push toward the upper end of Mid.
No work location or country is specified in the posting. Kpler is a global company headquartered in Europe (Paris/Brussels), and the posting references a globally distributed team. The role is not stated as US-based or remote-US, so the US-based flag is set to false and no CBSA is assigned.
The relational database requirement is stated as 'a relational database with real schema evolution' — PostgreSQL is listed as the canonical example but any relational DB would satisfy it; alternatives reflect common peers.
SQLAlchemy is listed with the qualifier 'or equivalent ORM', meaning the ORM requirement is a hard gate but the specific tool is interchangeable; no other ORM is named so alternatives are left empty.
Airflow/Astronomer, TypeScript/Node API stack (NestJS, Express, tsoa, TypeORM), Prophet, and scikit-learn all appear under the 'Desirable' section and are marked as preferred.
No compensation figures are mentioned in the posting.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.