Solutions Engineering · Product Data Analytics · Forward Deployment

Engineer by title. Firefighter for data disasters. I fix (almost) anything that's broken.

I work with product and business teams so data stops being a problem and starts being useful.

No adjectives. Just results from my work.

Results across product, data and delivery, without the usual CV clichés. Each one links to the experience behind it.

15+

teams and projects, one-to-one, across 10 countries: listening to problems and needs, then delivering solutions clients are happy with

OpenSC · MS · Job&Talent

From designing and analysing your data to leaving the system up and running.

I analyse behaviour and metrics, build the infrastructure behind them and work with the team until the solution works, is understood and remains maintainable.

Product data analytics

Product-focused data analytics, A/B testing, forecasting, ML, LLMs and agents.

Data / analytics engineering

Data modelling and warehouses. Building, optimising and orchestrating datamarts and ETLs with SQL, Python and dbt.

Business intelligence

Dashboards, reporting and self-service tools so the team can answer its own questions without depending on a data analyst every five minutes.

Solutions engineering

Full lifecycle: design, development, implementation, maintenance and continuous improvement of data solutions.

Forward deployment

Embedding with clients and teams to remove blockers, modernise integrations and support implementation, so the team can keep using the solution without depending on me.

Workflow automation

Scripts, workflows and internal tools that remove manual overhead and let boring tasks run themselves.

A few projects, because talk is cheap. The rest are in the portfolio.

Between projects, I keep building things. My CV says what I have done; these projects show what I know how to build.

Research, consulting, startups. Different worlds, same standard.

Each environment has its own pace and rules. Having worked across all three helps me understand both the business conversation and what needs to be built next.

Shall we talk?

A problem, a proposal or just the urge to talk about data: any of the three is a good reason to write to me.

eduardoalmazang@gmail.com