> Markdown version of [/jobs/ext/1340958-full-stack-engineer-ruby-on-rails](https://www.wearedevelopers.com/jobs/ext/1340958-full-stack-engineer-ruby-on-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).

---

# Full-Stack Engineer - Ruby on Rails

- **Company:** feedbackfruits
- **Location:** Amsterdam, Netherlands
- **Experience:** Expert
- **Salary:** €5,417.0 - €7,667.0
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Microsoft Azure, Code Review, Continuous Integration, Ember.Js, Ruby on Rails, Software Engineering, Capybara, Rspec, Production Code
- **Published:** July 19, 2026
- **Apply:** https://nl.indeed.com/viewjob?jk=2cce2b41607505b7

## About the Role

* You have 5+ years of professional software engineering experience and Ruby on Rails is your home stack: you've shipped production code with it, you know its conventions, and you're comfortable in its edges
 * You write tests as a matter of course, not as an afterthought. RSpec and Capybara are part of your regular toolkit, and you write tests that actually catch things rather than just confirm the happy path
 * You are user-oriented: when you're deciding how a feature should work, your first instinct is to think about the person using it, not the implementation that's most convenient
 * You've worked in a legacy codebase before and come through it well. You know what to fix, what to leave, and how to leave things better than you found them without getting stuck in a refactoring spiral
 * You understand CI/CD well enough to work within good practices and to nudge a codebase toward them when they're missing
 * You communicate clearly, give honest feedback in code reviews, and take it just as well. You're collaborative without needing everyone to agree with you
 * You are pragmatic and document your decisions; you'd rather make a thoughtful trade-off and write it down than chase the perfect solution indefinitely
 * Familiarity with Ember.js or migration scenarios from it to Hotwire is a genuine advantage here; experience with AI dev tooling, Azure, or observability practices would serve you well too



## 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)
- [Fireside Chat with David Heinemeier Hansson](https://www.wearedevelopers.com/videos/980-fireside-chat-with-david-heinemeier-hansson)
- [The AI-Ready Stack: Rethinking the Engineering Org of the Future](https://www.wearedevelopers.com/videos/1706-the-ai-ready-stack-rethinking-the-engineering-org-of-the-future)

## Related Articles

- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)
- [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline)
- [The 7 Most Popular Backend Frameworks for Developers](https://www.wearedevelopers.com/magazine/403-the-7-most-popular-backend-frameworks-for-developers)
- [Find a Developer Job: 12 Best Job Sites For Developers](https://www.wearedevelopers.com/magazine/165-find-a-developer-job-12-best-job-sites-for-developers)
- [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs)
- [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated)