Real, anonymous reports from people who interviewed for Software Engineer at Exela Technologies, newest first and distilled into what to expect across the loop.
My process felt like a classic recruiter-to-tech pipeline that stretched across multiple steps. After applying through an online portal, I first had an assessment, then I cleared a technical test and moved into a telephonic interview. When that went well, I got another virtual technical interview with a technical interviewer before eventually reaching HR.
I went through a fairly straightforward, tech-heavy flow that started with a mix of fundamentals and day-to-day development topics. After an initial screening, I was brought into rounds where the focus was C# and ASP.NET with MVC, plus SQL basics like CRUD. I remember being asked about stored procedures and functions, and there was also a clear emphasis on LINQ concepts (including things around dictionaries/hash tables and error handling). The technical questions also touched on more practical topics like garbage collection and how to think about performance (“fine tuning” came up), and the conversation drifted into design patterns.
The interview process typically involves multiple rounds, starting with an initial screening, followed by two technical rounds, and concluding with HR discussions. Candidates should expect a blend of virtual and possibly face-to-face interactions throughout the stages.
Candidates will face technical interviews focused on practical problem-solving, OOP concepts, and specific technologies like C#, ASP.NET, and the MEAN stack. Expect to write code on the spot and discuss real-world applications rather than just theoretical knowledge.
The final stages often include discussions about team fit and personal experiences, moving away from technical depth. Candidates should be prepared to articulate their past experiences and how they align with the company's culture.
HR interactions can be challenging, particularly regarding salary expectations, which may not align with technical performance assessments. Candidates should be prepared for potential inconsistencies and unclear timelines during this phase.
The atmosphere can vary significantly, with some candidates reporting welcoming environments while others experienced one-directional interviews that felt scripted. It's important to gauge the dynamic and adapt accordingly.
Candidates should focus on a wide range of technical topics, including OOP principles, SQL basics, and performance considerations, as well as being ready to discuss their resume in detail. A solid grasp of these areas can help build confidence during the interviews.