Senior Product Engineer (Software) (mwd)

Roger is the operating system for dental practices. We automate the work dental teams shouldnt 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. Were early well-funded and moving fast.

Were looking for a Senior Product Engineer who wants to own a product area end to end: understand the practices 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 youre accountable for whether what you built actually solves the problem not just for whether the code merged.

What youll 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 youll 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 youll 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 heres 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 cant explain what a module does it doesnt 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 isnt 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 to the people who answer the phones for our customers. Decisions get made in a conversation not a committee.

Who you are
Senior-level with significant experience shipping and operating production systems youve been paged for your own code
A track record of owning projects end to end: from a vague problem statement through delivery to production and iteration
Used to working cross-functionally with product design data and non-technical stakeholders and comfortable talking to end users directly
You think beyond your own code: business context user needs and product goals shape what you build
You take ownership without waiting for instructions make decisions under ambiguity and escalate when it matters
You communicate openly and clearly in writing and in person with technical and non-technical people alike
Our stack is Ruby on Rails Go and Dart/Flutter. Deep experience in at least one of these helps; strong fundamentals matter more than any specific language
Bonus not required: experience in healthcare dental or another regulated domain; or with integrating into legacy on-premise systems

Location language and setup
Location: You live in Germany and can be in our Berlin office regularly. The role is hybrid: 23 days a week on site the rest remote
German: Business-fluent German (C1 or better) is required. Youll talk to practices read PMS vendor documentation and work with German regulatory and billing concepts daily. Our team language is English
Eligibility: You already hold the right to work in Germany.
Working hours: Full-time

Why Roger
The opportunity is absurd. A market worth billions that still runs on fax machines and phone tag
Real leverage. Youll be one of 6 engineers. Your area is yours your decisions shape the product not a committees
Hard interesting problems in a space most tech companies ignore: legacy integrations regulated data real-world workflows with real-world stakes
Engineers who care about craft. We argue about architecture not politics
Compensation:base salary depending on experience plus equity participation and benefits: Deutschlandticket Urban Sports Club 30 days vacation and Hrmony (50 in-kind compensation).