No meetings. Kanban with one daily sync, then aligning with the people on the ticket. More focus time, nobody asks what you do, and also more flexibility.
Big company, big team. Nobody cares about you; you are just a number.
No team atmosphere.
You receive ticket after ticket like a robot. No empathy.
Poor design. Old Word documents. Use Figma or Sketch or anything; check the new trends.
A lot of bugs. People just want to finish work and deliver tickets, with no interest in maintaining a good codebase. This makes it very hard to enjoy.
This was my experience, but maybe you are lucky. Capgemini is big, therefore I’m sure there might be some better/good projects as well.
Learn about the new standards.
Empathy.
Make smaller, happy teams instead of big teams where people are just a number and ticket solvers.
I had a great experience with the interview process. It included two rounds: * Technical * HR The technical round focused on basic JavaScript questions, while the HR round was mostly about work-related discussions. I made it to the final round, a
Good process, very clear and direct. Although it took a couple of months, communication with the HR team was good and the interviewers' feedback was genuine.
The frontend interview focused heavily on React, JavaScript, and performance optimization techniques. I was asked about hooks like useEffect, useMemo, and useCallback, along with component lifecycle, prop drilling, and state management strategies. W
I had a great experience with the interview process. It included two rounds: * Technical * HR The technical round focused on basic JavaScript questions, while the HR round was mostly about work-related discussions. I made it to the final round, a
Good process, very clear and direct. Although it took a couple of months, communication with the HR team was good and the interviewers' feedback was genuine.
The frontend interview focused heavily on React, JavaScript, and performance optimization techniques. I was asked about hooks like useEffect, useMemo, and useCallback, along with component lifecycle, prop drilling, and state management strategies. W