Product Builder (all genders) at GLP Transit

, , Germany -

Full Time

Start Date

Immediate

Expiry Date

07 May, 26

Salary

105000.0

Posted On

06 Feb, 26

Experience

2 year(s) or above

Remote Job

Yes

Telecommute

Yes

Sponsor Visa

Skills

Building Software, Evolving Software Platform, Thriving on Change, First Principles Thinking, Product-Minded, Shipping Code, Shaping Problems, Internal Sense of Done, Simplifying Problems, Leveraging AI, Agentic Coding, Handling Ambiguity, Navigating Friction, Async Communication, Deep Focus, Judgment Optimization

Industry

Description

Let’s get one thing out of the way first: If you’re looking for a list of very specific requirements, you won’t find them here. Not in this job posting. Not later in the role. We are building and evolving a software platform. That’s the job. So, yes, you’ll spend most of your time building, changing, and often throwing away code. How that gets done has changed more in the last 6-12 months than in the decade before. Writing static requirements feels pointless. Some people thrive on that kind of change. Others freeze. This role is for the former. We work best with people who think in jumps, patterns, and first principles – not checklists. What are we even doing? Insurance. Pension insurance. If that already makes you lose interest, that’s fine. Better to know now. Being “product-minded” is already hard for software engineers in domains they deeply relate to. Insurance just makes it even harder. But if you zoom out: the pension gap affects nearly every working person in Europe. It’s one of the most broadly impactful problems you can work on. And precisely because it’s complex, regulated, and frankly boring at first glance, it’s also one of the hardest. Boredom here is a signal, not a property. Turning bone-dry, high-stakes complexity into something people understand, trust, and stick with for 30-40 years is the product challenge. That’s where the fun is. So what is this role? Software Engineer? Product Manager? Product Designer? It’s for people who make these boundaries irrelevant. You care about code, but you care more about whether the right thing gets shipped. You’re energized by incomplete information. You’d rather shape the problem than wait for the perfect spec. You have a strong internal sense of what “done” means, and you defend it. What success feels like here You ship things that didn’t exist before. Not because they were requested, but because they mattered. You simplify problems others try to solve with more process. You use AI and agentic coding as leverage, not as a shortcut. You’re trusted with ambiguous, high-impact problems. And you deliver. But impact here doesn’t stop at code. You’re willing to step outside any traditional role if that’s what moving the product forward requires. That might mean talking directly to partners, explaining trade-offs, running an internal training, or navigating organizational friction. You don’t confuse “that’s not my job” with focus. You can go deep for hours – and then surface with something concrete that others can use, decide on, or build on. We’re not optimizing for velocity. We’re optimizing for judgment. How we actually work This matters. A lot. Very few meetings No stand-ups, no rituals, no ceremony Async by default Flexibility in when and how you work Fully remote (with offsites twice a year) Long stretches of uninterrupted focus are normal – and protected If your best work doesn’t come from linear days or perfect routines, you’ll fit right in. If you’re unsure whether you fit: good sign. You show us what this person looks like. Baseline (non-negotiable) You are legally allowed to work where you live (Ideally Germany, EU-wide for the right person). You are fluent in written and spoken English. You have built and shipped real digital products in production environments. Helpful, but not mandatory Native-level German and a deep cultural understanding of German- or Swiss-speaking markets. We don't want to put it out as a hard requirement, but it will significantly increases the impact you can have – especially in a domain like pension insurance, where language, trust, and nuance matter. We ask for a cover letter detailing your motivation to fill this role. Doesn't need to be long, in fact short is preferred, just try to make it have soul. Understand that we are unlikely to respond to your application without. If a benefits list is the reason you apply for a job, this is probably not the right one. We don’t try to win you over with perks. We focus on doing meaningful work with people who care about what they’re building. Our benefits exists to make that sustainable. We can tell you about them later in the process. And funny enough, they are a bit more exciting than a gym membership. Compensation We expect to pay a base salary between EUR 84.000-105.000. We re-adjust after 6-12 months. We pay voluntary, company-wide bonuses (historically ~3–10%), depending on business performance. We’ve paid them every year since 2019. How we hire The first round will be a short 15 min get-to-know. Ideally that gives both sides an appetite for more. Afterwards there will be 2-3 more conversations with peers and the wider team. We value different perspectives and backgrounds and are committed to an inclusive workplace. We don’t discriminate based on any legally protected characteristic – and we care far more about how you think and work than how well you match a template.

Responsibilities

The core responsibility involves building and evolving a software platform, spending significant time writing, changing, and discarding code to address complex problems in the pension insurance domain. This role requires stepping outside traditional boundaries to ensure the right product gets shipped by engaging in necessary tasks like partner communication or internal training.