The beauty of a junior feature is that we more experienced people know that you don’t know everything yet.In fact, we probably need to learn a lot of bad traits, behaviour, attitude and thinking.
What I think is important is that you understand why you are not finishing your projects.You see them as learning material: does this mean that you get your learning goals? And if you would develop through it, what more could you learn? Why do you choose to stop?
In a few years you may be sitting on the other side of the application table.What questions would you ask a junior developer about this topic? If you can explain that, you are already a very end, it shows that you have self-reflection and that you have thought about the conversation.
A job interview is not a contest, see it as a possibility to determine as soon as possible if you fit the company.If that is not the case: next! You don’t want to work at a company that doesn’t fit?
If you’re only working on personal projects, that’s usually enough.If you can show something then it is of course a plus, but if you have not finished your projects then that is certainly not a problem.
I am currently a Software engineering student and I have worked for two companies.During the interviews I always had the question whether I was working on personal assignments. If you can’t show anything at that time, make sure you can make clear which frameworks and languages you have applied. What was the size of your project? Why did you start that project? What have you learned?
You should usually be able to answer these types of questions.Make sure your enthusiasm radiates. But my advice to you is to finish a project from head to toe once. I also did this and I can show this to my manager and so on. That shows that you are an entrepreneurial person. But as far as I can make out, you are also:).
Make something off then!This is not so difficult if you can program at least a bit. You can also finish a “Hello World”. If it complies with the specification then it is finished. But even better you start with something new. Keep it small, but make sure it works.
In my experience as a software developer (now 14 years of professional) you can find it more important to know what experience you have gained during your projects.You could tell about a learning project without going into detail about whether the project is complete or not. More importantly, the challenges and techniques that have come to your path, because that is what your future employer benefits.
Even if you have (demonstrable) professional experience, it still does not mean that the project you have worked on needs to be finished.
If you are asked to show your own code that you can program, the company will not actually go through a project in its entirety, but search for positive (or negative) connecting points in your code.
Preferably you give a fair answer.Well-rounded projects are definitely a plus, but partially rounded up can also be instructive, so name it.
Then you make yourself something fun that you can show!When I was at the point where you are sitting, I have played a game. That was trickier than I thought, but I learned a lot from it.
- Be honest
- Be clear about your ambitions and expectations
- Demand for development opportunities
The best advice I can give is to be honest.There is nothing more painful (for both parties) than a mismatch in expectations.
Also remember that if you are not honest about the things that really matter, your colleagues will get behind quite quickly.Your reputation will then be soap, not just within the company you are applying for. The software development world is smaller than you think.
Nothing wrong with Juniors
The second point is that in my eyes there is nothing wrong with being a junior, but be clear in the conversation about expectations to grow fast.It quickly becomes clear which juniors ‘ senior material ‘ are and which are not. Juniors who are ‘ senior material ‘ are sought after and can climb up quite quickly.
People are also more willing to accept mistakes from a junior.Working in the industry for customers is different than working on a personal project and also requires additional skills. That will have to develop you to go up.
The Senior Junior
A senior junior is someone with many years of experience, but with the skills of a junior.You can find them on almost every project and everyone wants to get there. So it is important that you do not linger in the junior role, so be sure to ask what your development possibilities are, and make use of them as well.
Should you still feel like you are stuck in a junior role then there are two possibilities (how rapper the better)
- You get no/bad support-> change from employer
- Maybe you overrated your skills
- Looking for a less complex project
- Thinking about your career
I am afraid that during my job interview for Junior software developer I will be asked what software I have developed.I never finished projects because I only see them as learning material. What kind of answer do I give?
That you have developed with the creation of software.Or that it is software that already existed and that your team was concerned with improvements/adjustments (whether or not based on user input).
I can’t imagine they are in sun call expecting that 1 single developer is responsible for full programming.There are always many more people involved: from designers to testers etc.