I think being dismissed shouldn't be a bench-mark for determining whether or not software engineering is for you.
The only benchmark should be whether or not you like software engineering and to really arrive at an answer, you should work in the industry for a few years, ideally 3 or 4.
I have been an engineer for 3.5 years now and I think I like it, which is why I continue to be in the industry. The day I don't enjoy doing it, that's the day I'll call it quits and figure another line of business out. :)
Being rejected is normal, maybe you are to slow I am in no position to judge, but maybe they just didn't understand what a junior without 5 years of practical experience is. Even a senior can slow down by lacking domain knowledge or missing knowledge of a particular framework.
you are a beginner don't let others tell you how they perceive your efficiency. Move on learn the best practices, challenge yourself and grow .... besides that no one looks at the failures before your success but giving up will never let you reach success ...
Hi Josef Let me tell you something, you cannot be quick if you are junior, no body can, being slow is normal in the beginning. I am slow too, although I am ahead of you in the field by one year. But your speed will increase gradually so you don't have to worry, and even if you are really slow in grasping new technologies, you might be fast in applying them.. and you might be gifted in connecting the dots between different technologies. So don't let a point of weakness put you down, you might have a lot of strengths. I remember when you first joined hashnode, you were very passionate and you invested a lot of time and effort to learn, And I really believe that this is all what it takes to become a developer : passion, effort and time. So forget about your previous experience and look ahead to fulfill your dream. Good luck
Adi Pothuri
Hey man I feel your struggle and have been there. It takes a while to get your feet wet into this new world. The more time you spend tinkering around with technologies, the faster you'll find something that interests you and one that you become a master at. But I sort of agree with the small company, you'll need a good amount of fundamentals before you dive into things link architecture, design patterns, or even feature-building.
I have an Computer Science bachelor's and it was still hard for me to get used to the industry. It takes time with learning, growth, and experience. Hang in there, don't call it too soon!