We’re looking for somebody who’s really great
- You need to be experienced in both Ruby and Rails and also know where the boundaries lie between them. You need to be able to code in Ruby without any of Rails’ training wheels.
- You enjoy mentoring juniors and giving in-depth feedback during code reviews. While you appreciate the small stuff, you recognize bikeshedding and can avoid its pitfalls.
- You code with reason and can justify the important decisions you made during development.
- You know and apply best practices. That means the usual like version control, testing, and refactoring; but also good object-oriented design, DRY, SRP,…
- You’re aware of the trade-offs involved in proper engineering and can make balanced business decisions, keeping in mind all the stakeholders of the project.
- You’ve got opinions on code design and you can stand by them, but you’re professional enough to not let them get in the way of a consensus if necessary.
- You have good knowledge and foresight of potential performance issues that might arise when working with large datasets.
- We’re not only working with our own API but also a bunch of external parties who speak JSON, REST, XML, or SOAP. You can not be afraid of WSDL and advanced XML parsing.