Real, anonymous reports from people who interviewed for Software Engineer at Cei, newest first and distilled into what to expect across the loop.
I went through a fairly compact multi-round process that started with a paper-and-pen style aptitude + programming screen. It felt very MCQ-leaning and fundamentals-heavy: aptitude questions mixed with programming concepts like time complexity and OS topics, and then a set of coding questions where I had to attempt part of what was given (I was presented with seven programming questions but needed to solve four). The coding questions were written as algorithms/program logic prompts, and the overall structure was very “do what you can within the set.”
My interview journey was a campus-style process with multiple rounds that stayed in the same orbit of aptitude plus DSA-style coding. I started with a written test that mixed logical and technical MCQs and included SQL plus algorithm questions. Then I got a technical coding round where I had to choose to solve some of the provided prompts—sliding window, coin change, and a pattern-style problem were part of what I saw—and I was expected to complete enough questions to move forward.
The interview process typically begins with an aptitude test that combines logical reasoning and programming fundamentals, often in a multiple-choice format. Candidates should prepare for questions covering time complexity, operating systems, and basic algorithms.
Following the initial screening, candidates face multiple technical coding rounds focused on data structures and algorithms, where they must solve a set of programming problems. Expect to encounter questions that require practical problem-solving skills and a clear explanation of thought processes.
The final stages include HR interviews that assess cultural fit and communication skills, often tying back to technical discussions. Candidates should be prepared to discuss their experiences, reasoning, and how they approach problem-solving.
Interviews often delve into real-world applications of software development concepts, including discussions on SDLC/STLC and specific technologies relevant to the role. Candidates should be ready to discuss their practical experience and how it relates to the job description.
The overall interview process is structured and can feel intense, with candidates needing to perform consistently across various rounds. Candidates should be aware that the process may take longer than expected, with a focus on both technical and interpersonal skills.
Candidates reported a lack of clarity and delays in receiving feedback, which can be frustrating. It's important to remain patient and proactive in following up after interviews, as the timeline may not be as prompt as anticipated.