Treezor

Treezor

FinTech / InsurTech

Paris, Berlin, Madrid, Milan, Rennes

Technologies and tools

    Backend

    • PHP
      PHP
      100%
    • Go
      Go
      100%
    • SQL
      SQL
      50%
    • Python
      Python
      50%
    • Node.js
      Node.js
      50%

    Frontend

    • TypeScript
      TypeScript
      100%
    • React JS
      React JS
      100%

    Devops

    • Serverless
      Serverless
      100%
    • AWS
      AWS
      100%
    • Terraform
      Terraform
      75%
    • Docker
      Docker
      75%

Organization and methodologies

The Tech team operates according to the Agile methodology, organizing two-week sprints. We kick off each cycle with a Sprint Planning to clearly define goals, followed by Sprint Reviews that include demos to showcase the progress made.

Every squad meets daily for 15 minutes during a daily meeting. These gatherings aim to discuss potential obstacles and daily goals, ensuring a convergence towards the same objectives for all team members.

We value the participation of everyone in Tres Amigos meetings and Sprint Planning. Individual contribution is crucial to maintaining a strong team dynamic and making sound technical decisions.

Projects and tech challenges

Migration sur AWS

Migration sur AWS

Treezor has integrated a full-fledged bank into a lambda. Our platform operates with a serverless stack powered by AWS, fully leveraging managed services such as:

  • API Gateway,
  • Lambda,
  • DynamoDB,
  • SNS,
  • SQS,
  • KMS,
  • S3, etc. This allows us to focus on our core expertise: core banking.

Treezor represents a multitude of services meeting specific business requirements such as scalability, low latency, and high resilience.

Every day, we send over 3 million webhooks to our clients, process more than 90 million API calls, and handle hundreds of thousands of card transactions, all with minimal latency. And all of this, without relying on a single server.

IMCCL

With the growing demand for control in the fields of mobility, catering, and social benefits (CSE), an increasing number of fintechs are seeking solutions.

IMCCL presents itself as a rule engine that enables clients to implement card usage restrictions without requiring heavy development on their part.

This engine evaluates, during transactions, complex business rules based on transactional data, metadata, or extensive history.

Technical challenges:

Managing hundreds of thousands of requests in real-time. Providing clients with a simple API.

IMCCL

Recruitment process

Step 1: Interview with our Talent Acquisition Manager

Step 2: Technical interview with your future Manager

Step 3: Technical test and/or meeting with your future team