Ruby Backend Engineer

Evil Martians are looking for a fully remote Ruby Backend Engineer to join our distributed team.What We Offer- $65K – $110K gross annual salary.
- We are a remote-first company and we hire globally (19 years of remote experience and async communication).
However, to maintain a healthy work-life balance for our workers, we require a minimum of 3 hours of daily overlap with the Pacific Timezone.
- We can support your relocation to Portugal if you want.
- A significant impact: Work in a small, dedicated team, collaborating directly with startup founders and engineers.
You won't just close tickets—you'll shape products, care for the business, and solve real user problems.
- Architectural freedom: Lead a new project every one to two years.
You'll have the autonomy to choose the technology stack and make key architectural decisions from the ground up.
- Transparent finances and revenue sharing.
- Open source culture (AnyCable, Yabeda, TestProf, and many other popular projects were created here).
Support for conference speaking and professional growth.
- Most of the people in your team can code, including founders, managers, and designers.You Fit This Position If- Ruby and Rails.
"Ruby is for developer happiness" are not empty words for you.
You know the Rails Way and when it's better to derail from it.
- Performance optimization expertise.
Experience optimizing Ruby and Rails applications, detecting and fixing performance bottlenecks, dealing with emergencies, and collaborating with our SRE team when needed.
- Database mastery.
Advanced knowledge and optimization experience with relational databases (PostgreSQL specifically), and some experience with non-relational databases (Redis, Elasticsearch).
- Adaptable to any codebase.
Ready to work with codebases of varying age—sometimes starting projects with a clean slate, sometimes improving legacy codebases to optimize them and bring in modern software engineering practices.
- Programming polyglot (or willing to become one).
Besides Ruby, we use Go, TypeScript, Elixir and Rust on our project backends—sometimes for microservices, sometimes entire projects are written in non-Ruby languages.
- Think like a product owner.
You are driven to understand the "why" behind your work.
For you, engineering is about helping people and businesses succeed.
You understand the processes of a modern startup.
- You don't just use a step‐step guide instead always try to learn your tools very deeply.
Advanced knowledge of Ruby and Ruby on Rails, with experience organizing large codebases in a clean and maintainable way, testing and profiling Ruby code.
- A "manager of one."
You are a master of your own time and can work effectively without micromanagement.
You practice careful reading, clear async communication, and proactive questioning.
You can work asynchronously, document your ideas and solutions, self‐manage planning, and take ownership of tasks.
- You have good English writing skills and aren't afraid to speak on calls.
Russian speaking skill would be a big advantage for communicating with our Russian‐speaking teammates in Europe, the US, and Japan.
- Your story.
Tell us about your experience, interests, your previous projects, and your role (what did you do or achieve).
- Code showcase.
As a starting point, we need to see some sample code.
You can send us links to your GitHub projects or Pull Requests.
You can also create (secret) GitHub Gists to send us code samples from your closed source projects: something that solves a non‐obvious, advanced task, or examples of beautiful code.
Ideally, you would also describe what the code does, include tests, and a general description of the feature or the problem relevant to the code.
- Location & relocation.
Mention your current location and if you're open to relocation.
We do not hire in Russia.The Hiring Process- We check out your code snippets—or ask for a few more samples.
- A technical interview via Zoom (in Russian).
Important: we will NOT ask you to participate in stressful "whiteboard" programming, nor do we ask lame, dated "puzzle" interview questions.
We're interested in your knowledge, experience and potential.
- A take‐home test task.
Usually we'll ask you to write a new library (Ruby gem) or make a pull request for an existing open source project.
We'll strive to provide good feedback throughout the process, and, if the task is generally complete but still requires some changes, the chance to improve it.
Beyond the interview, you could use the result of this task to extend your personal open source portfolio;
sometimes these become proper, valuable projects in the Ruby community, or valued as important changes to existing libraries.
Some ended up in the Ruby Weekly newsletter.
- Zoom interview with the CEO of Evil M