JOBSEARCHER

Lead Rails Software Engineer

Lead Rails Engineer One Step Software · Remote (US) · Full-TimeAbout One StepOne Step Software is the #1 SaaS platform built for recovery residences and sober living homes since 2017. We help sober living operators run their programs so they can support people struggling with addiction and mental health challenges. Our customers do life-changing work, and our job is to make the admin side easier so they can spend their time on the people who need their help. We're a small, close-knit, flat organization. We look for people who are passionate and hardworking, and who thrive with real autonomy and responsibility. We want people who care about their work and want to make a big difference in the world.
The Role: We're looking for a Lead Rails Engineer who loves building great products and wants to own the technology behind a platform that thousands of people in recovery depend on. You'll be hands-on, working with a team of engineers, and making technical decisions. You'll work closely with our CEO, product, customer success and sales. You'll decide how we build, what we build on and how we ship fast without breaking the things our customers rely on.
What You'll Do:
  • Own One Step's architecture, codebase and infrastructure from end to end
  • Write production code every day
  • Turn CEO and product priorities into realistic technical plans, and ship them
  • Keep the platform secure, reliable and compliant, including how we handle sensitive resident data
  • Maintain our engineering standards for code review, testing, deployment and documentation
  • Use AI coding tools and agents to ship faster
  • Build and maintain integrations with payments, partners and other tools our customers use
  • Work directly with customers and customer success to understand problems and fix what matters most
  • Set success metrics for engineering (uptime, speed, bugs, delivery) and share results with the team
What We're Looking For:
  • 10+ years as a software engineer, including time as a tech lead or the most senior engineer on a team
  • Experience working at a startup, ideally a B2B SaaS company
  • A track record of shipping products real customers use and love
  • Strong Rails experience
  • Experience with security and sensitive data. Healthcare, HIPAA or behavioral health experience is a big plus
  • You use AI tools every day to write, test and review code, and you know where they help and where they don'tYou communicate clearly with non-engineers and can explain technical decisions in plain English
  • You're curious, learn fast and love testing new tools
  • You're self-directed and can keep several projects moving without someone checking inWhat Success Looks Like in Your First Year
  • A stable, secure platform customers trust, with fewer bugs and faster fixes
  • A predictable release rhythm, so product and customers know what's coming and when
  • An engineering workflow built around AI that lets a small team ship like a much bigger one
  • A thorough understanding of our product works and what our clients need and expect from our product
  • Clear engineering metrics, reviewed monthly
Why Join Us:
  • Your work directly supports people in recovery and the organizations that serve them
  • Real ownership: your technical decisions shape the whole product
  • Fully remote
  • Be around other smart, passionate, optimistic people
  • A small team where your ideas get heard and put into practice quickly 401(k) with company match
  • Health insurance and other benefits
How to Apply: Email your resume and answers to the questions below to eva@onestepsoftware.com with the subject line "Lead Rails Engineer." Applications without answers to these questions won't be considered. What product or system are you most proud of building? What was your role, what didn't work at first, and how did you know it was successful? Tell us about a technical decision you got wrong. What happened, and what did you learn? How has AI changed the way you write and ship code? Walk us through your current workflow. How do you decide when to move fast and when to slow down and build it right? What part of the development cycle or other tasks do you not use AI for and why?