J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez EvolutionIQ en févr. 2025
Entretien
I interviewed with EvolutionIQ in February 2025 after a recruiter reached out via LinkedIn. The first round was a recruiter screen with a coding question at the end. The recruiter didn't seem technical and only seemed to care about the solution producing correct results, but I solved it optimally.
The next round was a system design round where I was also asked some behavioral questions. The system design part was straightforward, focusing on tradeoffs and different ways the system could be designed, as well as follow-ups around different problem constraints and how they affect the architecture.
About a week afterward, I received a rejection email with no feedback whatsoever, and the recruiter did not respond to requests for feedback.
Questions d'entretien [1]
Question 1
- Talk about a complex problem you managed to tackle.
- How do you manage disagreements at work?
- What kind of technical problems are you most excited about?
J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez EvolutionIQ
Entretien
The first step was the recruiter screen, which included a fast 15 min coding problem. Then came coding rounds with engineers. The problems I received involved using dicts, recursion, arrays. For some reason I was given a lot of React problems. Maybe they saw I used to do a lot of UI and meant to make it easy, but I had been only practicing LC and system design since I'm interviewing with OpenAI. From Q&A it sounded like they did >= 80% frontend so it could be that interview panel.
J'ai postulé en ligne. J'ai passé un entretien chez EvolutionIQ
Entretien
I had a recruiter screen with a live coding challenge (LeetCode easy level) and an interview with the hiring manager.
HM looked bored. He read me three questions, I answered them, and offered, "I also had to solve challenge X while doing Y, we can dive deeper into that if you want".
No follow-up questions have been asked. Not even acknowledgment of an answer, like "ok, sounds good". The guy just kept reading.
10 minutes into a 30-minute interview, he said, "If you don't have questions for me, we can end it here".
Questions d'entretien [1]
Question 1
Standard behavioral questions: Hardest tech challenge you solved, conflict with a coworker, etc.
J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez EvolutionIQ
Entretien
I had a 45-minute interview scheduled with the recruiter. The first part of the conversation was mostly about my background, experience, and the role I was applying for. The recruiter asked about my previous projects, technical skills, and how my experience aligned with the position.
Just when I thought we were wrapping up, they threw in a coding question at the end—definitely a curveball! It wasn’t something I was expecting in a recruiter screen, so it caught me a bit off guard. The problem itself wasn’t too complex but required some quick thinking.
Questions d'entretien [1]
Question 1
Didn't expect coding question during the screening round. Recruiter asked disjoint set question.