Real, anonymous reports from people who interviewed for Software Engineer at GEP, newest first and distilled into what to expect across the loop.
I went through a fairly standard multi-round software engineering loop with one elimination-style OA, two technical rounds, and a final HR, and I felt the difficulty was mostly medium overall.
I experienced an average-difficulty process that leaned heavily toward hands-on problem solving plus deeper discussion of my background.
The interview process typically consists of an online assessment followed by multiple technical rounds and an HR discussion, often completed in a single day or over two days. The overall timeline can vary, with some candidates experiencing quick decisions while others face longer waits.
Candidates can expect two or more technical interviews focusing on coding, data structures, algorithms, and sometimes SQL or system design, with difficulty levels ranging from basic to challenging. The second technical round is often considered a critical screening stage.
HR rounds typically emphasize fit and alignment with company values, often involving discussions about past experiences and managerial-style questions. Candidates should be prepared to articulate their project experiences clearly.
Expectations for technical knowledge can be high, particularly in areas like SQL, .NET, and front-end frameworks such as Angular. Candidates should be ready for in-depth discussions and practical problem-solving related to their technical skills.
The initial coding assessments may include basic algorithm questions and data structure problems, with some candidates reporting a mix of easier and more complex tasks. Success in these rounds often hinges on clear coding logic and problem-solving skills.
Many candidates noted the importance of preparing for edge cases in SQL and being ready to discuss their project work in detail. Strengthening fundamentals and practicing coding under pressure were common recommendations.
