> Markdown version of [/jobs/ext/2791613-staff-software-engineer-ruby-rails](https://www.wearedevelopers.com/jobs/ext/2791613-staff-software-engineer-ruby-rails). 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). --- # Staff Software Engineer - Ruby/Rails - **Company:** Victory Live - **Location:** Atlanta, GA, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Confluence, JIRA, Cloud Computing, Github, PostgreSQL, Ruby on Rails, Redis, Ruby, Software Construction, Software Engineering, Datadog, Data Logging, GitHub Copilot, Amazon ElastiCache, Rspec, Grafana, Technical Debt, Backend, Kubernetes, Slack, Apache Kafka, Interactive Whiteboards, Kibana, Restful APIs, Terraform, Docker, Pagerduty, Microservices - **Published:** September 8, 2026 - **Apply:** https://www.careerjet.com/jobad/us7024430a9a29579d87f4b165ae14d872 ## About the Role * 10+ years of professional software development experience. * Strong proficiency in Ruby on Rails; experience with Hanami is a plus. * Strong experience building and maintaining high-throughput backend services and APIs at scale. * Deep understanding of software engineering best practices. * Familiarity with the rest of our stack: Redis, Kafka, Postgres, Datadog, Grafana, Kubernetes, Helm, Kong, Terraform, Docker, GitHub. * Familiarity with AWS services such as RDS, ElastiCache, CloudSearch, EKS, and MSK., * Knowledge of live ticket sales or experience working within a fast-paced industry. * Mentorship and leadership experience guiding onshore and offshore teams. * Genuine interest in growing the engineers around you and shaping team culture, even without a formal management track. ## Description Victory Live is looking for a Staff Software Engineer to own the technologies and processes that power our B2B marketplace on Ruby on Rails and Hanami. You'll ship features across several business-critical monoliths and microservices, retire technical debt, and set the standards other engineers build against. This is a chance to shape one of our main revenue engines at a premier live event ticketing company. RESPONSIBILITIES * Collaborate across teams to influence engineering work, ensuring decisions align with divisional strategy. * Drive large-scale technical initiatives in our Rails and Hanami services, solving highly complex problems and shipping scalable, secure solutions. * Provide guidance and support to engineers, helping them grow and work through hard technical problems. * Work with Architects to design and implement system-level solutions within company standards. * Define and promote engineering best practices across teams, from RSpec coverage to service boundaries. * Identify and pay down technical debt in legacy Rails code to keep it maintainable. * Hold the team's code to a high bar through rigorous review, consistent with our quality program. * Write high-quality code yourself on the most complex and critical work., * You'll build the infrastructure live events run on; millions of tickets, hundreds of venues, many of the largest teams and events in the world. * A lean team where decisions move fast and your code reaches real fans, often the same week. * Every release has stakes. Every improvement is felt. * High expectations, low tolerance for politics, and a culture built on writing well and shipping with care. OUR VALUES We build the systems that power live event ticketing, and we hold a high bar for how we do it. Four principles run through everything: * Quality of life. Sustainable processes over heroics. Nobody should be a single point of failure, and nobody should be afraid to take a vacation. * Quality of code. Clarity over cleverness. If a teammate needs a long explanation to follow your code, it needs simplifying. Tests prove your work; they aren't optional. * Protection of production. Every change is reviewed, tested, and observable. We build with monitoring in mind from day one so we find problems before our users do. * Shared knowledge. We work across time zones, so we communicate in the open. Questions go in channels, not DMs, and one answer becomes shared knowledge. ENGINEERING PRINCIPLES We are an AI-native engineering team. Here is what that looks like in practice: * AI-assisted engineering. Every engineer uses Claude, Claude Code, Copilot, and agentic tooling as a routine part of their workflow. * Async-first. Most decisions happen in writing through Jira, Confluence, PR descriptions, design docs. We over-communicate on changes and under-communicate on noise. * Ownership mindset. Engineers are responsible for what they write and no code reaches production without review. Reviewers are co-owners. * Observability is part of "done." If the on-call engineer can't understand a system without reading source, more logging, metrics, and dashboards are needed. * Preservation of quality of code and life. We write code that is clean, tested, and maintainable so it serves us well over time, and we build sustainable processes so no one burns out or becomes a single point of failure. * Shared knowledge and continued education. We grow as a team by learning from each other through reviews, documentation, and collaboration. OUR STACK & WAYS OF WORKING * Ruby on Rails and Hanami power our B2B marketplace, distribution integrations, and partner-facing APIs * Web & mobile clients, REST APIs, microservices * Frameworks and tools: Rails, Hanami, Sidekiq, Puma, ActiveRecord, RSpec, RuboCop * Data: Postgres, Redis, Kafka * Cloud & infra: AWS (RDS, ElastiCache, CloudSearch, EKS, MSK), Kubernetes, Helm, Kong, Terraform, Docker * AI tooling: Anthropic / Claude Code, GitHub Copilot, in-house agentic workflows * Observability: Datadog, Grafana, Elastic/Kibana, OpsGenie * Collaboration: Jira, Confluence, GitHub, Slack, Miro * Async-first, agile cadences, distributed onshore + offshore teams ## Related Videos - [Build and Deploy a Fullstack App with Open Source Tooling](https://www.wearedevelopers.com/videos/775-build-and-deploy-a-fullstack-app-with-open-source-tooling) - [Coffee with Developers: David Heinemeier Hansson](https://www.wearedevelopers.com/videos/875-coffee-with-developers-david-heinemeier-hansson) - [Improving quality with Agentic AI with Rovo Dev and Xray](https://www.wearedevelopers.com/videos/2005-improving-quality-with-agentic-ai-with-rovo-dev-and-xray) - [Navigating the Corporate Jungle: Life as a Developer in a large Company](https://www.wearedevelopers.com/videos/621-navigating-the-corporate-jungle-life-as-a-developer-in-a-large-company) - [Coroutine explained yet again 60 years later](https://www.wearedevelopers.com/videos/690-coroutine-explained-yet-again-60-years-later) - [Collaboration Quantified: Lessons from Open Source Developer Networks](https://www.wearedevelopers.com/videos/1422-collaboration-quantified-lessons-from-open-source-developer-networks) ## Related Articles - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [The 7 Most Popular Backend Frameworks for Developers](https://www.wearedevelopers.com/magazine/403-the-7-most-popular-backend-frameworks-for-developers)