Bon - Recensione dipendente - Chef De Projet presso Cofidis

4,0
22 mag 2026
Consiglia
Gradimento del CEO
Pronostico commerciale

Vantaggi

La cantine est pas mal

Svantaggi

Il faut marcher depuis la gare

Esplora altre recensioni su Cofidis

3,0
13 apr 2026
Consiglia
Gradimento del CEO
Pronostico commerciale

Vantaggi

Good work-life balance policy and generally respectful working hours. Competitive salary for new employees joining the company.

Svantaggi

For professionals interested in digital product development, this is not the best environment. The organization still operates much more with a project management mindset rather than a product management culture. As a result, APMs tend to act mainly as backlog managers and PMs as project managers rather than true product leaders. There is little discussion around product ROI, product performance metrics, or modern product discovery practices. Cloud tools are largely blocked across the company, which limits experimentation and modern ways of working. Internal communication is still done through Skype, which feels outdated in 2026. A large portion of employees have been with the company for 10, 15, or even 20+ years and appear demotivated, often waiting for dismissal to access severance compensation and unemployment benefits. This creates teams that are often less efficient and highly resistant to change. Leadership development and formal management training seem limited, which contributes to a work environment that may feel less dynamic and less attractive for professionals seeking to build modern skills and face new challenges.

5,0
24 feb 2026
Consiglia
Gradimento del CEO
Pronostico commerciale

Vantaggi

good environment, nice perks, life balance

Svantaggi

They built proprietary frameworks, without any real knowledge on what they are doing with this. Mixing mermaid with minimal apis. The architecture leadership act as developer and fight for this internal framework. My advice, if you like to program, avoid this kind of job. Also, they don't really understand api first. Using gateways for internal purposes, in some cases a simple get does 6-7 http calls, because they have a main source area that create an api and expose to an internal gateway. After this, usually another area does a "business" get of this api, this happens more 2 times at least.. Sometimes, they have an api that just calls another api and gives the same return, because in their mind they need a core api and a client api that gives the answer..

Vedi recensioni per: Utile|Valutazione|Data|Tutto