Ashish Mishra

Yes, my name is Mishra. Currently, I'm working as a back-end developer for the past 2.2 years. And I mainly work on the Express framework, and I've worked with databases such as MySQL and PostgreSQL. I have implemented various third-party APIs like Azure integration, RADIUS integration, and Stripe integration. And I have worked on mostly social e-commerce websites. I mostly work on social e-commerce websites and get web applications.

If I got the chance to accelerate myself in this job opportunity and I am very good at handling and maintaining the code. And I'm also comfortable with the company's requirements. And if the company gives me any task, then I'm the person who can do very well with it.

First for building any API, we need to understand the requirements of an API. Like, suppose if we are building a sign-up API or a log-in API, then we have to understand the fields which are required for sign-up and the fields which are required for log-in. We have to understand the flow of the API, then we have to see how the data will flow and what the request cycle and response cycle will be. So, according to that, we will build the API.

There are various ways of creating a server and databases for functionality and application, like I have mainly worked on MongoDB. In MongoDB, we have a package called Mongoose and we use that Mongoose for the database connection and for the server connection on the local machine, we use the localhost or like local host or port 8080 or anything we want. So that's how we connect the server and database for functionality in an application.

Well, as you know, user interface is an important part in any web application where users can interact with the website. So, designing user interaction on a web page is quite a big task and it should be user-friendly. Like, it should be smooth and the data should flow from one place to another within the application very smoothly. So I mainly used React and re-adjusted HTML, CSS, and JavaScript for building a user-friendly interface.

I don't have any knowledge about enterprise standards for a software application. The standards and how I ensured compliance are not known to me. I don't have any experience in this. Like, for a software application, what are the standards and how did you ensure compliance? Like, it's different on a project requirement. Like, if we are supposedly using a payment integration. So, there are various methods for the remaining integration in our application and we can use Razor Pay and Stripe integration and all the other things, but it depends on how long our website is and how many modules are there in our website? So, if you asked me, then I would go for a Stripe integration because it is easier to build and it is easy to integrate in the web application. And their documentation is quite easy. And then it is one of the standard options which we can use for the payment integration.

In React JS, we mostly use functional based components and class based components. For the implementation of handling design, we mostly depend on the GXS. For designing, we have it's dependent on our folder structure and our project structure use, like, for a login or for us, use screen sessions should be a different folder. And for authenticating the users and for payment should be a different folder. This is how we should design the UI. For React and it should be synced with the data because as you know in real data is all about the state. So, the implementation of you is mainly dependent on the sync and synchronization with the data.

No, I've never used Jenkins integration for continuously living our past projects. I've never worked on Jenkins.

I've never worked on Kubernetes and Docker, but I've heard about Docker and Kubernetes. Docker and Kubernetes are basically used for microservices. I'm currently working on a social e-commerce platform. They're planning to move that application onto a microservices architecture, so we can use Docker and Kubernetes to build our application on a microservices architecture where Docker and Kubernetes are used.

We have to design an application that uses APIs to meet both consumer and technical needs. I'm not familiar with this topic, so I don't have any knowledge on it.

As a team, we have to work with each other. It's good to have a strong sense of ownership with teamwork. Like, I have to know my part in the company, what tasks they're given to me, and what are the deadlines they're given to me. So I have to start with all that scenario and try to deliver that task or project as required by teamwork, and deliver that project on time. I should write the code in a more proficient and efficient way.