> Markdown version of [/jobs/ext/4750508-senior-software-engineer](https://www.wearedevelopers.com/jobs/ext/4750508-senior-software-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 Software Engineer - **Company:** STUDENT JOB - **Location:** Indianapolis, IN, United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** JavaScript (Programming Language), PHP (Programming Language), Amazon Web Services, Asana, Cascading Style Sheets (CSS), Software as a Service, Django Web Framework, Github, Python (Programming Language), Laravel, PostgreSQL, Ruby on Rails, Standard Sql, Next.js, Web Applications, Rspec, AI Coding Agents, Heroku, Api Management - **Published:** November 16, 2026 - **Apply:** https://www.juju.com/job/2_177124849 ## About the Role * 5+ years building and maintaining production web applications, ideally including several years of Ruby on Rails. * Strong SQL and PostgreSQL skills: you can read a query plan, write a safe migration on a large table, and model data that has to stay consistent. * Comfort with server-rendered Rails (ERB and Stimulus), plus plain JavaScript and CSS. * A testing habit. You write specs because they let you change code safely, not because CI requires them. * Experience working in a large codebase you didn't write, and judgment about when to refactor and when to leave it alone. * Experience working on a remote team. * Clear written communication. Most of our collaboration happens in tickets, pull requests and Slack. We prefer Rails experience, but we'll consider strong engineers from other web stacks, such as Python/Django, PHP/Laravel, or JavaScript/Next.js, who are ready to get productive in Rails quickly. Nice to Have * Experience with payments, banking or fintech, such as banking API integrations, ACH, card issuing, ledgers or reconciliation. * Experience building multi-tenant SaaS. * Experience running background jobs and third-party API integrations at scale. * Experience with edtech, government or nonprofit software. * Experience with Hotwire and/or ReActionView. * Experience with Heroku, AWS and GitHub Actions. ## Description You'll own features end to end in Theodore, our Rails monolith. That means reading a state's program rules, designing the data model, shipping the change, and answering the support question two weeks later. You'll work closely with product and program operations, and leave each part of the codebase a little better than you found it. You'll weigh in on architecture, while our Staff engineer sets direction across the whole system. What You'll Do * Build and maintain features across our portals for families, schools, vendors and program administrators. * Turn program rules (eligibility, award amounts, approved expenses) into configuration and code that differs by program. * Build features that move real money through our banking integrations: ACH disbursements, virtual card payments, reimbursements and reconciliation. Correctness matters more than speed here. * Build auditable systems that track every dollar in a ledger and record who changed what, and why. * Protect sensitive family data, including financial and personal records, in everything you build. * Write thorough RSpec tests, and improve the coverage and reliability of the ones we have. * Modernize older code toward current Rails conventions, both as part of feature work and as dedicated projects. * Review pull requests with care, and write your own so they're easy to review. * Take turns on business-hours triage: investigate production issues, trace them through logs and data, and fix the root cause., * Every change goes through a pull request with review and a passing CI run. * Work is tracked in Asana and discussed in Slack; we write things down. * We ship small, safe changes frequently, and document every release for compliance. * We use AI coding tools every day, but a person owns every line we ship. Whether an agent wrote the code or you did, you're expected to understand it, test it and stand behind it. Work Environment * Fully remote within the United States. The team meets in person about once a quarter for a few days of team-building. Other travel, such as for a client meeting, is rare. The company pays for all work-related travel. * Engineers are rarely expected to attend client meetings. * Primarily computer-based work, including extended periods of reading code and documentation and participating in video meetings. * We believe that healthy conflict produces great work, and strive to create opportunities for everyone, regardless of role or seniority, to share their knowledge and perspective toward that end.