Senior Product Engineer (Software) (m/w/d)

Roger is the operating system for dental practices. We automate the work dental teams shouldn’t be doing by hand – from treatment plans to patient communication to revenue optimization – and we plug directly into the practice management systems (PMS) that German practices already run on. We’re early, well-funded, and moving fast. We’re looking for a Senior Product Engineer who wants to own a product area end to end: understand the practice’s problem, decide what to build, ship it, run it, and improve it with real usage data. Not tickets. Outcomes. We call the role Product Engineer on purpose. You work directly with product, design, and practices, and you’re accountable for whether what you built actually solves the problem – not just for whether the code merged. What you’ll build Everyone works across the whole product; people build deeper expertise in some areas, but who works on what can change quickly. Over a typical quarter you’ll touch things like: • PMS integrations – connecting Roger to the practice management systems German practices run on, so our workflows sit on top of live practice data instead of beside it • Treatment plans and cost estimates (HKP) – turning a manual, error-prone paper process into something a practice team gets right the first time • Patient communication – recalls, reminders, and follow-ups that practices today handle by phone, fax, and sticky note • Revenue and billing workflows – helping practices bill what they actually did, correctly and on time • The Roger apps – web and Flutter clients that practice staff use all day, every day Whatever your area, you’ll own it from the first conversation with a practice to the dashboard that tells you whether it worked. What we expect • Own outcomes, not tasks. You define scope, timelines, and success criteria for your area, and you align stakeholders around them • Make technical decisions and stand behind them. Architecture, trade-offs, what to build versus buy – you decide, document why, and course-correct when the data says so • Know the system, not just your service. Roger is one product. You keep enough context across PMS integrations, data model, and clients to make decisions that hold up outside your corner • Raise the bar continuously. Testing, documentation, CI/CD, observability – you leave every area better than you found it • Shape how we work with AI. Our tooling and practices are still evolving. You contribute to them actively rather than waiting for a playbook • Enable others. Code reviews, knowledge sharing, pairing – a senior here makes the people around them better How we work AI-native engineering, honestly described. Most of us run several coding agents in parallel, all day. Writing code is no longer the bottleneck. Reviewing it, testing it, and deciding what not to ship is. So here’s what that actually means for you: • You write specs and plans before you prompt. Skipping design thinking is where projects fail – not the AI • You review agent output with the same rigor as any PR. If you can’t explain what a module does, it doesn’t ship • You test relentlessly. A solid test suite is how you turn an unreliable agent into a reliable system • Your fundamentals are strong enough to evaluate, correct, and improve whatever AI produces – architecture, security, performance • You know the spectrum: when a throwaway prototype is fine and when full engineering discipline applies • You expect to spend as much time reviewing and validating as writing. If that sounds like a downgrade, this isn’t the right team. If it sounds like leverage, read on Patient data is not a detail. Roger handles health data (GDPR Art. 9) and sits inside practices bound by professional secrecy (§ 203 StGB). Data minimization, access control, EU processing, and a clear head about what may go to which model provider are part of the engineering bar here – not a compliance checkbox someone else owns. Small team, short paths. You talk to practices, to product, and