Icertis logo

Icertis Architect Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 7 interview experiences · FREE TO READ

2.9 Rounds average
Difficult Typical difficulty
85.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Icertis.

Showing 3 of 7
Icertis logo
Icertis

Architect

Engineering · a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Technical Coding

I went through 2 interview rounds for a .Net Architect role. Both were deep dives into the .Net ecosystem and how different C# features are applied. I felt I did well in both, answering most questions. However, they ghosted me afterwards. Even after the first round, HR took 1.5 weeks to schedule the second. It's weird that my candidate portal still says I'm in the process, but HR isn't responding to my follow-ups. Very unprofessional. They should at least have the courtesy to let candidates know the outcome, whether it's a yes or no. They were unprofessional in their communication, even though rejections happen for many reasons. Seriously consider if you want to apply here, as your time and effort in interviews mean nothing to them.

Confirmed questions2 questions
  • Tell me about multi-threaded use cases within the .Net ecosystem.
  • How are C# features applied in real-world scenarios?
Icertis logo
Icertis

Architect

Engineering · a year ago

Senior Difficult Positive experience Accept offer 3 rounds
Interview process
Technical screen Technical screen Recruiter call
Interview formats
Technical Technical Behavioral

The whole thing had 3 stages. 2 technical and 1 HR. My interview experience with Icertis was awesome. The process was easy, well-planned, and structured, making it simple to keep focused and ready. From the first contact to the actual interviews, it felt like they respected my time and made me feel valued. The interview panel had smart and sharp people who were ready and paid attention. The questions were tough but made sense. It was clear the interviewers wanted to check my tech skills and also see how I solve problems and work with others. The interviewers took time to explain what they expected for the job and how it fits with what Icertis wants to do. I liked being able to talk about how I could help with important goals, which gave me a good sense of purpose and clarity. This made the job seem even better because I could see how my work would directly affect the company’s direction. Throughout the interview, I could feel Icertis’ commitment to its FORTE values—Fairness, Openness, Respect, Teamwork, and Execution. Talking about these values showed the company’s effort to build a helpful and inclusive work environment. This focus felt right to me, and I felt a real connection to the company’s values, making me more interested in joining.

Confirmed questions3 questions
  • Were there questions about Microservices design patterns and database performance optimization?
  • Did you get questions about designing for database performance?
  • Were there any design-related questions?
Icertis logo
Icertis

Architect

Engineering

Staff Difficult Positive experience Accept offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Technical System Design

This was a great experience interviewing with ICERTIS. There were 2 rounds in total. The first round was technical, involving hands-on design and coding problems. The interviewer was very helpful and gave me enough time to think before solving. The questions were relevant to the role's requirements. The second round was also conducted well, with the interviewer asking questions that covered all aspects of the role. The talent acquisition team was very cooperative and disciplined, and flexible with scheduling interviews and other discussions. Overall, the interview experience with ICERTIS was good.

Confirmed questions1 question
  • Design a system based on a given scenario to meet both functional and non-functional requirements.

Icertis Architect Interview Questions

Quoted word for word from Icertis interview reports.

Design a system based on a given scenario to meet both functional and non-functional requirements.

Read reports

Tell me about multi-threaded use cases within the .Net ecosystem.

Read reports

Were there questions about Microservices design patterns and database performance optimization?

Read report

Did you get questions about designing for database performance?

Read report

Formats, difficulty and experience

Across all 7 Icertis interview reports.

Interview formats

Technical 52.9%
Behavioral 23.5%
Coding 11.8%
System Design 11.8%

Interview difficulty

Easy 14.3%
Average 14.3%
Difficult 71.4%

Candidate experience

Negative 14.3%
Positive 85.7%