Software Engineer applicants have rated the interview process at Reply with 2.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 68.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 13 days to get hired, when considering 117 user submitted interviews for this role. To compare, the hiring process at Reply overall takes an average of 16 days.
Common stages of the interview process at Reply as a Software Engineer according to 117 Glassdoor interviews include:
Phone interview: 42%
Skills test: 14%
One on one interview: 12%
Presentation: 11%
Personality test: 10%
Background check: 6%
Group panel interview: 2%
IQ intelligence test: 1%
Drug test: 1%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Reply in Aug 2023
Interview
Colloquio conoscitivo e tecnico con l'azienda con domande in linea con la posizione. A fine processo c'era interesse da entrambe le parti ma il colloquio con HR centrale non ha dato esito positivo ma non sono riuscito a capire perchè
Interview questions [1]
Question 1
Quale è una tua caratteristica positiva e una negativa. programmazione: singleton e domande di sql.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Reply nel mese di giugno 2026, Collouio tecnico per full stack developer, la posizione era per un full stac developer su react e python, con focus su AI e integrazione modelli llm
The interviewers were professional and the discussions were generally pleasant. The process was straightforward, although communication between stages could have been more consistent and timelines were sometimes unclear. Overall, a decent experience, but greater transparency around next steps would improve the candidate experience.
Interview questions [1]
Question 1
"Walk us through a recent project and explain the technologies, trade-offs, and challenges involved."
I had two interviews, a technical live coding challenge with average logic questions that did indeed go well, and a technical task to be built in a week. The latter was a type project I didn't have many experience of, and technically didn't need experience of to access the job as it was an entry level (graduate) position.
Interview questions [1]
Question 1
Programming logic questions, build a project in a week task.