Real, anonymous reports from people who interviewed for Software Engineer at Konrad Group, newest first and distilled into what to expect across the loop.
I started with a recruiter-style screen that felt more like a quick conversation than a deep assessment. It was short—around 20 to 30 minutes—and focused on getting comfortable with my background and motivations. I was asked standard behavioral prompts like introducing myself, why I wanted to work there, and even what I did in my free time. A couple times the vibe included checking company interest and my availability, and one screen mixed languages (Spanish with some English). Overall it wasn’t technical at all, and it didn’t feel like there was enough time to truly judge fit.
My interview journey was noticeably harder and felt more like an endurance test than a guided technical discussion. I went in for an in-person technical interview that lasted about two hours, and it included real coding pressure—then I was hit with a LeetCode-style hard problem. After that, I was given a React-oriented take-home assessment that added even more weight.
The initial recruiter call is typically brief, lasting 15-30 minutes, focusing on fit and background rather than technical skills. Candidates should expect behavioral questions and a relaxed atmosphere, but some felt it was too short to fully assess their capabilities.
The technical interview varies in difficulty but often includes coding challenges, system design questions, and discussions about web fundamentals. Candidates should prepare for both live coding and conceptual questions, with a focus on practical application and problem-solving.
Candidates typically face a timed take-home assignment that often involves building features in a React-based application. The tasks can be complex and require effective time management, as they are designed to assess both coding skills and prioritization under pressure.
The final interview stage often involves a conversation with senior leadership, focusing on cultural fit and values alignment rather than technical assessments. This step is generally more informal and allows candidates to discuss their motivations and experiences.
Candidates noted that the interview process is generally well-structured with clear stages, but communication can be slow, leading to uncertainty about progress. Some experienced delays and a lack of feedback, which affected their overall impression of the process.
The overall difficulty of the interview process varies, with some candidates finding it challenging yet fair, while others felt overwhelmed, especially during the take-home assignments. Many reflected on the need for better preparation and time management skills to navigate the intensity of the assessments.