Initial HR screening call, then something they called an e2e interview. The topic and format was completely different to what I was told by the recruiter, leaving me blindsided once I got into the interview. I was told we would be using something like a google draw app but it actually all happened in a google doc
Acudí a una entrevista en monday.com (Varsovia, Mazovia)
Entrevista
Overall, I really enjoyed the interview process. The rounds were well structured, practical, and relevant to the role. I also appreciated the interviewers’ attitude: they were professional, respectful, and genuinely focused on understanding my thinking rather than just checking for memorized answers.
Preguntas de entrevista [3]
Pregunta 1
Be prepared to explain how you would solve a realistic technical task related to the company’s product or internal systems.
Be prepared for an advanced system design discussion. Expect to lead the conversation around event-driven architecture, queueing choices, fault tolerance, retries, idempotency, backpressure, ordering guarantees, observability, and trade-offs between specific technologies such as Kafka, RabbitMQ, SQS, Pub/Sub, or similar services. You should be able to justify why you would choose one approach over another.
Be prepared for a standard coding interview in your preferred programming language. Practicing medium-level LeetCode problems should be enough preparation.
Me postulé en persona. El proceso tomó 2 semanas. Acudí a una entrevista en monday.com (Tel Aviv) en nov 2017
Entrevista
The process consisted of three sessions, two technical and one with human resources. It was very open, transparent and professional. They really focus on finding the best possible cultural/professional fit. You really get all the information you need to understand if that workplace suits your ambitions.
Preguntas de entrevista [2]
Pregunta 1
Go through real live engineering problem and describe how would you solve it.
