Fairly Made

Fairly Made

Luxus, Móda, SaaS / Cloudové služby

Paris, Milano

Technologies and tools

    Backend

    • Rust
      Rust
      100%
    • Redis
      Redis
      100%
    • RabbitMQ
      RabbitMQ
      100%
    • PostgreSQL
      PostgreSQL
      100%
    • Node.js
      Node.js
      100%
    • Nest JS
      Nest JS
      100%
    • MongoDB
      MongoDB
      100%

    Frontend

    • Vue.js
      Vue.js
      100%
    • Quasar Framework
      Quasar Framework
      100%
    • JavaScript
      JavaScript
      100%

    Devops

    • Prefect
      Prefect
      100%
    • Google Cloud Platform
      Google Cloud Platform
      100%
    • GitHub
      GitHub
      100%
    • Elastic Cloud
      Elastic Cloud
      100%

NestJS ⚙️

Opinionated framework to build highly testable, maintainable and scalable backend services. Harvestr / Figma / Whimsical - At the heart of the product team to centralise requirements and translate them visually.

Organization and methodologies

Our Tech & Product team is made up of a Product Team (Product and UX/UI), a Platform Team (Core, DevOps and Cyber), and a Data Team to provide everything needed by the Feature Teams.

As far as rituals are concerned, we start the week with a meeting to share news across the company and also within the Tech team. Every morning, we have a Daily and a Weekly is scheduled every week with your manager. Peer Programming and Code Reviews are organised as needed. Everyone is free to organise sessions on demand. It is important that each team member is proactive and does not hesitate to propose organisational improvements.

Projects and tech challenges

Tech challenge

Tech challenge

We maintain 4 backend services (including data services and various compute engines) with 5 interfaces. Our number one challenge this year is to move to a microservices architecture to break our monolith.

Recruitment process

  • A first call interview with our Head of HR (20 minutes) to get to know each other.
  • A technical test to be done at home depending on the position (about 3 hours)
  • A face-to-face interview to debrief the technical test with our CTO and a lead Dev, followed by a meeting with part of the team (1h30)