profile-pic
Vetted Talent

Vishal kumar

Vetted Talent
I am Software Engineer with professional experience of over 5+ years in building consumer focused online application, products, services and crm using PHP/Laravel, Python/Django. Developed well designed various processes, web application, third party integration and database structures. I have good work experience and I can thrive in working in fast paced, high tech environment with cross functional teams using agile methodology.
  • Role

    Software Developer

  • Years of Experience

    6 years

Skillsets

  • Generative AI
  • No-sql management
  • Cd-ci pipelines
  • unittest
  • Strapi cms
  • Wagtail
  • Graphene
  • LLM models
  • Open AI
  • S3
  • pytest
  • Jira
  • Jenkins
  • Hadoop
  • GraphQL
  • Python - 5 Years
  • ELK
  • EC2
  • DynamoDB
  • Docker-compose
  • AWS Lambda
  • API Gateway
  • SQL
  • Selenium
  • automation
  • Docker
  • PySpark
  • Agile
  • AWS - 4 Years
  • Python - 6 Years

Vetted For

11Skills
  • Roles & Skills
  • Results
  • Details
  • icon-skill_image
    Senior Backend Engineer - Python/Django (Remote)AI Screening
  • 63%
    icon-arrow-down
  • Skills assessed :experience working with clients outside India, Frontend technologies, react, API development, Distributed Systems, DRF, English, Django, GCP, Postgre SQL, Python
  • Score: 25/40

Professional Summary

6Years
  • Jan, 2022 - Present4 yr 4 months

    Software Developer

    Reckonsys Tech Labs
  • Aug, 2020 - Dec, 20211 yr 4 months

    Software Developer

    Peachmode
  • Aug, 2018 - Jul, 20201 yr 11 months

    Python/PySpark Developer

    Stemmons Business Services

Applications & Tools Known

  • icon-tool

    AWS

  • icon-tool

    Vue

  • icon-tool

    Shopify

  • icon-tool

    Stripe

  • icon-tool

    Flask

  • icon-tool

    AngularJS

  • icon-tool

    Requests

  • icon-tool

    Microservices

  • icon-tool

    Docker

  • icon-tool

    Docker-Compose

  • icon-tool

    GitHub Actions

  • icon-tool

    Jenkins

  • icon-tool

    Redis

  • icon-tool

    Elasticsearch

  • icon-tool

    Laravel

  • icon-tool

    Vue.js

  • icon-tool

    Pyspark

  • icon-tool

    Hadoop

  • icon-tool

    Selenium

  • icon-tool

    SVN

  • icon-tool

    Git

Work History

6Years

Software Developer

Reckonsys Tech Labs
Jan, 2022 - Present4 yr 4 months
    Developed a Full Stack deployment process through Docker and CI/CD pipelines. Led scalable backend design and entity relationship modeling. Created dynamic content websites with STRAPI and WagTail CMS. Resolved bugs using Agile methodologies, collaborated effectively, and maintained source control repositories.

Software Developer

Peachmode
Aug, 2020 - Dec, 20211 yr 4 months
    Managed backend infrastructure for Django product shopping website with Redis caching and Elasticsearch. Integrated payment gateways and logistics operations. Oversaw Laravel backend and Vue.js frontend systems. Developed Shopify API integrations for product websites.

Python/PySpark Developer

Stemmons Business Services
Aug, 2018 - Jul, 20201 yr 11 months
    Worked on Big Data processing and cloud computing. Built models using PySpark, Pandas, and Scikit-learn. Automated tasks with Selenium and implemented ETL processes on Hadoop. Maintained existing applications and version control repositories.

Achievements

  • Developed a Full Stack deployment procedure through the utilization of Docker, Docker-Compose, GitHub Actions, and Docker Hub.
  • Developed a dynamic content website for my recent company utilizing STRAPI CMS, showcasing proficiency in modern content management systems and web development technologies.

Major Projects

2Projects

Full Stack Deployment with Docker and Jenkins

    Developed a Full Stack deployment process using Docker, Docker-Compose, GitHub Actions, and Jenkins for an efficient CI/CD pipeline.

Dynamic Content Website with STRAPI CMS

    Developed a dynamic content website using STRAPI CMS, showcasing proficiency in modern web development and CMS technologies.

Education

  • B.Tech

    Maharishi Dayanand University (2018)
  • High School Diploma

    Kendriya Vidyalaya (2014)

Certifications

  • Social Network Analysis Using R - LinkedIn

  • Social network analysis using r

  • Machine learning engineer

  • Data science using python

  • A-z python for data science

AI-interview Questions & Answers

My name is Vishal Kumar. I was born and brought up in. I did my schooling from. During my schooling period, I participated in a lot of cultural and sports activities at traditional and national levels. Then I decided to pursue a BTech in computer science. So, I did my BTech from Maharishi Gyan University in Gurgaon with a decent CGPA. While I was in college, I interned at multiple startups, and I worked there as a Python developer. And after I completed my BTech, I started doing jobs in software solution companies. So, currently, I am holding 6 years of experience as a Python Django developer. Yeah. And my hobbies are to explore and travel, to explore and travel, food. Thank you.

JSON web tokens basically mean JSON web authentication token. So JSON web tokens are used to authenticate the front-end request, which are passed to the back end for any API to fetch the data. We provide a token to secure our back end with our JWT token. So that token, in every request, we need to send the JWT token to the back end to get the API response. This will create a secure layer for our APIs so that anyone cannot access all the APIs yet. And the endpoints we need to implement JWT are, like, first, we need to have an endpoint for creating a token. For creating a token, we can add that API in the login itself when the user creates a login and enters their username and password and logs in. We can issue an authentication token to them. Then we can use that authentication token to pass into all of the requests, and we can give them data. So one of the APIs to fetch a new token along with it, then we can have a verified token API. So it will verify all the tokens coming from the front end. And we can also set an expiration to our JWT token. Once the token is expired and the user's session is selected, then we can refresh the token and that will be the process. So these are three different kinds of API which we will need to implement the data portal.

Yes, select related and prefetch. These are Django ORM queries. So in select related, we can if you want to select a relational singular column, then we use select_related. We'll support like we have two models. 1 is an author model and one is a book model. So every book has an author. So if you want to select the books which have which author, then we can do books.objects.select_related() and then we can do author. So that will fetch us the author. And if you want to select the author's name, then we can do author__name. So that is the use of select_related. So in prefetch phase, we basically use this to refresh all the relational data which is present in that model object. So we will use prefetch_related to select all the relations without doing another query to fetch that relation. So these are the two concepts.

Yep. So view and model view user. All three things are used to write the views of Django. Views of Django, which are displayed on the web browser, means which is getting shown on the web browser. So in view, like, the major difference between view, user, and model user. It's in the model user. We will have the view related to the model itself. So the getting such fetching of the model record and the updating the model record and deleting from the model report. These are the credit of, yeah. Like, credit application which we can apply on a model object. So those functionalities will already be provided by the model user. So we can just directly name the function. Like, if we name the function get, set, then it will fetch out first the reports for us from the model itself. And you said we will have to define the model from which model it is related to. Or we can even skip doing that part for relating it to the model. We can directly write our custom new APIs where we can use any model in the custom view API. We can define the function and use the custom model, and that we can work on that. The custom view is basically it's just like a view set. Just that the definition, the syntax for writing the view and defining it in URLs is a little different, and we do have some less functionality.