> Markdown version of [/jobs/ext/4012002-senior-ruby-on-rails-engineer](https://www.wearedevelopers.com/jobs/ext/4012002-senior-ruby-on-rails-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior Ruby On Rails Engineer

- **Company:** Kode Health, Inc.
- **Location:** Columbus, OH, United States (Remote available)
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** HTML, JavaScript (Programming Language), Artificial Intelligence, Application Integration Architecture, Automation of Tests, Cascading Style Sheets (CSS), Code Review, Relational Databases, PostgreSQL, Ruby on Rails, Ruby, Software Engineering, SQL Databases, Systems Integration, Web Application Frameworks, ReactJS, Agentic-AI, Vue.js, AngularJS, Figma, Front End Software Development, Claude
- **Published:** October 29, 2026
- **Apply:** https://www.careerbuilder.com/job-details/senior-ruby-on-rails-engineer-columbus-oh--4bb65344-8866-4114-a08d-3281718a6e0c

## About the Role

Ruby on Rails, Healthcare, Ruby on Rails, Medical Coding, Artificial Intelligence (AI), Process Development, Leading Edge Technology, Software Engineering, Best Practices, Mentoring, * Must reside in the United States of America and be a U.S. citizen or permanent resident with verified U.S. government-issued ID.

 * Must not live in California, United States of America.
 * 5+ years of professional software engineering experience, including 3+ years building and maintaining production Ruby on Rails applications, with examples of work you personally delivered.
 * Strong Ruby and Rails fundamentals, relational data modeling, SQL, and practical experience with PostgreSQL or a comparable relational database.
 * Experience creating user interfaces with HTML, CSS, JavaScript, and a modern frontend approach. Hotwire experience is preferred; React, Angular, Vue or similar front-end framework experience is also valuable.
 * A habit of verifying your own work, including automated tests, browser checks, failure cases, and follow-up after release.
 * Experience integrating APIs and troubleshooting application behavior across the stack.
 * Clear written and verbal communication, including explaining tradeoffs and working through disagreement with colleagues.
 * Practical experience using AI tools in engineering, along with the judgment to question their output and validate results.
 * An interest in consistent, accessible interfaces and the details that make a workflow understandable and reliable.

## Description

* Partner with product managers to understand user needs and business priorities, refine requirements, and define what a successful result looks like.
 * Write and maintain Product Requirements Documents, implementation plans, estimates, and release plans in collaboration with the team.
 * Build and improve Ruby on Rails features across the application, including data models, integrations, and user-facing workflows.
 * Help build and improve user-facing AI agents, including their behavior, integrations, evaluations, and automated tests.
 * Create consistent interfaces using a design system, by leveraging AI or inspecting design tools, such as Figma, Claude Design, etc. and experienced with creating consistent user experiences, reusing components, styles, and interaction patterns thoughtfully.
 * Write appropriate automated tests, exercise important user flows yourself, review code, and resolve issues found during review.
 * Plan safe deployments, check behavior after release, and follow through when something does not work as intended.
 * Use AI throughout planning, design, development, review, and release preparation. Understand and verify its output, protect sensitive information, and take responsibility for the finished work.
 * Improve how we work by identifying a real problem, listening to others, and proposing changes whose benefits justify their cost.

How we collaborate

We value curiosity, thoughtful feedback, and respect for the people who use and maintain our software. We expect engineers to explain their reasoning, consider alternatives, and change their minds when the evidence warrants it.

We make decisions together and support the agreed direction. When new evidence or a material risk calls for another conversation, we raise it clearly and constructively. We balance quality, scope, and speed around the needs of the business and its users.