As a Back-end / Data Engineering Intern you will be a member of the Data Ops Team. This position implies close collaboration with all members of the team, as well as members of our Data Science, Data Analyst, Full-Stack and DevOps Teams.

Primary objectives of a Back-end / Data Engineering Intern are:

• Design and develop software components for data collection (connectors for various IoT devices and third-party services, web hooks) and ingestion of collected data.

• Design and develop software components for data processing (for example, with Python Pandas), as well as other internal software, tools and APIs to support the data processing.

• Automate data processing tasks and their monitoring in production (for example, orchestration of batch processing jobs using Airflow).

• Design efficient data models using various storage technologies (cloud file storages, HDFS, relational DBs and non-relational DBs, dbt).

• Collaborate with DevOps Engineers for production delivery and related objectives.

We are looking for a student interested in general back-end, or distributed, or data engineering that is studying for a postgraduate degree, a master (M2), or an equivalent university course and is looking for a final 6-month internship. Candidates for this position are expected to have:

• Strongly engineering-oriented profile. (Please, note that this position is not suitable for the typical requirements of research internships, and is oriented towards software engineering).

• Strong programming skills in Python. Experience with other languages is a plus.

• Experience with SQL and Git.

• A good taste for high quality software. Rigor.

Knowledge in all of the following areas is a plus:

• Pandas

• DBT, Trino

• Apache Iceberg

• Docker, Kubernetes

• Cloud Platforms (AWS / GCP / Azure)

• Agile (Scrum) or Lean (Kanban)

Being passionate about IT ourselves, we are looking for a likewise passionate person with a good team spirit.

• Phone call. 30 minutes. Objective: confirm the intent and the match.

• Technical interview. A lot of pair programming, coding, design, a little theory, a few non-technical questions. No whiteboard programming, no trick questions. In the office (preferred) or remote. 4 hours with breaks.

• Fit interview. Meet more team members. In the office only. 2 hours.

Optionally, we may propose a take-home exercise, remote with no deadline. It reduces the time spent during the technical interview and may take about 4 hours to complete.