profile-pic
Vetted Talent

Vaibhav Patel

Vetted Talent
Dynamic and results-driven frontend engineer with over 8 years of experience in software development, seeking to drive innovation and deliver exceptional results in your organization.
  • Role

    Principle Full-stack Engineer

  • Years of Experience

    8 years

Skillsets

  • MongoDB
  • Zero chain
  • Dall-e apis
  • Gpt 4 apis
  • TypeScript
  • Solidity
  • PostCSS
  • OpenAI
  • Node.js
  • Next.js
  • Bootstrap
  • HTML5
  • Custom llm models
  • CSS
  • Performance Optimization
  • react - 7 Years
  • Responsive Design
  • Git
  • SQL - 8 Years
  • JavaScript - 8 Years

Vetted For

15Skills
  • Roles & Skills
  • Results
  • Details
  • icon-skill_image
    Senior Frontend Engineer - React, React Native (Remote)AI Screening
  • 78%
    icon-arrow-down
  • Skills assessed :DRF, handling images, handling videos, media-rich applications, uploading compressing videos, Component Lifecycle, ES6 syntax, Next Js, react, Routing, State management, Django, Python, React Native, Type Script
  • Score: 39/50

Professional Summary

8Years
  • Oct, 2022 - Jan, 20241 yr 3 months

    Principle Full-stack Engineer

    Atlus Cloud
  • Oct, 2018 - Sep, 20223 yr 11 months

    Senior Full-stack Engineer

    Hammr

Applications & Tools Known

  • icon-tool

    React

  • icon-tool

    Sass

  • icon-tool

    Git

Work History

8Years

Principle Full-stack Engineer

Atlus Cloud
Oct, 2022 - Jan, 20241 yr 3 months
    Led the development team in architecting and implementing the Atlus platform, utilizing React, React Native, and Solidity + Zero Chain technologies. Collaborated closely with stakeholders to gather requirements, define project scope, and establish milestones for successful project delivery. Designed and developed user-friendly interfaces and features to enhance the usability and functionality of the Atlus platform. Implemented robust data storage and retrieval mechanisms using Solidity and Zero Chain to ensure data security and integrity. Conducted thorough testing and debugging to identify and resolve any issues or bugs in the Atlus application, ensuring a seamless user experience. Provided technical guidance and support to team members, fostering a collaborative and productive work environment. Regularly communicated project updates and progress to stakeholders, addressing any concerns and ensuring alignment with project goals and objectives.

Senior Full-stack Engineer

Hammr
Oct, 2018 - Sep, 20223 yr 11 months
    Joined the development team in crafting and deploying the Hammr platform, leveraging React, Next.js, and Node.js technologies. Collaborated extensively with construction industry professionals to grasp their workflows and needs, ensuring Hammr's alignment with industry requirements. Designed and implemented intuitive interfaces and functionalities to simplify project planning, scheduling, budgeting, and communication processes. Established robust backend systems using Node.js to manage data, user authentication, and authorization within Hammr. Conducted comprehensive testing and debugging to ensure Hammr's stability and reliability, promptly addressing any encountered issues or bugs. Offered hands-on technical assistance and training to users, enabling them to effectively utilize Hammr for streamlined project management. Worked in tandem with AWS specialists to optimize Hammr's hosting infrastructure and security protocols, safeguarding project data integrity. Maintained transparent communication channels with stakeholders, providing regular updates and incorporating feedback to align project objectives with expectations.

Achievements

  • Collaborating with startups backed by Y Combinator to refine adaptability and innovation skills
  • Worked on more than 25 enterprise-level projects across various industries and domains
  • Top-rated plus developer on Upwork

Major Projects

2Projects

Atlus Cloud

Oct, 2022 - Present3 yr 1 month
    Led the development team in architecting and implementing the Atlus platform utilizing React, React Native, and Solidity + Zero Chain technologies.

Hammr

Oct, 2018 - Sep, 20223 yr 11 months
    Joined the development team in crafting and deploying the Hammr platform, leveraging React, Next.js, and Node.js technologies.

Education

  • Master of Computer Applications | MSCIT

    Uka Tarsadia University (2014)

AI-interview Questions & Answers

Yeah. So I'm Webo Patel, and, uh, since 8 year, I have worked as a JavaScript developer. I have a meta certified developer. So during that, uh, the development time, I worked with the many framework related JavaScript like React JS, Node JS, React Native, Vue JS. Computer React, uh, JS. I have worked with the many libraries like, uh, reductoolkit, real query. I know about the component library. I have worked with the, uh, many component libraries like Intelli, Material UI, Chakra, all those things. I know about the, uh, testing, like, end to end and end to end testing as well as the soft testing. So I know about the library that we have used, like React testing tool, uh, JS and some other thing. I have worked with the many enterprise client as well as the start up, so I know about how we can communicate with the team in a remote area. I also, uh, lead junior developers during the development time. I know about the agile process. I know about how we can work with the scrum, how we can assign tasks to QA as well as the back end guy. I know about how we can communicate between the, uh, like, QA, the back end guy, the scrum master, all those things. So I try to do a they want development. So I I I have knowledge about how we can communicate with the the PM and the QA, the back end guy. So most of the thing is, uh, the communication is a major thing on a remote area. So I know about all those thing and all about how we can work with the remote team.

Can you discuss the use of tools such as React Native Debugger to optimize performance in a React Native app. Okay. So using a tool like, uh, React Native Debugger can, uh, significantly enhance perform performance optimization in a React Native applications by enabling the effective tracking. So state change and action. Implicitty called the component hierarchy, monitoring network request. The capabilities of allowing the developer to identify, uh, bottleneck, uh, thing, improve app responsiveness, and, uh, streamline debugging process. So all those things, uh, we need to do for optimizing the performance of the React Native app. So the like, uh, unnecessary state change, unnecessary action calling, the component hierarchy, like, what, how we can, uh, define our component structure and all those thing on a particular, uh, seen that having a effect on the, uh, in our application. So using a native debugger, we have utilized that thing and enhance our performance.

So here is the one function for the calculate the bill amount. So there is, uh, several parameters like a person one amount, person two amount, person three amount, uh, text percentage, and a tip. So instead of first of all, the naming conversion was not, uh, good for that. Suppose we have, uh, calculate the total bills, the function names would be calculate total bill. In that, there is a several, uh, parameter was passed, so the person there is a, like, a manually defined, like, person 1, person 2, person 3. Instead of that, we need to pass as a error like a person 1, person 2, person 3. So if we use a error that time, uh, it's working for the infinite person. So we have passed a person amount in the error. The text person, the anti it's okay. In the next line, we have some of the all persons. So here, instead of the calculating the, uh, separate variable, we sum to we have sum all 3 person, and edit the text for all those. So instead of the we have using again, calculate the amount of the all those first person, we have used some of the calculation and then applied the purse, uh, tax for a certain day. After that, we have add some tip on, uh, the finalized amount and return it. That's it.

Explain a sync storage in React Native and also define when to use it and when to not. So when we talk about the sync storage in React Native, is a pattern for managing and catching app data efficiency. So so for that, we have used a library like a sync storage for React Native. For the storage optimized. So use it So use it when we need to, uh, purchase data across the session, like, uh, user preference or offline access. All those things, we need to store the same storage. And, uh, when we need to use, like, avoid it for sensitive data without uh, encryption or high high security recommended data. So when we use any, uh, like, uh, purchase data across the session, we have used a sync storage, but avoiding to store a sensitive data like a user information, the password thing, and all those thing. That data was not encrypted that we need to avoid to store in a a sync storage.

What is fraud dealing, and how can we avoid it. So when we talk about the props dealing, it's it's a thing that we have passed, uh, our props from parent to the children. So if we have used to the some value to the children that we have, uh, passed the value in a props. Suppose there is a child component, there's a parent component that having the child component, there is this there is a one, uh, sub child component. So if you pass data from parent to the sub child, we have to pass to the children. The children have passed their data to the sub child. So when we talking about the props drilling, we have used, uh, contact API as well as the Redux for passing the value from prop. If you're having a same structure on a hierarchy, we have used a context API. So in a parent component, we have set some value in a context and, uh, that's, uh, purchase the data in a context. In the child component, we we purchase that data using a context. So we get, uh, data from directly from the parents to the sub children using a context. Other than we have used, uh, other than we have used, uh, like, Redux for managing, uh, data from parent to the so we when we send any data to the parents, it says it will allow him to the get the data using a user selector on a child component. So that thing we have used for, uh, avoiding the props dealing.