Real, anonymous reports from people who interviewed for Software Engineer at Sagitec Solutions, newest first and distilled into what to expect across the loop.
Get your personalized Sagitec Solutions Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My interview felt unusually calm compared to what I expected. The questions were mostly common, and I ended up answering around ninety to ninety-five percent correctly. Even with that, I didn’t get clear feedback afterward, which honestly made the whole thing feel a bit strange.
The process itself started with a test screen—MCQs covering basic .NET and OOP topics like CLR and CTS, plus general OOP concepts. After the test, the technical discussion went into OOP in more detail, along with C# and ASP.NET basics, and then SQL topics showed up as well, including things like joins and even elements such as cursors. There was also direct coding-style checking where they asked me to work through small pieces rather than just talk theory.
> 1 year
Average Positive Pune
After a recruiter-style call through a consultancy, I was scheduled for interviews in a pretty straightforward order. First came a test covering aptitude, then a technical round centered on OOP fundamentals and the way I think through them at an application level. The OOP questions pulled at concepts like inheritance and its types, plus polymorphism, encapsulation, and basics around OOP interfaces, and I also had to answer SQL questions about things like data types and how joins and subqueries work.
What surprised me most was how coding showed up as a practical check rather than only theory. I remember being asked to reverse a string without using a built-in string method, and there were also scenario-based questions mixed into the technical discussion. Overall, it felt like they were measuring whether I could connect the fundamentals to small, concrete tasks.
> 1 year
Average Neutral Pune
I went through a longer campus-style journey that started with a written test. The test mixed aptitude with OOP, and I remember it covering both core …
> 1 year
Easy Neutral India
My process had a steady rhythm that made it feel structured, even though it still required me to be on top of basics. It started with an aptitude scre…
> 1 year
Average Neutral New Delhi
I only had a single technical interview round, and it moved incredibly fast. The interviewer asked just a small set of questions—around five—and I did…
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
Technical Screening
Most candidates begin with a technical screening that includes multiple-choice questions on OOP concepts and SQL fundamentals, often focusing on topics like inheritance, polymorphism, and joins. Candidates should prepare for both theoretical questions and practical coding challenges.
OOPSQLMCQs
Hands-On Coding Assessment
Interviews typically include hands-on coding assessments where candidates are asked to solve problems or explain code outputs, emphasizing practical application of OOP principles and SQL queries. Being able to articulate thought processes during coding is crucial.
CodingPractical AssessmentOOP
Behavioral & HR Discussions
The final HR round often involves discussions about background and experience, but many candidates report a lack of clarity regarding feedback and outcomes, which can lead to confusion and disappointment. Candidates should be prepared to discuss their projects in detail.
HRFeedbackProject Discussion
Overall Process Experience
Candidates describe the interview process as structured yet lengthy, with some experiencing significant waiting times between rounds. It is important to stay patient and maintain focus on core technical skills throughout the process.
Process LengthStructurePatience
Compensation Discussions
Compensation discussions often occur late in the process, and candidates have noted discrepancies between initial offers and final discussions, leading to frustration. Being prepared for negotiation and understanding the company's compensation philosophy is advisable.
CompensationNegotiationExpectations
Candidate Reflections
Many candidates expressed a desire for clearer feedback and a more respectful use of their time throughout the interview process. Preparing questions to ask about feedback and the next steps can help mitigate this issue.