Real, anonymous reports from people who interviewed for Software Engineer at Yochana, newest first and distilled into what to expect across the loop.
My interview felt fairly grounded in resume details. The conversation started with questions connected to what I’d already written down—projects, experience, and the key tech I claimed—and then it expanded into basic programming and OOP concepts. I remember being asked about OOPS explicitly and also facing SQL-related questions.
My interview started with a discussion of my project background, then shifted into a more focused deep dive. I was asked about the streaming-related work from my experience and had to walk through my project in detail. Since my projects involved Kafka, a big chunk of the questions followed that thread.
The interview process typically starts with an online assessment followed by technical rounds that include coding and project discussions, often culminating in an HR round. Candidates noted that the overall structure felt organized and predictable, although some experienced delays in receiving follow-up communication after interviews.
Technical interviews often emphasize core programming concepts, particularly in Java, OOP principles, and practical problem-solving scenarios. Candidates reported that questions were generally aligned with their resumes and aimed at assessing both theoretical knowledge and practical application.
Candidates frequently engaged in discussions about their past projects, with interviewers probing for detailed explanations and scenario-based questions related to the technologies used. This focus on real-world application required candidates to articulate their thought processes and decision-making clearly.
The HR round typically assesses cultural fit, communication skills, and career aspirations, often involving questions about teamwork and adaptability. Candidates felt that this round was less technical and more focused on personal alignment with the company's values and expectations.
Overall, candidates described the difficulty of the interviews as average, with some noting that while the questions were straightforward, they required careful thought and clarity in responses. Many felt that the interviewers aimed to evaluate their problem-solving abilities rather than trick them with difficult questions.
Several candidates expressed frustration with the lack of communication following their interviews, particularly regarding updates on their application status. This lack of transparency left some feeling deflated, despite having completed the technical portions successfully.