profile-pic
Vetted Talent

Mayur Panchal

Vetted Talent

I’m a Senior PHP Developer with 12+ years of experience building secure, scalable web applications using Laravel, CodeIgniter, and WordPress. Skilled in backend development, cloud architecture (AWS, Azure), CI/CD, and Linux server management. I’ve worked with global teams to deliver high-performing solutions across eCommerce, enterprise, and SaaS platforms.

  • Role

    Senior PHP Developer

  • Years of Experience

    13 years

  • Professional Portfolio

    View here

Skillsets

  • react
  • Linux server management
  • HTML/CSS
  • Docker
  • Azure Server
  • AWS
  • APIS
  • Radis
  • CodeIgniter
  • Agile frameworks
  • Responsive Web Design
  • MVC Framework
  • cloud architecture
  • Back-End Development
  • Laravel - 4 Years
  • E-Commerce
  • Jira
  • GitLab
  • Git - 6 Years
  • AJAX
  • JavaScript - 12 Years
  • jQuery
  • MySQL - 10 Years
  • PHP - 13 Years
  • Wordpress - 8 Years
  • Wordpress - 8 Years
  • Laravel - 4 Years

Vetted For

15Skills
  • Roles & Skills
  • Results
  • Details
  • icon-skill_image
    Full Stack Developer (Remote)AI Screening
  • 53%
    icon-arrow-down
  • Skills assessed :Babel, Jest, Mocha, CSS, Symfony, AWS, Git, HTML, JavaScript, MVC, MySQL, OOPs, PHP, SQL, webpack
  • Score: 48/90

Professional Summary

13Years
  • Feb, 2018 - Present8 yr

    Senior PHP Developer

    Flydocs india Pvt. Ltd.
  • Jun, 2015 - Jan, 20182 yr 7 months

    Senior PHP Developer

    ETRAFFIC
  • Feb, 2013 - May, 20152 yr 3 months

    PHP Developer

    Proacsys Technologies
  • Nov, 2011 - Jan, 20131 yr 2 months

    PHP Developer

    Sterling Softwares

Applications & Tools Known

  • icon-tool

    WordPress

  • icon-tool

    Opencart

  • icon-tool

    PHP

  • icon-tool

    XAMPP

  • icon-tool

    MySQL

  • icon-tool

    cPanel

  • icon-tool

    FTP server

  • icon-tool

    jQuery

  • icon-tool

    Git

  • icon-tool

    CSS3 & CSS5

  • icon-tool

    HTML5

  • icon-tool

    Javascript

  • icon-tool

    Ajax

  • icon-tool

    Laravel

  • icon-tool

    Jira

  • icon-tool

    Skype

  • icon-tool

    WampServer

  • icon-tool

    Google PageSpeed Insights

  • icon-tool

    Apache

  • icon-tool

    CodeIgniter

  • icon-tool

    FileZilla

  • icon-tool

    Azure

  • icon-tool

    AWS (Amazon Web Services)

  • icon-tool

    GitLab

  • icon-tool

    CI/CD

  • icon-tool

    GitHub

  • icon-tool

    Docker

  • icon-tool

    AWS

Work History

13Years

Senior PHP Developer

Flydocs india Pvt. Ltd.
Feb, 2018 - Present8 yr
    To manage the team and fix complex issues and ensure delivery timelines are met. Develop secure, scalable, and high-performance software products. Create CI/CD integration with the use of GitHub. Handles client communication to understand the requirements. Managing Linux server using command line functions.

Senior PHP Developer

ETRAFFIC
Jun, 2015 - Jan, 20182 yr 7 months
    Develop secure, scalable, and high-performance software products. Write well-designed, testable code. Resolve and troubleshoot code and software-related issues. Integrate software components into a fully functional software system.

PHP Developer

Proacsys Technologies
Feb, 2013 - May, 20152 yr 3 months
    Write well-designed, testable code. Resolve and troubleshoot code and software-related issues. Integrate software components into a fully functional software system.

PHP Developer

Sterling Softwares
Nov, 2011 - Jan, 20131 yr 2 months
    Write well-designed, testable code. Resolve and troubleshoot code and software-related issues. Integrate software components into a fully functional software system.

Major Projects

7Projects

Redhorseproducts

Retreat Caravans

Relationship Audits

Ridetek

All4silver

Netwireless

MyFlydocs

Education

  • B.E. Computer Science

    Gujarat University (2011)

AI-interview Questions & Answers

Yeah. My cell my mentor, and I have more than 13 years of Europe. Years of experience in PHP Laravel, JK, Ray, Symphony, codeigner, MySQL, JK, JavaScript as well as some other, tool like Jira gate, GitLab, JACD, That is,

Uh, yes. Regarding the user experience, uh, that how can we improve? That is the main thing is the we need to reduce the clicks so user can do the less click and, uh, give the all the functionality that we require. There should be a cover. And, uh, also, the regarding the performance wise, the we can use the, uh, some security layer, uh, like, uh, CSRF means token token, uh, security layer that we can use so that, uh, we can, um, better security for the code, and as well as the regarding the performance that we we can use the coding standard, uh, that we can use.

Yes. Regarding the, uh, automatic deployment approach regarding the AWS services. So, yeah, in this one, we can use the pipeline. CICD, uh, means, uh, continue integration and continue deployment. So with the use of the, um, Jira or Bitbucket, there is some other tool also. So with the use of the, uh, this tool, we can, um, we can, uh, upload, uh, into the server automatically. Before the upload, we can use, uh, error checking and some whatever we we need to do at before the upload that we can, uh, do. Yes.

Yes. Regarding the, uh, MVC architecture, the how can we handle the multiple user role and permission? So in this one, uh, we can give the, uh, check the permission, uh, before, uh, before we route any function in means controller file. So at that time, we can, first of all, check that, uh, this user has permission or not. If not, then we can, uh, redirect to, uh, error page or whatever page. So, uh, based on this one, at the starting of the, uh, controller file, we can check every time that this user has permission or not. So that is a, uh, best thing. And that means that we can use the one common function for this one and adding to the old dispatch that, uh, we can do. Uh, one another thing is if we want to check every time, then we can use token also. And, also, uh, we can use the, uh, constructor, uh, for this type of functionality that we need to check each and every function. So, uh, based on this one, we can check.

Okay. So regarding the optimized MySQL, so we can use, first of all, the, um, regarding the data type, whatever we use, there should be a proper. Means, uh, if we want to use the integer data and if we give the, uh, WellCare, that is not good. So if our, uh, data is, uh, small int, like, uh, tiny int, So we only use the tiny int data type, not integer. Yeah. So that is just one example. So another one is we can use the parameter at, uh, parameter is, uh, query. So, uh, this is the also the, uh, security purpose. And, uh, regarding the optimization, uh, we can use less condition and with uh, more joins that we, uh, we cannot, uh, less sub sub, uh, sub query. That is also one another one. So after that, um, our data is not redundant. Means, uh, every time, uh, he needs to go in one go and after that, he don't need to go multiple times through, uh, store into temporary tables. So that is, uh, we can optimize the MySQL database.

Okay. Uh, regarding the parallel recovery, uh, actually, uh, we can use regarding the, um, there are some backup, uh, front job we can add into the AWS. So that, uh, if any failure or something happened, then we can give it back to our, um, working code. That is one option. Yeah. And another one is, uh, we can find that, uh, why this error error recoveries, uh, happen. Yeah. So if is there any mistake in the code or any part of the process, then we can fix this out, uh, the proper solution. That is, uh, I am thinking.

Yes. Uh, in this one, first of all, the, uh, set retry function, this function is not exist. Actually, the function name should be a set price. So, uh, that is, uh, we can fix this, uh, bug.

Okay. Uh, in this function, the this is on a r e variable is only test for regular expression. Uh, and, uh, if we need to compare with the regular expression, then this is not proper syntax. We also need to add, um, like, we can use the re.rig.rig regular expression, I g a x. And after that, the, uh, function name, we can use. And, uh, okay. Sorry. Uh, the main issue yes. Uh, yes. That is, uh, that is the main issue that it is a regular expression. We you cannot direct a re.test. It should be a, uh, re., uh, re g expression means e x, something like syntax. So, uh, um, that is it should be. So that is the main, uh, correct answer.

Regarding the security in PHP application that, uh, first of all, the applicants should be a token based. So, uh, every time, every request should be checking a token. So that is the first one, like, a CSRF token we are using normally. So, uh, if outside of the any, um, any request are coming into the server, then, uh, we cannot go up there. So first one is this one and also the data protection. So we use the encryption method for, uh, data that, um, also, they use the parameter parameter right address, uh, string a query string. So, uh, all the database query, we can secure, protect our data that is, uh, from my side.

Regarding the session management. So, uh, when we use the any any variable that we need to get in in every page of, uh, request So we can use the session. Like, Sam, after the login, uh, we use the user ID every time or first name, last name, or email address. So at that time, we are using the session. And session is, uh, stored in, uh, database as well as the file also. Yeah. So, um, so that, uh, at that time, we are used to session.

Yes. Uh, regarding the if we use the React, uh, as a content, so that time, we can use the PSP back end. Uh, so, uh, at that time, we can use the token every time. So whenever the, uh, request coming from the react at that time, the token whatever token is sent, So at that time, we can check the token in PHP side. So after that, uh, we can know that the this request is proper or not. So, uh, that is, uh, we need to check.