Answer the question
In order to leave comments, you need to log in
Is it normal for a backender jun to be asked to design a database?
At one of the vacancies, I saw that a junior was required to design a database, since at work he would be directly involved in this. And it would be okay if it was some kind of narrowly focused specialist, they also ask the backender to know half of the js frameworks. It seems to me, or in 1 case it is very self-confident - to allow a junior backender to design a database, and in the second case it is a trite attempt to find a specialist of all trades? (Do not hit for the question, I'm only at the beginning of the journey and do not quite understand if this is normal)
Answer the question
In order to leave comments, you need to log in
If you are only at the very beginning of the journey, and the only question that worries you at the same time is “do they want too much from me?”, then you will not go far along this path. In this profession, any experience is valuable. And the opportunity to gain additional knowledge is a plus for the vacancy, not a minus.
The essence of the profession of a programmer is that you are learning all the time. That is, any knowledge gained is not the top, but just another step. And it's just stupid to set some kind of framework - "we will teach this, and this is what they want a lot."
What does self-confidence have to do with it - it's not at all clear.
Of course, all the code of the junior will be code-reviewed, that is, no one will upload this database directly to production.
But at the same time, no one will create a simple database for him for a small service, such as product reviews: no one needs such a helpless jun. It is assumed that even at the training stage, he already did similar projects and knows how to design a database for them.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question