
With over seven years of experience in software development, Jubin Patel is a seasoned Developer adept at crafting innovative solutions across diverse domains including e-commerce, healthcare, media, gaming, and fintech. His expertise spans front-end and back-end development, with a strong proficiency in technologies such as React.js, HTML5, CSS, D3,js, Angular.js, Node.js, Python, SQL, NoSQL and various cloud platforms. Jubin has a proven track record of delivering high-quality applications, having worked as a Senior Software Engineer at EPAM Systems and as a Freelancer with multiple startups. His hands-on experience in translating UI/UX designs into functional components, integrating authentication systems, and conducting rigorous testing and code reviews underscores his commitment to delivering robust and scalable solutions. Jubin's technical acumen, coupled with his passion for innovation, make him a valuable asset in the software development landscape
Contractor
Multiple StartupsSenior Software Engineer
EPAM SystemsSystem Engineer
Tata Consultancy Services
ReactJS
Node.js
AWS (Amazon Web Services)

Design pattern

Microservices

Javascript

SQL

NoSQL

API Design

Responsive Design

UI/UX Design
Figma

HTML/CSS

Python

PostgreSQL

MongoDB

Firestore

Github

Bitbucket

AWS

GCP
.png)
Heroku
.png)
Firebase

Elasticsearch

Microservices

Redux

D3.js

Express.js

Material UI

Ant Design

Jasmine

Karma

Jest
.png)
Jenkins

Mixpanel

Google Analytics

Auth0

Contentful CMS

RDS
Pyspark

Amazon SageMaker

Amazon RDS

React.js

Angular

GCP

Microservices

Redux

Material UI

Redux

Material UI
My name is Jupin Patel. I have over eight years of experience in software development. I have worked with various service-based companies like TCS and EPAM, as well as multiple startups such as Made by Hidden Infinity, Huddl, Quantenna AI, and Project Symantec Momentum. I have around eight years of experience working in React, Node.js, JavaScript, Angular, and Python. I have developed multiple front-end and full-stack applications. I started my journey as a developer with Tata Services in February 2016, where I worked with a client in healthcare and developed multiple marketing and internal applications for the client. After that, I worked as a freelancer with multiple startups, where I developed multiple e-commerce and Fintech applications for the client in React and Node.js with AWS, GCP, or Heroku hosting. After that, I worked full-time as a senior software engineer with EPAM Systems, where I worked with two major clients: the London Stock Exchange Group and Thomson Reuters. I worked on full-stack applications in Angular and React. Currently, I'm working with a startup called Projective Environmental, where I'm developing an AI-based product for the client in React to basically automate reports, phase 1, and nominal site assessment reports. They write in Word, and I'm developing a web application using Draft.js. Apart from React, Node.js, Angular, and Python, I also have experience working with technologies such as AWS, Google Cloud Platform, Heroku, Auth0 authentication, Cognito authentication, Google Analytics, SEO implementation in the application based on feedback given by the SEO executive, and Next.js, Express.js, and multiple other tools and technologies used by multiple clients. That's it regarding my experience.
Yes. So we should try to avoid using "important" because if we use "important," it will override all the styles that are returned after it if "important" is not used. So, basically, if you are implementing a color red important in a component class right now, so basically if you have any style series implemented after it will be color blue without "important." So, basically, that blue color will be overridden with red because we have returned "important" there. It's essential to use "important" as much as possible until and unless it's very necessary to do it. And even if we are implementing it, we should make sure that we try to do it at the component level. The smallest component level, like, if you're overriding, you should override it at, say, a button, not implement it in a global style because a global style will override everything if we are not using "important" in the application. So that has some of the things that you should avoid.