About
Matomo provides privacy-friendly analytics that gives organisations ownership of their data and helps them understand activity, make better decisions, and improve their work. Its open-source product, cloud platform, plugins, integrations, and customer-facing features rely on Matomo Core.
Responsibilities
•Understand customer problems before committing to solutions
•Help shape priorities and decide what to build
•Build across the stack to address product problems
•Ship incrementally, learn from real usage, measure outcomes, and iterate
•Use AI throughout the engineering workflow
•Diagnose and solve complex problems across a large, mature codebase
•Strengthen Matomo's security, performance, scalability, reliability, and resilience
•Protect the integrity, accuracy, and trustworthiness of customer data
•Strengthen capabilities for demanding enterprise use cases
•Build and evolve APIs and platform capabilities used by plugins and integrations
•Evolve consent, privacy, and responsible data collection capabilities
•Advance server-side tracking, data anonymisation, and data-health monitoring
•Enhance goals, ecommerce reporting, and dashboards
•Simplify analytics workflows and make functionality easier to use
•Evolve the design system to create a more consistent and usable product experience
Requirements
•Deliver software independently and take ownership of customer problems, product decisions, and technical direction
•Be comfortable navigating complex, mature systems and unfamiliar codebases
•Debug difficult interactions and make incremental improvements without unnecessary rewrites
•Balance immediate customer needs with long-term platform health
•Work across frontend, backend, databases, APIs, product flows, documentation, and customer feedback
•Use AI tools regularly or be strongly motivated to do so
•Take responsibility for product decisions, technical correctness, security, privacy, maintainability, and customer impact
•Work independently, document thinking clearly, and collaborate asynchronously
•Explain technical and product trade-offs clearly
•You will not enjoy the role if you: mainly want greenfield products, see maintenance or reliability work as less valuable, expect requirements to be fully defined, prefer replacing existing systems, measure success mainly by code quality, are uncomfortable using AI, need a large team or formal processes, prefer extensive polishing before user feedback, dislike writing documentation, or are uncomfortable balancing speed, backward compatibility, and platform health
Conditions
•The role is 100% remote, limited to Germany, the UK, or Ireland
•No unpaid multi-day projects are expected
•The hiring process usually includes an online aptitude test, a People & Culture interview, a technical skills interview, and a final technical interview
