#038 ML Никита Васильев и Вероника Голубева. Кто такие дата-инженеры?

#038 ML Никита Васильев и Вероника Голубева. Кто такие дата-инженеры?

#038 ML Nikita Vasiliev and Veronika Golubeva. Who are data engineers?

🎙 Machine Learning Podcast 👥 5K 📅 May 10, 2022 ⏱ 59 min 👁 956 📄 expert opinion 🧭 2026-10-09
Available in: English (current) Français

Keywords

data engineerpipelineSQLSparkHadoop

Summary

The podcast episode discusses the role of data engineers, featuring two senior professionals, Nikita Vasiliev and Veronika Golubeva. They explain that data engineers are responsible for building and maintaining data pipelines, ensuring data quality, and supporting data science teams. The conversation covers differences between data engineers, data analysts, and data scientists, emphasizing that data engineers often work behind the scenes collecting, processing, and delivering data. They share their career paths, noting that both entered data engineering somewhat accidentally after starting with databases. The discussion then focuses on required skills: SQL, Python, algorithm knowledge, and familiarity with big data tools like Hadoop, Spark, Hive, and Impala. They also mention MPP systems such as Greenplum and Teradata. The guests stress that the exact responsibilities and tools vary by company, and there is no one-size-fits-all architecture. They advise newcomers to master core SQL and Python, then learn specific technologies based on job needs. Finally, they discuss how to build data infrastructure from scratch, but admit that ideal solutions depend on business context. The episode is a practical overview for anyone interested in pursuing a data engineering career.

184 words

Critical Evaluation

Value of the Information & Strength of the Argument

The value of the information lies in the direct experience of the speakers, who provide concrete examples of daily tasks, common tools, and career transitions. Their argumentation is grounded in real-world scenarios, such as handling inconvenient data ownership between teams and choosing between different tech stacks. While they do not present formal research or data, their insights are credible due to their senior positions. The discussion is pragmatic, emphasizing practical skills and adaptability rather than theoretical frameworks. The argumentation is coherent, with both guests often agreeing and complementing each other’s points, strengthening the overall message. However, some claims could benefit from more structured evidence or references to industry standards.

Scientific Rigor, Source Quality, Title Accuracy

The scientific rigor is moderate; the episode is an opinion-driven discussion without citations to academic papers or official documentation. The quality of sources is limited to personal experience and references to tools like Spark and Hadoop, but no formal sources are mentioned directly. The description includes links to hackathon platforms (Devpost, MLH) and podcast distribution channels, which are not academic. The title aligns well with the content, as the entire episode revolves around explaining what data engineers are. No apparent disconnect exists. Since no user comments were provided, public reception cannot be evaluated.

217 words

Title / Content Match

The title accurately reflects the content, which focuses on defining the role of data engineers.

Quality & Reliability

7/10

The podcast features experienced data engineers sharing practical insights, but relies on anecdotal evidence and lacks verifiable sources within the episode.

Key Moments

Cited Sources

External References

Contribution & Novelties

The episode offers a practical, experience-based overview of data engineering, filling a gap in typical AI/ML podcasts that focus on data science. It demystifies the role by explaining real-world challenges and tools.

Pour aller plus loin :

  • Apache Spark — Distributed computing framework widely used in data pipelines.
  • Apache Hadoop — Ecosystem for distributed storage and processing of big data.
  • Apache Airflow — Workflow management platform for orchestrating data pipelines.

70 words

Radar Profile

The radar profile shows high scores in technical level and information quantity, but lower scores in reliability and source quality. This indicates a technically rich yet opinion-based discussion, suitable for practitioners but not for those seeking rigorous academic validation.

Reliability 6/10