Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en Kin Insurance en sept 2025
Entrevista
Coding assessment was a simple program to parse and do some processing a file/data set. I tried not to spend too much time on it (about a day) but I separated the different stages of the processing "pipeline" into their own modules with interfaces between them, unit and integration testing, no dependencies.
Initially they liked my solution and moved me forward to the behavioral interview which was 2 engineering managers drilling me with "tell me a time you..." with follow ups ("what did you learn from that", "describe X tech you used").
I'm not sure why, but from the get-go the two managers definitely didn't want me to be there. Felt like a bad date.
It ended and I got rejected with a "actually your coding assessment solution was bad" email.
Otras opiniones sobre las entrevistas para el puesto de Software Engineer en Kin Insurance
Envié una solicitud electrónica. El proceso duró 3 semanas. Acudí a una entrevista en Kin Insurance
Entrevista
1- Phone screening.
2- Another interview asking about my background and stuff.
3- they gave me the classic bank_ocr_kata challenge to take home and they mention that you need to spend no more than 2 hours so I was able to only finish 1 task.
then you have another interview with 2 developers working in the company.
one asking and the other just observing.
Preguntas de entrevista [1]
Pregunta 1
debug the application.
why is this not working.
how is that working.
explain your code.
ps: in the debug part he will ask you a question and if u take more than 3 sec to answer he will answer for you. DON"T let him answer for you! ask him to give you some time to think.
he already knows the answers that's why he is impatient.
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en Kin Insurance en nov 2021
Entrevista
HR interview
Behavioral Interview
Tech/coding review
Like other experiences here - the coding interview was a little confusing. On one hand I need to work on verbally explaining my code - it’s fair if I got knocked out for that. OTOH the senior level programmer seemed really impatient when I needed clarification on how he wanted me to change my application. I began one approach and he cut me off. It seemed also there was an expectation the code would have unit tests? They gave us 2 hours!
The code problem is 100% google-able.
Company should supply example data - the one thing I googled up and used.
Company should clarify expectations during the code review. I think an actual discussion would work better then an awkward presentation with commands thrown in.
Fwiw - I generally got good vibes from the company.
