Three candidate reports describe CEI's Software Engineer interviews: a written or aptitude screen, Java and OOP-focused technical rounds with SQL, and an HR or manager conversation. Two candidates got no offer and one did.
$90K
Avg. Base Comp
$110K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed for software engineering roles at CEI describe a screening-heavy process that starts with a written test before any conversation. Two of the three report a pen-and-paper first round. One described aptitude questions plus coding without an IDE. The other described a test that ran several hours, with 10 aptitude questions, 20 technical questions covering OS basics, time complexity and DBMS, and seven coding problems of which four had to be solved. Pseudocode or real code was acceptable. The third candidate described a moderate aptitude test.
The technical rounds centred on Java and object-oriented programming. Candidates also mention SQL queries and database definitions, and one cited database design and data structures. One was asked about college projects and the difference between a web application and a website. The candidate who received an offer said the questions were straightforward rather than LeetCode-hard, but interviewers pressed for hands-on detail on anything listed on the resume.
The last stage was an HR or manager conversation covering fit, communication and background. Round counts differ between reports (three or four), so expect some variation. Outcomes were mixed: two no-offer results, one of which mentioned SQL window functions and deeper OS topics as weak spots, and one offer. Practice writing code by hand, review Java OOP and core SQL, and prepare to explain your projects clearly.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Cei process.
I interviewed at CEI for a graduate engineering role back in 2024, and it turned out to be a multi-stage on-campus process. The first round was pen-and-paper, which included an aptitude section and a coding component. I remember being caught off guard by the low-tech format — no IDE, no compiler feedback, just me and my handwriting under time pressure. The aptitude questions tested problem-solving and logical reasoning, while the coding part covered algorithmic thinking. After that initial screening, I was invited to their Chennai campus for subsequent rounds. The second and third rounds were technical interviews focused on Java and object-oriented programming concepts, along with SQL queries and database definitions. The interviewers went deeper into OOP fundamentals and tested my ability to write efficient queries. There was also a general HR round mixed in to assess cultural fit and communication skills. Looking back, I think the main issue was that the entire process felt disconnected from real-world development — pen-and-paper coding doesn't translate well to how you actually write software. Their feedback to campus was that candidates lacked the necessary skill set, but I felt like the format itself didn't give us the best opportunity to demonstrate what we could actually do. Ultimately, no offers came from my cohort or from this process.
Prep tip from this candidate
If you interview at CEI, prepare for pen-and-paper coding by practicing algorithm problems offline without an IDE — focus on Java OOP concepts (inheritance, polymorphism, encapsulation) and SQL fundamentals like joins, aggregations, and basic query optimization before the technical rounds.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Cei
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Random SQL Sample | |
| Weighted Keys | |
| Flight Records | |
| Prime to N | |
| Largest Salary by Department | |
| Upsell Transactions | |
| Top 3 Users | |
| Raining in Seattle | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| First Touch Attribution | |
| Job Recommendation | |
| Over 100 Dollars | |
| Minimum Change | |
| Find the Missing Number | |
| Recurring Character |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an aptitude-based first round. Two describe a pen-and-paper format with a coding component, and one notes there was no IDE. One describes a test lasting several hours, with technical questions on OS, complexity and DBMS plus seven coding problems of which four were required. Another found the aptitude test moderate.
Candidates report technical rounds focused on Java and object-oriented concepts, with SQL queries and database definitions also mentioned. One was asked to explain programs and work through coding problems. The experiences differ on whether there were one or two technical rounds, so the exact count may vary.
Candidates describe interviewers probing college projects and listed skills. One was asked to explain a web application versus a website. The offer-receiving candidate said interviewers wanted hands-on detail on anything listed on the resume, so be ready to walk through your work.
The final stage is reported as an HR round on cultural fit and long-term aspirations, or a manager round mixing behavioral questions such as 'Tell me about yourself' with a few basic technical questions. One candidate describes it as more relaxed than the technical rounds.
