Rahul Senapati

Thank you for allowing me to have an interview in a particular domain. I'm glad to have applied for this position. My name is Rahul Shrikant Sanapati, and I have a result-driven 10-year experience in the dot net platform. I have worked on several technical skills, including dotnetcore, which is the latest version, asp.netmvc, asp.net, all platform technology, c sharp, and vb.net as programming languages, as well as a database, and Oracle. In my entire 10-year experience, I have a vivid domain knowledge. Now you can say that I have expertise in banking, finance, health care, insurance, and I also worked in the oil and gas sector. The second most advantageous thing I have experienced is that in my previous organization, I had to develop a software from scratch. So, I had to put myself into different roles to develop a software from scratch. This means I had to do analysis, customer acquisition, discuss with the business team for functionality, develop documentation, decide on the approach in the hybrid model, do development, do testing, act as a project manager while discussing with the business team, and then deploy in the solution environment. So, I've been into each role to do that particular task. Now, coming to the technology I have been working on, which I have already mentioned, I have worked on software like entity framework. I have worked on DevOps for CICD pipeline in Azure as well as GitHub. I also work with Azure Cloud, such as Azure functions, Azure services, logic app, and Azure Redis app for catching purposes for high-intense application purposes. That's all I have to say. Now, in terms of having domain knowledge, you can review my profile so that you can get a better understanding of it. And that's all from my side today. Thank you.

What I've been following are some practices when they're looking at a particular architecture. So while considering this particular question, I have to understand the particular architecture, the concern behind that particular web development, what it would be. First, we need to understand the architecture. So when we have a framework, the documentation part or any kind of change because we need to understand the architecture even in high-intensity applications, even in any kind of architecture, performance is a concern. Then we need to understand that we're using a high-level design format. Then we need to break it into a low-level design format where we need to see how we can fix it or how we can draw it in terms of having it into a design pattern or with the help of including a solid principle in it. So these are the particular areas that we need to focus on to check if everything seems lengthy and resilient in terms of having or creating a good architecture software. If we follow this certain kind of thing, then we are good to go, and we don't have a long backend error for a long duration if we follow this kind of strategy.

That would be a concern. Now that would be a good question to ask on this board for a project failure. That might be a question where you have done certain things in terms of your deployment or in terms of a certain functionality which you are not withdrawing or which is not up to the expectations that they have been drawn. In that, we have to know that certain recurring thing won't happen again once we have learned from it or kept in mind. And that's the thing that we need to check on. So we need to have a weekly or monthly review for this failure account, as when you say, we need to be having a weekly or monthly review so that everything is in line with the project purpose and for the tracking purposes, so that the majority of your project failure concerns would get removed.

Now the coming point, your question for this is the accuracy and reliability of data analyzers. 1st, we need to think about how you approach the data. Now the data would be in the form of an Excel sheet, data in JSON format, and data in text format. We need to understand how the data is approached and how you analyze the data and how the data should be more flexible in your architecture level than we drive the software component. So you need to be aware of everything when you validate your accuracy. Now, data accuracy, when I say that it can't be achieved in a standard single day. It means that it has to mature over time, and it means that you need to do more and more testing and more business-driven approaches into it so that your software's data accuracy will be scaled upon.

Have you worked with Weave API? These are template and discovery in building web page. Yeah. Good. Web API is mainly used for an application interface for service-based content when you totally depend on fetching the database on the server-side. So, it is an interaction between your application and your software concern. Now, the software concern may be the API; it's an application programming interface that can drive in three areas, which are now five, but it is mainly in three areas: web, Windows, mobile, IoT, and cloud-based applications. So, these are the five areas that you have worked in. And when you say about Razor template, Razor template is mainly used. It's like a higher version of HTML content. Or, you can say it's dynamic content generation where you can drive your code multiple labels, for example, in Excel. You have to write your HTML content, and you can inherit JavaScript or jQuery packages. At the same time, you have been using your runtime C# or.NET code when you will use the template with Razor. Now, coming to your Web API point, Web API is a vivid concept where you can have your REST architecture principles that you have to take care of while developing your REST API while building a Web API application. Now, there are many tools out there that make you more robust and scalable to do it. So, it is totally up to you how you develop based on your business functionality, but this is the current scenario that you have to be involved in with your Web API.

So how will we proceed if we can pause it, we're going to use it for the I'm sorry. Hold on. Okay. Now, coming back to your point on delegates and events. So, delegates is mainly used as a pointer-based function when you have to generate a value multiple times within the same object or same return type. And let's take an example: you have an addition or a subtraction. So, you have to call a particular class method into your delegate property instead of calling a method, so that your runtime environment can output multiple values. This can be achieved with the help of an event. So, events will use to notify that which particular action has to be performed, and that particular action is performed with the help of delegates. So, it's like a handshake between events and delegates. Now, a real-time example when you say, in terms of the banking and finance sector, when you have a lump sum calculator. When I say a lump sum calculator, it means a mutual fund, then you have to perform certain operations to check a particular stock or a particular mutual fund for a 5 to 10 year perspective. In that particular 5 to 10 year period, when you generate the sequence of your deposited money or you're investing your money, then you will perform this kind of event or delegate. So, I've been using delegates in the banking and finance sector. Now, coming to the point of your interface override, it is a subclass of an interface. So, an abstract class is like a concrete class, and an interface is mainly used to declare methods in the inherited class. So, we mostly use inheritance, which is morally, compliant with the SOLID principle. Now, coming back to your garbage collection. So, basically, we need to create a software that utilizes more memory management or garbage collection. So, in respect to your software location, if your architecture is not good, your memory management will not be effective, which will consume more and more memory on your server level, making you hang at certain point of time. Your application will not be able to perform more scalably and more robustly. So, garbage collection is used when we have to provide for any kind of connection that we need to use, and we need to withdraw that connection itself or certain objects' variables where we won't be able to accept more and more for that. Then we can release that particular object to make the architecture clear of your garbage collection.

When would you choose an abstract class containing a usable piece of code? Explain the pros of this study, and how to extract your code. So, basically, an abstract class is mainly used to act like a concrete class. It is mainly used when you have a design pattern. So, when you're developing in any kind of software, you have to implement it in the form of if you have a product-level application or an ecommerce-level application. So, at that point, at that particular point of time, you can use an abstract class where you can define a Surtitle method within your class, or you have to define that particular method, or you can define it in the inherited class. And that's a particular approach is where you can use an abstract class. So, that would be more advisable. So, coming back to your point, in terms of reality, when you use that particular approach, you can use it in terms of an ecommerce application as the 1st advantage, or any kind of financial-based application you can do. So, this would be the approach for the usability of your code.

It's like a situation when you take the initiative to solve a problem, but basically, take responsibility. What was the result? Okay. So there might be a situation. Like, when you say the dotnet platform in the dotnet platform, you might get multiple errors at a certain point in time when you develop certain functionality that never works, or the functionality approach may not extend to that particular required network. You mean to say that at that point in time, we need to take that approach. We need to take the initiative to see how the approach would be. Now even if it's an application concern, so we need to retest that for the application even in the UAT session or any pre-production session to check if the application is giving errors in the live environment so that we can replicate the same if we need to check. The second thing is if it's at the database level, then we need to replicate the same thing. We need to check. And the third thing is we need to check the network connectivity itself because if that's the case, it might also create an issue when there's high traffic on the application and you're able to see it. When you see that the application reaches a certain point, then we need to see how we can configure and how we can avoid that type of error in that particular note.

So what is the difference between view function and stored procedure? Okay. So view is like a dynamic view is like a constant data. Data that can be updated or it's for a temporary basis or you can say you can modify view every day to day or every month to month basis. That is a view. It's a starting data. You can say, in spite of creating a heavy reliance on main table. A function is nothing but a small piece of code that can be executed. In a real-time environment, when I say function, you can use a small code that calculates any particular business logic. That's a function. A stored procedure is nothing but a series of executable statements. You can drive a heavy, intense statement in terms of stored procedure. However, only selects are allowed in a function. But in a stored procedure, you can write data manipulation language kind of queries. And stored procedure is mainly used for high-intensity applications. That's what I have been told earlier also.