Wiki
Data Science Careers
Archive-backed career guidance for data scientist roles: role targeting, CV evidence, portfolio signals, interviews, salary, and ambiguous titles.
Related Wiki Pages
Definition and Scope
A data science career is the path into data scientist roles and across adjacent roles. In the DataTalks.Club podcast archive, guests describe that path as a role-fit problem, not a title chase. Candidates need to understand the kind of data scientist role they want. They also need to show work that matches it and ask whether the company has enough data maturity for the role to succeed.
The title can cover product analytics, applied machine learning, research, and experimentation. It can also cover dashboards or first-data-hire work. For the role, see Data Scientist Role. For the interview path, see Data Scientist Interview Roadmap and Data Scientist Interview.
Common Path
Most guests describe the same career sequence. Choose a target role, find the missing skills, build evidence, then use the job search to test fit. Luke Whipps gives the recruiter version in Land Data Scientist Roles. Around 16:15 and 19:50, he connects stronger CVs to industry alignment, real projects, and business problems. Around 37:54, he recommends tailored applications because the candidate needs to map their skills to the company problem.
Sarah Mestiri gives a similar sequence in Tech Job Search Strategy. Around 10:59, she organizes the job search around goals and networking. She also covers CV and strategy. Around 14:30 and 20:01, she asks candidates to define the target role before collecting courses or tools.
Use her episode alongside Job Search and Career Transitions in Data. Without a target role, every portfolio project and CV bullet competes for a different job.
Guest Differences
Guests agree that data science careers need practical evidence, but they differ on where that evidence should come from.
Ksenia Legostay describes a gradual move from project management into analytics and then machine learning in From Project Manager to Data Scientist. Around 8:33, she starts with a skills gap assessment. Around 22:32, she treats planning, stakeholder communication, and KPI work as transferable strengths. Around 32:43, she recommends starting with analysis work and turning it into a portfolio before moving deeper into machine learning.
Andrada Olteanu gives a more project-public path in Career Transition from Analytics to Data Science. Around 14:26 and 32:14, she explains how Kaggle notebooks and GitHub helped her turn analytics experience into data science evidence. Around 36:41, she keeps data validation, domain knowledge, and exploratory analysis as analyst strengths.
Tereza Iofciu adds a caution from the hiring side in Data Science Jobs. Around 20:06 and 23:01, she argues that candidates should look at the actual responsibilities, team setup, and objectives behind a data scientist title. That can mean walking away from a role that’s Data Engineering, Data Analyst Role, or an undefined first-data-hire position.
Skills
Guests treat skills as evidence for a role, not as a universal checklist. Ksenia Legostay names programming and statistics around 13:00 in From Project Manager to Data Scientist. She also names domain expertise. Around 41:07, she adds Git and testing. She also adds Docker, deployment, and clean code because data science work has to move beyond notebooks when a team depends on it.
Misra Turp frames the day-to-day role differently in Data Science Career Playbook. Around 9:01, she describes trained models and pipelines as deliverables. She also includes reports and presentations. Around 30:11, she names stakeholder communication as a major challenge.
Put communication beside modeling and Python, while keeping SQL and statistics in the core skill set. For the technical core, use Data Science, Machine Learning, and MLOps.
Portfolio Evidence
A data science portfolio should show how the candidate works, not only show notebooks. Luke Whipps ties portfolio strength to use-case alignment around 19:50 and 25:04 in Land Data Scientist Roles. The project should show what problem the candidate solved, which tools they used, and what changed because of the work.
Oleg Novikov makes the same point from the interview side in Data Science Interview Guide. Around 2:42, he discusses building a project to stand out. Around 45:46, he suggests cold-start projects, synthetic data, and blogging for candidates who lack industry experience.
Portfolio pages should show problem framing, data choices, evaluation, and limitations. They should also show communication, not only model scores. See Machine Learning Portfolio Projects for project examples.
Public work can help, but the format depends on the target role. Andrada Olteanu uses Kaggle notebooks and GitHub in Career Transition from Analytics to Data Science around 32:14. Misra Turp recommends relevant projects and real-world data around 54:31 and 58:14 in Data Science Career Playbook. For product data science, the project needs business reasoning and metrics. For ML-heavy roles, it needs modeling, evaluation, and production judgment.
CV, Screening, and Interviews
Recruiters and hiring managers screen for clarity first. In Hiring Data Scientists and Analysts, Alicja Notowska explains profile screening around 21:32. She covers education signals around 27:10 and CV clarity around 28:41. Around 32:40, she warns against buzzword-heavy CVs because they make it harder to understand what the candidate did.
Oleg Novikov uses a similar screen in Data Science Interview Guide. Around 18:28, he treats the CV as a landing page for the role. Around 25:51, he emphasizes personal contribution and removing noise. Around 32:03, he moves from business goals to evaluation metrics in case studies.
Use that interview advice with CV Screening, behavioral stories, and SQL. Keep ML fundamentals and take-home tasks in the same prep plan. Use Salary Negotiation when the conversation moves from interviews to offers.
Tereza Iofciu adds that candidates should evaluate the interview process. In Data Science Jobs, she discusses take-home burden around 16:25, role clarity around 23:01, and salary transparency around 37:08. A career page therefore can’t treat every offer as progress. A better role usually has clear responsibilities, a real team context, useful feedback, and a plausible path to growth.
Transitions Into Data Science
Career changers can reuse prior domain knowledge, software habits, product context, and stakeholder experience. They still need data science evidence that matches the role. Ksenia Legostay’s transition from project management shows one path. Keep planning and stakeholder strengths, add statistics and programming, then move from analysis into machine learning.
Andrada Olteanu’s analytics-to-data-science path shows another. Keep data validation and domain knowledge, then make Python, notebooks, and public projects visible.
Alicja Notowska covers career changers around 47:36 and portfolio projects around 59:30 in Hiring Data Scientists and Analysts. Sarah Mestiri covers career changers and return-to-work candidates around 9:27 in Tech Job Search Strategy, then recommends practical work over course collection around 26:28. The transition rule is consistent across these episodes. Use courses to close skill gaps, but let projects, referrals, and role-specific stories support the application.
Related Pages
These pages cover role boundaries, interviews, search, and adjacent career paths.