The Monetization team owns how customers buy and keep buying Planday: the checkout experience, subscription management, payments, and the systems behind them (our subscription and billing services, plus the integration layer to Zuora, Salesforce and Intercom). When a customer upgrades a plan, adds a product, or gets an invoice, that is our code path.
As a Full Stack Engineer at IC2, you will build and maintain features across that path, front end and back end, with support from engineers on the team. You will start with well-scoped pieces of customer-facing work and grow into owning features end to end.
You will join a cross-functional team of full stack engineers, a QA engineer, a UX researcher and a product manager. You will be paired with an engineer as your mentor from day one, and you will be expected to ask questions early and often: in a domain where mistakes are visible on customer invoices.
You will use AI coding tools every day, as the whole team does. We care less about how fast you can produce code and more about whether you can tell good output from plausible-looking output, and whether you can explain and defend what you ship.
Create software: Build features across the stack: C# / .NET services and React + TypeScript front ends (We have one service in Java). Contribute to solution design discussions and take part in code reviews, both giving and receiving feedback.Work with AI tools, with judgement: Use AI coding assistants as part of normal delivery. Read, test and question what they produce. Never merge code you cannot explain line by line.Test software: Write and automate tests alongside your changes. Treat quality as part of the work rather than a later stage, with support from the team's QA engineer.Resolve issues: Help triage and fix development and production issues in the subscription, checkout and payments flows. Learn to trace a problem across services and third-party platforms, and communicate impact in business terms.Engineering standards : Learn and apply Planday's Engineering Standards. Take part in the Backend and Frontend Guilds to build a shared standard with engineers outside the team.Understand the domain : Build working knowledge of how plans, entitlements, invoices and payments fit together. In monetization, the business rules are the hard part; the code is often the easy part.Continuous improvement : Keep growing your knowledge of the technologies we use, and bring back what you learn to the team.Deliver in production : Ship your own changes through our CI/CD pipelines and watch how they behave once live.Success looks like
First three months: you ship small customer-facing changes to production with review support, you can explain the plan-change and invoicing paths in your own words, and you ask for help before you are stuck for a day.First twelve months: you own well-scoped features end to end across front end and back end, you catch your own errors before review does, you are a dependable second pair of eyes in code review, and you can explain the customer and revenue impact of what you build.Quality and pace: You deliver at a predictable, sustainable pace and flag risks and blockers early rather than at the deadline.Learning: You actively learn from your peers, act on feedback, and turn each review comment into something you no longer need told twice.Judgment with AI: You use AI tools to move faster without lowering the bar: you verify output, you confidently spot wrong suggestions, and you own everything you merge.Communication: You keep your team informed, write clearly in tickets and pull requests, and give Product accurate information so scope and timing decisions can be made.
