Roger

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

Berlin, Germany full-time Mid Salary not listed
full-time Mid level Technology & IT Curated
Sign in to apply Free account — we bring you straight back to this role.

About the role

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 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 – you’ve 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: 2–3 days a week on site, the rest remote
• German: Business-fluent German (C1 or better) is required. You’ll 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. You’ll be one of 6 engineers. Your area is yours – your decisions shape the product, not a committee’s
• 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: €75,000 – €95,000 base salary depending on experience, plus equity participation and benefits: Deutschlandticket, Urban Sports Club, 30 days’ vacation and Hrmony (50€ in-kind compensation).

Find more English Speaking Jobs in Germany on Arbeitnow

Interview prep

Walk in with sharper answers.

Use this as a quick practice sheet before you speak with the employer.

Mid
Technology & IT Figma Remote Collaboration Writing Senior Product Mid level

Likely questions

  1. Tell us about work you have done that is close to the Senior Product Engineer (Software) (m/w/d) role.
  2. How would you approach your first 30 days at Roger?
  3. Which of Figma, Remote Collaboration and Writing have you used recently, and what did it help you achieve?
  4. Describe a time you solved a problem without waiting to be told exactly what to do.
  5. How do you handle busy days, changing priorities, or pressure at work?

Prepare before the call

  • A recent example that proves your experience with Figma, Remote Collaboration and Writing.
  • One short story with a problem, your action, and the result.
  • Two examples that show the strengths listed on your CV.
  • A clear reason why this role and company interest you.
  • Your availability, preferred work style, and salary expectations.

Ask them

  • What would success look like in the first 90 days?
  • What are the main problems this hire should help solve?
  • How does the team give feedback and measure good work?
  • What does a normal working week look like for this role?
Practice line

I am interested in the Senior Product Engineer (Software) (m/w/d) role because I can bring practical experience in Figma, Remote Collaboration and Writing, learn the team quickly, and contribute to the outcomes Roger needs from this hire.

Related jobs.

More roles from this company or category.