Remote Ruby on Rails Engineer (Senior, Short-term, LATAM, US) ##26576

We need a builder who thinks like a founder. Not an engineer who waits for specs — someone who sees a problem, decides what to build, designs it, ships it, and measures whether it moved revenue. All in the same week, sometimes the same day.

You'll have more autonomy than you've probably ever had. That should excite you, not scare you.

This is not a traditional engineering role. There is no product manager writing you tickets. There is no designer handing you Figma files. There is no sprint planning meeting where someone tells you what to work on.

You will look at a business problem — "recruiters can't message 50 candidates at once" or "we have no idea which marketing channel drives hires" — and you will figure out what to build, how it should look, how it should feel, and then build it. You'll ship it to real enterprise customers (DPR, Swinerton, Brasfield & Gorrie, Haskell) and iterate based on what happens.

You'll work with AI coding tools daily. We use whatever's best — Claude Code, Codex, Cursor, whatever just pulled ahead this week. The tools change fast and you're expected to stay on top of that. Traditional engineering timelines don't apply — a feature that used to take two weeks ships in two days. The bottleneck is no longer typing code. It's judgment: knowing what to build, why it matters, and whether it's good.

• Contract: Short-Term (3 to 6 months)

• Location: LATAM, US

• Start Date: ASAP

• Eastern Time (EST) business hours

• Roughly 8–4, 9–5, or similar U.S. working schedule

• Interview Process: Initial interview with Technical Manager, Culture fit interview with the hiring manager, Take-home assignment.

• You'd be the 2nd or 3rd engineer, working directly with the VP of Engineering & AI.

• Rails 7.2 (monolith), Tailwind CSS, Stimulus.js, PostgreSQL, Redis, Sidekiq

• AI-assisted development (Claude Code, Codex, Cursor — whatever's best right now)

• OpenAI API, Twilio, Customer.io, Stripe, Segment, Amplitude

• AWS infrastructure

❌THIS ROLE IS NOT FOR YOU IF…

• You prefer well-defined tasks with clear requirements and acceptance criteria

• You need a product manager or designer to tell you what to build and how it should look

• You identify as "backend" or "frontend" rather than "engineer"

• You think shipping fast means shipping sloppy

• You haven't used AI coding tools in your actual workflow (not just tried them once)

• You optimize for code architecture over user outcomes

• You want a large team with established processes, code review gates, and clear role boundaries

• You're more comfortable executing someone else's vision than forming your own

• You tend to propose technical improvements without asking "does this matter right now?"

• You trust AI-generated code without deeply understanding what it's doing — especially on business logic

• You've shipped things that needed to be fixed multiple times because you didn't verify the output before handing it off

• Build full-stack product across a Rails 7.2 monolith with Tailwind and Stimulus.js, plus various AI integrations. Move between backend data modeling, frontend UX, infrastructure, and third-party integrations without needing someone to context-switch you.

• Make product decisions. You'll evaluate your own work through the lens of "does this solve the user's actual problem elegantly?" not "does this match the spec?" You'll kill features mid-build if they're not working. You'll push back on requests that don't make sense.

• Ship to enterprise customers. Our customers are large general contractors. They have real workflows, real expectations, and real revenue attached. What you build has to work, look professional, and feel polished. When you hand something to a teammate or a customer, it works. It doesn't come back three times for fixes. You take ownership of the outcome — not just the pull request.

• Think about the business. Every feature connects to revenue. You should be able to articulate why what you're building matters for the path from $650K to $3M ARR. If you can't, you should be building something else. You also know what not to build — you won't propose optimizing a $300/month cost center when the company needs to 4x revenue. You have a sense of scale and what actually moves the needle.

• Work with AI as a collaborator, not a toy. You're not "experimenting with AI." You're using agentic coding tools as your primary development environment. You've already made the cognitive shift from writing every line to directing, reviewing, and refining AI-generated output at high velocity. You stay current on what's best — if something new pulled ahead last week, you've already tried it. But here's the thing: you're the one accountable for what ships. If the AI gets the business logic wrong and you don't catch it, that's on you, not the tool.