The Product team works every day to ensure the quality and reliability of the Steeple application across all its interfaces. The Product team's projects are both ambitious and technical, enabling us to develop new functionalities and meet our users' needs a little better every day. It's a team effort that requires very good (internal) communication!
Steeple
Mobile Apps, SaaS / Cloud Services, Software
Rennes, Bordeaux, Lille, Lyon, Madrid, Milan, Strasbourg, Toulouse
Tech team
Employee breakdown
Front-end Developers
29.0%
Back-end/Full-stack Developers
38.0%
DevOPS
3.0%
Fluter
6.0%
Product Owners
9.0%
Designers
6.0%
Engineering Manager
3.0%
Chargé de qualité logiciel
3.0%
Directeur Produit
3.0%
Key figures
91 %
unit test coverage
Technologies and tools
Backend
Node.js
100%Ruby On Rails
100%Ruby
100%Redis
100%PostgreSQL
100%Firebase
100%
Frontend
JavaScript
100%Vue.js
100%SCSS
100%SASS
100%TypeScript
100%Nuxt.js
100%Storybook
100%Vuetify
100%Axios
100%
Devops
Heroku
100%GitHub
100%Docker
100%Kubernetes
100%Terraform
100%AWS
100%
Automated Testing ⚙️
Essential for an industrialized project, testing is an integral part of our development process. We use RSpec for Ruby, Jest and Cypress for the front end.
JIRA ⚙️
The ultimate collaborative working tool, it enables us to organise and communicate on the work to be done.
Figma ⚙️
A user interface design tool. It gives our teams a concrete view of the screens to be developed, depending on where the application will be displayed (TV, web browser or mobile).
Organization and methodologies
On a day-to-day basis, the Product team is organised around the ShapeUp agile method:
- 6-week development cycles: during which the technical teams (from 2 to 5 people) work autonomously on projects directed by the Roadmap, accompanied by the Product Owner
- Daily scrum: to share progress, help each other and provide potential alerts
- A 2-week Cool Down phase: during this phase, the following activities take place:
- A retrospective whose objective is continuous improvement (quality, process, etc.) via concrete, achievable action plans
- A demonstration phase enabling the teams to present and share the projects they have completed
- A development period for subjects outside the Roadmap, such as corrections and maintenance (technical debt management, documentation, version upgrades, etc.)
- Preparation of prioritised topics for the next cycle: exploration, reflection on the design and technical breakdown, etc., in order to start development in the best possible conditions.
Projects and tech challenges
Public API
As part of Steeple's evolution and platform development, numerous clients and partners would like to consume our data to integrate it into their tools. The requests and use cases are diverse and numerous, such as having access to:
- The list of members in an organisation to directly integrate it into an HRIS tool.
- Integrating Steeple Messaging with instant messaging tools. To meet this need for external integration, Steeple is developing and providing its own Public API along with comprehensive documentation.
Applications and Microservices
Microservices offer numerous advantages in web development. This modular approach allows an application to be broken down into autonomous services, promoting scalability, flexibility and continuous deployment. Microservices also enable code reuse and the adoption of new technologies, providing an effective solution for building scalable, high-performance web applications.
At Steeple, we have made the decision to transition our development towards a microservices architecture. For this purpose, we have chosen Node.js technology to complement our existing Ruby backend.
Recruitment process
🔎 Steeple wants a simple and transparent recruitment process (just like our solution)
- Step 1: Initial phone or video interview with Thomas, Recruitment Manager
- Step 2: Discussion with Sébastien, Product Manager
- Step 3: Role-play and discussion with the Tech Lead
- Step 4: Interview with Jean-Baptiste, our founder