Product Manager - Carbon Management

This role centres on owning a defined segment of osapiens' Carbon Management solution suite, which spans Corporate Carbon Footprint, Product Carbon Footprint and decarbonisation. You would be expected to drive that area end to end, from early discovery through to delivery, shaping what gets built rather than merely documenting what others decide. A significant part of the mission is translating dense methodological and regulatory requirements into clear product direction that engineering, UI/UX and delivery colleagues can act on. On a practical level, that likely means maintaining and prioritising a roadmap grounded in customer feedback and market insight, monitoring the shifting regulatory environment and judging what each change means for the product, and weighing methodological rigour against usability, technical feasibility and commercial impact. You would be the connective tissue between compliance experts who know the standards and developers who build the calculation logic. The longer-term objective is to build standardised, scalable carbon software for recurring customer needs rather than one-off solutions, so the role carries real responsibility for how the product evolves commercially as well as technically.

The clearest learning curve here is carbon methodology itself. Because the role sits across CCF, PCF and decarbonisation, a candidate could expect to deepen practical fluency in corporate carbon accounting, product-level footprinting, life-cycle assessment logic and the standards that underpin them. That is a rare, portable specialism in the sustainability job market. Beyond domain knowledge, the position offers exposure to B2B SaaS product craft at scale, including how data models, calculation engines and ERP/PLM integrations come together in a platform serving thousands of customers. Working alongside compliance experts and engineers would sharpen the ability to negotiate technical trade-offs and defend product decisions with evidence. Mentorship is also plausible given the framing alongside senior product leaders, so someone entering mid-level could realistically absorb roadmapping discipline, prioritisation frameworks and stakeholder management from more experienced colleagues while building a reputation in a fast-moving regulatory niche.

The posting points to someone with roughly two to five years in product management, product ownership or an adjacent product role, ideally inside a B2B SaaS environment. Experience in a regulated or regulation-driven industry would matter because carbon software is fundamentally shaped by rules that change often, so comfort with ambiguity and shifting requirements is essential. Technically, the ideal candidate is at ease with data models, calculation logic and software integrations, and can hold a functional conversation with engineers about trade-offs without pretending to be one. A product mindset oriented towards standardised, scalable solutions rather than bespoke builds is explicitly valued, as is a data-informed, collaborative style. On qualifications, English at C1 is a baseline and German is a strong plus given the Munich base. Domain knowledge in PCF, LCA, CCF or corporate carbon accounting would clearly separate a strong applicant from an adequate one, though the wording suggests it is a differentiator rather than a hard gate.

Because this is a product role wrapped around a technical domain, the most persuasive applications will make the carbon-plus-product intersection explicit. Rather than listing responsibilities, a candidate might pick one or two examples where they turned a complex or regulated requirement into a shipped, reusable feature, and describe the trade-offs they navigated. Concrete evidence of prioritising standardisation over bespoke work would speak directly to the language in the posting. It would also help to demonstrate genuine familiarity with the regulatory environment osapiens operates in, EU carbon and disclosure rules, footprinting standards, the direction of travel in supplier and product data. A short, specific observation about how regulation drives product design would signal that the candidate understands why this role exists and is not simply applying to any ESG job. Finally, since the company is a fast-growing unicorn with an international team and a hybrid Munich setup, showing comfort with cross-functional, multilingual collaboration and a bias towards shipping would align well. A tailored note on why carbon software specifically, rather than sustainability generally, could be the decisive differentiator.

The role sits squarely inside osapiens' Carbon Management pillar, so the sustainability focus is carbon accounting and decarbonisation rather than broad ESG storytelling. That means the products this person helps shape likely enable customers to calculate corporate and product-level footprints, and then act on that data to reduce emissions. Given the platform's design, carbon data captured once is reused across other compliance and reporting needs, which makes this role a load-bearing part of the wider offering. The company's overall model blends carbon with product compliance, supplier intelligence, disclosures and traceability, so the role probably intersects with supplier engagement and traceability, footprints often depend on upstream data that customers do not control directly. Regulatory alignment, particularly around European disclosure and product rules, is likely a constant theme, since the platform's selling point is mapping data to multiple requirements automatically. In governance terms, the focus is less on board-level ESG strategy and more on the unglamorous but essential plumbing: accurate methodologies, auditable calculations and reporting that stands up to scrutiny. For someone motivated by measurable climate impact rather than communications, that is arguably the more consequential end of sustainability work.

The most obvious challenge is the constant tension between methodological rigour and usability. Carbon standards are intricate and evolving, yet customers need software that feels straightforward; a product manager here has to decide repeatedly where precision can be simplified and where it cannot. Getting that balance wrong in either direction (too complex to adopt, or too loose to trust) would undermine the product. Regulatory volatility compounds this. Standards and disclosure requirements shift, so roadmap commitments made today might need revisiting tomorrow, and the role explicitly involves monitoring that environment. That demands comfort with uncertainty and the discipline to avoid over-promising. There is also the cross-functional challenge of aligning compliance experts, engineers and delivery teams who each see the product through a different lens, plus the commercial pressure to build scalable solutions that serve many customers rather than the loudest one. Balancing customer feedback against platform standardisation is likely a recurring judgment call.

A typical day would probably be a mix of internal alignment and analytical work rather than a single steady task. It might start with a stand-up or sprint check-in with engineering, then move into a session with UI/UX colleagues refining how a footprint calculation is presented to users, followed by time reviewing requirements or data model questions that need product judgement. Interspersed through the week rather than the day would be conversations with compliance experts to validate methodology, customer calls or feedback triage to understand recurring pain points, and roadmap grooming to decide what moves forward. Given the regulatory focus, part of the rhythm likely involves scanning upcoming rule changes and assessing whether they warrant product action. The role is also hybrid, with three in-office days in Munich, so a good portion of the week would involve face-to-face whiteboarding and informal problem-solving, while remote days lean towards focused documentation and prioritisation work. Variability would spike around release cycles or regulatory deadlines.

Starting with ownership of a defined area, the natural progression would be expanding scope across the broader Carbon Management suite, and potentially into other pillars of the osapiens HUB such as disclosures or traceability. In a company of this size and growth trajectory, that kind of widening remit tends to arrive faster than in larger, more static organisations. The domain expertise gained is also a career asset in its own right. Deep fluency in carbon accounting and footprinting, combined with B2B SaaS product skills, positions someone well for senior product roles in climate tech, or for leadership positions where regulatory and methodological knowledge is scarce. Beyond promotion, there is plausible exposure to high-visibility work, since carbon sits at the centre of the platform's value proposition and the company serves thousands of customers. Leading a well-received product area here could be a strong platform for recognition both internally and across the wider sustainability software market.

The most immediate stakeholders are engineering, UI/UX and delivery colleagues, since the role explicitly involves bringing features from concept to release with them. These interactions would be operational and frequent, centred on requirements, trade-offs and execution. Compliance experts form another key group, and the relationship here is distinctive: they hold the methodological authority that the product must respect, so the product manager has to translate their input into something buildable without diluting its accuracy. Senior product leaders would act as mentors and decision-shapers, given the framing of working alongside them. Externally, customers and prospects are central stakeholders, since their recurring needs drive standardisation and roadmap priorities. There may also be indirect engagement with partners or supplier networks, since carbon data often depends on upstream information flowing through the platform's supplier ecosystem, making stakeholder alignment a genuinely cross-boundary task.