After applying, I went straight into two technical rounds that lasted about an hour each. They were with senior developers, and what stood out to me was that I never spoke with anyone from HR—no recruiter-style touchpoint at all during the interviews, which felt odd given how structured the process otherwise seemed.
In both sessions, I was able to answer almost all of the technical questions, and the second round’s questions felt very similar to the first. Midway through the process I didn’t feel like there was a mismatch, but then I received an email saying my skills didn’t align with what they needed. It left me genuinely confused, because if that conclusion had been true, it felt like they could have reached it after the first interview.
3 months ago
Easy Negative Indonesia
My interview started with a meeting that was supposed to cover background and architectural alignment, with the hiring manager and a senior software engineer on the call. I expected a proper walkthrough before any technical evaluation, and for a while it felt like it might get there.
But as I was explaining my engineering background, the hiring manager abruptly cut me off. They made an immediate assumption that my skill set wasn’t a fit for their web development needs and ended the meeting on the spot. There was no deeper screening, and no technical assessment at all—just a quick shutdown based on a snap judgment.
3 months ago
Average Positive Melbourne
My process began with a phone screening from HR. After that, I was given the chance to interview at their office, and the overall vibe felt friendly a…
11 months ago
Average Neutral Indonesia
My interview process leaned heavily on what they could confirm from my CV. A lot of the discussion felt like background checks, and the technical part…
11 months ago
Average Positive Hamilton, Waikato
The interview itself felt well-paced and the questions were the right length—not dragged out, but not skimmed either. Before the session, I used the j…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Stages
The interview process typically consists of multiple stages, starting with a phone screening, followed by technical interviews and behavioral assessments, often culminating in discussions with senior leaders. Candidates should be prepared for a structured pathway that includes both technical and soft skill evaluations.
Interviews often blend technical questions with behavioral inquiries, emphasizing candidates' past experiences and problem-solving approaches rather than purely technical challenges. Candidates should prepare to discuss their work history and how it relates to the role, using frameworks like STAR for behavioral questions.
Technical questionsBehavioral questionsSTAR
Communication & Follow-up
Several candidates reported issues with communication during the process, including delays in feedback and lack of clarity about next steps. It's advisable for candidates to follow up proactively if they experience long wait times or unclear communication.
Communication issuesFollow-upFeedback delays
Interview Tone & Environment
The overall tone of interviews can vary from formal to conversational, with many candidates noting a friendly and low-stress atmosphere. Candidates should be prepared for a mix of relaxed discussions and structured evaluations, which can help ease nerves.
ConversationalFriendly atmosphereLow-stress
Expectations on Fit & Culture
Interviews often focus on assessing cultural fit and alignment with company values, with questions about teamwork, motivations, and future ambitions. Candidates should be ready to articulate their personal values and how they align with the company's mission.
Cultural fitValues alignmentTeamwork
Technical Assessment Variability
The depth and focus of technical assessments can vary significantly, with some candidates experiencing light technical questions while others faced more rigorous evaluations. Candidates should prepare for both light and in-depth technical discussions based on the role's requirements.