Roger is the operating system for dental clinics.
We automate the workflows that dental teams shouldn't be doing manually – from treatment plans to patient communication to revenue optimization.
We're early, well-funded, and moving fast.
We're looking for a Senior Software Engineer who wants to own real problems, not just tickets.
Tasks
Profile & Experience
●Senior-level with significant experience shipping and operating production systems
●Track record of owning projects end-to-end: from concept through delivery to production
●Experience working cross-functionally with Product, Design, Data, and other stakeholders
●Preferred stack: Ruby on Rails, Go, Dart/Flutter – but strong fundamentals matter more than specific languages
How You Work
●You think beyond your own code – you understand business context, user needs, and product goals
●You take ownership proactively and drive projects to completion without waiting for instructions
●You communicate openly and clearly with stakeholders, technical and non-technical alike
●You make decisions under ambiguity and escalate when it matters
●You enable other engineers through code reviews, knowledge sharing, and raising the bar
Agentic Engineering Mindset
●You use AI agents as a force multiplier – not a crutch. You orchestrate, review, and own the output
●You write specs and plans before prompting. You know that skipping design thinking is where projects fail, not the AI
●You review AI-generated code 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 understand the spectrum: you know when to vibe-code a prototype and when to apply full engineering discipline
Requirements
What We Expect
●Own scope, timelines, and stakeholder alignment for your projects
●Make and be accountable for technical decisions
●Build and maintain broad context – know the system, not just your service
●Continuously raise engineering standards: testing, documentation, CI/CD, observability
●Actively shape how the team works with AI tooling – contribute to evolving our practices as the technology matures
Benefits
Why Roger?
●A market worth billions that still runs on fax machines and phone tag. The opportunity is absurd
●A team small enough that your decisions shape the product – not a committee's
●Hard, interesting problems in a space most tech companies ignore
●Engineers who care about craft – we argue about architecture, not politics
●Competitive salary, equity participation, and solid benefits – we'll talk specifics in the process