J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Academia.edu en oct. 2024
Entretien
Process included lengthy call with recruiter, after which two technical screens were scheduled. The first was a screen using coderpad. The idea was to write some code and solve a variation of a common problem. The problem itself wasn't difficult, but I didn't feel like the interview was structured very well. There were no written instructions provided, rather the interview spoke quickly and I was expected to take notes of the requirements. They failed to mention and important part of the requirements so I had to go back and rewrite. It would be helpful to have some bit of spec going in (maybe that's the point). After handling the first section, I was then asked to generate test cases for the code, but the expectations here were not communicated very well so I wasn't sure what the interviewer was asking for. Your mileage may vary on this interview depending on your interviewer's ability to communicate clearly. I didn't get moved on to the next round.
J'ai postulé via la recommandation d'un employé. J'ai passé un entretien chez Academia.edu en janv. 2026
Entretien
Worst interview experience I have ever had even though I was able to solve the problem. They ased a variation of fizz buzz problem which was easy but then they asked to write a function to test it which sounds simple but there were 2^4 possible test numbers that I was supposed calculate. The interview was explaining the problem verbally which was so absurd. I have never seen anyone not writing down the problem statement. The interviewer could not explain the problem properly. I had given up but at the end I was able to come up with a solution but I was least interested in the company. Got rejected but anyways I don't want to work at a company where they say something else and do something else.
J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Academia.edu en nov. 2025
Entretien
The interview process was one of the longest I’ve experienced: six calls in total. The technical stages included a system design interview, a behavioural interview, and a “virtual on-site” session where I spent four hours solving technical problems with three different team members. I completed all stages, including the final four-hour session, which I felt went well. However, later that same day I received a brief, generic rejection email from a no-reply address (previous communications had come directly from HR).
What was disappointing wasn’t just the outcome, but the complete lack of feedback. When I followed up to request it, the response was again short and impersonal - simply wishing me luck without offering any details or constructive insights.
Questions d'entretien [1]
Question 1
Have you ever been in the situation where stakeholder's view conflicts with a member of the engineering team? What did you do?
