Senior Ruby on Rails Engineer

Who we are We build real-money and social gaming platforms that entertain millions of players. When someone wins a tournament at 2am, our Rails services notice, move the money, and write it all down for the regulator. Reliability, data integrity, and security matter here as much as shipping fast. Some days, more. What this job isYou’ll design, build, and scale the backend of our game platform: player accounts, wallets, game sessions, promotions, and the APIs our games and partners depend on. It’s high-availability, it’s regulated, and it’s full of money that has to move exactly once. If that last sentence made you sit up straighter, keep reading. AI isn’t a side quest hereLet’s be direct about this, because most job posts aren’t. AI is core to how we build software at Gameplay Network. Every engineer here works with Claude daily: planning features, root-causing production incidents, writing migrations, reviewing diffs, and automating the boring parts we used to pretend we enjoyed. “Have you asked Claude” is a standup sentence, not a punchline. So yes, you’ll need to be an expert. Not “I tried a chatbot once” expert. Expert as in: you know how to hand an agent the context it needs, split the work between you and it, catch its confident nonsense before it ships, and own every line that lands in main no matter who typed it. The bar for judgment goes up, not down. AI makes strong engineers faster and sloppy engineers dangerous, and we only hire the first kind. If you think AI-assisted development is cheating, this isn’t your job. If you think it means you can stop reading code, it’s really not your job. But if you’ve felt the thing where you ship in an afternoon what used to take a week, and your first thought was what that makes possible: hello. Keep reading. Who you areStrong opinions, loosely held. You’re not married to your ideas about programming, but you’ll defend them until a better one shows up.If you don’t use Vim, you wish you did every time you watch Aaron Patterson fly through a live-coding exercise.You want to be at Rails World every year. When you can’t make it, you catch up on YouTube and feel a little robbed.You contribute to open source where you can, and you read new Rails release notes the way other people read movie reviews.You love design patterns, you hate leaky concerns, and you can smell a code smell from two directories away.What you’ll doBuild the core platform. Design and maintain scalable Rails services behind real-time gameplay, wallet transactions, and player accounts.Ship APIs that our partners, and internal tools depend on. RESTful by default, Turbo Streams and WebSockets when the page has to move on its own.Own the data models. Well-indexed PostgreSQL schemas and ActiveRecord queries that stay fast under real player load.Keep the bar high. Write RSpec suites, review code, and hold the line on correctness, security, and maintainability.Run it in production. Instrument services, watch the dashboards, triage incidents, and make the latency graphs go down and to the right.Take compliance seriously. Authentication, authorization, encryption, and audit logging built for a regulated industry. (Regulators really do read the logs.)Work across the whole shop. Product, game designers, QA, and DevOps, from spec through deploy.Leave things better. Find the bottlenecks and the tech debt, then make the case and fix them.What you’ll bring10+ years building production software, most of them with Ruby on Rails in the room. We’re on Rails 7.2 and 8.x and Ruby 3.3, and we don’t let versions rot.Fluency in MVC, ActiveRecord, and Rails conventions, plus the judgment to know when to break them.Deep PostgreSQL experience: schema design, indexing, and query plans you can actually read. Redis for the fast paths.The modern Rails front end: Turbo Frames and Streams, Stimulus, ViewComponent, and Tailwind, served over importmaps. There’s no webpack here. We’re not sorry.Background jobs with Solid Queue, or enough Sidekiq scar tissue that the switch takes you a weekend.Comfort with concurrency: our app server is Falcon and our service calls run on the async gem, so fibers aren’t a trivia topic here.Event streaming with Kafka or queue technologies (NATS/RabbitMQ): producing, consuming, and knowing what “at least once” implies for a wallet.API craft: Faraday clients against platform services, Jbuilder responses, JWT in the middle.Real fluency with AI-assisted development. Claude writes code here every day; your job includes directing it well and owning what it produces.Tests you’d stake a deploy on: RSpec, FactoryBot, VCR, and Capybara, running in Bitbucket Pipelines on every push.Production sense: Datadog dashboards, Airbrake triage, structured logs, and the instinct to check the graph before the group chat.Web security fundamentals. In this industry, “mostly secure” is not a category.Git, pull requests, and code review as a daily habit, not a formality.Clear writing and clear speaking on a distributed, cross-functional team.Bonus pointsHotwire Native. Our iOS app is this codebase wearing a native shell, and engineers who understand the bridge are gold.You’ve shipped in gaming, iGaming, sports betting, or another compliance-heavy industry.You’ve lived in a 100% SLA environment and still sleep fine.Real-time features over ActionCable: broadcasts, presence, leaderboards that move while you watch them.Payments, wallets, or other systems where the ledger has to balance.AWS in practice: S3, Cognito, SQS, SNS, Lambda, ECS, Aurora/RDS.Golang for the hot paths.Contentful or another headless CMS feeding a server-rendered front end.A CS degree, or the self-taught equivalent with the commit history to prove it.What you getA competitive rate.Remote work and flexible hours. We care that it ships and that it works, not where you sit.Conference support. Rails World, obviously.Hard problems: real-time gameplay, financial integrity, and scale you can feel.A team that reviews code like it matters, because here it does.Pitch usSend your résumé and a short note about the most interesting backend problem you’ve ever solved. The race condition that kept you up at night. The migration you rehearsed for a week. We’d rather read that than a formal cover letter. GitHub links and code samples are welcome, never required. $ rails new career --database=postgresql # your move.