Saviant Consulting Interview Process - Mid-level Fullstack Engineer

I interviewed for a .NET Full Stack Developer role. The interviews were more focused on practical knowledge and real-world scenarios rather than just theoretical questions.

I received a call from the recruiter and after discussing my experience, current role, and technology stack, the interview process started.

1st round: Initial HR/recruiter discussion

The first discussion was a behavioral call with the recruiter. They asked about my overall experience, current project, technical skills, notice period, and salary expectations. They also explained the role and the interview process.

Nothing too complicated in this round. Just be clear about your experience, current responsibilities, and the technologies you have worked with.

2nd round: Technical interview

This was the most interesting part of the process. The questions were mostly based on my current and previous projects, along with some in-depth technical concepts.

The interviewer wanted to understand how well I knew the systems I had worked on and whether I could explain the technical decisions behind them.

Some of the areas discussed were

• Project architecture and how different components communicate.

• How does your application handle increasing traffic?

• How would you handle thousands of concurrent requests?

• What is a circuit breaker, and where would you use it?

• How do you handle failures when a downstream service is unavailable?

• Difference between retries, timeouts, and circuit breakers.

• How do you identify and resolve API performance issues?

• Database optimization, indexing, and handling large datasets.

• .NET concepts like dependency injection, async/await, middleware, and exception handling.

The questions were not limited to definitions. For example, if you know what a circuit breaker is, you should also be able to explain why it is needed, how it works, and how you would implement it in a real project.

I would suggest preparing your current project thoroughly. Be ready to explain the architecture, request flow, challenges you faced, and the solutions you implemented. You may get multiple follow-up questions based on a single answer.

3rd round: HR/cultural fit

This round was more about your working style, ownership, and how you approach problems.

One thing I found interesting about Saviant was its independent working culture. There isn't much emphasis on senior or junior designations. The expectation is that everyone takes ownership of their work, makes decisions, and contributes to solving problems rather than always depending on someone else.

Some of the discussion areas included

• How do you handle a task when requirements are unclear?

• What do you do when you get stuck on a technical problem?

• How comfortable are you working independently?

• How do you approach learning a new technology?

• Have you ever taken initiative beyond your assigned responsibilities?

• How do you handle disagreements within a team?

My suggestion would be to prepare a few real examples from your experience where you took ownership, solved a challenging problem, or proactively suggested a better approach.

Preparation Tips

A few things I would recommend to anyone preparing for Saviant:

1. Know your project well. Don't just explain what you developed. Understand the architecture, traffic handling, database interactions, integrations, and possible bottlenecks.

2. Focus on practical concepts. Revise topics like circuit breakers, caching, load balancing, scalability, async programming, and database optimization.

3. Prepare scenario-based questions. Think about what happens when an API fails, the database becomes unavailable, traffic increases, or a service takes too long to respond.

4. Understand the why behind your implementation. Be prepared to explain why you chose a particular approach and what alternatives you considered.

5. Show ownership. They seem to value people who can work independently, take initiative, and drive tasks to completion.

Overall Experience

Overall, I found the interview process practical and engaging. The focus was more on how you apply your knowledge in real projects than on how many theoretical concepts you can remember.

Final Outcome

I received an offer from Saviant Consulting after successfully completing the interview process. Overall, it was a good experience, and I enjoyed the practical discussions.