It started off with a brief introduction, where the interviewer asked me to walk through my background and past experiences. After that, they posed a single main technical question for me to work through. The session was structured in multiple steps — the interviewer began with a fairly straightforward version of the problem, then gradually layered on more complexity as we progressed. Each stage required a bit more reasoning, so it felt like the difficulty was intentionally ramped up in a step-by-step manner.
Overall, the flow of the conversation felt pretty typical for a standard technical interview. It wasn’t overly tricky or filled with surprises, but instead focused on assessing how I approached a problem, broke it down, and adapted to new constraints as they were introduced.
Otras opiniones sobre las entrevistas para el puesto de Software Engineer en Insi
Propose a fix to compiler slowness, take into account python overhead, must work across suite of compilation targets, caching is required to reduce end to end time. Interview was ok, but very slow follow up due to poor HR processes
Acudí a una entrevista en Insi (Londres, Inglaterra)
Entrevista
The interview process for a software engineer role usually starts with resume screening followed by a quick 15-30 minute recruiter call. Next comes a technical phone screen (45-60 mins) with 1-2 coding questions on platforms like LeetCode. Candidates who pass are invited to virtual or onsite interviews (4-6 rounds), which typically include: 2-3 coding/algorithm rounds, 1 system design round, and 1-2 behavioral/cultural fit interviews. Some companies also add a take-home assignment or pair-programming session. The entire process usually takes 2-6 weeks, and strong performance across coding, design, and communication is key to receiving an offer.
Las mejores empresas en cuanto a «Remuneración y beneficios» cerca de ti
