Solicité el puesto a través de la recomendación de un empleado. El proceso duró 3 semanas. Acudí a una entrevista en intive (Córdoba) en oct 2023
Entrevista
The process is rather clear; you get one meeting with HR, a technical interview, and then an interview with a manager for the team you would collaborate with. Communication is constant and there is not too much time between steps.
Preguntas de entrevista [1]
Pregunta 1
HR
*What do you enjoy doing?
*What is your preferred compensation?
*What is your English proficiency level?
Technical:
*What is the difference between a thread and a process?
*What can you use as keys in a dictionary in Python?
Solicité el puesto a través de un captador. El proceso duró 1 semana. Acudí a una entrevista en intive (Mumbai) en may 2025
Entrevista
I recently had an interview that began with a brief self-introduction, followed by in-depth technical questions covering core Java concepts, Spring Boot frameworks, Docker, Kubernetes orchestration, and Microservices architecture and design.
HR screening, then technical interview with a principal developer. Starting off with going over the CV, then moving from there to more detailed questions. Fast paced, very in-depth technical interview No offer due to position being closed
Preguntas de entrevista [1]
Pregunta 1
Q: queues in general Q: dead letter queue Q: aws experience Q: docker image size optimization Q: docker-swarm and kubernetes questions Q: nosql vs sql Q: transactions and acid Q: conceptual: how would you sort 8gb of data with only 2gb of memory Q: python vs js in general Q: typing and mypy Q: fastapi vs other frameworks Q: REST vs rpc Q: request retrying approaches Q: circuit breaker pattern Q: python dunder methods Q: decorators Q: context managers Q: multi inheritance and mro Q: classmethod vs staticmethod Q: memory in python (reference count, garbage collector) Q: threads vs async vs multiprocessing Q: monkeypatching Q: pytest fixtures Q: GIL Q: design patterns Q: SOLID Q: Ci & CD tools
