Want to know if this job is worth applying to?
Berlin, Deutschland
Remote only
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.
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.
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:
Understand the problem before committing to a solution.
Help shape priorities, not just implement them.
Build across the stack wherever the problem takes you.
Ship incrementally and learn from real usage.
Measure outcomes and iterate.
Use AI throughout your workflow.
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:
Diagnosing and solving complex problems across a large, mature codebase.
Strengthening the security, performance, scalability, reliability and resilience of Matomo.
Protecting the integrity, accuracy and trustworthiness of the data customers rely on.
Strengthen capabilities that support increasingly demanding enterprise use cases.
Building and evolving APIs and platform capabilities used by Matomo plugins and integrations.
Evolving how Matomo handles consent, privacy and responsible data collection.
Advancing server-side tracking, data anonymisation and data-health monitoring.
Enhancing analytics capabilities such as goals, ecommerce reporting and dashboards.
Simplifying complex analytics workflows and making powerful functionality easier to use.
Evolving Matomo's design system to create a more consistent and usable product experience.
We’re a small team competing with companies many times our size.
That means we optimise for impact.
We value:
Customer problems over technical elegance.
Shipping over endless planning.
Simple solutions over unnecessary complexity.
Ownership over handoffs.
Iteration over perfection.
Clear writing over excessive meetings.
Pragmatic engineering over abstract architecture.
AI where it helps us move faster.
Measuring outcomes over assuming we were right.
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.
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 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:
What problem are we solving?
Who has this problem?
Is this the simplest useful solution?
How will we know this made things better?
What should we do if the data shows we were wrong?
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 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.
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 prefer owning outcomes over receiving detailed tickets.
You enjoy solving difficult problems in existing systems as well as building new functionality.
You can quickly diagnose complex or intermittent bugs.
You can move from customer feedback or operational evidence to investigation, product decision and implementation.
You care about reliability, performance and data accuracy, not only visible feature work.
You can improve a mature codebase without assuming it needs to be rewritten.
You use AI tools heavily and are actively improving how you work with them.
You are pragmatic: you can make a focused improvement now while recognising when a deeper change is needed.
You can explain technical and product trade-offs clearly.
You enjoy working across product, engineering, UX, data and customer feedback.
You like small teams where your decisions and output visibly matter.
below for intermediate only:
You're excited to take on increasingly ambiguous problems.
You want to grow beyond implementation into shaping products and technical decisions.
You mainly want to work on new greenfield products.
You see maintenance, debugging, reliability or performance work as less valuable than feature development.
You want a product manager to define most requirements before you start.
You are uncomfortable investigating problems where the cause is initially unclear.
You prefer replacing existing systems rather than understanding why they work as they do.
You measure success mainly by code quality rather than user or business impact.
You are uncomfortable using AI as part of your normal engineering workflow.
You need a large team, narrow responsibilities, or highly formal processes to be effective.
You prefer polishing a solution extensively before showing it to users.
You dislike writing proposals, documentation, or product notes.
You are uncomfortable balancing speed, backwards compatibility and long-term platform health.
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.
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.
