Real, anonymous reports from people who interviewed for Software Engineer at Hiver, newest first and distilled into what to expect across the loop.
My assessment felt harshly one-sided from the start. After reaching the interview stage, I got a rapid, high-pressure block of LLD questions—seven of them—where I was expected to produce working code for each within about an hour. The interviewer supplied working context and basically wanted textbook-style answers, and there wasn’t any real willingness to discuss tradeoffs or collaborate.
I went through a structured four-round process: an initial HR-style introductory discussion, then a DSA coding round with Graph and DP-style questions. After that came an LLD round where I had to design something like Splitwise, and the last step was an HLD discussion focused on designing my previous system. Overall it felt like a fairly deliberate sequence that pushed both my problem-solving and how I think about system design.
The interview process typically consists of multiple rounds, including an initial HR discussion, followed by technical interviews focusing on data structures, algorithms, and system design. Candidates should expect a mix of coding challenges and discussions about past projects and technical choices.
Candidates will face algorithmic coding questions, often in a timed setting, with expectations for proficiency in specific programming languages like Python or JavaScript. Be prepared for both low-level design (LLD) and high-level design (HLD) discussions, as well as domain-specific questions.
The interview experience can vary significantly based on the interviewer's style, with some candidates reporting a more collaborative and engaging atmosphere while others felt the process was rigid and checklist-driven. It's important to adapt to the interviewer's approach and seek clarification when needed.
Interviews often include discussions about company culture, team dynamics, and personal fit, especially in later rounds with co-founders or hiring managers. Candidates should be prepared to articulate their values and how they align with the company's vision.
Candidates have noted that communication regarding expectations, such as preferred programming languages or interview formats, can be unclear, leading to misunderstandings. It's advisable to confirm details about the interview process and requirements upfront to avoid surprises.
While many candidates reported a well-organized and professional interview process, the outcome often hinged on specific performance metrics or alignment with management's expectations. Reflecting on the experience can provide insights into areas for improvement in future interviews.