Tread - Staff Backend Engineer (Rails)

• Strong Rails experience, or strong experience in a comparable backend framework and willingness to ramp fast. • You think in systems — interfaces, schemas, invariants, failure modes — and you've shipped designs that held up as the product scaled past their original assumptions. • You can model workflows where the source of truth is unreliable and the system still has to settle correctly. • High ownership. • Daily, opinionated use of AI coding tools. • You can debug production issues and explain root causes. • Background in logistics, ops, payments, or fintech. • We deploy continuously, review PRs the same day, and invest in correctness up front so on-call stays light. • AI tooling is part of the infrastructure. We maintain a shared internal skills library across Claude Code and Cursor, with namespaced agent skills the whole team uses for reviewing diffs and resolving PR feedback. We engineer the agent loop itself — skills, prompts, review pipelines. We invest in the dev environment and CI work that makes coding agents useful: devcontainers, fast feedback, pre-approved permissions, cloud agent support. Improving the SDLC is first-class engineering work. • This isn't the right role if you want to: • Write only CRUD endpoints. • Treat AI coding tools as a side experiment. • Send something you've worked on where the backend had real complexity. A repo, a write-up, an architecture doc, a postmortem. One good thing beats a long resume.