Interview: a Stockholm risk data scientist

An interview with a risk data scientist

Professional headshot of Julia Ekberg, Stockholm risk data scientist

Julia Ekberg is a Stockholm-based risk data scientist at a regional analytics firm. We spoke about the realities of customizing volatility forecasting models for the Scandinavian context, the unique technical challenges, and the career impact of a strong peer feedback culture. Her experience highlights that local knowledge and honest critique matter as much as raw technical skill.

Describe your typical day as a risk data scientist adapting volatility models for Scandinavian markets.

Most of my mornings are spent combing through local market data, looking for outliers that global models tend to ignore. Volatility forecasting in Scandinavia means adapting to regional quirks—seasonal shifts, regulatory events, and unique liquidity issues. My day is a cycle of testing hypotheses, discussing findings with peers, and refining models that rarely behave like their textbook versions.

What are the most rewarding and difficult aspects of your current role?

The highlight is when collaboration uncovers a pattern none of us could spot alone. The challenge is convincing stakeholders that local context matters—what works for one region can mislead in another. The real reward comes from seeing a model actually improve after it’s been through a round of blunt peer review.

How does machine learning change the adaptation process compared to traditional models?

Global machine learning models often struggle with the nuances of local markets. We spend a lot of time retraining algorithms on regional data and running backtests against local shocks. The peer review process is where most mistakes are caught, especially those you’re too close to see yourself.

What advice do you have for newcomers adapting volatility models to local contexts?

For anyone starting out: don’t underestimate the value of local data knowledge. Get hands-on experience with actual market feeds, not just sample sets. Listen to feedback—even the uncomfortable kind. That’s where your blind spots live.

How has your approach to data science changed over your time in the field?

Early in my career, I assumed technical skill would be the main barrier. In practice, the ability to communicate with peers and stakeholders—and to accept criticism—is just as important as coding ability. Technical growth depends on openness to feedback and a willingness to iterate.

Back: Blog

Want technical details?

Download our brochure

Questions on analytics careers?

Join an info session

Cookie usage on this site

We use cookies and similar technologies to enhance site functionality, analyze usage, and remember your preferences. For details, review our Cookie Policy or adjust your settings below.

Essential cookies

Essential cookies are required for secure site access and basic functions.

Analytics cookies

Analytics cookies help us monitor usage and improve services. Data collected is anonymized.

Marketing cookies

Marketing cookies may personalize content or advertising through trusted partners.