I started with an HR screening that focused on my motivations and a quick overview of the company and the role. It also touched on compensation, and the tone felt smooth and conversational. A week later I moved into a technical interview with a hiring manager and a team member, where they probed my background by pulling specific points from my resume and asking about related training and certifications. The whole vibe stayed fairly collaborative—there was room to clarify questions, and the discussion stayed grounded in whether I had the basics to ramp up given the documentation and onboarding the company relies on.
After that first technical conversation, the process kept moving through additional rounds where the emphasis shifted a bit toward how I work through problems. I went through interviews that mixed technical themes with scenario-style prompts, and I felt the interviewers were mainly evaluating my problem-solving approach and my day-to-day working experience. Some sessions were pretty Java-and-framework specific, with questions spanning fundamentals like data structures and OOP concepts, plus APIs and typical service behavior. At times it was casual and high-level rather than a deep dive.
11 months ago
Average Positive Malaysia
My process started normally: I went through a few rounds, totaling about three interviews, and each one included multiple interviewers. Even though the overall difficulty sat around “average,” the sessions weren’t purely technical—they mixed in back-and-forth questions about my background along with questions tied to how I’d approach engineering work. I remember having to manage my explanations because they sometimes seemed annoyed by how long I talked, but I kept answering anyway.
One technical stage stood out because it focused on specific Java/JVM and backend development concepts, including how Spring Boot REST services work and the methods involved. There wasn’t any take-home component in my journey, so the coding pressure stayed inside the live interview format. The questions felt like they were trying to measure both my recall and my ability to walk through what I’d done before.
> 1 year
Average Positive Malaysia
I went through a slower, more drawn-out hiring flow that started with coding and then stretched into multiple waits. After applying in December, I eve…
> 1 year
Average Positive Manassas, VA
My journey started with an HR recruiter call that felt straightforward. The recruiter was friendly and welcoming, and the focus was on basic screening…
> 1 year
Difficult Neutral Kuala Lumpur
My interview experience included a noticeable technical-screen setup and then a more intense set of technical conversations. Before I got to the inter…
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 & Timeline
The interview process typically begins with an HR screening followed by multiple technical interviews, but candidates have reported varied timelines, with some experiencing long delays between stages, leading to frustration. Overall, the process can feel organized, but communication about next steps can be inconsistent.
HR screeningmultiple roundscommunication
Technical Interviews & Coding Assessment
Candidates face a mix of technical interviews that assess Java, backend development, and system fundamentals, often without a take-home component. The technical depth can vary, with some interviews focusing on problem-solving and real-time coding under pressure.
Javabackend developmentreal-time coding
Behavioral & Fit Questions
Initial conversations often emphasize fit and communication, with behavioral questions about past experiences and problem-solving approaches. Interviewers are generally described as supportive, fostering a collaborative environment, which can help candidates perform better.
Some candidates reported challenging experiences with panel interviews, where the structure felt uneven and questions were asked without much context. This can create a distracting environment that impacts performance, especially when multiple senior interviewers are involved.
The overall candidate experience is heavily influenced by the professionalism of the recruitment process, with some candidates noting that clear communication and timely feedback are crucial. Poor communication can lead to a negative impression, even if the technical interviews go well.
communicationprofessionalismcandidate experience
Difficulty Level & Candidate Preparedness
The difficulty of the interviews is generally described as average to above average, with candidates encouraged to prepare for both technical depth and the ability to articulate their thought processes clearly. Many candidates felt that their performance was as much about communication as it was about technical knowledge.
average difficultycommunication skillstechnical knowledge