-intro: "How can you tell if a "data scientist" job is really a data engineering role — or a mismatched hire waiting to happen? In this episode, Tereza Iofciu, PhD and seasoned data practitioner, walks through practical ways to spot misleading data job titles, hiring red flags, and how to build clearer, healthier data teams. Tereza brings experience across data science manager, data scientist, data engineer and product manager roles, plus teaching and community leadership (neuefische, PyLadies Hamburg, PSF community award), grounding her advice in real hiring and team-building work. <br><br> We cover why companies rename roles, examples from Scala, Elasticsearch, ETL and Airflow stacks, and the costs of vague job descriptions. You’ll get a role-clarity checklist (team structure, objectives, responsibilities vs. tech lists), signals of data maturity, interview pitfalls (time-consuming take-home tasks, syntax-focused tests), red flags in descriptions (long tech lists, “rockstar” language), and tactics for researching employers (LinkedIn, team pages, conference talks). Also discussed: salary transparency, remote-work fit, retention and career ladders. <br><br> Listen to learn concrete signals and questions to evaluate job descriptions, interviews, and shape better data hiring and team design."
0 commit comments