At Elevo, we think a well crafted software can help induce a positive paradigm shift in how companies think about management and feedback. Historically, it's been backwards: HR software usually emulates existing workflow in a clunky, disengaging way. We believe in deliveringa management framework that works, enabled by a smooth, beautiful software to make people management work better.
We are inspired by the best practices we have witnessed first hand in our past experiences in bigger tech companies such as Apple, Google or Criteo.
We are looking for pragmatic, like-minded people that like to think through challenges to deliver the best product we can.
🎉 Our Culture
- Our software aims at being simple, reliable, and yet customizeable to adapt most workflows. We start simple, then expand.
- It happens we try to do the same with our organization.
- We use a kind of 2-weeks Scrumban, keeping what works for us. We design, plan, and discuss together. We do a retrospective once a week, when we discuss technical and organizational matters alike.
💻 Our Stack
- We keep things as simple and up-to-date as necessary.
- On the backend we use Ruby on Rails 6 with PostgreSQL as our main database for our JSON:API endpoints, and Redis for jobs and cache (think volatile data).
- On the frontend, we use React 16.8 with Flow, ES6, and Babel.
- We have an evolving UIKit, spanning from Figma to React, consisting in a set of components, styles and guidelines we reuse. Bulma is its CSS (or should we say SASS) foundation.
- We have thousands of Rspec tests, units, integration, API, and E2E, integrated in CI with other linters (Rubocop) and prettiers (well, actually mainly one, called Prettier). We even have spawnable staging environments and data tests for heavy migrations.
- All of this is monitored through HostedGraphite dashboards, and Sentry, LogEntries, Sqreen and NewRelic allow us to stay on top of possible issues, should they arise despite our extensive test suite.
- Possible future evolutions include: using Sorbet to static-type our Ruby, use GraphQL instead of JSON:API if it makes sense, make use of React hooks, integrate Danger in our CI or make a native 65c816 app.