Does a front-end developer need to have a bunch of completed projects behind him?

Question

Layout

Actually the question is: does a front-end developer need to have a bunch of completed projects behind him in order to get to social security?

Those. will it be a BIG plus that I have, for example, 10 landing pages, instead of 5?

PS This question arose precisely because, according to the stories of teachers from courses on social security, they usually drive JS'u strongly.

Tell me from your experience please.

Answer 1

a bunch of made-up projects to get to social security?

If in a web studio - yes

Those. will it be a BIG plus that I have, for example, 10 landing pages, instead of 5?

If in a web studio - yes

from courses on social security usually drive on JS'u strongly.

Because a front-end developer is, in addition to layout, the ability to do complex things related to business logic, and not just a button to draw.
Your experience - do 1 large, complex project that will show your potential employer that you are not just a layout designer, but also an excellent specialist who understands architecture, OOP, and the ability to design complex UI systems.

Answer 2

Does a front-end developer need to have a bunch of completed projects behind him?

Preferably.

Those. will it be a BIG plus that I have, for example, 10 landing pages, instead of 5?

Will.

Tell me from your experience please.

Such an experience. A React developer came to our company who typeset on floats and it’s almost impossible to call that he knows how to do it right. There were a lot of bugs, he didn’t hear about adaptability at all. Therefore, in the project, when he was given a task to layout the components, he was a little confused.

Answer 3

The key components of a successful job search (if you are not a beginner):
- already existing work experience (the more the better)
- the number of different companies in which you have worked (preferably in a different direction)
- the so-called proven record of success, i.e. some portfolio of projects (preferably different ones), especially not ordinary websites, but more complex projects. Open-source projects of your authorship are also very suitable (if they have at least some value)
- your current and past title. From a junior they can easily be taken to a middle, but never to a senior.
- your education (both a diploma and various courses, books, etc.)
- your additional activities (such as mentoring, speaking at conferences, etc.)
If you are a beginner and have not had a job in your specialty before:
- You need to show as many projects as possible so that these projects can be credited for experience. To show that you already did this a year ago. The most important thing is to reach at least some experience. Without experience, they don’t take anywhere and don’t invite them to social services (since the same people without experience, 300 people respond to each vacancy of a junior)
- As much written code as possible (open source, github with experiments, etc.)
- As much as possible information about education and skills.
PS Try to do something other than landing pages. Landing pages are not a product at all, now you can make yourself a landing page in a bunch of designers without any knowledge of programming and layout.

Answer 4

Well, how are you going to learn practical life? What is stopping you from going to an interview and finding out for yourself, and not being heard by fools

Answer 5

Ceteris paribus, a larger number is a plus, but not a fundamental one.
I would look more at complexity and quality. That is, 3 good projects are better than 10 good projects.

Answer 6

A bunch of projects is good, especially if they are different. In my experience, everything should be shown. There was a case where I showed a bunch of projects, many good ones, and one very ancient, crooked, lurid, accidentally preserved in the portfolio, I wanted to remove it already, I was ashamed of it. So it was this that Mr. Mammoth hooked on the customer, he said - like this, let's work, make it to us in a similar style.