Data & analytics
Modelling with a business case attached, by a practitioner who knows when a simple heuristic beats a model.
Not every company that wants a data scientist needs one yet, and not everyone carrying the title has taken a model further than a notebook. Done properly, the role is modelling with a business case attached: demand forecasting that changes what you order, pricing support that changes what you charge, credit and churn risk that changes who you call, and optimisation where the constraints are real. Done properly, it also includes saying early when a simple heuristic will beat a model.
The data scientists on Hellenic Talent come from industry data science teams, top consultancies, and quantitative roles in banking and telecoms. They have taken models to production and lived with them afterwards, which is a different discipline from building them.
What to test in the first conversation, whoever you end up hiring.
Lived with data drift
Has run models in production, where data drifts and pipelines break, not only in notebooks and competitions.
Payoff before technique
Starts from the business case and the data you actually have, not from a favourite technique.
Speaks without jargon
Can explain a model to the executive who has to act on it, without hiding behind vocabulary.
Knows when not to model
Willing to recommend a heuristic, or no model at all, when that is the honest answer.
No textbook datasets here
Realistic about the data in Greek and Cypriot mid-market companies, which is messier than the textbooks assume.
A short call is enough to understand the situation and tell you honestly whether the network has the right data scientist for it.
Engagements run remote, hybrid, or on-site, for clients in Greece, Cyprus, and the rest of the world.