Build analytics people can trust.
Help define what analytics looks like in an AI-first world.
Most analytics platforms ask organisations to trade control for insight.
For almost 20 years, Matomo has shown there is another way: powerful, transparent and trustworthy analytics that respects privacy, gives organisations ownership of their data, and helps people understand what's happening, make better decisions, and improve their work.
More than one million websites use Matomo.
That means you'll work on software that is widely used, technically demanding, and close enough to customers that your work has a visible impact.
It's a rare opportunity for engineers: solving meaningful, complex product problems while seeing the difference your work makes for customers.
We are independent, profitable, and open source.
We are not trying to become a smaller copy of Big Tech analytics platforms.
We are building a different kind of analytics company: one where privacy, transparency, customer control, and product quality are part of the core product, not marketing claims.
This role focuses on Matomo Core, the foundation of our product and the platform our open-source users, cloud customers, and wider plugin ecosystem depend on.
If you want unusually high ownership, visible impact, hard product & platform problems, and the opportunity to strengthen a widely used open-source platform , Matomo is worth a serious look.
Why this role matters Matomo Core is the foundation of our open-source product, cloud platform, plugins, integrations and customer-facing features.
It has evolved over many years and operates across a wide range of environments, use cases and data volumes.
Every improvement to Core benefits customers, open-source users, plugin developers and engineering teams across the Matomo ecosystem.
We are bringing responsibility for Core into a newly formed European team.
You'll help shape how this team works, where it focuses and how it creates the greatest impact across Matomo.
As a Product Engineer, you’ll help decide where Core can create the greatest impact.
That could mean solving a difficult customer problem, strengthening an existing capability, creating a new platform capability, or simplifying the Core platform to make it easier to evolve.
You’ll work on a mature and technically complex product.
The challenge is not simply to preserve what exists.
It is to understand why it exists, recognise where it is holding customers or engineers back, and evolve it without disrupting the open-source users, customers, integrations and plugins that already depend on it.
What you’ll own You'll own problems, not just code.
This is not a traditional feature-ticket engineering role.
You'll understand customer problems, shape solutions, build across the stack, ship incrementally and continuously improve what you release.
AI should be part of your everyday workflow.
You'll own work from problem to outcome:
For senior: You'll help shape what we build, not only how we build it.
You'll identify opportunities others haven't seen, influence technical and product direction, and help establish how the Core team operates as it grows.
For intermediate: You'll contribute to deciding what we build, working closely with product, engineering and customers rather than simply implementing predefined requirements.
You'll own meaningful problems end-to-end while building confidence in navigating ambiguity and product trade-offs.
What the work looks like You'll work across the Core platform wherever you can create the greatest impact.
Examples include:
How we work We’re a small team competing with companies many times our size.
That means we optimise for impact.
We value:
We care about high standards, but we do not confuse high standards with slow processes.
We would rather ship a small useful improvement, learn from it, and improve it than spend months perfecting something before customers see it.
At the same time, changes to Matomo Core can affect a large number of customers, integrations and plugins.
You should be able to move pragmatically while recognising when additional investigation, testing or migration planning is necessary.
What we’re looking for For senior: You're already operating with a high degree of autonomy.
You naturally identify valuable opportunities, make pragmatic decisions in ambiguous situations, and multiply the team's impact through the systems you build, the decisions you influence and the way you approach problems.
For intermediate: You're already comfortable delivering software independently and are looking to take greater ownership of customer problems, product decisions and technical direction.
You enjoy building products You get motivated by solving customer problems and delivering value, not by technical novelty alone.
You care whether people actually use and benefit from what you build.
Seeing a feature make a real difference is more rewarding to you than building something technically clever that nobody uses.
You naturally ask:
You are comfortable with complex, mature systems You do not need every problem to start with a clean architecture or an empty repository.
You are comfortable tracing behaviour across an unfamiliar codebase, understanding historical constraints, debugging difficult interactions, and making incremental improvements without unnecessary rewrites.
You can balance immediate customer needs with longer-term platform health.
You know when to fix the immediate issue, when to address the underlying cause, and when a broader architectural change is justified.
You are comfortable across the stack You are happy working wherever the problem takes you: frontend, backend, databases, APIs, product flows, documentation, or customer feedback.
Our stack includes PHP, MySQL, JavaScript, Vue.js, and TypeScript.
Exact stack experience is useful, but not required.
We care more about your ability to learn, reason, ship, and solve meaningful problems.
You use AI as part of how you work We make heavy use of AI-assisted development throughout our engineering workflow.
You should already be using AI tools regularly or be strongly motivated to do so.
We expect Product Engineers to use AI to increase output and quality.
AI does not replace your judgment.
You remain responsible for product decisions, technical correctness, security, privacy, maintainability, and customer impact.
You’ll probably thrive here if
You may not enjoy this role if
Remote work Matomo is a remote company.
We work mostly asynchronously and rely heavily on clear written communication.
You should be comfortable working independently, documenting your thinking, and collaborating without needing constant meetings.
Location 100% remote — Germany, UK or Ireland only.
Hiring process Our process is designed to understand how you think, build, communicate, and use AI in realistic product engineering work.
The process usually includes: Application → Screening → Online aptitude test → People & Culture interview → Technical skills interview → Final technical interview.
We do not expect unpaid multi-day projects.
We want to understand how you approach ambiguous problems, make trade-offs, use AI, and ship useful product improvements.
Diversity and Inclusion InnoCraft (trading as Matomo) values what makes you unique.
We’re an inclusive employer and welcome applicants from all backgrounds, because diverse perspectives help us build better products.
Interested?
If you care about solving meaningful customer problems, improving software that people depend on, working with high ownership, and making privacy-friendly analytics more secure, reliable, accurate and useful, we’d like to hear from you.
You will be redirected to the company's ATS