Software Engineer applicants have rated the interview process at Crédit Agricole with 3.4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 29% positive. To compare, the company-average is 53.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 19 days to get hired, when considering 7 user submitted interviews for this role. To compare, the hiring process at Crédit Agricole overall takes an average of 19 days.
Common stages of the interview process at Crédit Agricole as a Software Engineer according to 7 Glassdoor interviews include:
Phone interview: 27%
Skills test: 27%
One on one interview: 13%
Background check: 13%
Personality test: 7%
Group panel interview: 7%
IQ intelligence test: 7%
Here are the most commonly searched roles for interview reports -
The interview process is smooth with friendly interviewer. I was told that will be informed for the results but end up never reply to me. Should not tell the interviewee to wait for the notification if you are not going to inform the unselected candidates
Interview questions [1]
Question 1
what is the most challenging task during your last project
I applied online. I interviewed at Crédit Agricole in Nov 2025
Interview
Hard, 3 people who conducted the interview. asked technical questions about framework and experience about programming. lasted about 1 hour with many questions. conducted at their office in the morning
I applied through a staffing agency. I interviewed at Crédit Agricole (Paris)
Interview
Le processus est simple et court : vous réalisez d’abord un entretien technique d’environ une heure avec un Tech Lead. Si l’évaluation est positive, la RH reviendra vers vous sous quarante-huit heures pour confirmer votre sélection, préciser la date d’entrée souhaitée et initier immédiatement les étapes contractuelles et administratives nécessaires.
Expliquez comment Spring applique le principe d’inversion de contrôle (IoC) par l’injection de dépendances et quels bénéfices cela apporte à la testabilité d’une application .
Quelles responsabilités l’annotation @SpringBootApplication combine-t-elle et que se passe-t-il en coulisse lors du démarrage d’une application Spring Boot ?
Comment Spring Boot détermine-t-il les classes d’auto-configuration à charger et comment peut-on en exclure une de façon ciblée ?