Candidatei-me por meio de recrutador(a). O processo levou 2 semanas. Fui entrevistado pela Svitla Systems (Buenos Aires) em ago. de 2023
Entrevista
It started with a message on LinkedIn, followed by a very polite and fun exchange, then a short English checkup, an internal interview, an interview with the technical team at the customer, and finally an interview with the Manager of the product.
Perguntas de entrevista [1]
Pergunta 1
Was given a scenario for application integration, was asked about the challenges and mitigation strategies that I was able to see.
Candidatei-me por meio de recrutador(a). O processo levou 2 semanas. Fui entrevistado pela Svitla Systems (Kyiv, ) em set. de 2022
Entrevista
There were 3 stages of interviewing process: 1) With HR, 2) With PM from Svitla Systems - technical interview, 3) With the client - technical interview. Questions in part 2 were
Candidatei-me por meio de recrutador(a). Fui entrevistado pela Svitla Systems (Kyiv, ) em abr. de 2022
Entrevista
Interviewed for 2 different projects (of 2 different Svitla customers).
Initial contact with Svitla was with Svitla recruiter. First step of the recruitment process is a 15m call with recruiter.
Recruitment process to both of Svitla customers was a 30min call with Svitla project (manager) coordinator and a ~1h technical interview with the customer.
The first customer shortlisted me but chose the other guy, the second customer chose me as their first pick (all according to Svitla recruiter).
Svitla recruitment team did great, 10/10, really swift and honoured my every request. Kudos to them!
Perguntas de entrevista [3]
Pergunta 1
Customer 1. Code review.
Review code of service/dao layer. The idea is to make the interviewee notice as many pitfalls as possible and fix them without creating more, like:
-Spring's @Transactional standard pitfalls
-Therad-safe counter
-N+1 problem
Customer 2. A question on microservice architecture.
Given you have 3 microservices, each owns its own part of data. What would you do to ensure retrieval of aggregated data owned by all 3 services with minimum latency and network overhead?
Customer 2. Code review.
Review code of controller (mostly) layer. The idea is to make the interviewee notice as many pitfalls as possible and fix them without creating more, like:
-Single responsibility principle violation
-Dependency inversion principle violation
-Potential OOM
-Overall bad coding practices
