# Full Stack Product Engineer (100% Remote - Germany | UK [Innocraft](https://gurify.com/jobs?q=Innocraft) · Berlin · Posted today Remote Full-time [Full Stack](https://gurify.com/jobs/fullstack) [Apply on the original posting → (opens in a new tab)](https://jobs.lever.co/innocraft/e22e02f0-31ae-4650-8304-d236b34c8cda) ## Job description Full Stack Product Engineer (100% Remote - Germany | UK | Ireland) Company: InnoCraft Location: London / Dublin / Düsseldorf / Manchester / Cork / Frankfurt / Berlin Type: Full-time \n 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: - 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. How we work 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. ### 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: - 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 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 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 may not enjoy this role if - 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 impac **Live in Innocraft’s hiring system.** Read from the company's own applicant tracking system, not reposted from a job board — so it's a real, open requisition rather than an ad that outlived the role. We remove it as soon as it disappears at source. ## More jobs like this - BU [(Senior) Full-Stack Engineer | Frontend-leaning (f/m/d)](https://gurify.com/job/senior-full-stack-engineer-frontend-leaning-f-m-d-at-bunch-646a11df0c4d) Bunch · Berlin · last week - BU [(Senior) Full-Stack Engineer | Frontend-leaning | Platform Team (f/m/d)](https://gurify.com/job/senior-full-stack-engineer-frontend-leaning-platform-team-f-m-d-at-d76cd1e155b8) Bunch · Berlin · last week - BU [(Senior) Full-Stack Engineer | Frontend-leaning | Platform Team](https://gurify.com/job/senior-full-stack-engineer-frontend-leaning-platform-team-at-bunch-af0f5c2fa027) Bunch · Spain · last week - BU [(Senior) Full-Stack Engineer | Frontend-leaning | Platform Team](https://gurify.com/job/senior-full-stack-engineer-frontend-leaning-platform-team-at-bunch-99385425b8d8) Bunch · Spain · last week - MY [Full Stack Engineer](https://gurify.com/job/full-stack-engineer-at-mytomorrows-a83b49148c6c) Mytomorrows · Amsterdam HQ · last week - SY [Senior Full Stack Engineer](https://gurify.com/job/senior-full-stack-engineer-at-sygnia-558c6e9487ab) Sygnia · Tel Aviv, Israel · last week ```json {"@context":"https://schema.org/","@type":"JobPosting","title":"Full Stack Product Engineer (100% Remote - Germany | UK","description":"\u003Cp\u003EFull Stack Product Engineer (100% Remote - Germany | UK | Ireland)\u003Cbr /\u003ECompany: InnoCraft\u003Cbr /\u003ELocation: London / Dublin / D\u0026#252;sseldorf / Manchester / Cork / Frankfurt / Berlin\u003Cbr /\u003EType: Full-time\u003C/p\u003E\u003Cp\u003E\\n\u003C/p\u003E\u003Cp\u003EBuild analytics people can trust. Help define what analytics looks like in an AI-first world.\u003Cbr /\u003EMost analytics platforms ask organisations to trade control for insight.\u003C/p\u003E\u003Cp\u003EFor 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\u0026#39;s happening, make better decisions, and improve their work.\u003C/p\u003E\u003Cp\u003EMore than one million websites use Matomo. That means you\u0026#39;ll work on software that is widely used, technically demanding, and close enough to customers that your work has a visible impact. It\u0026#39;s a rare opportunity for engineers: solving meaningful, complex product problems while seeing the difference your work makes for customers.\u003C/p\u003E\u003Cp\u003EWe 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.\u003C/p\u003E\u003Cp\u003EThis 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.\u003C/p\u003E\u003Cp\u003EIf you want unusually high ownership, visible impact, hard product \u0026amp; platform problems, and the opportunity to strengthen a widely used open-source platform, Matomo is worth a serious look.\u003C/p\u003E\u003Cp\u003EWhy this role matters\u003Cbr /\u003EMatomo Core is the foundation of our open-source product, cloud platform, plugins, integrations and customer-facing features.\u003C/p\u003E\u003Cp\u003EIt has evolved over many years and\u0026#160;operates across a wide range of environments, use cases and data volumes.\u0026#160;Every improvement to Core benefits customers, open-source users, plugin developers and engineering teams across the Matomo ecosystem.\u003C/p\u003E\u003Cp\u003EWe are bringing responsibility for Core into a newly formed European team. You\u0026#39;ll help shape how this team works, where it focuses and how it creates the greatest impact across Matomo.\u003C/p\u003E\u003Cp\u003EAs a Product Engineer, you\u2019ll 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.\u003C/p\u003E\u003Cp\u003EYou\u2019ll 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.\u003C/p\u003E\u003Cp\u003EWhat you\u2019ll own\u003Cbr /\u003EYou\u0026#39;ll own problems, not just code.\u003C/p\u003E\u003Cp\u003EThis is not a traditional feature-ticket engineering role. You\u0026#39;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.\u003C/p\u003E\u003Ch3\u003EYou\u0026#39;ll own work from problem to outcome:\u003C/h3\u003E\u003Cp\u003E-\u003Cbr /\u003EUnderstand the problem before committing to a solution.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EHelp shape priorities, not just implement them.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EBuild across the stack wherever the problem takes you.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EShip incrementally and learn from real usage.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EMeasure outcomes and iterate.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EUse AI throughout your workflow.\u003C/p\u003E\u003Cp\u003EFor senior: You\u0026#39;ll help shape what we build, not only how we build it. You\u0026#39;ll identify opportunities others haven\u0026#39;t seen, influence technical and product direction, and help establish how the Core team operates as it grows.\u003C/p\u003E\u003Cp\u003EFor intermediate: You\u0026#39;ll contribute to deciding what we build, working closely with product, engineering and customers rather than simply implementing predefined requirements. You\u0026#39;ll own meaningful problems end-to-end while building confidence in navigating ambiguity and product trade-offs.\u003C/p\u003E\u003Ch3\u003EWhat the work looks like\u003C/h3\u003E\u003Cp\u003EYou\u0026#39;ll work across the Core platform wherever you can create the greatest impact.\u003C/p\u003E\u003Ch3\u003EExamples include:\u003C/h3\u003E\u003Cp\u003E-\u003Cbr /\u003EDiagnosing and solving complex problems across a large, mature codebase.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EStrengthening the security, performance, scalability, reliability and resilience of Matomo.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EProtecting the integrity, accuracy and trustworthiness of the data customers rely on.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EStrengthen capabilities that support increasingly demanding enterprise use cases.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EBuilding and evolving APIs and platform capabilities used by Matomo plugins and integrations.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EEvolving how Matomo handles consent, privacy and responsible data collection.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EAdvancing server-side tracking, data anonymisation and data-health monitoring.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EEnhancing analytics capabilities such as goals, ecommerce reporting and dashboards.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003ESimplifying complex analytics workflows and making powerful functionality easier to use.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EEvolving Matomo\u0026#39;s design system to create a more consistent and usable product experience.\u003C/p\u003E\u003Cp\u003EHow we work\u003Cbr /\u003EWe\u2019re a small team competing with companies many times our size.\u003C/p\u003E\u003Cp\u003EThat means we optimise for impact.\u003C/p\u003E\u003Ch3\u003EWe value:\u003C/h3\u003E\u003Cp\u003E-\u003Cbr /\u003ECustomer problems over technical elegance.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EShipping over endless planning.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003ESimple solutions over unnecessary complexity.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EOwnership over handoffs.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EIteration over perfection.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EClear writing over excessive meetings.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EPragmatic engineering over abstract architecture.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EAI where it helps us move faster.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EMeasuring outcomes over assuming we were right.\u003C/p\u003E\u003Cp\u003EWe 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.\u003C/p\u003E\u003Cp\u003EAt 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.\u003C/p\u003E\u003Ch3\u003EWhat we\u2019re looking for\u003C/h3\u003E\u003Cp\u003EFor senior: You\u0026#39;re already operating with a high degree of autonomy. You naturally identify valuable opportunities, make pragmatic decisions in ambiguous situations, and multiply the team\u0026#39;s impact through the systems you build, the decisions you influence and the way you approach problems.\u003C/p\u003E\u003Cp\u003EFor intermediate: You\u0026#39;re already comfortable delivering software independently and are looking to take greater ownership of customer problems, product decisions and technical direction.\u003C/p\u003E\u003Ch3\u003EYou enjoy building products\u003C/h3\u003E\u003Cp\u003EYou get motivated by solving customer problems and delivering value, not by technical novelty alone.\u003C/p\u003E\u003Cp\u003EYou 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.\u003C/p\u003E\u003Ch3\u003EYou naturally ask:\u003C/h3\u003E\u003Cp\u003E-\u003Cbr /\u003EWhat problem are we solving?\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EWho has this problem?\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EIs this the simplest useful solution?\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EHow will we know this made things better?\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EWhat should we do if the data shows we were wrong?\u003C/p\u003E\u003Ch3\u003EYou are comfortable with complex, mature systems\u003C/h3\u003E\u003Cp\u003EYou do not need every problem to start with a clean architecture or an empty repository.\u003C/p\u003E\u003Cp\u003EYou are comfortable tracing behaviour across an unfamiliar codebase, understanding historical constraints, debugging difficult interactions, and making incremental improvements without unnecessary rewrites.\u003C/p\u003E\u003Cp\u003EYou 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.\u003C/p\u003E\u003Ch3\u003EYou are comfortable across the stack\u003C/h3\u003E\u003Cp\u003EYou are happy working wherever the problem takes you: frontend, backend, databases, APIs, product flows, documentation, or customer feedback.\u003C/p\u003E\u003Cp\u003EOur 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.\u003C/p\u003E\u003Ch3\u003EYou use AI as part of how you work\u003C/h3\u003E\u003Cp\u003EWe make heavy use of AI-assisted development throughout our engineering workflow.\u003C/p\u003E\u003Cp\u003EYou 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.\u003C/p\u003E\u003Cp\u003EAI does not replace your judgment. You remain responsible for product decisions, technical correctness, security, privacy, maintainability, and customer impact.\u003C/p\u003E\u003Ch3\u003EYou\u2019ll probably thrive here if\u003C/h3\u003E\u003Cp\u003E-\u003Cbr /\u003EYou prefer owning outcomes over receiving detailed tickets.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou enjoy solving difficult problems in existing systems as well as building new functionality.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou can quickly diagnose complex or intermittent bugs.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou can move from customer feedback or operational evidence to investigation, product decision and implementation.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou care about reliability, performance and data accuracy, not only visible feature work.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou can improve a mature codebase without assuming it needs to be rewritten.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou use AI tools heavily and are actively improving how you work with them.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou are pragmatic: you can make a focused improvement now while recognising when a deeper change is needed.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou can explain technical and product trade-offs clearly.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou enjoy working across product, engineering, UX, data and customer feedback.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou like small teams where your decisions and output visibly matter.\u003C/p\u003E\u003Cp\u003Ebelow for intermediate only:\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou\u0026#39;re excited to take on increasingly ambiguous problems.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou want to grow beyond implementation into shaping products and technical decisions.\u003C/p\u003E\u003Ch3\u003EYou may not enjoy this role if\u003C/h3\u003E\u003Cp\u003E-\u003Cbr /\u003EYou mainly want to work on new greenfield products.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou see maintenance, debugging, reliability or performance work as less valuable than feature development.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou want a product manager to define most requirements before you start.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou are uncomfortable investigating problems where the cause is initially unclear.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou prefer replacing existing systems rather than understanding why they work as they do.\u003C/p\u003E\u003Cp\u003E-\u003Cbr /\u003EYou measure success mainly by code quality rather than user or business impac\u003C/p\u003E","identifier":{"@type":"PropertyValue","name":"Gurify","value":"full-stack-product-engineer-100-remote-germany-uk-at-innocraft-9bd2307a395f"},"url":"https://gurify.com/job/full-stack-product-engineer-100-remote-germany-uk-at-innocraft-9bd2307a395f","datePosted":"2026-09-28","validThrough":"2026-11-12T23:59:59Z","hiringOrganization":{"@type":"Organization","name":"Innocraft","sameAs":"https://jobs.lever.co/innocraft"},"directApply":false,"jobLocationType":"TELECOMMUTE","applicantLocationRequirements":{"@type":"Country","name":"Germany"},"employmentType":"FULL_TIME"} ``` ```json {"@context":"https://schema.org/","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Jobs","item":"https://gurify.com/jobs"},{"@type":"ListItem","position":2,"name":"Germany","item":"https://gurify.com/jobs/germany"},{"@type":"ListItem","position":3,"name":"Full Stack Product Engineer (100% Remote - Germany | UK","item":"https://gurify.com/job/full-stack-product-engineer-100-remote-germany-uk-at-innocraft-9bd2307a395f"}]} ```